My router is a Linux PC. It is connected directly to the cable modem. So I
know which addresses the router has:
>ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
defaul
t qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP
group default qlen 1000
link/ether 00:d0:b7:3f:3f:d7 brd ff:ff:ff:ff:ff:ff
inet 73.37.165.179/23 brd 255.255.255.255 scope global enp1s10
valid_lft forever preferred_lft forever
inet6 2001:558:6014:3e:a038:4872:4d66:a81/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::2d0:b7ff:fe3f:3fd7/64 scope link
valid_lft forever preferred_lft forever
3: enp0s7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP
group default qlen 1000
link/ether 00:23:54:f9:4c:c1 brd ff:ff:ff:ff:ff:ff
inet 192.168.42.2/24 brd 192.168.42.255 scope global enp0s7
valid_lft forever preferred_lft forever
inet6 2601:444:47f:c71e::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::223:54ff:fef9:4cc1/64 scope link
valid_lft forever preferred_lft forever
Can a cable modem have multiple addresses? I wouldn't think so as it should
just be a bridge.
On Sun, Sep 3, 2017 at 9:57 AM, Andrew Lunn <andrew at lunn.ch> wrote:
> On Sun, Sep 03, 2017 at 08:19:13AM -0500, gregrwm wrote:
> > On Sun, Sep 3, 2017 at 7:47 AM, Jon Schewe <jpschewe at mtu.net> wrote:
> >
> > > I'm trying to debug some issues with my internet connection. I have
> > > Comcast and the traceroute results are not coming back what I expect.
> On my
> > > router my routing table looks like this:
> > >
> > > >netstat -rn
> > > Kernel IP routing table
> > > Destination Gateway Genmask Flags MSS Window
> irtt
> > > Iface
> > > 0.0.0.0 73.37.164.1 0.0.0.0 UG 0 0
> 0
> > > enp1s10
> > > 73.37.164.0 0.0.0.0 255.255.254.0 U 0 0
> 0
> > > enp1s10
> > >
> > > Given that, I expect the first hop in a traceroute to be 73.37.164.1,
> but
> > > it's not.
> > > >traceroute -n 8.8.8.8
> > > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> > > 1 96.120.48.69 8.890 ms 14.915 ms 15.659 ms
> > > 2 68.85.168.121 14.833 ms 15.604 ms 15.575 ms
> > > 3 96.108.188.62 14.502 ms 14.484 ms 14.665 ms
> > > 4 96.108.188.101 15.455 ms 16.596 ms 16.574 ms
> > > 5 68.86.94.81 28.011 ms 26.859 ms 26.841 ms
> > > 6 68.86.85.158 24.289 ms 19.757 ms 22.386 ms
> > > ...
> > >
> > > Can anyone explain what's going on here?
> > >
> >
> > your traceroute addresses starting with 68.85.168.121 identify as comcast
> > hosts.
>
> 96.120.48.69 is also a comcast address is you do a whois for it.
>
> Routers have multiple interfaces, and each interface should have an IP
> address. 73.37.164.1 is the address of one interface on the
> router. Quite likely, 96.120.48.69 is an address on one of the other
> interfaces of the router.
>
> Andrew
>
>
>
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> tclug-list at mn-linux.org
> http://mailman.mn-linux.org/mailman/listinfo/tclug-list
>
>
--
http://mtu.net/~jpschewe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20170903/5c72d071/attachment-0001.html>