DHCP4 client (dhcpcd) is running
. . . but is still waiting for data
DHCP6 client (dhclient6) is running
. . . but is still waiting for data
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:1f:1f:e4:4f:66 brd ff:ff:ff:ff:ff:ff
inet6 fe80::21f:1fff:fee4:4f66/64 scope link
valid_lft forever preferred_lft forever
wlan0 is up
bssid=00:81:d8:42:1e:9a
ssid=BTHub3-TZM5
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
However, there is still no internet connection and ifconfig wlan0 produces:
As I understand it, there should be a line inet addr:, which indicates to me that DHCP has not done what I expected it to although there is an inet6 addr: line. As far as I can see from YAST there is nothing wrong with my DHCP settings. I may be barking up the wrong tree - can anyone help? Are there other tests/commands I should run to shed light on this?
That should give the MAC address of your router. Then, if you otherwise know what that MAC address should be, see if there is a match. Also check that your router is not setup for MAC filtering, though it seems unlikely that it would have given you an IP address if that were the problem.
I’m guessing that you probably have a 2Wire router, though I don’t think that should be significant.
? (192.168.1.254) at <incomplete> on wlan0
? (192.168.1.64) at 00:23:54:f0:f3:16 [ether] on wlan0
Not sure what means on the first line as ifstatus wlan0 gives:
wlan0 name: 802.11n WLAN Adapter
DHCP4 client (dhclient) is running
DHCP6 client (dhclient6) is running
. . . but is still waiting for data
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:1f:1f:e4:4f:66 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.65/24 brd 192.168.1.255 scope global wlan0
inet6 fe80::21f:1fff:fee4:4f66/64 scope link
valid_lft forever preferred_lft forever
Configured IPv4 routes for interface wlan0:
169.254.0.0/16 - - wlan0
Active IPv4 routes for interface wlan0:
default via 192.168.1.254
169.254.0.0/16 scope link
1 of 1 configured IPv4 routes for interface wlan0 up
wlan0 is up
bssid=00:81:d8:42:1e:9a
ssid=BTHub3-TZM5
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=192.168.1.65
All looks good to me apart from that first line in arp -a. Is there any other clue to the problem? I did check that Firefox tried and failed to connect as before.
Apparently my router (BT HomeHub3; probably not known in the US) does not support MAC filtering. Not sure what a 2-wire router is, but I did find this, which may make more sense to you than it does to me: BT Broadband - and How to Survive It! .
That’s what puzzles me too. I wondered if it might be a problem with the browser, but even if that were the case I should get a response from my router with ping, but all I get back is the message that the ‘Destination Host is unreachable’. Yet there is nothing I can find that suggests the link between system and router has been lost.
Knurpht - tried restricting wlan0 to DHCP4, but that did not produce any change. I’ll try the static settings shortly.
I’ve been fiddling with this for so long and gone down so many blind alleys that I may well have put on an obscure setting that is causing all this. Perhaps I should try a clean install (with 12.2). It’s a desperate step; any views?
Assuming that you have another computer on that LAN, try using that to find the MAC address of the router. Then see if you can hardwire that MAC address into the arp tables (use the “arp” command as root). Check the man pages.
The last time I did that, I found it useful to create a small file in the format of “/etc/ethers”, and then use the “-f” option to arp. But I was dealing with a different problem - I was visiting elsewhere, and the home network was badly configured with two different routers answering to the same IP. So I use “arp” to hardwire the router that worked.
When your computer is successful in getting a DHCP address, it is contacting the router with a broadcast - essentially making a request to address 0. And it can do that without having the MAC address of the router. Once it has an IP, it seems unable to get a MAC address.
My best guess - and it is only a guess - is that there might be a driver problem in making arp requests. If all else fails, you could try installing the compat package (not sure of its name), and using the Windows driver for your wifi card. I have no experience with that.
The computer I am using is dual bootable, Linux and Vista. It works fine, except that the internet connection works on Vista while on Linux (ie openSUSE) it doesn’t. On Vista, which runs McAfee, the network map that McAfee brings up confirms the IP address for the router I am using. What is curious is that the router is shown as offline although it is doing what it is supposed to do. To me it seems as if some flag is set in the router saying it is offline; the flag is ignored in Vista but not in openSUSE. Does this give any clues?
You were getting “host unreachable” with ping attempts. And that is what normally happens when the ARP protocol fails to discover the MAC address that corresponds to the ip address you are sending to.
To me, that indicates some incompatibility between the two systems (opensuse and the router).
That’s why I suggest trying the compat-wireless drivers, if you can work out how to do that.
You might try a google search with your network card model number and “linux” in the search argument, to see if you can find other people who have run into the same problems and perhaps solved it.
On 09/22/2012 02:56 PM, nrickert wrote:
>
> You were getting “host unreachable” with ping attempts. And that is
> what normally happens when the ARP protocol fails to discover the MAC
> address that corresponds to the ip address you are sending to.
>
> To me, that indicates some incompatibility between the two systems
> (opensuse and the router).
>
> That’s why I suggest trying the compat-wireless drivers, if you can
> work out how to do that.
>
> You might try a google search with your network card model number and
> “linux” in the search argument, to see if you can find other people who
> have run into the same problems and perhaps solved it.
I do not think that compat-wireless would make much difference. From what has
been posted, the wireless device has connected and associated. Any problem in
getting an IP is due to some problem in the rest of the system. Changing the
driver will not cure that.
Forgot to respond to nrickert’s suggestion that I add in the compat-wireless packages; seeing lwfinger’s reply above reminded me. I did this under my previous thread mentioned in my first post, where association either did not take place or was immediately dropped. lwfinger suggested I add the compat-wireless packages, which immediately resolved the association problem but exposed the dhcp problem which is the subject of this thread. So unfortunately no further mileage in that, it would seem. I was interested to discover in my net searches that my router uses a Linux kernel {perhaps most of them do), although of course that is no guarantee of success. I will continue searches along the lines that nrickert suggests, but I have found nothing yet. In view of the anomaly of McAfee under Vista showing the router to be offline yet working normally, I am inclined to the view that there is an incompatibility between router and openSUSE rather than the network card, but I’ll keep trying.