MESSAGE
| DATE | 2014-08-17 |
| FROM | Ruben Safir
|
| SUBJECT | Re: [NYLXS - HANGOUT] networking puzzle - Optimum Tech Support to
|
Love this chat
Jean C.: Hi, my name is Jean C. and I will be assisting you today.
Ruben Safir: My current setup for my server in the house is a fit/pc
connected to a
optimum static subnet that is described as follows
eth1 Link encap:Ethernet HWaddr 00:01:C0:09:A6:09
inet addr:96.57.23.82 Bcast:96.57.23.87 Mask:255.255.255.248
inet6 addr: fe80::201:c0ff:fe09:a609/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2290256 errors:0 dropped:0 overruns:0 frame:0
TX packets:3117484 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:741616664 (707.2 Mb) TX bytes:3512272625 (3349.5 Mb)
I use an internal set up that is described as follows
www:~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:01:C0:09:A6:08
inet addr:10.0.0.5 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:c0ff:fe09:a608/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:773973 errors:0 dropped:0 overruns:0 frame:0
TX packets:916441 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:71336040 (68.0 Mb) TX bytes:728493565 (694.7 Mb)
My routing has behaved very strangely since I've had this setup and it
is a real mystery to me as to why it seems to be broken.
Ruben Safir:
The current routing is as follows
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 96.57.23.81 0.0.0.0 UG 0 0 0 eth1
0.0.0.0 96.57.23.82 0.0.0.0 UG 0 0 0 eth1
10.0.0.0 10.0.0.5 255.255.255.0 UG 0 0 0 eth0
96.57.23.80 96.57.23.82 255.255.255.248 UG 0 0 0 eth1
96.57.23.81 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
Ruben Safir: This is extreme overkill It should work like this
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 96.57.23.82 0.0.0.0 UG 0 0 0 eth1
10.0.0.0 10.0.0.5 255.255.255.0 UG 0 0 0 eth0
96.57.23.80 96.57.23.82 255.255.255.248 UG 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
This defines the internal route to 10.0.0.0 connecting through 10.0.0.5
and that works.
the external network should work as defined at 96.57.23.80 through
96.57.23.82 which is eth1. This seems to work since I can ping
96.57.23.81 which is the cable modem gateway.
However 0.0.0.0 through 96.57.23.82 fails misserably. It won't route
out unless I explicitely define 96.57.23.81 as a host routed through
eth1 and only then can I add another default
0.0.0.0 96.57.23.81 0.0.0.0 UG 0 0 0 eth1
This shouldn't be necessary. What am I missing here?
Ruben
Jean C.: I am truly sorry for any inconvenience, I will be glad to
assist you with this issue Ruben.
Jean C.: Are you having an issue with the Internet connection ?
Ruben Safir: why are you asking me that?
Ruben Safir: do you have a networking person there?
Jean C.: I am a networking technician Ruben . Can you be more specific
regarding your issue ?
Ruben Safir: sure
Ruben Safir: My current setup for my server in the house is a fit/pc
connected to a
optimum static subnet that is described as follows
eth1 Link encap:Ethernet HWaddr 00:01:C0:09:A6:09
inet addr:96.57.23.82 Bcast:96.57.23.87 Mask:255.255.255.248
inet6 addr: fe80::201:c0ff:fe09:a609/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2290256 errors:0 dropped:0 overruns:0 frame:0
TX packets:3117484 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:741616664 (707.2 Mb) TX bytes:3512272625 (3349.5 Mb)
I use an internal set up that is described as follows
www:~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:01:C0:09:A6:08
inet addr:10.0.0.5 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:c0ff:fe09:a608/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:773973 errors:0 dropped:0 overruns:0 frame:0
TX packets:916441 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:71336040 (68.0 Mb) TX bytes:728493565 (694.7 Mb)
My routing has behaved very strangely since I've had this setup and it
is a real mystery to me as to why it seems to be broken.
Ruben Safir:
The current routing is as follows
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 96.57.23.81 0.0.0.0 UG 0 0 0 eth1
0.0.0.0 96.57.23.82 0.0.0.0 UG 0 0 0 eth1
10.0.0.0 10.0.0.5 255.255.255.0 UG 0 0 0 eth0
96.57.23.80 96.57.23.82 255.255.255.248 UG 0 0 0 eth1
96.57.23.81 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
Ruben Safir: This is extreme overkill It should work like this
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 96.57.23.82 0.0.0.0 UG 0 0 0 eth1
10.0.0.0 10.0.0.5 255.255.255.0 UG 0 0 0 eth0
96.57.23.80 96.57.23.82 255.255.255.248 UG 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
This defines the internal route to 10.0.0.0 connecting through 10.0.0.5
and that works.
the external network should work as defined at 96.57.23.80 through
96.57.23.82 which is eth1. This seems to work since I can ping
96.57.23.81 which is the cable modem gateway.
However 0.0.0.0 through 96.57.23.82 fails misserably. It won't route
out unless I explicitely define 96.57.23.81 as a host routed through
eth1 and only then can I add another default
0.0.0.0 96.57.23.81 0.0.0.0 UG 0 0 0 eth1
This shouldn't be necessary. What am I missing here?
Ruben
Ruben Safir: is that specific enough?
Jean C.: Please allow me a few moments while I look in to this for you.
Ruben Safir: thanks
Jean C.: Can you please verify your address ?
Ruben Safir: My network addreess or my physical address
Jean C.: Physical address
Ruben Safir: 1580 East 19th Street Brooklyn, USA 11230 Apt 1-E
Jean C.: Thank you.
Jean C.: Thank you for waiting. I am still researching this issue for
you, would you mind holding for just a few more moments please?
Ruben Safir: no problem
Jean C.: I am so sorry to keep you waiting, Ruben. I am still working on
this issue. Would you be able to provide me just a few more moments? I
appreciate your patience.
Jean C.: From why I can see we show the static IP service is up and
running . We show no issues with the static ip service we have
provided .I'm sorry but that is beyond the scope of what we support
here. Once our equipment is working properly and you have access to the
Internet .
Jean C.: Thank you for waiting.
Ruben Safir: it only is working after I jimmyrig it
Jean C.: Not sure what you mean by that ruben.
Ruben Safir: this route
Ruben Safir: 96.57.23.80 96.57.23.81 255.255.255.248 UG 0
0 0 eth1
96.57.23.81 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
Ruben Safir: That is jimmyrigged and not normal
Ruben Safir: but it is the only way it works
Jean C.: You are using an attached device correct ?
Ruben Safir: yes, my linux router
Jean C.: May be that's the issue .
Ruben Safir: you wouldn't say that if you understood what I was saying :(
Ruben Safir: this will never get fixed
Ruben Safir: I need a higher level networking guru
Jean C.: According to our tools we show no issues with the modem or the
static IP service .
Ruben Safir: it doesn't gateway correctly
Jean C.: Is there anything else that I can assist you with, Ruben?
Ruben Safir: my external eth1 is 96.57.23.82
Ruben Safir: 96.57.23.81 is the cable modem
Ruben Safir: it should respond that it is a gateway when packets are
routed to it on broadcast and addressed for the outside
Ruben Safir: they DON'T
Ruben Safir: The packets need to be explicitley told to route though
96.57.23.81, something the gateway should be taking care of an not
slightenly dropping such routing requests
Ruben Safir: 96.57.23.82 say - Hey I have a packet to Google, anyone
know how to send it out?
Ruben Safir: 95.57.23.81 should respond YES - I'm connected to the outside
Ruben Safir: it doesn't
Jean C.: I am terribly sorry for any inconvenience, Ruben. We show that
the modem and the static IP service is working properly from this side .
Ruben Safir: it is fucked and I'm sick of it because it makes rebooting
a PIA
Ruben Safir: is that explicit enough
Jean C.: Once again, I sincerely apologize for any inconvenience, Ruben.
Is there anything else that I can assist you with, Ruben?
Ruben Safir: yes - why does the gateway not respond to network routing
requests?
On 08/16/2014 11:07 PM, Ruben Safir wrote:
> My current setup for my server in the house is a fit/pc connected to a
> optimum static subnet that is described as follows
>
> eth1 Link encap:Ethernet HWaddr 00:01:C0:09:A6:09
> inet addr:96.57.23.82 Bcast:96.57.23.87 Mask:255.255.255.248
> inet6 addr: fe80::201:c0ff:fe09:a609/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2290256 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3117484 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:741616664 (707.2 Mb) TX bytes:3512272625 (3349.5 Mb)
>
>
>
> I use an internal set up that is described as follows
>
> www:~ # ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:01:C0:09:A6:08
> inet addr:10.0.0.5 Bcast:10.0.0.255 Mask:255.255.255.0
> inet6 addr: fe80::201:c0ff:fe09:a608/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:773973 errors:0 dropped:0 overruns:0 frame:0
> TX packets:916441 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:71336040 (68.0 Mb) TX bytes:728493565 (694.7 Mb)
>
>
> My routing has behaved very strangely since I've had this setup and it
> is a real mystery to me as to why it seems to be broken.
>
>
>
> The current routing is as follows
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 96.57.23.81 0.0.0.0 UG 0 0 0 eth1
> 0.0.0.0 96.57.23.82 0.0.0.0 UG 0 0 0 eth1
> 10.0.0.0 10.0.0.5 255.255.255.0 UG 0 0 0 eth0
> 96.57.23.80 96.57.23.82 255.255.255.248 UG 0 0 0 eth1
> 96.57.23.81 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
>
>
> This is extreme overkill It should work like this
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 0.0.0.0 96.57.23.82 0.0.0.0 UG 0 0 0 eth1
> 10.0.0.0 10.0.0.5 255.255.255.0 UG 0 0 0 eth0
> 96.57.23.80 96.57.23.82 255.255.255.248 UG 0 0 0 eth1
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
>
>
> This defines the internal route to 10.0.0.0 connecting through 10.0.0.5
> and that works.
>
> the external network should work as defined at 96.57.23.80 through
> 96.57.23.82 which is eth1. This seems to work since I can ping
> 96.57.23.81 which is the cable modem gateway.
>
> However 0.0.0.0 through 96.57.23.82 fails misserably. It won't route
> out unless I explicitely define 96.57.23.81 as a host routed through
> eth1 and only then can I add another default
>
> 0.0.0.0 96.57.23.81 0.0.0.0 UG 0 0 0 eth1
>
>
> This shouldn't be necessary. What am I missing here?
>
> Ruben
>
>
>
|
|
