All,

I have read the 2-3 posts here that talk about the requirement for a managed switch that supports 802.1q off the back of a Ubiquiti unit, if you want to talk to the WAN (internet gateway). In my case a Bullet M2 HP.

I have in my possession a Cisco 2950-24 managed switch. It is a layer 2 switch that supports 802.1q on its configured vlans.

The problem I have is that CLI is the most obtuse configuration methodology I have ever seen. Not that I haven't been studying, I have. I'm just not sure I'll get smart on this in a reasonable period of time.

Is there someone out there who is smart on this stuff who could lend me a helping hand? I'd sure appreciate it.

73,

Chuck...

WB6YOK

If my commands are correct the below should give you the WAN port on EVERY port of the switch (aka plug your local network into any port)   except for those ports that you use the interface command on to change over to handle bbhn traffic.

Cisco switches are nice, but they take a lot of knowledge to understand in, I suggest research what each of these command s do to understand what your being asked to setup.

#Enables administrative mode
enable
<you may have to enter a password here>

#Setup the vlan database:
vlan database
vlan 10 name "BBHN Network"
vlan 2 name "BBHN DTDLINK"
exit

#Enable configuration mode
conf t
# Assuming Interface 23 on module 0 is what you want to configure to be the port the BBHN node plugs into: -- puts the interface into a trunking mode.

interface FastEthernet0/23
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk native vlan 10

# repeat the above for each bbhn port changing the number to to the correct interface

# You can add a vlan 11,12,13 etc if you want to get advanced to have the "lan" port of each device on its own vlan if you need to mix and match but this is another subject.

exit

exit

#save the configuration to the startup config so when you reboot the switch it sticks around

copy running-config startup-config

* DISCLAIMER * I have not tested the above commands -- Any configuration is at your own risk.

Cisco gear is great, rugged (heck 1watt through-hole resistors are never argued with right?)

One thing to keep in mind is power usage.

I think the average consumption is 60w on a Cisco Switch by my last memory. 

That said the ruggedness of the Cisco gear is probably more likely to survive any local issues than a home quality device.

I actually had a Cisco router short out, smoke a few circuits, reboot, disable the port, and 3 weeks later when I decided to clean it I realized the smoke I smelt and the internet reboot was actually the router after I checked  the router configs before shutdown.

Just something to think about if you need the node to run on emergency power.

Update...... Im looking to lay the ground work to allow a user to set the VLAN-ID "???", in the mean time im looking for the config file... If the Dev team has interest in creating a Gui for it? Q:were is the 8021q trunking config at in /? and what Lib is being used? I dont see kmod-8021q in the package list http://www.broadband-hamnet.org/download/backfire/10.03.1/ar71xx/packages/Packag es.gz. So? kmod macvlan looks interesting...

Im just not seeing how 8021q aka Stacked VLANs 802.1ad is being configured.  

http://wiki.openwrt.org/doc/networking/network.interfaces

KJ6DZB,

It might be better if you start a new thread rather than reviving older resolved threads.

This would allow you to not need to post the same message in multiple forums and will also allow users to find your post easier.