I have SuSe 11.1, with a network card,a wireless dongle and a home network with a d-link 524 router. The network card works well. The wireless dongle works in windows on this PC. With Suse 11.1 I can ping the router with both the dongle and the wireless card connections, not connected at the same time of course. I have the same setup for the ip, name server and encryption for both connections. I am using a static ip address. This setup works for both connections with windows but in SuSe with the network card only. The wireless dongle does not connect to the router but does ping the router. Seems strange - any suggestions?
clivesteventon wrote:
> I have SuSe 11.1, with a network card,a wireless dongle and a home
> network with a d-link 524 router. The network card works well. The
> wireless dongle works in windows on this PC. With Suse 11.1 I can ping
> the router with both the dongle and the wireless card connections, not
> connected at the same time of course. I have the same setup for the ip,
> name server and encryption for both connections. I am using a static ip
> address. This setup works for both connections with windows but in SuSe
> with the network card only. The wireless dongle does not connect to
> the router but does ping the router. Seems strange - any suggestions?
If the wireless can ping the router, it must be authenticated and associated,
which is what we generally mean by “connecting”. What doesn’t work?
Please post the output of
/usr/sbin/iwconfig
/sbin/ifconfig
I can ping the router but when I enter the url for the router into a browser it does not connect. Connects ok with the network card with the same settings for ip address, DNS and encryption. Parameters from iwconfig and iwlist are given below. Everything appears ok but the browser does not reach the address. Thanks for the reply.
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:“dlinkap”
Mode:Managed Frequency:2.462 GHz Access Point: 00:11:95:37:49:3B
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:019F-E6E0-216F-45B5-9290-F41D-29F2-29D4-EE61-865F-CCD6-4C4D-C823-ECD8-981B-2CAB [2] Security mode:open
Power Management:off
Link Quality=71/100 Signal level:-54 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Admiral:/home/clive # iwlist scan
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
wmaster0 Interface doesn’t support scanning.
wlan0 Scan completed :
Cell 01 - Address: 00:11:95:37:49:3B
ESSID:“dlinkap”
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=51/100 Signal level:-52 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000000f6e40117f
Extra: Last beacon: 32ms ago
Admiral:/home/clive # ping -c 5 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.060 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.055 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.058 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.050 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.051 ms
— 192.168.0.1 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 0.050/0.054/0.060/0.010 ms
Admiral:/home/clive # ping -c 5 66.70.73.150
PING 66.70.73.150 (66.70.73.150) 56(84) bytes of data.
From 192.168.0.2: icmp_seq=1 Destination Host Unreachable
From 192.168.0.2 icmp_seq=1 Destination Host Unreachable
From 192.168.0.2 icmp_seq=2 Destination Host Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host Unreachable
From 192.168.0.2 icmp_seq=4 Destination Host Unreachable
From 192.168.0.2 icmp_seq=5 Destination Host Unreachable
with the network card
— 66.70.73.150 ping statistics —
5 packets transmitted, 0 received, +6 errors, 100% packet loss, time 4017ms
, pipe 3
Admiral:/home/clive # ping -c 5 66.70.73.150
PING 66.70.73.150 (66.70.73.150) 56(84) bytes of data.
64 bytes from 66.70.73.150: icmp_seq=1 ttl=50 time=26.4 ms
64 bytes from 66.70.73.150: icmp_seq=2 ttl=50 time=25.9 ms
64 bytes from 66.70.73.150: icmp_seq=3 ttl=50 time=26.7 ms
64 bytes from 66.70.73.150: icmp_seq=4 ttl=50 time=28.6 ms
64 bytes from 66.70.73.150: icmp_seq=5 ttl=50 time=29.4 ms
You forgot /sbin/ifconfig.
Additionally post:
ping -c1 195.135.220.3
ping -c1 suse.com
/sbin/route -n
cat /etc/resolv.conf
sorry, ifconfig with dongle and ifconfig with network card, in that order.
Thanks
Admiral:/home/clive # ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:E2:17:9C:19
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:43246 errors:0 dropped:0 overruns:0 frame:0
TX packets:29774 errors:80 dropped:0 overruns:0 carrier:80
collisions:0 txqueuelen:1000
RX bytes:41404381 (39.4 Mb) TX bytes:4573679 (4.3 Mb)
Interrupt:20 Base address:0xcc00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:48776 errors:0 dropped:0 overruns:0 frame:0
TX packets:48776 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4520812 (4.3 Mb) TX bytes:4520812 (4.3 Mb)
wlan0 Link encap:Ethernet HWaddr 00:17:9A:CF:E8:15
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::217:9aff:fecf:e815/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14017 (13.6 Kb) TX bytes:13542 (13.2 Kb)
wlan0:rou Link encap:Ethernet HWaddr 00:17:9A:CF:E8:15
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
wmaster0 Link encap:UNSPEC HWaddr 00-17-9A-CF-E8-15-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Admiral:/home/clive # ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:E2:17:9C:19
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::204:e2ff:fe17:9c19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:43161 errors:0 dropped:0 overruns:0 frame:0
TX packets:29698 errors:74 dropped:0 overruns:0 carrier:74
collisions:0 txqueuelen:1000
RX bytes:41305075 (39.3 Mb) TX bytes:4560745 (4.3 Mb)
Interrupt:20 Base address:0xcc00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:48639 errors:0 dropped:0 overruns:0 frame:0
TX packets:48639 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4507626 (4.2 Mb) TX bytes:4507626 (4.2 Mb)
Would you please read carefully and post all informations you were asked?
But even from ifconfig one can see that this cannot work, two interfaces in one subnet are activated at the same time.
I have also run the additional commands you requested. First the dongle then the network card.
Thanks
Admiral:/home/clive # ping -c1 195.135.220.3
PING 195.135.220.3 (195.135.220.3) 56(84) bytes of data.
From 192.168.0.2: icmp_seq=1 Destination Host Unreachable
— 195.135.220.3 ping statistics —
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
Admiral:/home/clive # ping -c1 suse.com
PING suse.com (195.135.220.3) 56(84) bytes of data.
From Admiral (192.168.0.2): icmp_seq=1 Destination Host Unreachable
— suse.com ping statistics —
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
Admiral:/home/clive # /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
Admiral:/home/clive # cat /etc/resolv.conf
/etc/resolv.conf file autogenerated by netconfig!
Before you change this file manually, consider to define the
static DNS configuration using the following variables in the
/etc/sysconfig/network/config file:
NETCONFIG_DNS_STATIC_SEARCHLIST
NETCONFIG_DNS_STATIC_SERVERS
NETCONFIG_DNS_FORWARDER
or disable DNS configuration updates via netconfig by setting:
NETCONFIG_DNS_POLICY=’’
See also the netconfig(8) manual page and other documentation.
Note: Manual change of this file disables netconfig too, but
may get lost when this file contains comments or empty lines
only, the netconfig settings are same with settings in this
file and in case of a “netconfig update -f” call.
Please remove (at least) this line when you modify the file!
search Mshome
nameserver 192.168.0.1
Network card
Admiral:/home/clive # ping -c1 suse.com
PING suse.com (195.135.220.3) 56(84) bytes of data.
64 bytes from turing.suse.de (195.135.220.3): icmp_seq=1 ttl=46 time=129 ms
— suse.com ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 129.606/129.606/129.606/0.000 ms
Admiral:/home/clive #
Admiral:/home/clive # /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
Admiral:/home/clive # cat /etc/resolv.conf
/etc/resolv.conf file autogenerated by netconfig!
Before you change this file manually, consider to define the
static DNS configuration using the following variables in the
/etc/sysconfig/network/config file:
NETCONFIG_DNS_STATIC_SEARCHLIST
NETCONFIG_DNS_STATIC_SERVERS
NETCONFIG_DNS_FORWARDER
or disable DNS configuration updates via netconfig by setting:
NETCONFIG_DNS_POLICY=’’
See also the netconfig(8) manual page and other documentation.
Note: Manual change of this file disables netconfig too, but
may get lost when this file contains comments or empty lines
only, the netconfig settings are same with settings in this
file and in case of a “netconfig update -f” call.
Please remove (at least) this line when you modify the file!
search Mshome
nameserver 192.168.0.1
As I said, two interfaces active at the same time using the same subnet (and even the same IP) can not work!
Thanks for the comment
“two interfaces in one subnet are activated at the same time.”
Of course I have the network card in the PC at all times. When I insert the dongle, I disconnect the wire connection from the network card to the router but I do not remove the card. Works OK with windows but that is not saying much.
Is there a fix or must I actually remove the card from the PC?
Thanks…
Well, before you start opening your machine ripping out your card rotfl! (I am just to honest, another missed chance to have some real fun), yes there is a very simple fix for that.
Unplugging the cable is one thing, deactivating the device is the other.
The output of ifconfig clearly shows, that you did not deactivate eth0.
You should read this here to let the OS do the job.
My network keeps losing the gateway address - openSUSE Forums
I used yast network settings and for the network card selected no ip address. The overview page now reads for the card
Device Name eth0 will not be started at all.
However the dongle still does get get through, DRAT! I am now using my laptop to connect. Appreciate your help but I obviously need more.
Thanks…
Without real information, help makes no sense as it’s just “wild stabs in the dark”.
Use the script linked in the third post here:
Getting Your Wireless to Work - openSUSE Forums
Upload the output file to a nopaste-service and link it here.
And BTW, you should have read the other linked thread completely, because it would have given you a much better solution than turning eth0 off.
here is the most recent output from ifconfig with eth0 suppressed.
ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:E2:17:9C:19
inet6 addr: fe80::204:e2ff:fe17:9c19/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:3 dropped:0 overruns:0 carrier:6
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:20 Base address:0xcc00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5391 errors:0 dropped:0 overruns:0 frame:0
TX packets:5391 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:425330 (415.3 Kb) TX bytes:425330 (415.3 Kb)
wlan0 Link encap:Ethernet HWaddr 00:17:9A:CF:E8:15
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::217:9aff:fecf:e815/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:562 errors:0 dropped:0 overruns:0 frame:0
TX packets:4544 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:179786 (175.5 Kb) TX bytes:317523 (310.0 Kb)
wlan0:rou Link encap:Ethernet HWaddr 00:17:9A:CF:E8:15
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
wmaster0 Link encap:UNSPEC HWaddr 00-17-9A-CF-E8-15-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Why do you repeatedly ignore my suggestions?
And what is the sense of this second IP wlan0:rou which is the same as the gateway?
I read through your first link
“My network keeps losing the gateway address - openSUSE Forums” but unfortunately did not really grasp the latter part. Apparently killing eth0 for the network card would work so I did that. I have also worked my way through the sticky
“Getting Your Wireless to Work - openSUSE Forums” before asking for help. Reading it again I do not find the script which you wish me to run, could you be more explicit? It is getting late here in Nova Scotia so I shall come back to this problem to-morrow. It must be possible to get the d**d dongle to work!
Thanks
Sorry, but this turns out to be complete waste of time for me, as you just don’t carefully read before you post, I’m out.
Good luck and good bye.
I appear to have lost my buddy - too bad he was really helpful. Obviously the eth0 had to be suppressed which left the problem of the wlan0:rou. The PC appeared to have two wlan0 connections. This second was a phantom. When I copied the rt33.bin file - the driver required by the firmware - I placed copies in /lib/firmware and three subdirectories. This may have resulted in loading the driver twice? Anyway I removed all but one copy, leaving rt73.bin in the /lib/firmware/my current linux version. The phantom wlan0:rou has disappeared and I just have wlan0 displayed in ifconfig. I can now contact the router with Firefox as well as ping and I can ping the outside world as suggested in the introductory sticky. Obviously the correct placement of the driver is essential. However my internet connection is very slow. The router mount is fast but the rest of the world is glacial. If I cannot solve that problem I shall start a new thread! I really appreciate the help I received, this forum is great!
Final Report - Hardware problem:
Once the conflicts with eth0 and the phantom lanw0 were removed the wireless dongle began to work - with bizarre behavior. When the PC and dongle were first turned on in the morning everything worked properly with fast connections. After five minutes of activity and as the dongle started to feel warm to the touch features started to become intermittent and fail. ie:
could no longer load the router page or reach any other website on any browser. However ping to external sites always worked, trace route worked, Thunderbird email would receive messages but not send them. Skype always logged in and would send text messages but not place calls. Peer to peer transfer (emule) worked normally with good transfer speeds. I could reach one website - the example Samba site referenced in the sticky and I could go to the sub pages of that site with no probems. The dongle had previously worked properly in windows XP - for over two days and 30 hours. It now failed in both Suse and Windows. It is not a port problem as DMZ did not help. It is a USB2 device in a USB1 socket so there may be a timing problem.
End of game. I mounted a Belkin 54g version B which works perfectly. No problems at all with Suse 11.1; had to download a driver for windows. I have additional comments which I will put in a second report.
Additional comments: The Belkin 54g was identified as F5d7050A in the Yast hardware listing. It is B, which requires a different driver from A in XP. Works perfectly in both operating systems. I needed to switch back and forth between a wired and a wireless connection in order to contact the internet whie debugging the dongle - hence the problem with eth0. Use Yast - Network Settings - Ethernet adapter - Edit - Harware -_General - Activate Device and choose “on cable connection”. Makes things easy to go back and forth and does not conflict.
I have my PC moved from my home office and set up in the sitting room - hence the need for wireless. To mount the dongle I had to locate the router in full view of the kitchen and the outside world - we have a great many windows. I could then easily switch connection type. The wireless in the Dlink router cut out every hour of so, day and night. Probably external noise - does not like the microwave oven for instance. The same router always works perfectly in the office which is more sheltered - connecting to a laptop. I move the router about 5 feet to a more sheltered location well away from line of site to the kitchen - behind a wall, and mounted a directional antennae where the router had previously been located. Wireless;) no longer disconnects. So a proper location and a directional antenna helps remove interference dropouts.