Date: Sun, 10 Mar 2013 08:17:04 +0200 From: =?UTF-8?B?0JLQuNGC0LDQu9C40Lkg0KLRg9GA0L7QstC10YY=?= <corebug@corebug.net> To: doug@safeport.com Cc: freebsd-questions@freebsd.org Subject: Re: vlan routing Message-ID: <CAKB6gVhmLNGgx6-zx2fJxFomdx-wDQ7eWYj6mjkSh7Byxm9bhA@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1303092036110.3582@oceanpt.safeport.com> References: <alpine.BSF.2.00.1303092036110.3582@oceanpt.safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2013/3/10 <doug@safeport.com>: > I am trying set this up. First I munged the IP addresses. Not to worry if I > hit yours. I did the following commands: > > ifconfig vlan0 create > ifconfig vlan0 vlan 95 vlandev fxp0 > ifconfig vlan0 inet 134.217.128.117 netmask 255.255.255.0 > ifconfig fxp0 add 134.217.128.117 netmask 255.255.255.0 > route add -inet 134.217.128.117 134.217.128.1 > > ifconfig shows: > > fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=8<VLAN_MTU> > ether 00:d0:b7:56:cf:ab > inet 45.22.17.3 netmask 0xfffffc00 broadcast 45.22.19.255 > inet 45.22.17.17 netmask 0xffffffff broadcast 45.22.17.17 > inet 134.217.128.117 netmask 0xffffff00 broadcast 134.217.128.255 > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active > bge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> > ether 00:09:5b:60:e4:1f > media: Ethernet autoselect (none) > status: no carrier > vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > ether 00:d0:b7:56:cf:ab > inet 134.217.128.117 netmask 0xffffff00 broadcast 134.217.128.255 > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active > vlan: 95 parent interface: fxp0 > > Needless to say it does not work. The switch is programmed correctly (I am > told). My questions are (1) it seems like the option got applied to the > wrong interface; (2) what did I miss?? > > I also tried booting the system with IP of 134.217.128.117 but I did not get > the rc.conf macros correctly. I do know I can not route through the switch > without going the vlan commands. > > _____ > Douglas Denault > http://www.safeport.com > doug@safeport.com > Voice: 301-217-9220 > Fax: 301-217-9277 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" I guess you shouldn't put the same IP address on two interfaces (vlan and fxp0), you need to decide wherther you need tagged or untagged vlan frames there and, depending on this decision put the IP address on VLAN interface (tagged variant) or fxp0 (untagged one). If i understand your task correctly, then this line is faulty from your configuration: > ifconfig fxp0 add 134.217.128.117 netmask 255.255.255.0 You don't need it. > route add -inet 134.217.128.117 134.217.128.1 This is smth absoulutely wrong:) Basically, if you only need a vlan interface that could be used for routing, you need these commands only: ifconfig vlan95 create ifconfig vlan95 inet 134.217.128.117/24 vlan 95 vlandev fxp0 and in /etc/rc.conf you should put such strings: cloned_interfaces="vlan95" ifconfig_vlan95="inet 134.217.128.117/24 vlan 95 vlandev fxp0" for the interface to be created on reboot. Hope this helps. -- ~~~ WBR, Vitaliy Turovets NOC Lead @TV-Net ISP NOC Lead @Service Outsourcing company +38(093)265-70-55 VITU-RIPE X-NCC-RegID: ua.tv
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKB6gVhmLNGgx6-zx2fJxFomdx-wDQ7eWYj6mjkSh7Byxm9bhA>