* Rikard Johnels [02-03-06 21:36]:

...

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

Seems to me that the router is set to 192.168.1.1 It gives you 192.168.1.2 Observe the .1.x Its not .0 as you had before

I have tried that also to no avail, but the docs with the router claim 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:~ # 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 --- 4 packets transmitted, 0 received, 100% packet loss, time 3013ms -- 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

* Paul Cartwright [02-04-06 05:37]:

try www.routerlogin.net

I have, but appears the router is not resolving the address.

and when I got it working I also installed a little package called netgo . it sets up the IPs for different setups..

sound good, but atm I only have two boxes and both are desktops. tks, -- 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

* Joseph Loo [02-03-06 21:36]:

If youlook carefully, your addres is 192.168.1.2 on the first test.

agreed, the first test is on the WGT624

On the second test you are 192.168.0.2.

test is on the RP114

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.

thanks, I tried that: 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:~ # 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 --- 4 packets transmitted, 0 received, 100% packet loss, time 3013ms -- 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

* Carl Hartung [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: 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: 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 :^) ps: I really appreciate and envy your analytical approach and excellent ability to convey information. -- 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

On Friday 03 February 2006 23:17, Patrick Shanahan wrote: Hi Patrick, Scratch the "same cable" question... now I get it:

RP114:

This is the cabled connection and it works.

WGT624:

This is the wireless connection that is misbehaving. Why is this "eth0" and not "wlan0"? - Carl

On Fri, 2006-02-03 at 23:17 -0500, Patrick Shanahan wrote:

* Carl Hartung [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: 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: 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

On Sat, 2006-02-04 at 10:00 -0500, Patrick Shanahan wrote:

* Ken Schneider [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

On Sat, 2006-02-04 at 13:09 -0500, Patrick Shanahan wrote:

* Ken Schneider [02-04-06 11:33]:

...

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.

Doesn't seem to make any difference. I have used both, rcnetwork restart and rcnetwork restart etho, with apparent difference.

note: I have set to not alter /etc/resolv.conf. It seems to interfer with my no-ip dyns setup.

OK. What do you have in /etc/sysconfig/network/routes as this will make a difference. It needs to be 192.168.1.1 for the new router till it is configured. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

On Sat February 4 2006 1:56 pm, Patrick Shanahan wrote:

ok, this leads to another possible solution. /etc/sysconfig/network/routes is zero file length and /etc/resolv.conf contains nameserver 192.168.0.1

but would that cause a problem with dotted quads and not using names?

192.168.10.1 is the router.. # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.10.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.10.1 0.0.0.0 UG 0 0 0 eth0 on the laptop, not default route, no connection. Ran netgo, added default route to 192.168.10.1 for eth1 ( wireless), and up came my network connection. -- Paul Cartwright Registered Linux user # 367800

On Saturday 04 February 2006 14:32, Jim Cunning wrote:

I've been following this thread and am coming to the conclusion the problem may be very basic. It also isn't clear from everything passed back and forth that you know precisely what does work and what doesn't.

Hi Jim, I totally agree this has to be something basic. In another post I brought up the following: Patrick wrote:

... The router supplies dhcp because I have a dynamically assigned ip and ... with the WGT624, dhcpcd service starts and that should be used instead from the router. and: The dhcpcd service does *not* start when I use the RP114.

In other words: - with the *working* connection, the RP114, dhcpcd is *not* running. - with the *broken* connection, the WGT624, dhcpcd *is* running. Patrick also wrote:

note:  I have set to not alter /etc/resolv.conf.  It seems to interfer with my no-ip dyns setup.

This is all in the same part of the same YaST module, isn't it? You either elect to enable dhcp or disable it and configure the NIC manually. Maybe an incompatible mix of settings... and:

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.

Does dhcpcd usually start, do it's job and then shut down? Could it be 'backgrounding' instead because it can't get an IP etc. from the WGT624? - Carl

Patrick Shanahan wrote:

* Alan Dowley [02-03-06 21:36]:

...

...

But I cannot talk to the WGT624 (192.168.0.1).

My neighbor has one of these and I tried to connect via wireless with 9.3 + DLink Airexpert. I could not connect via wireless if anything was connected by cable (hard wired). When I disconnected the cable to her laptop I could connect via wireless.

Tried every conceivable config but it just wouldn't work. Gave up and she now has Linksys 54G wireless router and I can connect when I take my laptop over there.

Yea, but I have not even been able to access the router to configure. There is *no* wireless out of the box.

I did have trouble at first trying to communicate and had to keep powering off the router and changing the cable to different ports. Think it finally allowed me to connect on port 4, and even this was at the 3rd attempt. When I managed to configure it it would only allow one connection at a time - cable or wireless - never the two together.

On Friday 03 February 2006 21:57, Alan Dowley wrote:

When I managed to configure it it would only allow one connection at a time - cable or wireless - never the two together.

If you have two nics on the same subnet (wireless or not), the machine is not going to know which one is the gateway connection. It may also be otherwise confused. This is normal unless you configure for it. Check your route -n with both cable and wireless connected. You will probably not find a UG (default gateway) listed.

* Mike McMullin [02-04-06 01:27]:

Not great help here Patrick, but I understand that USR has a $50 mail in rebate for their wireless base stations, offer on till end of April or so. If you return this critter mayhap you might want to check one out.

Does the USR work with linux? Have you expierence or knowledge of a functional linux environment with the USR. (Still have 5 or 6 of the early USR modems). tks, -- 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

* Patrick Shanahan [02-04-06 10:03]:

* Paul Cartwright [02-04-06 05:16]:

...

I had to power off the DSL modem, connect the 614 via ethernet cable to my PC, powered up the router and was able to get to it. Then I changed the netgear IP to 192.168.10.1 . When you get in and make a change like that, I also was told to unplug the router for 30 seconds.

so my router IP's are 192.168.10.2 for my desktop and 192.168.10.3 for my wireless.

Trying now, will report.

Still unable to access the WGT624 so changing the ip is not possible. tks, -- 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

* Carl Hartung [02-04-06 13:08]:

Note: dhcpd = the server daemon, assingns LAN client IP addresses dhcpcd = the client daemon, requests IP leases from the dhcp server

Does your cable modem have dhcp enabled? IOW, does it serve IP addresses to your clients *through* the RP114 (the RP114 built-in dhcp server is off?)

now you have posed a question I cannot presently answer. The RP114 is at 192.168.0.1 and I have 192.168.0.1 for dns in /etc/resolv.conf nameserver 192.168.0.1 This brings some enlightment. I need to change that after putting the WGT624 in line to see the dns.

Also, either router can probably be configured as follows:

a) a client to the modem's built-in routing capability and dhcp server. In this arrangement, the router acts like a switch, passing client IP lease requests to the modem for service. With this arrangement, the modem's LAN-facing IP is the default gateway and DNS.

b) (bridged?) with the modem's internal router/dhcp server turned off. With this arrangement, the *router* serves IPs via dhcp instead of the modem and *it's* LAN-facing IP acts as the default gateway and default DNS.

