Mailinglist Archive: opensuse (3767 mails)

< Previous Next >
Re: [SLE] Cannot talk to netgear WGT624 wireless router ??
  • From: Patrick Shanahan <ptilopteri@xxxxxxxxx>
  • Date: Tue, 7 Feb 2006 15:47:05 -0500
  • Message-id: <20060207204705.GA2605@xxxxxxxxxxxxxxx>
* Hans du Plooy <hansdp-lists@xxxxxxxxxxx> [02-07-06 11:32]:
> Stop the network on your PC with rcnetwork stop.
> Give your network card a static IP
> ifconfig eth0 192.168.0.2

did

> ifup eth0

wahoo:~ # rcnetwork status
Checking network interfaces:
lo running
eth0 running

wahoo:~ # rcnetwork stop
Shutting down network interfaces:
eth0 done

wahoo:~ # ifconfig eth0 192.168.1.2

wahoo:~ # ifup eth0
Starting DHCP Client Daemon on eth0... . . IP/Netmask: 192.168.1.3 / 255.255.255.0

wahoo:~ # arp -an
? (192.168.1.2) at <incomplete> on eth0
? (192.168.1.1) at 00:14:6C:42:BC:32 [ether] on eth0

wahoo:~ # rcnetwork status
Checking network interfaces:
lo running
eth0 running

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

--- 192.168.1.2 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1018ms

wahoo:~ # ping 192.168.1.3
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.159 ms
64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.122 ms

--- 192.168.1.3 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1008ms
rtt min/avg/max/mdev = 0.122/0.140/0.159/0.021 ms

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

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4013ms

wahoo:~ # cat /etc/resolv.conf
search localhost wahoo.no-ip.org nf2.no-ip.com clmboh1-dns2.columbus.rr.com
nameserver 192.168.1.1



>
> I suspect that the dhcp in the router might be misconfigured. Not sure
> how that would be possible, as the dhcp server should not start under
> those circumstances. But it may be possible.
>
> Otherwise, use arp to put an IP in your arp table for the router (the
> MAC address should be printed on the bottom, and/or somewhere on the
> box). I've had to do this many times before when dealing with new
> clients that have existing printservers etc. that need attention.

wahoo:~ # arp -an
? (192.168.1.2) at <incomplete> on eth0
? (192.168.1.1) at 00:14:6C:42:BC:32 [ether] on eth0


note: read manpage for arp, but do not understand syntax for adding
arp addresses.

tks,

ps: returned first WGT624, unable to address router. Am performing
presently on replacement.

--
Patrick Shanahan Registered Linux User #207535
http://wahoo.no-ip.org @ http://counter.li.org
HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

< Previous Next >
Follow Ups