Mailinglist Archive: opensuse (3767 mails)

< Previous Next >
Re: [SLE] Cannot talk to netgear WGT624 wireless router ??
  • From: Ken Schneider <suse-list@xxxxxxxxxxxxx>
  • Date: Sat, 04 Feb 2006 08:08:08 -0500
  • Message-id: <1139058488.11452.18.camel@xxxxxxxxxxxxxxxxx>
On Fri, 2006-02-03 at 23:17 -0500, Patrick Shanahan wrote:
> * Carl Hartung <suselinux@xxxxxxxxxxxxx> [02-03-06 22:22]:
> >
> > I don't know why there aren't any man pages for these utilities, but they seem
> > like they'd be extremely helpful in situations such as your's. The problem
> > is, I'm not really able to experiment with these right now... a lot going on.
> > Anyway, I'm hoping you might oblige and tell me what happens, if anything :-)
> >
>
> Well, I find differences which are probably the problem. One anyway:
>
>
>
> RP114:
>
> wahoo:~ # ifstatus eth0
> dhcpcd not running
> eth0 is up
> 2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen
> 100
> link/ether 00:50:ba:b9:71:f8 brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.2/24 brd 192.168.0.255 scope global eth0
>
> current lease for eth0:
> IPADDR=192.168.0.2
> NETMASK=255.255.255.0
> GATEWAY=192.168.0.1
> HOSTNAME='dhcppc1'
> DOMAIN='no-ip.org'
> DNS=192.168.0.1
> DHCPSIADDR=192.168.0.1
> DHCPCHADDR=00:50:BA:B9:71:F8
>
>
> WGT624:
>
> wahoo:~ # ifstatus eth0
> dhcpcd running
> eth0 is up
> 2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen
> 100
> link/ether 00:50:ba:b9:71:f8 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
>
> current lease for eth0:
> IPADDR=192.168.1.2
> NETMASK=255.255.255.0
> GATEWAY=192.168.1.1
> DNS=192.168.1.1
> DHCPSIADDR=0.0.0.0
> DHCPCHADDR=00:50:BA:B9:71:F8
>
>
> wahoo:~ # ps aux|grep dhcp
> root 2507 0.0 0.0 1516 428 ? S 22:41 0:00 /sbin/dhcpcd -D -R -N -t 999999 -h wahoo eth0
> root 2600 0.0 0.0 1764 576 pts/27 S 22:42 0:00 grep dhcp
>
>
>
> Seems that dhcpcd is active with the wireless router and not the wired
> router and has given the router 192.168.1.1 (so the address in the
> manual is *wrong*).
>
> I have no hostname assigned with the WGT624 and DHCPSIADDR is not
> assigned (?).
>
> Netsearch reveals that DHCPSIADDR is my external address which I would
> assume should be 192.168.1.1 in the WGT624 case.
>
> A search in Yast2, System Config Editor, reveals nothing that makes sense
> in the present situation.
>
> But I am still unable to ping or access 192.168.1.1 and if I stop dhcpcd,
> I loose eth0.
>
>
> I am still blind to something or you are presuming more knowledge in
> front of my keyboard than exists :^)
>
>
>
It would appear that there are two DHCP servers running, the one in the
(WGT624) router and one on the PC called wahoo (but not in the router
RP114). This will create a conflict as both are using different subnets.
It appears that one of the routers is using 192.168.1.x (WGT624) and the
other is using 192.168.0.x (RP114). Which ever DHCP is able to answer a
request for an address first wins. If the PC answers first no network,
if the router is fast enough the network works. I suggest you turn off
the DHCP process on the PC, restart the network and see what happens.
Also use rcnetwork restart and more needs to be restarted than eth0.

Also, pinging yourself should always work:

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

Hope this helps.


--
Ken Schneider
UNIX since 1989, linux since 1994, SuSE since 1998


< Previous Next >
Follow Ups