Re: VLAN Trunking with Freebsd
If you are just creating from the command line and want cisco router like subinterfaces, the following works (I have the vlan module built into my kernel might need to load it otherwise.) [EMAIL PROTECTED] (19:22:09 ~) 0 # ifconfig bge0.1 ifconfig: interface bge0.1 does not exist [EMAIL PROTECTED] (19:22:13 ~) 0 # ifconfig bge0.1 create [EMAIL PROTECTED] (19:22:15 ~) 0 # ifconfig bge0.1 bge0.1: flags=8842BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3RXCSUM,TXCSUM ether 00:e0:81:2d:a3:16 media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 1 parent interface: bge0 [EMAIL PROTECTED] (19:22:17 ~) 0 # ifconfig bge0.1 destroy Not certain how thats represented in rc.conf, Will have a look. ifconfig_bge0.1=create ip_address/mask should work ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VLAN Trunking with Freebsd
Hey, I am sure this topic has been discussed before, however, I have been coming across unanswered inquiries within the last two months about possibly using the trunking aspect of 802.1q standard network routing, with only freebsd. I have attempted to create mulitple vlan interfaces and have failed, on 6.3-Stable. Does anyone know if the vlan emplimentation on Freebsd allows for trunking or, at the least, multiple vlans per physical device? This is my config: cloned_interfaces=vlan2 vlan3 vlan4 vlan5 ifconfig_re0=inet 192.168.1.62 netmask 255.255.255.192 ifconfig_re1=inet 192.168.1.254 netmask 255.255.255.128 ifconfig_bge0=inet a.b.c.d netmask 255.255.255.240 ifconfig_em0=up ifconfig_vlan2=192.168.41.1 vlan 2 vlandev em0 ifconfig_vlan3=192.168.19.3 vlan 3 vlandev em0 ifconfig_vlan4=192.168.42.1 vlan 4 vlandev em0 ifconfig_vlan5=192.168.100.1 vlan 5 vlandev em0 re0, re1, bge0 are ordinary interfaces (non-802.1q), and em0 is connected to a switch with 802.1q support. HTH, Nejc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VLAN Trunking with Freebsd
This is my config: cloned_interfaces=vlan2 vlan3 vlan4 vlan5 ifconfig_re0=inet 192.168.1.62 netmask 255.255.255.192 ifconfig_re1=inet 192.168.1.254 netmask 255.255.255.128 ifconfig_bge0=inet a.b.c.d netmask 255.255.255.240 ifconfig_em0=up ifconfig_vlan2=192.168.41.1 vlan 2 vlandev em0 ifconfig_vlan3=192.168.19.3 vlan 3 vlandev em0 ifconfig_vlan4=192.168.42.1 vlan 4 vlandev em0 ifconfig_vlan5=192.168.100.1 vlan 5 vlandev em0 re0, re1, bge0 are ordinary interfaces (non-802.1q), and em0 is connected to a switch with 802.1q support. maybe off-topic but when buying switches make sure it's clearly written 802.1Q support. There are VLAN capable switches, some very cheap, that just block traffic between ports except between port 1 and others, but no vlan tagging. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VLAN Trunking with Freebsd
Nejc Škoberne wrote: Hey, I am sure this topic has been discussed before, however, I have been coming across unanswered inquiries within the last two months about possibly using the trunking aspect of 802.1q standard network routing, with only freebsd. I have attempted to create mulitple vlan interfaces and have failed, on 6.3-Stable. Does anyone know if the vlan emplimentation on Freebsd allows for trunking or, at the least, multiple vlans per physical device? This is my config: cloned_interfaces=vlan2 vlan3 vlan4 vlan5 ifconfig_re0=inet 192.168.1.62 netmask 255.255.255.192 ifconfig_re1=inet 192.168.1.254 netmask 255.255.255.128 ifconfig_bge0=inet a.b.c.d netmask 255.255.255.240 ifconfig_em0=up ifconfig_vlan2=192.168.41.1 vlan 2 vlandev em0 ifconfig_vlan3=192.168.19.3 vlan 3 vlandev em0 ifconfig_vlan4=192.168.42.1 vlan 4 vlandev em0 ifconfig_vlan5=192.168.100.1 vlan 5 vlandev em0 re0, re1, bge0 are ordinary interfaces (non-802.1q), and em0 is connected to a switch with 802.1q support. If you are just creating from the command line and want cisco router like subinterfaces, the following works (I have the vlan module built into my kernel might need to load it otherwise.) [EMAIL PROTECTED] (19:22:09 ~) 0 # ifconfig bge0.1 ifconfig: interface bge0.1 does not exist [EMAIL PROTECTED] (19:22:13 ~) 0 # ifconfig bge0.1 create [EMAIL PROTECTED] (19:22:15 ~) 0 # ifconfig bge0.1 bge0.1: flags=8842BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3RXCSUM,TXCSUM ether 00:e0:81:2d:a3:16 media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 1 parent interface: bge0 [EMAIL PROTECTED] (19:22:17 ~) 0 # ifconfig bge0.1 destroy Not certain how thats represented in rc.conf, Will have a look. Vince HTH, Nejc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
