weird problem with ADSL router

[lester]

Hello!

After messing around with my ADSL router for a while without being able to talk with it, I discovered that the only way I have to establish a connection with it is pinging it while pressing its reset button.
I'm not a network expert ... but I think this is a bit nonsense.

this is network setup:
root@fax:/home/fax# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:C0:9F:2D:AE:B7
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27970 errors:0 dropped:0 overruns:0 frame:0
TX packets:28105 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4519907 (4.3 Mb) TX bytes:2101938 (2.0 Mb)
Interrupt:4

root@fax:/home/fax# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

default gw is my ADSL router.

This is the tcpdump output on my router's reset (router (and default gw) 192.168.2.1, me 192.168.2.2)

19:02:54.167336 arp who-has 192.168.2.1 tell 192.168.2.1

nothing else ... bored of waiting for something to happen, I ping it:

19:03:47.174120 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 1
19:03:48.174231 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 2
19:03:49.174071 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 3
19:03:50.173915 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 4
19:03:51.173766 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 5
19:03:52.172575 arp who-has 192.168.2.1 tell 192.168.2.2
19:03:52.173272 arp reply 192.168.2.1 is-at 00:08:27:12:8c:7b
19:03:52.173608 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 6
19:03:53.173457 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 7
19:03:54.173309 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 8
19:03:55.173157 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 9
19:03:56.173002 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 10
19:03:57.172854 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 11
19:03:58.172702 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 12
19:03:59.172546 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 13
19:04:00.172396 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 14
19:04:01.172245 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 15
19:04:02.172090 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 16
19:04:03.171954 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 17
19:04:04.171790 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 18
19:04:05.171644 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 19
19:04:06.171482 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 20
19:04:07.171343 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 21
19:04:08.171176 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 22
19:04:09.171034 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 23
19:04:10.170876 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 24

the router is not answering to pings (while I think it should ...) so I reset it again, while still pinging it:

19:04:10.289539 arp who-has 192.168.2.1 tell 192.168.2.1
19:04:10.354455 arp who-has 192.168.2.2 tell 192.168.2.1
19:04:10.354502 arp reply 192.168.2.2 is-at 00:c0:9f:2d:ae:b7
19:04:10.355069 IP 192.168.2.1 > 192.168.2.2: icmp 64: echo reply seq 24
19:04:11.171724 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 25
19:04:11.172515 IP 192.168.2.1 > 192.168.2.2: icmp 64: echo reply seq 25
19:04:12.172571 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 26
19:04:12.173418 IP 192.168.2.1 > 192.168.2.2: icmp 64: echo reply seq 26
19:04:13.173417 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 27
19:04:13.174322 IP 192.168.2.1 > 192.168.2.2: icmp 64: echo reply seq 27
19:04:14.174268 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 28
19:04:14.175158 IP 192.168.2.1 > 192.168.2.2: icmp 64: echo reply seq 28
19:04:15.175146 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 29
19:04:15.176074 IP 192.168.2.1 > 192.168.2.2: icmp 64: echo reply seq 29
19:04:16.175962 IP 192.168.2.2 > 192.168.2.1: icmp 64: echo request seq 30
19:04:16.176895 IP 192.168.2.1 > 192.168.2.2: icmp 64: echo reply seq 30

now all is ok, and I can connect to the web and post my weird problem ...

I tried with 2 computers connected (192.168.2.3), the result is the same, the one who doesn't ping the router while it's resetting won't receive answers to pings.

It's not that terrible problem, because as you can see I can get online, but I have to ping-reset the router each time I turn one of the computers in my lan ...
Can anyone help me?
thanks

[smutt]

Return the ADSL router and get another one. It's broken.
Your other option is to keep a process in the background pinging your ADSL router constantly. So that you don't have to worry about that when you want to reset it

[lester]

I feared that ...

Also I thought that it might be a "bug" in the router when using it with dynamic IP, this router has been used for about a year without problems, but with static IP.
And also when I was trying to have it working it was responding to pings normally (but didn't connect to the web because of wrong settings I put in it), the problem appeared only when I found the correct settings, that is, when I finally told it to have a dynamic IP.

thanks anyway, I think will go on pinging the router until get a new one