Maybe I'm very confused, but it seems this must be a simple thing... an oversight... I think it'll help to "zoom in" on these details for a closer look.

Yes, this may indeed clear things. I am away from home for a few and cannot make tests. I will return to list when able. Presently ssh'ing from son's house. Installing ME box for grandson with wireless internet access. tks, -- 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

On Sat, 2006-02-04 at 22:20 +0100, Kulla wrote:

Also, your network card is eth(x), and wireless is always wlan(x) Actually, that's not a given.

Atheros based chips (madwifi driver) show up as ath0, ath1, etc. If I remember correctly, on the Dell i6000 laptop I tried when shopping for a new one, the SUSE Live DVD bought showed the wired (broadcom) network as eth0 and the wirless (ipw2000 driver) as eth1. My Prism54 based card (prism54 driver) in my firewall at home also shows up as eth1 The broadcom (ndiswrapper driver) in my notebook shows up as wlan0 Hans

* Hans du Plooy [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

On Wed, 2006-02-08 at 17:54 -0500, Patrick Shanahan wrote:

* Patrick Shanahan [02-07-06 16:17]:

...

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

It's usually something simple <grin>... KISS

The firewall did not allow access to 192.168.1.1. Started Yast2 and re-recognized the nic, restarted 'rcSuSEfirewall2 restart' and the router was addressable and is now in use.

This seems odd to me. During your run with this thread I've changed cable routers to, and back again. In neither transition did the firewall stop access to the router. The one I changed to (and back from) was 192.168.1.1, and my original was 192.168.0.1. I'm mentioning it because your situation has me curious.

Only unfortunate thing, my ip changed for the first time since I got cable access, probably because I have had some heavy access lately, and no-ip.com did not adjust quickly enough for me to realize the problem.

btw: I am unable to configure dynamic dns on the router. ???

Thanks to everyone for all the suggestions and help. The BEST.

Mike -- Waiting to install a gigabit pci wireless base card when I have more time