Hi Bob!
The problem doesn`t seems to be your ISP... and not your fault too... but the way
packets are routed...
if you put a route like you said:
>route add -net 64.65.0.0 netmask 255.255.0.0 gw 64.65.206.1 eth1
everithing belonging to the range 64.65.0.0/16 works ok... the problem is that you
have another DSL connection, in another place but from the same DSL ISP, right? That
other connection doen`t belong to the 64.65.0.0/16 range...
what happens from your side... you try to access taht other box, your linux reads the
ip address and says..."this isn`t 64.65.0.0/16, so it goes trough the T1 isp"... and
that`s the way things are... at least ip routes :-)
As you said, if you don`t find the networks bellonging to your DSL ISP, every packet
different from 64.65.0.0/16 will go trough the T1 line...
If you want, send your addresses, and what you want route and maybe we can find some
way to do this...
orlando
>> you set T1 ISP as your default and your replys from ping to the DSL ISP
>> comes from the T1?
>> like that: ping DSP-ISP
>> reply (coming from T1-ISP) xxx ms ???
>This is the case, and it happens for all traffic, not just a ping. But
>it works on EVERYONE ELSE's system, just not the DSL ISP!
>
>One thing I just found, by watching a TCPDUMP during an external ping: I
>get a reply from my (t1) reply packet, saying "Admin Filter Prohibited".
>
>> try adding a static route including your DSL ISP...
>>
>> something like
>>
>> ip route 64.65.0.0 255.225.0.0 64.65.206.162
>
>I did the following:
>route add -net 64.65.0.0 netmask 255.255.0.0 gw 64.65.206.1 eth1
>
>Which works, as long as the source IP within the DSL network is within
>64.65.x.x. However, I do have a DSL line that is on a different range
>(yet the same ISP). I can make it work by doing the above command,
>specifying that IP for the first set of numbers. But honestly, should I
>have to do all this work, trying to figure all the IP addresses of my
>DSL ISP just to make their networks work? It seems like there must be
>another way.
