01-30-2020
Virtual Interfaces on Linux
Hi,
I have RH Linux system on which we have a 10Gb nic card that we want to configure multiple Virtual interfaces that are all tagged on the switch side.
Here is what I am trying to do, I want to have clients from different vlans that are truncked to be able to communicate with my RHEL server on just one interface.
1 Physical NIC -> Virtual interface 1 ( with vlan 1 )
-> Virtual interface 1 ( with vlan 2 )
-> Virtual interface 1 ( with vlan 3 )
-> Virtual interface 1 ( with vlan 4 )
10 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
. (0 Replies)
Discussion started by: Driver
0 Replies
2. Linux
This is actually my second attempt at installing Linuix on my mechine. Instead of wiping my HD (big mistake), I thought I would give the LiveCD option a try.
I was able to boot Virtual Linux under option 2 (the "happy" mode that doesn't freeze while loading) normally... until I got to the login... (2 Replies)
Discussion started by: invot
2 Replies
3. Red Hat
Hi everyone,
Can you please tell me the procedure to configure Virtual ip (CARP) mechanism into the Redhat Linux?
Thanks in advanced.
Regards,
Jagdish Machhi (1 Reply)
Discussion started by: jagdish.machhi@
1 Replies
4. High Performance Computing
Hi Guys,
I'm busy building a LVS-NAT cluster on Red-Hat server 5.1 and I need a kernel that has LVS capabilities for a red-hat server 5.1. Is the anyone who can advise me where I can get this kernel. I have already visited the following site Ultra Monkey: and this has old kernels e.g. 2.4.20... (2 Replies)
Discussion started by: Linux Duke
2 Replies
5. Solaris
Hello All,
I have a requirement to add multiple virtual interfaces on a non-global zone (Solaris 10). The global zone is a 2 node Veritas Cluster Server. So, my question is do we have to make any modifications to the cluster config (which I think should not be the case)? Can anyone help with me... (11 Replies)
Discussion started by: mahive
11 Replies
6. Linux
My setup consists of a hardware node, which hosts several virtual machines (OpenVZ, to be precise). The hardware node has two network interfaces (<ifA>, <ifB>) connected to different subnets (<networkA>, <networkB>). I want to route the traffic of certain VEs over <ifB> while routing the other VEs... (0 Replies)
Discussion started by: bakunin
0 Replies
7. UNIX for Dummies Questions & Answers
After installing PV (Para virtual drivers) drivers I m not able to check the network speed of my Ethernet port.
Please check the output of mii-tool and ethtool.
# mii-tool eth0
SIOCGMIIPHY on 'eth0' failed: Operation not supported
# ethtool eth0
Settings for eth0:
Link... (2 Replies)
Discussion started by: pinga123
2 Replies
8. UNIX for Advanced & Expert Users
Hello,
I am trying to understand the VIRT field that shows in the TOP command output. I have a users application that appears to be leaking memory. I see that the field VIRT in the top output is showing 55.8g.
The question is where is that getting stored? The disk does not appear to have... (7 Replies)
Discussion started by: jaysunn
7 Replies
9. Solaris
Hi Al,
In course of understanding networking in Solaris, I have these doubts on Interfaces. Please clarify me. I have done fair research in this site and others but could not be clarified.
1. In the "ifconfig -a" command, I see many interfaces and their configurations. But I see many... (1 Reply)
Discussion started by: satish51392111
1 Replies
10. UNIX for Dummies Questions & Answers
So after getting a Nagios plugin up and running that checks certain things including network interfaces, I get an error off the one box I built (as opposed to all of the others that were built by a former employee). The error complains of the "NIC logical group" failing.
All the boxes are HP... (7 Replies)
Discussion started by: xdawg
7 Replies
LEARN ABOUT FREEBSD
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 line 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.
vlan initially assumes the same minimum length for tagged and untagged frames. This mode is selected by setting the sysctl(8) variable
net.link.vlan.soft_pad to 0 (default). However, there are network devices that fail to adjust frame length when it falls 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 is 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.
At present, these devices are capable of full VLAN processing in hardware: ae(4), age(4), alc(4), ale(4), bce(4), bge(4), bxe(4), cxgb(4),
cxgbe(4), em(4), igb(4), ixgb(4), ixgbe(4), jme(4), msk(4), mxge(4), nxge(4), nge(4), re(4), sge(4), stge(4), ti(4), txp(4), and vge(4).
Other Ethernet interfaces can run VLANs using software emulation in the vlan driver. However, some 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.
These interfaces natively support long frames for vlan: axe(4), bfe(4), cas(4), dc(4), et(4), fwe(4), fxp(4), gem(4), hme(4), le(4), nfe(4),
rl(4), sf(4), sis(4), sk(4), ste(4), tl(4), tx(4), vr(4), vte(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. 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
June 4, 2012 BSD