As fresh as it gets:

jackman@shuttle:~$ ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.428 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.358 ms
^C
--- 192.168.100.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.358/0.393/0.428/0.035 ms
jackman@shuttle:~$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.10.10.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
24.21.216.0     0.0.0.0         255.255.252.0   U     0      0        0 eth1
0.0.0.0         24.21.216.1     0.0.0.0         UG    100    0        0 eth1


The following is an excerpt from what I sent to comcast...

The following is a record of a DHCP renew receiving an offer from the
offending server:

root@shuttle:/home/jackman# ifdown eth1 && ifup eth1
ifdown: interface eth1 not configured
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/00:4f:4e:03:a2:3f
Sending on   LPF/eth1/00:4f:4e:03:a2:3f
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.100.2 from 192.168.100.1
DHCPREQUEST of 192.168.100.2 on eth1 to 255.255.255.255 port 67
DHCPACK of 192.168.100.2 from 192.168.100.1
bound to 192.168.100.2 -- renewal in 13 seconds.
ssh stop/waiting
ssh start/running, process 1491

root@shuttle:/home/jackman# nmap -sP 192.168.100.1
Starting Nmap 5.00 ( http://nmap.org ) at 2011-02-27 00:27 PST
Host 192.168.100.1 is up (0.00058s latency).
MAC Address: 00:17:9A:DD:F0:02 (D-Link)
Nmap done: 1 IP address (1 host up) scanned in 0.47 seconds

It turns out that my own modem is also accessible at 192.168.100.1,
but when I scan it, it returns the following:

root@shuttle:/home/jackman# nmap -sP 192.168.100.1
Starting Nmap 5.00 ( http://nmap.org ) at 2011-02-27 13:50 PST
Host 192.168.100.1 is up (0.00059s latency).
Nmap done: 1 IP address (1 host up) scanned in 0.15 seconds

Notice that nmap is not able to determine the MAC address. For
reference, the mac address on my own modem is (00.17.9A.DD.F0.00).

Also for reference, this is a typical DHCP request and its result:

root@shuttle:/home/jackman# ifdown eth1 && ifup eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 6727
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/00:4f:4e:03:a2:3f
Sending on   LPF/eth1/00:4f:4e:03:a2:3f
Sending on   Socket/fallback
DHCPRELEASE on eth1 to 192.168.100.1 port 67
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/00:4f:4e:03:a2:3f
Sending on   LPF/eth1/00:4f:4e:03:a2:3f
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 24.21.218.157 from 73.88.148.1
DHCPREQUEST of 24.21.218.157 on eth1 to 255.255.255.255 port 67
DHCPACK of 24.21.218.157 from 73.88.148.1
bound to 24.21.218.157 -- renewal in 154834 seconds.
ssh stop/waiting
ssh start/running, process 6847




On Sun, Feb 27, 2011 at 7:39 PM, Bill Barry <[email protected]> wrote:
> On Sun, Feb 27, 2011 at 6:45 PM, Jackman <[email protected]> wrote:
>> And, now, a rendering in ASCII:
>>
>>  ------------------
>> | MONSTER (Server) | <-- eth0:10.10.10.10, static
>>  ------------------
>>       |
>>  ------------------
>> | SHUTTLE (Router) | <-- eth1 outside (dhclient) / eth0:10.10.10.1
>> inside (dhcp3-server 10.10.10.0/24)
>>  ------------------
>
>
> What does route -n show on SHUTTLE?  MONSTER should not be able to see
> the 192.168.100.0  network if SHUTTLE is routing correctly.  Is
> SHUTTLE's connection stable, or is it dropping also?  Could it just be
> a loose cable?
>
> Bill
> _______________________________________________
> EUGLUG mailing list
> [email protected]
> http://www.euglug.org/mailman/listinfo/euglug
>
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug

Reply via email to