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 11:30:51 -0500
  • Message-id: <1139070651.11452.41.camel@xxxxxxxxxxxxxxxxx>
On Sat, 2006-02-04 at 10:00 -0500, Patrick Shanahan wrote:
> * Ken Schneider <suse-list@xxxxxxxxxxxxx> [02-04-06 08:10]:
> > 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).
>
> Separate physical connections. Historical connection was to the RP114.
> New situation is to replace the RP114 with the WGT624 for wireless
> cpabilities.
>
> > 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
>
> And does. This was provided to show different ip assigned by the WGT624.
>
> I believe the problem is that starting the net connection with the
> WGT624 starts dhcpcd which doesn't run with the RP114. BUT, stopping
> dhcpcd *kills* the connection.
>
My dumb thinking, the dhcpd process is what gets your IP address so yes
shutting down that process shuts down connection. You still may want to
use rcnetwork restart instead of rcnetwork restart eth0 as
routing info (/etc/resolv.conf) needs to be updated as well and I am not
sure if specifying eth0 as a parameter will update the default route as
well. Doesn't hurt to try unless you already have.

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


< Previous Next >
Follow Ups