[c-nsp] VLAN and switch and ?
Charles Regan
charles.regan at gmail.com
Mon Apr 13 19:58:49 EDT 2009
For those interested here is how I made it work.
I bought two 3550 switch.
ISP----Wireless-BH#1----3550#1----Fiber----2950----3550#2----Wireless-BH#2----ISPClients
On the 3550#1 the port connected to Wireless-Backhaul1 I've used the
following command.
switchport access vlan xx
switchport mode dot1q-tunnel
l2protocol-tunnel cdp
l2protocol-tunnel stp
l2protocol-tunnel vtp
spanning-tree bpdufilter enable
Same thing on the 3550#2
Everything works perfectly.
On Wed, Mar 4, 2009 at 7:35 PM, Deric Kwok <deric.kwok2000 at gmail.com> wrote:
>> Hi
>>
>> I only have l2tp configuration in linux router. Here is below.
>>
>> Pls note that i don't know Jeff suggestion how L2tp works out in your
>> network
>> it looks like his suggestion is same as L2tp so that I post to ask him
>>
>> I only know this l2tp worked in my setting before when doing in DSL
>>
>> HTH
>> !
>> interface Ethernet0
>> no ip address
>> speed 1000
>> duplex full
>> !
>> interface Ethernet0.120
>> description vlan120
>> ip address 10.0.0.6 255.255.255.252
>> !
>> interface Ethernet0.130
>> description vlan130
>> ip address 10.0.0.74 255.255.255.252
>> !
>> interface Ethernet0.140
>> description vlan140
>> ip address 10.0.0.54 255.255.255.252
>> !
>> !
>> interface Tunnel1
>> description vlan120
>> tunnel mode l2tp
>> tunnel peer name xxxx
>> tunnel local name deric
>> tunnel key kwok
>> tunnel virtual-template 1
>> !
>> interface Tunnel2
>> description vlan130
>> tunnel mode l2tp
>> tunnel peer name xxxx
>> tunnel local name deric
>> tunnel key kwok
>> tunnel virtual-template 1
>> !
>> interface Tunnel3
>> description vlan140
>> tunnel mode l2tp
>> tunnel peer name xxxx
>> tunnel local name deric
>> tunnel key kwok
>> tunnel virtual-template 1
>> !
>>
>>
>>
>> On Wed, Mar 4, 2009 at 4:48 PM, Charles Regan <charles.regan at gmail.com>
>> wrote:
>>>
>>> There's now way my switch will support L2TP.
>>>
>>> How would you setup VLAN in this setup.
>>>
>>> ISP needs to pass all his vlan (switchport mode trunk)
>>> I don't want ISP to have access to my network ... (swictchport access
>>> vlan 500, on both end ?)
>>> I want Internet acces from this ISP from his BackHaul1. (switchport
>>> access vlan 500, on my gateway router ?)
>>>
>>>
>>>
>>> On Wed, Mar 4, 2009 at 5:48 PM, Charles Regan <charles.regan at gmail.com>
>>> wrote:
>>> > On Wed, Mar 4, 2009 at 5:47 PM, Charles Regan <charles.regan at gmail.com>
>>> > wrote:
>>> >> There's now way my switch will support L2TP.
>>> >>
>>> >> How would you setup VLAN in this setup.
>>> >>
>>> >> ISP needs to pass all his vlan (switchport mode trunk)
>>> >> I don't want ISP to have access to my network ... (swictchport access
>>> >> vlan 500, on both end ?)
>>> >> I want Internet acces from this ISP from his BackHaul1. (switchport
>>> >> access vlan 500, on my gateway router ?)
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Mar 4, 2009 at 5:44 PM, Deric Kwok <deric.kwok2000 at gmail.com>
>>> >> wrote:
>>> >>> look like L2TP.
>>> >>>
>>> >>> Can I know why use it intead of typically vlan?
>>> >>>
>>> >>> Thank you
>>> >>>
>>> >>> On Wed, Mar 4, 2009 at 10:14 AM, Jeff Fitzwater <jfitz at princeton.edu>
>>> >>> wrote:
>>> >>>>
>>> >>>> Look at layer 2 tunneling for your switches. You would assign tunnel
>>> >>>> vlan
>>> >>>> ID and ISP would send tagged traffic into tunnel (Q in Q) and traffic
>>> >>>> would
>>> >>>> exit tunnel where ever needed. When you assign a port as a tunnel
>>> >>>> port, it
>>> >>>> becomes a tunnel-input and tunnel-output. You can have as many
>>> >>>> tunnel
>>> >>>> ports as you need. The ISP can now send what ever VLANs they want
>>> >>>> and you
>>> >>>> do not need to change anything.
>>> >>>> Read the doc and be aware of oversized packet handling within tunnel
>>> >>>> switches.
>>> >>>>
>>> >>>>
>>> >>>> Jeff Fitzwater
>>> >>>> OIT Network Systems
>>> >>>> Princeton University
>>> >>>>
>>> >>>> On Mar 4, 2009, at 9:46 AM, Charles Regan wrote:
>>> >>>>
>>> >>>>> Good Morning,
>>> >>>>>
>>> >>>>> I'll try to explain what I want to do... We are LOCAL NETWORK in
>>> >>>>> this
>>> >>>>> graphic.
>>> >>>>> The ISP wants to use our fiber link to connect to his wireless
>>> >>>>> customer.
>>> >>>>> We also want internet access from his Wireless Backhaul1.
>>> >>>>> ISP also use VLAN on his customer subscriber modules.
>>> >>>>>
>>> >>>>> How would you configure 2924 Switch and 2960 Switch, so that
>>> >>>>> everything is transparent from my side and his side ?
>>> >>>>> I don't want him to call me to add a new VLAN on our switch.
>>> >>>>>
>>> >>>>>
>>> >>>>> ISP ---Wireless BackHaul1 -- 2924 Switch ---- FIBER ---- 2960 Switch
>>> >>>>> ---- Wireless Backhaul2 ---- Access Point ---- Wireless subscriber
>>> >>>>> modules
>>> >>>>> |
>>> >>>>> |
>>> >>>>> |
>>> >>>>> |
>>> >>>>> |
>>> >>>>> |
>>> >>>>> |
>>> >>>>> |
>>> >>>>> |
>>> >>>>> |
>>> >>>>> LOCAL NETWORK LOCAL NETWORK
>>> >>>>>
>>> >>>>>
>>> >>>>> Will something like this work ?
>>> >>>>> switchport access vlan 500
>>> >>>>> switchport trunk encapsulation dot1q
>>> >>>>> switchport mode trunk
>>> >>>>> _______________________________________________
>>> >>>>> 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/
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> 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/
>>> >>>
>>> >>>
>>> >>
>>> >
>>> _______________________________________________
>>> 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