Hi,

Final update to my problem:

I dropped the Netgear switch and used a  Linksys^H^H Cisco switch.
The Linksys worked right out of the box.  Netgear's tech support lead
me nowhere... I opened a support ticket and someone acknowledged
that it was too complex for Level 1 support and escalated itto Level 2.
That's the last I heard from them... Netgear, I say boo!

I suppose this is simple for many folks, but I found this pretty hard
(atleast in the begining).  Should anyone care, here is the
complete solution I use for inter-VLAN routing:


Physical connections on the switch:
port 1: network A  -- 192.168.1.0/24
port 2: network B  -- 192.168.2.0/24
port 24: obsd router

Switch vlan setup:
vlan1: port 1 (untagged), port 24 (tagged)
vlan2: port 2 (untagged), port 24 (tagged)


On the obsd box, run
ifconfig fxp0 up
ifconfig vlan1 vlan 1 vlandev fxp0 192.168.1.1 255.255.255.0 up
ifconfig vlan2 vlan 2 vlandev fxp0 192.168.2.1 255.255.255.0 up

Finally, enable IP forwarding and adjust pf.conf to suit.

Note that the obsd box uses only a single physical NIC.  The
virtual vlan interfaces appear like real interfaces to most networking
systems like pf, and user land apps (and this can be exploited in
situations where there is a physical constraint on the number of
NICs you can add to a machine).  Using a 1000BT connection
between the switch and obsd box is recommended.

Only the obsd box and the switch need to be VLAN aware.  To
avoid MTU headaches and other incompatibilities, you must choose
a NIC that supports VLANs -- fxp, xl, sis, and the usual suspects.
The setup is totally transparent to all other devices.


Thanks to all who helped me through this.  Especially Brian
Shakelford and Camiel Dobbelaar.  Thanks guys!

- Raja


On 5/17/06, Raja Subramanian <[EMAIL PROTECTED]> wrote:
Hi,

On 5/16/06, Stuart Henderson <[EMAIL PROTECTED]> wrote:
> fwiw, current firmware release notes say this about VLANs:
>    "Bugs fixed: [...] Port based VLAN works abnormally with some
>    combinations of VLANs overlapping."
>

My switch is already running the latest firmware, and I'm still
having problems :-(

I'm unable to get my head around the alternate setup that Brian
suggested... and once I do, I'll try it out and post if it  fixes my
problem.

An update of my situation:

I'm able to use the default mtu of 1500 bytes on both sis/fxp
without any issues.

In my current setup it seems that my switch does not permit
the same MAC ID (of my router NIC) to appear on different
VLANs.  So long as I have only one vlan interface up at any
given time, everything works perfectly.

Many thanks to Camiel Dobbelaar (who IMO is worth Marlon
Brando's weight in diamond studded platinum) for all his
patience and guidance in helping me track down this issue. :-)

- Raja

PS: I'm sorry to spam the list with this problem.  It seems more
like an issue with my switch rather than obsd.

Reply via email to