There are reports that hw assisted VLANs caused problems
in bridging senarios. Users have reported that -vlanhwtag
and/or promisc on the physical interface helped. Using
-vlanhwtag helped in a case of mine.
On 12/20/2011 8:13 AM, Alexander Lunev wrote:
i made a little lab, all on 8.2-R:
freebsd1-le0.10 (192.168.2.1)<=====> bridge0( le0.10 - freebsd2 -
le1.10 )<=====> le0.10(192.168.2.1) - freebsd3
freebsd2 is a "switch" it has no ip addresses assigned to interfaces
(except localhost of course), "switch" is made by bridge0 interface
which contain vlan interfaces le0.10 and le1.10. Ethernet segments
freebsd1-freebsd2 and freebsd2-freebsd3 are different and not visible
to each other.
In this scheme i can ping 192.168.2.2 from 192.168.2.1 just fine, so
if your question was "will bridge work without ip addresses", then
answer is "yes".
--
your sweet isn't ready yet
On Mon, Dec 19, 2011 at 8:52 AM, saeedeh motlagh
<saeedeh.motl...@gmail.com> wrote:
you're right but we can't assign tow parent interface to one vlan in freebsd
therefore i define two vlans with the one vlan id.
although we can do it by blow command but it's not work too:
ifconfig gbeth0.10 create
ifconfig msk0.10 create
ifconfig
gbeth0.10: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=3<RXCSUM,TXCSUM>
ether 00:27:0e:03:4b:2f
media: Ethernet autoselect (1000baseT<full-duplex>)
status: active
vlan: 10 parent interface: gbeth0
msk0.10: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=100<TSO4>
ether 00:30:4f:63:5a:bc
media: Ethernet autoselect (none)
status: active
vlan: 10 parent interface: msk0
you know when i define vlans with ip addressess they work as i expected but
i want to know if i can define vlan without ip address as the switch beacuse
i wanna configure a freebsd box as a real switch in my network. maybe it's
impossible to do that :(
On Sun, Dec 18, 2011 at 10:52 PM, Alexander Lunev<sol...@gmail.com> wrote:
first of all, you should name and number you vlan same, if it's clan10
on the one side, then it's vlan10 on the other side and in betweeen.
then (though you have to do it first of all), you should understand
how vlan's work, and after that connect ports to each other according
to your scheme.
--
your sweet isn't ready yet
On Sun, Dec 18, 2011 at 10:01 AM, saeedeh motlagh
<saeedeh.motl...@gmail.com> wrote:
i have 3 freebsd system: 0.28 , 0.25 and 0.12 which 28 is assumed to be
switch here. one interface of 28 is connected to 25 and the other
interface
of 28 is connected to 12. as mentioned below, i've defined two vlan10
and
11 with the same vlan id on the 28 and bridge them.
now i can't ping 0.25 from 0.12. what's wrong here? should i define
vlan10
on 12 and 25?
please tell me if i'm misunderstanding.
this is the ifconfig for 0.28:
vlan10: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0
mtu 1500
options=3<RXCSUM,TXCSUM>
ether 00:27:0e:03:4b:2f
media: Ethernet autoselect (1000baseT<full-duplex>)
status: active
vlan: 10 parent interface: gbeth0
vlan11: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0
mtu 1500
options=100<TSO4>
ether 00:30:4f:63:5a:bc
media: Ethernet autoselect (none)
status: active
vlan: 10 parent interface: msk0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
ether d6:c4:f6:0f:5e:4f
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: vlan11 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 6 priority 128 path cost 55
member: vlan10 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 20000
On Sat, Dec 17, 2011 at 8:47 PM, Alireza Torabi
<alireza.tor...@gmail.com>wrote:
ŮŽAlso it's a good idea to to attach a ifconfig output.
On 12/17/11, saeedeh motlagh<saeedeh.motl...@gmail.com> wrote:
when i do that, the vlan is defined but from a system in a vlan, i
can't
ping the other one which is in the same vlan. so i think that the
vlan is
not working. am i right?
On Sat, Dec 17, 2011 at 1:15 PM, Juli Mallett<jmall...@freebsd.org>
wrote:
You probably just need to do ifconfig vlanxxx up instead of
assigning an
IP.
On Sat, Dec 17, 2011 at 00:08, saeedeh motlagh
<saeedeh.motl...@gmail.com> wrote:
hi every body
i wanna configure a freebsd box as a switch. in order to do that,
i
bridged
all my interfaces to have switching and it works fine. after that
i
want
to
have vlans on it. as you know, in a real switch, a vlan is
configured
just
by assigning a port to it without any additional configuration and
vlans
are submitted just by name. but in freebsd a vlan just works when
it
has
an
ip address (i think). when i define vlan121 on two freebsd systems
with
ip
address it works fine but without ip address i don't know how it
should
be
worked.
can sombody tell me if it is possible to simulate vlans in freebsd
as
they
are in a real switch? i mean can we have vlans without ip
addresses
which
works fine? maybe some kind of vlan which works by MAc address. is
it
possible?
it's so necessary for me to do that:(
yours,
motlagh
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
"
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org"
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
