[wplug] Verizon misconfiguration?

[Andrew Fisk]

As your dsl modem is connected to Verizon's network, there is no  
reason that they should not also use a private IP to get traffic from  
their DSL access point to a router with a external address.  This  
let's them do all there fun port blocking and DNS hijacking on the  
internal network and means they only have to use one external IP for  
all the customers on the that router.

They can route 10.xxx.xxx.xxx traffic on their internal network just  
like you can and as the wan interface of your dsl router is on their  
network (not on the internet) their is no issue with the address being  
routable.

If you want a straight shot out to the world you will have to pay them  
for a static IP -- but I don't think that that would solve your speed  
problem -- I am sure you will have to talk to some nice person in  
Bulgaria who will insist on going through pages 1 through 7 of his  
manual before you get to talk to a level 2 engineer who will actually  
test the line and dispatch a tech if the line is a problem.

You might find it less confusing to run a 192.168.xxx.xxx subnet  
internally, it is just as secure and should provide more than enough  
address space for your home (64K devices ) -- at least you won't get  
your stuff mixed up with verizons, and if they add a 10.61 network you  
won't be messed up while you (and verizon) figure out what happened.


Thanks

Andy
Spitfire Computer Services
Suite 19
2301 Duss Ave.
Ambridge, PA 15003
Phone (412) 749-0162
fax: (602) 476-8868
andy at spitcomp.com
www.spitcomp.com



On Dec 4, 2008, at Thursday, December 4, 20081:32 AM, Janos Dohanics  
wrote:

> Yesterday the connection in my house started to get really slow. I  
> have
> Verizon DSL.
>
> Casual pinging (www.verizon.net) shows:
>
> --- www.verizon.net ping statistics ---
> 114 packets transmitted, 99 packets received, 13% packet loss
> round-trip min/avg/max/stddev = 439.650/455.840/501.936/15.334 ms
>
> Pretty long ping times...
>
> So, I did traceroute:
>
> $ traceroute www.verizon.net
> traceroute to www.verizon.net (206.46.232.39), 64 hops max, 40 byte  
> packets
> 1  10.61.70.1 (10.61.70.1)  1.117 ms  0.913 ms  0.595 ms
> 2  10.6.8.1 (10.6.8.1)  402.001 ms *  396.624 ms
> 3  at-1-2-0-1715.CORE-RTR2.PITT2.verizon-gni.net (130.81.13.13)   
> 395.428 ms
> 395.059 ms  393.617 ms
> 4  so-7-0-0-0.CORE-RTR1.PITT2.verizon-gni.net (130.81.18.254)   
> 408.576 ms
> 402.801 ms  403.065 ms
> 5  * so-5-0-0-0.BB-RTR1.RES.verizon-gni.net (130.81.20.92)  407.405 ms
> 430.332 ms
> 6  130.81.17.97 (130.81.17.97)  407.966 ms  407.473 ms *
> 7  130.81.19.78 (130.81.19.78)  439.689 ms  438.633 ms  440.890 ms
> 8  so-1-0-0-0.CORE-RTR1.DFW03.verizon-gni.net (130.81.20.157)   
> 438.217 ms
> 439.749 ms  438.021 ms
> 9  po1.ctn-border1.vzlink.com (206.46.225.85)  440.523 ms  446.666 ms
> 447.796 ms
> 10  po121.ctn-core1.vzlink.com (206.46.225.18)  451.012 ms^C
>
> Hmm... my gateway is 10.61.70.1 - why is the next hop 10.6.8.1? I  
> only have a
> 10.61.70.0/24 LAN, and no 10.6.xxx.xxx network.
>
> Is Verizon misconfigured, or am I missing something?
>
> jd
>
> -- 
> Janos Dohanics
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug
>