Re: Can't access gateway IP
On Fri, May 03, 2013 at 11:05:13PM +0100, s0lid wrote: Hi, Im having an unsual issue with my debian 6.0.7 server. This is a fresh install and i set the IP settings to DHCP. It get the IP from my router(192.168.1.1), I tried to ping the router IP but it doesn't reply i tried to ping a computers it replies fine, I don't know what's going on here this is the first time i had an issue with debian in terms of network. The router is accessible and can be ping from my laptop. ---from my laptop--- $ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: icmp_seq=0 ttl=254 time=2.623 ms 64 bytes from 192.168.1.1: icmp_seq=1 ttl=254 time=1.000 ms $ ping 192.168.1.200 PING 192.168.1.200 (192.168.1.200): 56 data bytes 64 bytes from 192.168.1.200: icmp_seq=0 ttl=128 time=5.701 ms 64 bytes from 192.168.1.200: icmp_seq=1 ttl=128 time=2.320 ms ---from debian server--- root@debian:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=40.5 ms 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=1.96 ms 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=2.08 ms ^C --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 1.967/14.861/40.532/18.152 ms I don't know if there's an issue with TTL or even if it's related at all. I also run arp from the debian server and it can see the router's IP(192.168.1.1) root@debian:~# arp -a ? (192.168.1.1) at 40:4a:03:d6:ac:a9 [ether] on eth1 ? (192.168.1.101) at e0:f8:47:1e:a0:a6 [ether] on eth1 ? (192.168.1.105) at 08:00:27:b3:86:01 [ether] on eth1 ? (192.168.1.200) at 00:16:b6:1e:01:a0 [ether] on eth1 Although you got the IP address via DHCP, it is still possible that you have an IP collision - which could also give these symptoms, as different servers will have different ideas of IP/MAC mappings on the local network. To make things complicated, it often changes over time too, as caches and cache expirations are in effect. There's a couple of ways you can diagnose this: The easiest is to remove your suspected faulty box from the network (unplug network cable physically), and check whether the IP address still responds to pings. If it does, then something else has that IP address. To futher diagnose, this, you could manually change the IP address of the debian server to an IP address you know for sure to be free. Hope this helps -- Karl E. Jorgensen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130507061253.GA16935@hawking
Re: Can't access gateway IP
I did that before i even change ip addresses to make sure but there's no conflict on IP. Anyway i replaced my router with another one and all works perfectly. On Tue, May 7, 2013 at 2:12 PM, Karl E. Jorgensen karl.jorgen...@nice.com wrote: On Fri, May 03, 2013 at 11:05:13PM +0100, s0lid wrote: Hi, Im having an unsual issue with my debian 6.0.7 server. This is a fresh install and i set the IP settings to DHCP. It get the IP from my router(192.168.1.1), I tried to ping the router IP but it doesn't reply i tried to ping a computers it replies fine, I don't know what's going on here this is the first time i had an issue with debian in terms of network. The router is accessible and can be ping from my laptop. ---from my laptop--- $ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: icmp_seq=0 ttl=254 time=2.623 ms 64 bytes from 192.168.1.1: icmp_seq=1 ttl=254 time=1.000 ms $ ping 192.168.1.200 PING 192.168.1.200 (192.168.1.200): 56 data bytes 64 bytes from 192.168.1.200: icmp_seq=0 ttl=128 time=5.701 ms 64 bytes from 192.168.1.200: icmp_seq=1 ttl=128 time=2.320 ms ---from debian server--- root@debian:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=40.5 ms 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=1.96 ms 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=2.08 ms ^C --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 1.967/14.861/40.532/18.152 ms I don't know if there's an issue with TTL or even if it's related at all. I also run arp from the debian server and it can see the router's IP(192.168.1.1) root@debian:~# arp -a ? (192.168.1.1) at 40:4a:03:d6:ac:a9 [ether] on eth1 ? (192.168.1.101) at e0:f8:47:1e:a0:a6 [ether] on eth1 ? (192.168.1.105) at 08:00:27:b3:86:01 [ether] on eth1 ? (192.168.1.200) at 00:16:b6:1e:01:a0 [ether] on eth1 Although you got the IP address via DHCP, it is still possible that you have an IP collision - which could also give these symptoms, as different servers will have different ideas of IP/MAC mappings on the local network. To make things complicated, it often changes over time too, as caches and cache expirations are in effect. There's a couple of ways you can diagnose this: The easiest is to remove your suspected faulty box from the network (unplug network cable physically), and check whether the IP address still responds to pings. If it does, then something else has that IP address. To futher diagnose, this, you could manually change the IP address of the debian server to an IP address you know for sure to be free. Hope this helps -- Karl E. Jorgensen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130507061253.GA16935@hawking -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANZ3Tp0=pjefx+fsq=e-fj_+tuijcp413igza61+chgn9o+...@mail.gmail.com
Re: Can't access gateway IP
On 5/7/2013 2:44 AM, s0lid wrote: I did that before i even change ip addresses to make sure but there's no conflict on IP. Anyway i replaced my router with another one and all works perfectly. Then you should update the thread subject with SOLVED, whose/what assistance led to the the eventual fix, and what the fix was. I would assume my last post detailing my experience with Zyxel adsl routers may have had some influence. ;) -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51896a30.8000...@hardwarefreak.com
Re: Can't access gateway IP
On Sun, May 5, 2013 at 12:56 AM, s0lid s0lid101...@gmail.com wrote: On Sun, May 5, 2013 at 3:19 AM, Guido Martínez mtzgu...@gmail.com wrote: To narrow things down, I'd like to ask three questions. Do you have internet access from the server? Can you access the http or some other service installed in the router? and what if you change your server IP to 192.168.1.2, does that make a difference? No internet because i cant go pass through the gateway, No access with the router at all even i do nmap. I changed it to .254 but still same issue. All your network parms seem to be fine in the server. Try putting in an another NIC and see if it helps any. I agree with Guido - looks like your router could be b0rked. I have a ZyXel DSL modem/gw router (provided by the Telco) that begins to act strange every once in a while. The Telco says nothing wrong with the line! [a]. Usually a power cycle resolves the problem [a] To be fair they have send their tech support and replaced the unit a couple of times. -- Arun Khan Sent from my non-iphone/non-android device -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAHhM8gC+N7uOcYGe�ZPe+jgbS2mgV=5o-3ce4j8ehdpfw...@mail.gmail.com
Re: Can't access gateway IP
On 5/4/2013 1:28 PM, s0lid wrote: On Sat, May 4, 2013 at 6:02 PM, Stan Hoeppner s...@hardwarefreak.com wrote: On 5/4/2013 3:32 AM, s0lid wrote: On Sat, May 4, 2013 at 3:28 PM, Arun Khan knu...@gmail.com wrote: Can you do a static IP config for the server and check? Yes, same result with static. Any firewall rules in your gateway, to trap ping requests from a sub net? (a shot in the dark). no firewall running Ping the Debian 607 server from the router. Result? It can. I also can access it from my laptop going to the same router. BTW, which consumer router is this? You may have hit a firmware bug. i have a hunch it is, i just don't have another router to test on. This is a Zyxel whitelabeled to my telco so the firmware is custom made for my telco also. Is this a Zyxel 660R by chance? ADSL2+ router? I've had nothing but problems with mine in router mode. It's an OEM Embarq unit. It works fine in bridged mode. My SMC 7008ABR rackmount SOHO router/firewall/print server recently failed--after more than 8 years of flawless operation. So I configured the Zyxel/Embarq 660 for router mode and began creating NAT and firewall rules. It was a PITA. Every 60 seconds it requires that you reenter the password, and thus you lose anything you just configured if it took longer than 60 seconds. Forcing a user to be time rushed when creating firewall rules is just insane. Then... The last thing I did in the web GUI was create a TCP 25 egress filter rule. Upon saving the rule, the router inexplicably locked out all access, even on the telnet interface. Everything else still works, I just can't get back in. To fix this will require resetting the device to factory defaults, again, which will require recreating all of the existing rules, again. The 660 actually has nice features. Too bad this OEM model is so flaky it's impossible to actually configure and use the damn thing. You're in a similar OEM situation. Cut your losses, configure it for bridge mode, and use an aftermarket router, as I will be doing shortly. I've read the specs on a few models, and I think I'll probably acquire the TP-Link TL-R402M based on features, price, and reviews--currently $17 at Newegg. I've long since replaced the switch and print server functions of the SMC with other products, and I already have a POE wireless AP, so there's no reason to spend a lot on a replacement router. I'll miss the remote syslog facility of the SMC, but that one feature isn't worth the ~3x greater price of the next cheapest unit that offers it. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/518600e2.10...@hardwarefreak.com
Re: Can't access gateway IP
On 5/4/2013 2:26 PM, s0lid wrote: No internet because i cant go pass through the gateway, No access with the router at all even i do nmap. I changed it to .254 but still same issue. Some of these OEM telco Zyxel units have a fixed limit on the number of LAN hosts they will allow. The first Zyxel/Embarq unit my folks had, a 4xx series IIRC, only allowed one LAN host. IIRC this is enforced by MAC address. Read all the documentation provided by your telco. You may have hit such a limitation. Again, bridge mode and a consumer router fixes this, and other problems related to the telco/OEM modem/routers. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/518602af.6070...@hardwarefreak.com
Re: Can't access gateway IP
On Sat, May 4, 2013 at 7:55 AM, Bob Proulx b...@proulx.com wrote: s0lid wrote: ---from debian server--- root@debian:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=40.5 ms 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=1.96 ms 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=2.08 ms ^C --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 1.967/14.861/40.532/18.152 ms How did it move from 192.168.1.1 to 192.168.1.2? Did your machine receive an ICMP redirect packet from the router? Apologies i forgot to include the # ping 192.168.1.2 when copy and pasting the ping result. Please try again with 'ping -v' and post the output. It might show an ICMP redirect being received. same thing jus tthis. root@debian:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. I would run 'tcpdump -lni any' on both machines and look for the disconnect. If it is a noisy network then filter with 'host W.X.Y.Z' with the address of your client machine. tcpdump -lni any host W.X.Y.Z i got this from tcpdump while pinging my gateway 14:06:31.172753 ARP, Request who-has 192.168.1.1 tell 192.168.1.106, length 28 14:06:31.173851 ARP, Reply 192.168.1.1 is-at 40:4a:03:d6:ac:a9, length 46 14:06:50.602659 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 1, length 64 14:06:51.611094 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 2, length 64 14:06:52.620045 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 3, length 64 14:06:53.626974 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 4, length 64 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canz3tp1g8h-tycwkdvd9kuzka+hczzjjmn5ekpzw0ezqile...@mail.gmail.com
Re: Can't access gateway IP
On Sat, May 4, 2013 at 11:37 AM, s0lid s0lid101...@gmail.com wrote: i got this from tcpdump while pinging my gateway 14:06:31.172753 ARP, Request who-has 192.168.1.1 tell 192.168.1.106, length 28 14:06:31.173851 ARP, Reply 192.168.1.1 is-at 40:4a:03:d6:ac:a9, length 46 14:06:50.602659 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 1, length 64 14:06:51.611094 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 2, length 64 14:06:52.620045 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 3, length 64 14:06:53.626974 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 4, length 64 Check if netmask is setup correctly in the server config (/sbin/ifconfig eth1). Can you do a static IP config for the server and check? Any firewall rules in your gateway, to trap ping requests from a sub net? (a shot in the dark). -- Arun Khan -- Arun Khan Sent from my non-iphone/non-android device -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAHhM8gBs85Ad3qNL7FPNCxb=u7v-uq4zk6jaennpump72_u...@mail.gmail.com
Re: Can't access gateway IP
On Sat, May 4, 2013 at 3:28 PM, Arun Khan knu...@gmail.com wrote: On Sat, May 4, 2013 at 11:37 AM, s0lid s0lid101...@gmail.com wrote: i got this from tcpdump while pinging my gateway 14:06:31.172753 ARP, Request who-has 192.168.1.1 tell 192.168.1.106, length 28 14:06:31.173851 ARP, Reply 192.168.1.1 is-at 40:4a:03:d6:ac:a9, length 46 14:06:50.602659 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 1, length 64 14:06:51.611094 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 2, length 64 14:06:52.620045 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 3, length 64 14:06:53.626974 IP 192.168.1.106 192.168.1.1: ICMP echo request, id 2563, seq 4, length 64 Check if netmask is setup correctly in the server config (/sbin/ifconfig eth1). netmask looks fine root@debian:~# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 08:00:27:59:31:76 inet addr:192.168.1.106 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe59:3176/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:63 errors:0 dropped:0 overruns:0 frame:0 TX packets:103 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9615 (9.3 KiB) TX bytes:10143 (9.9 KiB) Can you do a static IP config for the server and check? Yes, same result with static. Any firewall rules in your gateway, to trap ping requests from a sub net? (a shot in the dark). no firewall running root@debian:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination root@debian:~# -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANZ3Tp2w2N5C6ohfo-uEpQfVJu2d=b7jy2miid2gub7a624...@mail.gmail.com
Re: Can't access gateway IP
On 5/4/2013 3:32 AM, s0lid wrote: On Sat, May 4, 2013 at 3:28 PM, Arun Khan knu...@gmail.com wrote: Can you do a static IP config for the server and check? Yes, same result with static. Any firewall rules in your gateway, to trap ping requests from a sub net? (a shot in the dark). no firewall running Ping the Debian 607 server from the router. Result? BTW, which consumer router is this? You may have hit a firmware bug. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5184dca1.4050...@hardwarefreak.com
Re: Can't access gateway IP
On Sat, May 4, 2013 at 6:02 PM, Stan Hoeppner s...@hardwarefreak.com wrote: On 5/4/2013 3:32 AM, s0lid wrote: On Sat, May 4, 2013 at 3:28 PM, Arun Khan knu...@gmail.com wrote: Can you do a static IP config for the server and check? Yes, same result with static. Any firewall rules in your gateway, to trap ping requests from a sub net? (a shot in the dark). no firewall running Ping the Debian 607 server from the router. Result? It can. I also can access it from my laptop going to the same router. BTW, which consumer router is this? You may have hit a firmware bug. i have a hunch it is, i just don't have another router to test on. This is a Zyxel whitelabeled to my telco so the firmware is custom made for my telco also. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canz3tp21uupc6wmkkmujrgrapgx+qsrojdz+dgjarnfawpj...@mail.gmail.com
Re: Can't access gateway IP
On Sat, May 4, 2013 at 3:28 PM, s0lid s0lid101...@gmail.com wrote: Ping the Debian 607 server from the router. Result? It can. I also can access it from my laptop going to the same router. BTW, which consumer router is this? You may have hit a firmware bug. i have a hunch it is, i just don't have another router to test on. This is a Zyxel whitelabeled to my telco so the firmware is custom made for my telco also. To narrow things down, I'd like to ask three questions. Do you have internet access from the server? Can you access the http or some other service installed in the router? and what if you change your server IP to 192.168.1.2, does that make a difference? Guido -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca++dqukqmv7wxczoeyxmldxyqb5tyw9qhjlufjth7vued77...@mail.gmail.com
Re: Can't access gateway IP
On Sun, May 5, 2013 at 3:19 AM, Guido Martínez mtzgu...@gmail.com wrote: On Sat, May 4, 2013 at 3:28 PM, s0lid s0lid101...@gmail.com wrote: Ping the Debian 607 server from the router. Result? It can. I also can access it from my laptop going to the same router. BTW, which consumer router is this? You may have hit a firmware bug. i have a hunch it is, i just don't have another router to test on. This is a Zyxel whitelabeled to my telco so the firmware is custom made for my telco also. To narrow things down, I'd like to ask three questions. Do you have internet access from the server? Can you access the http or some other service installed in the router? and what if you change your server IP to 192.168.1.2, does that make a difference? No internet because i cant go pass through the gateway, No access with the router at all even i do nmap. I changed it to .254 but still same issue. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANZ3Tp29ZEA8HBo26-fQ_f-bdwsZk2n4nP9V84z5LPe1N=v...@mail.gmail.com
Re: Can't access gateway IP
On Sat, May 4, 2013 at 4:26 PM, s0lid s0lid101...@gmail.com wrote: On Sun, May 5, 2013 at 3:19 AM, Guido Martínez mtzgu...@gmail.com wrote: On Sat, May 4, 2013 at 3:28 PM, s0lid s0lid101...@gmail.com wrote: Ping the Debian 607 server from the router. Result? It can. I also can access it from my laptop going to the same router. BTW, which consumer router is this? You may have hit a firmware bug. i have a hunch it is, i just don't have another router to test on. This is a Zyxel whitelabeled to my telco so the firmware is custom made for my telco also. To narrow things down, I'd like to ask three questions. Do you have internet access from the server? Can you access the http or some other service installed in the router? and what if you change your server IP to 192.168.1.2, does that make a difference? No internet because i cant go pass through the gateway, No access with the router at all even i do nmap. I changed it to .254 but still same issue. Oh, I thought it was just a 'ping' issue, not connectivity. It's probably a bug on the router side, then. You could try faking your server MAC, and see if it makes a difference, but I have no idea how to do that. Hope to help, Guido. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca++dqukgamznuavkhx-wb0r6ar9tkgczefngfwkygj3ner6...@mail.gmail.com
Re: Can't access gateway IP
s0lid wrote: ---from debian server--- root@debian:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=40.5 ms 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=1.96 ms 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=2.08 ms ^C --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 1.967/14.861/40.532/18.152 ms How did it move from 192.168.1.1 to 192.168.1.2? Did your machine receive an ICMP redirect packet from the router? Please try again with 'ping -v' and post the output. It might show an ICMP redirect being received. I would run 'tcpdump -lni any' on both machines and look for the disconnect. If it is a noisy network then filter with 'host W.X.Y.Z' with the address of your client machine. tcpdump -lni any host W.X.Y.Z Or use the wireshark GUI around tcpdump if you prefer. Bob signature.asc Description: Digital signature
Re: Can't access gateway IP
Hi all, On Fri, May 3, 2013 at 8:55 PM, Bob Proulx b...@proulx.com wrote: s0lid wrote: ---from debian server--- root@debian:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=40.5 ms 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=1.96 ms 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=2.08 ms ^C --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 1.967/14.861/40.532/18.152 ms How did it move from 192.168.1.1 to 192.168.1.2? Did your machine receive an ICMP redirect packet from the router? I think that's his laptop he's pinging, to show us that he has connectivity. He probably forgot to include the prompt line. I agree with using wireshark. It should provide valuable info. Guido -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CA++DQUku4b48kjpUr+jy9LaxRm8R6btjb42gbi=q1at7aws...@mail.gmail.com
