dsw has it right. You can see the VLANs of virtual network adapters even if they are inside an etherchannel. My ent0 is on VLAN 10 and my ent1 is on VLAN 20. Here is an example from one of my boxes.
hi,
i tried to configure an VLAN interface on my SF280 based on the documentation on docs.sun.com
# ifconfig eri1000 plumb up
Oct 21 13:41:26 cmsmaster ip: ip_rput_dlpi(eri1000): DL_ERROR_ACK for DL_ATTACH_REQ(11), errno 8, unix 0
ifconfig: SIOCSLIFNAME for ip: eri1000: no such interface... (2 Replies)
Hi all,
so server: FreeBSD 7.0 release,
interfaces on it DLINK DGE-528T with support of vlans :))
so first interface looks to LAN second to ISP.
I created vlan1 with id 1 and gave to it ip address and plug it in
tagged port of swith for vlan 1. so client from vlan1 reaches the server.
it... (2 Replies)
Hi all
My application is a monitoring application that monitors the incoming udp packet when ever required. When ever a particular source ip and port and dest ip and port is provided the filter will be framed based them. For eg,
char filterExpr;
filterExpr = "udp and src host 192.168.16.100... (0 Replies)
Hello. I want to Communicate 2 VLAN with router like this solution:
http://8pic.ir/images/83m0ouih8mmm9s1sfl56.jpg
For this purpose I'm configuring 2 Linux system as a switch and connect 4 host to them. Then a router is added to scenario.
The configuration of the switches is:
On DUT1(Linux):... (1 Reply)
Hi,
Is it possible to VLAN tag with a ce interface on Solaris 9? Link speed is gb.
ce:0:ce0:link_speed 1000
I have a ce0 interface I would need to have access to another VLAN as well as the one it's currently on.
What commands would I need to run?
Thanks.;) (2 Replies)
We have two hosts in same vlan with same route rules.
One of them is not able to connect to an outside IP while in another I get "failed: Connection timed out" while testing the connectivity through netcat.
I have tried mtr /traceroute and it gives me the same results.
Is there a netcat... (1 Reply)
Have 2 nics on physical system
net0 phys 1500 up --
net1 phys 1500 up --
1. I want to create a link aggregation with LACP enabled with above 2 nics
2. Create port-group(Like we create on ESXi) with VLAN-ID 2141
3. And assign this... (0 Replies)
Hi Guys,
Our lpars is currently running on 2 different vlans (20, 30). Now we have a requirement that vlan 30 needs to be change to vlan 31 at the same subnet. I'm not sure on what is the best approach for this or what change is involve on the AIX side.
This is our setup.
Network switch -... (5 Replies)
Hi Folks,
I am currently moving systems to a new environment, with some changes to the network requirements on the systems.
One of these changes is moving from just standard IPMP to using IPMP on top of a VLAN, I have used VLAN tagging befor without issue - however not with IPMP.
What I... (2 Replies)
Discussion started by: gull04
2 Replies
LEARN ABOUT DEBIAN
if_vlan
VLAN(4) BSD Kernel Interfaces Manual VLAN(4)NAME
vlan -- IEEE 802.1Q VLAN network interface
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device vlan
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_vlan_load="YES"
DESCRIPTION
The vlan driver demultiplexes frames tagged according to the IEEE 802.1Q standard into logical vlan network interfaces, which allows rout-
ing/bridging between multiple VLANs through a single switch trunk port.
Each vlan interface is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or using the
cloned_interfaces variable in rc.conf(5).
To function, a vlan interface must be assigned a parent interface and numeric VLAN tag using ifconfig(8). A single parent can be assigned to
multiple vlan interfaces provided they have different tags. The parent interface is likely to be an Ethernet card connected to a properly
configured switch port. The VLAN tag should match one of those set up in the switched network.
Initially vlan assumes the same minimum length for tagged and untagged frames. This mode is selected by the sysctl(8) variable
net.link.vlan.soft_pad set to 0 (default). However, there are network devices that fail to adjust frame length, should it fall below the
allowed minimum due to untagging. Such devices should be able to interoperate with vlan after changing the value of net.link.vlan.soft_pad
to 1. In the latter mode, vlan will pad short frames before tagging them so that their length stays not less than the minimum value after
untagging by the non-compliant devices.
HARDWARE
The vlan driver supports efficient operation over parent interfaces that can provide help in processing VLANs. Such interfaces are automati-
cally recognized by their capabilities. Depending on the level of sophistication found in a physical interface, it may do full VLAN process-
ing or just be able to receive and transmit long frames (up to 1522 bytes including an Ethernet header and FCS). The capabilities may be
user-controlled by the respective parameters to ifconfig(8), vlanhwtag and vlanmtu. However, a physical interface is not obliged to react to
them: It may have either capability enabled permanently without a way to turn it off. The whole issue is very specific to a particular
device and its driver.
By now, the list of physical interfaces able of full VLAN processing in the hardware is limited to the following devices: ae(4), age(4),
alc(4), ale(4), bce(4), bge(4), cxgb(4), em(4), ixgb(4), jme(4), msk(4), nge(4), re(4), sge(4), stge(4), ti(4), txp(4), and vge(4).
The rest of the Ethernet interfaces can run VLANs using software emulation in the vlan driver. However, some of them lack the capability of
transmitting and receiving long frames. Assigning such an interface as the parent to vlan will result in a reduced MTU on the corresponding
vlan interfaces. In the modern Internet, this is likely to cause tcp(4) connectivity problems due to massive, inadequate icmp(4) filtering
that breaks the Path MTU Discovery mechanism.
The following interfaces support long frames for vlan natively: bfe(4), cas(4), dc(4), fwe(4), fxp(4), gem(4), hme(4), le(4), nfe(4), nve(4),
rl(4), sf(4), sis(4), sk(4), ste(4), tl(4), tx(4), vr(4), and xl(4).
The vlan driver automatically recognizes devices that natively support long frames for vlan use and calculates the appropriate frame MTU
based on the capabilities of the parent interface. Some other interfaces not listed above may handle long frames, but they do not advertise
this ability of theirs. The MTU setting on vlan can be corrected manually if used in conjunction with such a parent interface.
SEE ALSO ifconfig(8), sysctl(8)BUGS
No 802.1Q features except VLAN tagging are implemented.
BSD April 14, 2010 BSD