[c-nsp] Verizon TLS
Jason Berenson
jason at pins.net
Sat Aug 16 14:13:28 EDT 2008
Huh?
FA0/0 connects directly to the TLS and FA0/1 connects to the customer
switch. The TLS passes through the router before it ever hits their
public switch.
list-cisco-nsp at pwns.ms wrote:
>> Servers
>>
>> |
>> 7206VXR ---------TLS-------- 2651XM ------- Public switch -------
>> Firewall ------- LAN
>>
>> CPE config:
>>
>> interface FastEthernet0/0
>> desc TLS side
>> no ip address
>> speed 100
>> full-duplex
>> !
>> interface FastEthernet0/0.xxx
>> encapsulation dot1Q xxx
>> ip address 192.168.1.2 255.255.255.252
>> (rate limit to 10M)
>> no cdp enable
>>
> [snip]
>
>> ip route 0.0.0.0 0.0.0.0 192.168.1.1
>>
>
> Your diagram and config conflict with each other; according to the config, you're routing to the TLS *through* the switch. According to the diagram, the 2651XM is directly connected to the TLS, and is directly connected to the switch.
>
> My guess is that the switch leaks traffic between VLANs. The easiest workaround is probably just to connect the 2651XM directly to the TLS. They didn't have the problem with the T1s since they weren't going through the switch.
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list