10 More Discussions You Might Find Interesting
1. IP Networking
I am having problems configuring bridged networking on Proxmox3.2/Debian7.0
I have 2 bridges - vmbr0 and vmbr1. I want to attach a gateway/firewall running in a virtual machine between the 2 and use it to connect out to the WAN through vmbr0.
I have removed the IP, mask and gateway from... (0 Replies)
Discussion started by: OSSVirt
0 Replies
2. UNIX for Dummies Questions & Answers
(3 Replies)
Discussion started by: samnyc
3 Replies
3. Ubuntu
Hi,
I need to override ioctl operation for a few USB drivers (sierra, option, cdc-acm) on Linux Ubuntu 2.6.34sb2 to support TIOCOUTQ command.
Unfortunately, none of the drivers I mentioned above support TIOCOUTQ because it seems unclear to know amount of data inside a modem.
Does Linux... (12 Replies)
Discussion started by: SDoroshenko
12 Replies
4. Linux
I encountered a variety of difficulties when implementing a system call as simple as HelloWorld example in Linux so far.
Firstly, according to the book "Linux Kernel Development Second Edition", I tried to implement a syscall in 2.6.31 but no way absolutely because 2.6.10 has a very different way... (5 Replies)
Discussion started by: sunnyhay
5 Replies
5. IP Networking
Dear all,
I have a Allied Telesyn AT-GS950 16 port switch.
All hosts&router have rtl8139 NICs.
OS : Slackware linux 12.1.
I use a switch with vlan technique to separate my network to some segment.
here my plan:
router eth0 ---> switch port 1
switch port 5 <--- eth0 host A
switch... (1 Reply)
Discussion started by: penyu
1 Replies
6. Linux
Hello All,
I know it's a tricky probably stupid question but I'm stuck.... :(
Is there any way to route different protocols through different eth cards for the same destination in Linux? With route add or something like it?
For instance:
FTP to/from 192.168.1.1 goes through eth0 - gw2... (1 Reply)
Discussion started by: pmpx
1 Replies
7. Linux
how i add new routes to my linux machine (1 Reply)
Discussion started by: youmna
1 Replies
8. Red Hat
I have just recently got into using Linux RedHat 9. So far I love it, I have set it up on a server I am running. Right now I have set up Samba and am running a file server for my house. I have four computers, the linux box is connected to the internet through a switch I have. There are two NICS in... (1 Reply)
Discussion started by: xTHESEUSx
1 Replies
9. Red Hat
:mad: I have just recently got into using Linux RedHat 9. So far I love it, I have set it up on a server I am running. Right now I have set up Samba and am running a file server for my house. I have four computers, the linux box is connected to the internet through a switch I have. There are two... (5 Replies)
Discussion started by: xTHESEUSx
5 Replies
10. Linux
How to use NAT Router in linux Redhat 6 ? and what
packages and configuration are required ? (1 Reply)
Discussion started by: salhoub
1 Replies
ovs-vlan-test(1) Open vSwitch Manual ovs-vlan-test(1)
NAME
ovs-vlan-test - check Linux drivers for problems with vlan traffic
SYNOPSIS
ovs-vlan-test [-s | --server] control_ip vlan_ip
Common options:
[-h | --help] [-V | --version]
DESCRIPTION
The ovs-vlan-test utility has some limitations, for example, it does not use TCP in its tests. Also it does not take into account MTU to
detect potential edge cases. To overcome those limitations a new tool was developed - ovs-test. ovs-test is currently supported only on
Debian so, if possible try to use that on instead of ovs-vlan-test.
The ovs-vlan-test program may be used to check for problems sending 802.1Q traffic which may occur when running Open vSwitch. These prob-
lems can occur when Open vSwitch is used to send 802.1Q traffic through physical interfaces running certain drivers of certain Linux kernel
versions. To run a test, configure Open vSwitch to tag traffic originating from vlan_ip and forward it out the target interface. Then run
the ovs-vlan-test in client mode connecting to an ovs-vlan-test server. ovs-vlan-test will display "OK" if it did not detect problems.
Some examples of the types of problems that may be encountered are:
o When NICs use VLAN stripping on receive they must pass a pointer to a vlan_group when reporting the stripped tag to the networking
core. If no vlan_group is in use then some drivers just drop the extracted tag. Drivers are supposed to only enable stripping if a
vlan_group is registered but not all of them do that.
o On receive, some drivers handle priority tagged packets specially and don't pass the tag onto the network stack at all, so Open
vSwitch never has a chance to see it.
o Some drivers size their receive buffers based on whether a vlan_group is enabled, meaning that a maximum size packet with a VLAN tag
will not fit if no vlan_group is configured.
o On transmit, some drivers expect that VLAN acceleration will be used if it is available, which can only be done if a vlan_group is
configured. In these cases, the driver may fail to parse the packet and correctly setup checksum offloading or TSO.
Client Mode
An ovs-vlan-test client may be run on a host to check for VLAN connectivity problems. The client must be able to establish HTTP connec-
tions with an ovs-vlan-test server located at the specified control_ip address. UDP traffic sourced at vlan_ip should be tagged and
directed out the interface whose connectivity is being tested.
Server Mode
To conduct tests, an ovs-vlan-test server must be running on a host known not to have VLAN connectivity problems. The server must have a
control_ip on a non-VLAN network which clients can establish connectivity with. It must also have a vlan_ip address on a VLAN network
which clients will use to test their VLAN connectivity. Multiple clients may test against a single ovs-vlan-test server concurrently.
OPTIONS
-s, --server
Run in server mode.
-h, --help
Prints a brief help message to the console.
-V, --version
Prints version information to the console.
EXAMPLES
Display the Linux kernel version and driver of eth1.
uname -r
ethtool -i eth1
Set up a bridge which forwards traffic originating from 1.2.3.4 out eth1 with VLAN tag 10.
ovs-vsctl -- add-br vlan-br
-- add-port vlan-br eth1
-- add-port vlan-br vlan-br-tag tag=10
-- set Interface vlan-br-tag type=internal
ifconfig vlan-br-tag up 1.2.3.4
Run an ovs-vlan-test server listening for client control traffic on 172.16.0.142 port 8080 and VLAN traffic on the default port of 1.2.3.3.
ovs-vlan-test -s 172.16.0.142:8080 1.2.3.3
Run an ovs-vlan-test client with a control server located at 172.16.0.142 port 8080 and a local VLAN ip of 1.2.3.4.
ovs-vlan-test 172.16.0.142:8080 1.2.3.4
SEE ALSO
ovs-vswitchd(8), ovs-ofctl(8), ovs-vsctl(8), ovs-test(8), ethtool(8), uname(1)
Open vSwitch December 2010 ovs-vlan-test(1)