[image: untitled.bmp]
thank you guys,
the above picture is my network topology. as you see, i have four end point
systems in the same range ip. three of them (c1, c3, c4) are the member of
vlan1 and the other one (c2) is the member of vlan2. these three systems
should ping each other and should not
On Sat, Dec 31, 2011 at 03:26, saeedeh motlagh
wrote:
> thank you guys for your answers but my problem is not solved yet:((
>
> the thing is, i wanna have something like this:
> a freebsd box which acts like switch (for example cisco 2960). i want to
> define vlanX on one interface (without any ip
This has worked for me in the past. Have you disabled all the hardware
vlan and ip offload options on those interfaces?
You should be able to use tcpdump on the parent interfaces to see if
the tagged packets are going in/out.
Adrian
___
freebsd-net@fre
thank you guys for your answers but my problem is not solved yet:((
the thing is, i wanna have something like this:
a freebsd box which acts like switch (for example cisco 2960). i want to
define vlanX on one interface (without any ip address) and it tags any
passing packets through that interface
hi Nikos
yes i read it and thank you so much but my problem is not solved yet :(.
would you please tell me step by step how should i do to have a vlan
freebsd switch?
we have four freebsd system as end nodes and one freebsd system as a
switch. two of four systems should be the member of vlan10 an
Yes, it is.
on "freebsd 0 aka switch":
ifconfig bridge0 create
ifconfig em0.10 create #em0 port is patched to the "real" switch to a
trunk port configured to accept at least vlan 10
ifconfig em1 #this port is patched to "freebsd 1"
ifconfig em2 #this port is patched to "freebsd 2"
ifconfig brid
On Tue, Dec 20, 2011 at 22:38, saeedeh motlagh
wrote:
> thankyou every body for your attention. yes bridging is done without ip
> address. i try to use all the point which is mentioned here but my problem
> is not solved yet.
> you know i have three freebsd box. i wanna to config the intermediate
thankyou every body for your attention. yes bridging is done without ip
address. i try to use all the point which is mentioned here but my problem
is not solved yet.
you know i have three freebsd box. i wanna to config the intermediate one
as switch and two others as vlan member. i want to have jus
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:
freebsd
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 con
On Dec 19, 2011, at 12:52 AM, saeedeh motlagh 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 cre
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 metric 0 mtu 1500
options
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.
--
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 fro
What is your network topology from the system you start ping to the
system which you're pinging?
--
your sweet isn't ready yet
On Sat, Dec 17, 2011 at 2:01 PM, saeedeh motlagh
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
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 wrote:
> You probably just need to do ifconfig vlanxxx up instead of assigning
16 matches
Mail list logo
