how-to block ads
|
|
Share Topic
 |
 |
|
Reviews:
 ·Future Nine Corp..
| reply to NormanS
Re: DHCP Spoofing / Half Bridgingsaid by NormanS 
Interesting...based on my SpeedStream 4100, as connected to my Netgear FR114P, and pushing a public IP address from the SS4100 to the Netgear FR114P:
C:\WINDOWS>tracert cs.washington.edu
Tracing route to cs.washington.edu [128.208.3.200]
over a maximum of 30 hops:
1 41 ms 55 ms 55 ms Suzuka [192.168.0.1]
2 69 ms 55 ms 27 ms adsl-64-174-91-254.dsl.sntc01.pacbell.net [64.174.91.254]
3 14 ms 14 ms 14 ms dist2-vlan50.sntc01.pbi.net [63.203.35.66]
[/BQUOTE :In this case, it would appear that the SpeedStream is using a different implementation technique. If I'm understanding your network correctly, it seems that the first hop is your netgear router at 192.168.0.1, then the next hop is a pacbell router at 64.174.91.254. On the other hand, perhaps 64.174.91.254 is your public IP. I admit I'm little confused about your network. If your netgear is at 192.168.0.1, why is the ping time taking on the order of 55ms? That seems rather high for a locally connected host over Ethernet. | |
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
2 edits | My Netgear is at 192.168.102.1. I do not know why it doesn't show in tracerts; it never did, though my old SMC Barricade does when I use it with a dial-up modem. If I doctor the tracert with the Netgear so it looked like the Barricade; well...SMC Barricade 7004BR:
C:\WINDOWS>tracert cs.washington.edu
Tracing route to cs.washington.edu [128.208.3.200]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms Shizuku [192.168.102.3]
2 165 ms 206 ms 192 ms nas93.SanJose1.Level3.net [209.247.21.227]
3 165 ms 192 ms 206 ms ge-7-0-1.core2.SanJose1.Level3.net [63.215.14.3]
C:\WINDOWS>tracert cs.washington.edu
Tracing route to cs.washington.edu [128.208.3.200]
over a maximum of 30 hops:
1 <10 ms <10 ms 14 ms Chihiro [192.168.102.1]
2 41 ms 55 ms 55 ms Suzuka [192.168.0.1]
3 69 ms 55 ms 27 ms adsl-64-174-91-254.dsl.sntc01.pacbell.net [64.174.91.254]
4 14 ms 14 ms 14 ms dist2-vlan50.sntc01.pbi.net [63.203.35.66]
BTW, I did not "invent" that first line out of whole cloth; I can trace it from the computer, thus:
C:\WINDOWS>tracert chihiro
Tracing route to Chihiro [192.168.102.1]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms Chihiro [192.168.102.1]
Trace complete.
SS4100 Routing Table:
Routing Table
Destination Netmask Gateway Interface
127.0.0.0 255.0.0.0 127.0.0.1 lo0
192.168.0.0 255.255.0.0 192.168.0.1 LAN
Default Gateway - 64.174.91.254 PPPoE
64.174.90.97 255.255.255.255 64.174.90.97 LAN
Diagnostic - Routing Table
Destination Mask Gateway Metric Active
Default -- 64.174.90.97 -- Yes
172.29.61.0 255.255.0.0 192.168.102.100 2 Yes
64.174.90.0 255.255.255.0 64.174.90.97 1 Yes
64.174.90.97 255.255.255.255 64.174.90.97 1 Yes
192.168.102.0 255.255.255.0 192.168.102.1 1 Yes
192.168.102.1 255.255.255.255 192.168.102.1 1 Yes
09/08/05 21:58:02 Slow traceroute chihiro
Trace chihiro (192.168.102.1) ...
192.168.102.1 RTT: 0ms TTL: 64 (Chihiro ok)
09/08/05 21:57:02 Slow traceroute cs.washington.edu
Trace cs.washington.edu (128.208.3.200) ...
192.168.0.1 RTT: 14ms TTL:170 (Suzuka ok)
64.174.91.254 RTT: 27ms TTL:170 (adsl-64-174-91-254.dsl.sntc01.pacbell.net ok)
63.203.35.66 RTT: 28ms TTL:170 (dist2-vlan50.sntc01.pbi.net ok)
--
Norman
~A deam, dream, no dream
~Voices of the night go across the forest
~A dream, dream, no dream
~Good night my good child | |
|
