I have a Linux tower (AMD FX 4300 Quad Core) 8GB RAM, vbox for W7, 22GB SWAP (prim 14GB SSD, two 4GB disk swap partitions). This system runs a W7 environment as a guest (obviously).
Needed to move it to a different location. Here is where it gets strange. Connecting to the SAME gateway server, just different physical location.
W7 can ping yahoo.com and get response. Linux can not!! Before the move it did.
I have been searching for what could cause this, so since my Gateway (clearOS 6) does not support IPv6, I disabled IPv6 (which someone else had a similar problem…). Rebooted and W7 can still get to the LAN and Internet, Suse can’t.
System was physically wired prior to this point. But now it is on a Netgear 4 port Bridge. It DOES get the IP address assigned to it (192.168.1.4). W7 gets its own IP address (ethernet is promiscuous to allow this).
It is as if the Host (SUSE) doesn’t get/recognize the DNS. And if I put 8.8.8.8 in for DNS, it still doesn’t work (one of Google’s DNS servers).
Finally got a CAT5 long enough to go from a smart switch to a cisco switch at the computer in question, and Voila!! SUSE now gets DNS etc.
Seems there is some problem with the Netgear WN2000RPTv2 bridge/extender. :rolleyes: It is interesting that W7 can work across it but “wicked” needs to be told to go stand in a corner until it decides to behave.
From what you describe,
It might be a cached routing table entry.
**
Possible solution 1**
Purge the device list (or look for your machine’s MAC address) in your wireless devices.
Possible solution 2
When you move, change the MAC address of your interface, is called different things. Easily done if you’re using Network Manager.
You might look into the specs and user manual of your wireless devices to see if they support roaming and/or mesh networking.
One would like to think that factory reset would solve the problem. But it didn’t. And that was the situation we started with so I could get it configured as a bridge.
One would also like to think that if they find a few others with SUSE and wicked having problems with the same device, that the device is the problem. But since windows works… maybe it is wicked. However, the circumvention was 50’ of CAT5.
It is interesting to note that I did not have to do anything special with the Cisco smart switch other than plug it in and plug in the CAT5 cables – it had been used with the same device before. No reconfig, no reset to factory. Hmmmm.