Sponsored Content
Full Discussion: Virtual Interfaces on Linux
Top Forums UNIX for Beginners Questions & Answers Virtual Interfaces on Linux Post 303043528 by new2prog on Thursday 30th of January 2020 02:41:50 PM
Old 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

Linux Virtual Memory Book

. (0 Replies)
Discussion started by: Driver
0 Replies

2. Linux

Virtual Linux Install Problem

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

Virtual ip or CARP configure in Redhat Linux

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

Building a Linux Virtual Server cluster

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

Adding multiple virtual interfaces on a non global zone.

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

Routing via several interfaces for hosted virtual machines

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

how to see network speed of virtual linux machine?

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

Linux Virtual Memory Question

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

Interfaces and Virtual-interfaces queries

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

Virtual etc interfaces??

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
IP-LINK(8)							       Linux								IP-LINK(8)

NAME
ip-link - network device configuration SYNOPSIS
ip [ OPTIONS ] link { COMMAND | help } OPTIONS := { -V[ersion] | -s[tatistics] | -r[esolve] | -f[amily] { inet | inet6 | ipx | dnet | link } | -o[neline] } ip link add [ link DEVICE ] [ name ] NAME [ txqueuelen PACKETS ] [ address LLADDR ] [ broadcast LLADDR ] [ mtu MTU ] type TYPE [ ARGS ] TYPE := [ vlan | veth | vcan | dummy | ifb | macvlan | can | bridge ] ip link delete DEVICE type TYPE [ ARGS ] ip link set { DEVICE | group GROUP } { up | down | arp { on | off } | promisc { on | off } | allmulticast { on | off } | dynamic { on | off } | multicast { on | off } | txqueuelen PACKETS | name NEWNAME | address LLADDR | broadcast LLADDR | mtu MTU | netns PID | netns NETNSNAME | alias NAME | vf NUM [ mac LLADDR ] [ vlan VLANID [ qos VLAN-QOS ] ] [ rate TXRATE ] [ spoofchk { on | off } ] | master DEVICE nomaster } ip link show [ DEVICE | group GROUP ] DESCRIPTION
ip link add - add virtual link link DEVICE specifies the physical device to act operate on. NAME specifies the name of the new virtual device. TYPE specifies the type of the new device. Link types: vlan - 802.1q tagged virtual LAN interface veth - Virtual ethernet interface vcan - Virtual Local CAN interface dummy - Dummy network interface ifb - Intermediate Functional Block device macvlan - virtual interface base on link layer address (MAC) can - Controller Area Network interface bridge - Ethernet Bridge device ip link delete - delete virtual link DEVICE specifies the virtual device to act operate on. TYPE specifies the type of the device. dev DEVICE specifies the physical device to act operate on. ip link set - change device attributes dev DEVICE DEVICE specifies network device to operate on. When configuring SR-IOV Virtual Fuction (VF) devices, this keyword should specify the associated Physical Function (PF) device. group GROUP GROUP has a dual role: If both group and dev are present, then move the device to the specified group. If only a group is speci- fied, then the command operates on all devices in that group. up and down change the state of the device to UP or DOWN. arp on or arp off change the NOARP flag on the device. multicast on or multicast off change the MULTICAST flag on the device. dynamic on or dynamic off change the DYNAMIC flag on the device. name NAME change the name of the device. This operation is not recommended if the device is running or has some addresses already configured. txqueuelen NUMBER txqlen NUMBER change the transmit queue length of the device. mtu NUMBER change the MTU of the device. address LLADDRESS change the station address of the interface. broadcast LLADDRESS brd LLADDRESS peer LLADDRESS change the link layer broadcast address or the peer address when the interface is POINTOPOINT. netns PID move the device to the network namespace associated with the process PID. netns NETNSNAME move the device to the network namespace associated with name NETNSNAME. alias NAME give the device a symbolic name for easy reference. group GROUP specify the group the device belongs to. The available groups are listed in file /etc/iproute2/group. vf NUM specify a Virtual Function device to be configured. The associated PF device must be specified using the dev parameter. mac LLADDRESS - change the station address for the specified VF. The vf parameter must be specified. vlan VLANID - change the assigned VLAN for the specified VF. When specified, all traffic sent from the VF will be tagged with the specified VLAN ID. Incoming traffic will be filtered for the specified VLAN ID, and will have all VLAN tags stripped before being passed to the VF. Setting this parameter to 0 disables VLAN tagging and filtering. The vf parameter must be specified. qos VLAN-QOS - assign VLAN QOS (priority) bits for the VLAN tag. When specified, all VLAN tags transmitted by the VF will include the specified priority bits in the VLAN tag. If not specified, the value is assumed to be 0. Both the vf and vlan parameters must be specified. Setting both vlan and qos as 0 disables VLAN tagging and filtering for the VF. rate TXRATE - change the allowed transmit bandwidth, in Mbps, for the specified VF. Setting this parameter to 0 disables rate limiting. The vf parameter must be specified. spoofchk on|off - turn packet spoof checking on or off for the specified VF. master DEVICE set master device of the device (enslave device). nomaster unset master device of the device (release device). Warning: If multiple parameter changes are requested, ip aborts immediately after any of the changes have failed. This is the only case when ip can move the system to an unpredictable state. The solution is to avoid changing several parameters with one ip link set call. ip link show - display device attributes dev NAME (default) NAME specifies the network device to show. If this argument is omitted all devices in the default group are listed. group GROUP GROUP specifies what group of devices to show. up only display running interfaces. EXAMPLES
ip link show Shows the state of all network interfaces on the system. ip link set dev ppp0 mtu 1400 Change the MTU the ppp0 device. ip link add link eth0 name eth0.10 type vlan id 10 Creates a new vlan device eth0.10 on device eth0. ip link delete dev eth0.10 Removes vlan device. SEE ALSO
ip(8) AUTHOR
Original Manpage by Michail Litvak <mci@owl.openwall.com> iproute2 20 Dec 2011 IP-LINK(8)
All times are GMT -4. The time now is 03:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy