|
I'm not sure if you're aware, but I've noticed an interesting flaw in traceroute. See, I have 2 different DSL modems strung together with MLPPP in order to render me the kind of speed that I need in order to stream 1080p HD from the internet. When my server is using only one of the two DSL modems to connect to the internet, traceroute works just fine. The moment that my server connects through the second modem as well to bridge them together with MLPPP into a single line with twice the speed, traceroute doesn't work in the normal manner, and I have to use the "-I" switch to make it work. I will show you what I mean...
Regular Traceroute noel@New-Laptop:~$ traceroute teksavvy.com
ICMP Traceoute noel@New-Laptop:~$ traceroute -I teksavvy.com
Now here's where it gets interesting... if I SSH into my server to try the same traceroute directly from the server (which is what uses MLPPP to bridge the two lines together), I get the following
Regular Traceroute noel@mail:~$ traceroute teksavvy.com
ICMP Traceroute noel@mail:~$ sudo traceroute -I teksavvy.com Do you have an explanation for this, and is there a way to fix
this, or is it a flaw to using MLPPP? I'd really like to know so
that I can adjust whatever I need to adjust to make it work
normally, without being forced to use the ICMP method. I'm very
puzzled as to why this is, and I would really appreciate it if it
could be fixed, or if this cannot be fixed (due to something with
MLPPP), if I at least had an explanation for what happens. I'm
just so confused as to how MLPPP can create this much issue with a
traceroute, considering that both modems should be connecting to
the same gateway. --
----------------------- Noel Lamothe [email protected] www.tech911solutions.com Home: 519-489-0448 (Kitchener, ON) Home (alt): 519-512-0459 (Brantford, ON) Home (alt): 716-566-9547 (Buffalo, NY) Fax: 519-489-4739 (Kitchener, ON) Fax (alt): 519-512-0936 (Brantford, ON) Cell: 519-998-8944 BBM PIN: D3AFF4AA |
