Mailinglist Archive: opensuse (3767 mails)

< Previous Next >
Re: [SLE] Cannot talk to netgear WGT624 wireless router ??
  • From: Joseph Loo <jloo@xxxxxxx>
  • Date: Fri, 03 Feb 2006 18:34:53 -0800
  • Message-id: <43E412CD.4030606@xxxxxxx>
If youlook carefully, your addres is 192.168.1.2 on the first test. On the second test you are 192.168.0.2. In the first case, your ping 192.168.0.1will not work because you are in the wrong sunet group. I suspect that your new box, you want to ping 192.168.1.1 where the admin web interface is at versus 192.168.0.1. I notice a lot of these router now are moving to the 192.168.1.x lcoation.

Patrick Shanahan wrote:
SUSE 9.0
Cable Internet Access

Wife got new box and we decided to go wireless.

Purchased Netgear WGT624 wireless router to replace the Netgear RP114
which has served me faithfully for several years.

But I cannot talk to the WGT624 (192.168.0.1).



wahoo:~ # rcnetwork restart eth0
Shutting down network interfaces: eth0 done
Setting up network interfaces: eth0 (DHCP) IP/Netmask: 192.168.1.2 / 255.255.255.0 done

wahoo:~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:BA:B9:71:F8 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6587810 errors:57 dropped:136 overruns:57 frame:0
TX packets:6461951 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 RX bytes:527992438 (503.5 Mb) TX bytes:1491372168 (1422.2 Mb)

wahoo:~ # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

--- 192.168.0.1 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6013ms


wahoo:~ # ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.155 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.127 ms

--- 192.168.1.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.127/0.141/0.155/0.014 ms


Replace with RP114:

wahoo:~ # rcnetwork restart eth0
Shutting down network interfaces: eth0 done
Setting up network interfaces: eth0 (DHCP) failed


wahoo:~ # ping 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=254 time=5.55 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=254 time=1.09 ms

--- 192.168.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1017ms
rtt min/avg/max/mdev = 1.094/3.325/5.556/2.231 ms

wahoo:~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:BA:B9:71:F8 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6590810 errors:57 dropped:136 overruns:57 frame:0
TX packets:6464931 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 RX bytes:529918728 (505.3 Mb) TX bytes:1491734541 (1422.6 Mb)

wahoo:~ # ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=0.163 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=0.123 ms
64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=0.119 ms

--- 192.168.0.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.119/0.135/0.163/0.019 ms




What am I missing or doing incorrectly, or is the WGT624 no good?


--
Joseph Loo
jloo@xxxxxxx


< Previous Next >
Follow Ups
References