Sponsored Content
Special Forums IP Networking Routing Network Traffic With Mandrake Post 8669 by Deuce on Tuesday 16th of October 2001 11:09:24 AM
Old 10-16-2001
Routing Network Traffic With Mandrake

I am running Mandrake 8.0 (KDE ver 2.1.1) on a machine with 2 NICs. This is a college project. I am attempting to configure this machine as a firewall, and to pass packets from one network to another. Eth0 is on my external network. Eth1 is on my internal network. I set the gateway in "netconf" to our school's router. My Eth0 is configured for the school's network (DHCP) and I can surf the internet with no problem.
Workstations on the internal network can ping both cards on my Mandrake machine, but CAN NOT go past ETH0!! I have downloaded several tutorials on ipchains and ip masquerading but none seem to be helping.

Please help!!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

routing - mandrake

I added a route entry with the route command. When I restart the network, this entry is gone. Therefore I wanted to edit the routing table by hand, but I didn't found a file to edit. Where is it? I'm using Mandrake 8.1. Thanks in advance. (2 Replies)
Discussion started by: sTorm
2 Replies

2. Cybersecurity

How to capture network traffic

Hi, Can someone give me the clue on how to capture network traffic at gateway. Thanx (2 Replies)
Discussion started by: kayode
2 Replies

3. Infrastructure Monitoring

Network Traffic

Hi all, Got a strange one here, well not so much strange, different :-) I need to work out if a server is particulary chatty, whether its talking / communicating heavily to a particular server, as Im planning to physically move the server to a different server, over a link. Hence the... (6 Replies)
Discussion started by: sbk1972
6 Replies

4. HP-UX

Monitoring traffic in the network

I Colleagues, Somebody can say me how to monitoring traffic in the network. also I am interested in monitoring memory. if somebody to know a guide with command advanced in unix welcome for me. Thank you for adcanced. (0 Replies)
Discussion started by: systemoper
0 Replies

5. IP Networking

Routing traffic problem between 3G and Office Lan Network

Hi, I would like to ask some networking solution regarding my work LAN and 3G usb network problem. I want to route my internet traffic to the 3G network and sometimes connect to some of my work network for ssh to configure some workstation or print something. Currently my problem is i can't... (0 Replies)
Discussion started by: jao_madn
0 Replies

6. Solaris

Traffic routing through wrong interface

Solaris-9 server is having one primary IP 10.41.161.14 on qfe0 and 10.41.116.0 on qfe3:1. Traffic is going through virtual interface instead of physical interface. How should I force traffic to go with primary interface. root@smtsrvn01:/# netstat -nr Routing Table: IPv4 Destination ... (2 Replies)
Discussion started by: solaris_1977
2 Replies

7. Infrastructure Monitoring

How do I know what traffic is in network port?

If I would like to know what connection , data , traffic in a network port ( eth0 ) , what can I do ? ps. because I always found the network is very slow , so I would like what the network port is doing . Thanks Login ID ust3 is currently in read-only mode for multiple infractions. Creating... (0 Replies)
Discussion started by: ust03
0 Replies

8. UNIX for Advanced & Expert Users

How to throttle network traffic?

Hi All I am resilience testing an application that is spread across multiple servers. One thing I will need to do soon is throttle the network traffic for specific interfaces within the test cluster. Specifically, maybe make a connection take twice or three times as long to respond.... I... (3 Replies)
Discussion started by: bbq
3 Replies

9. Proxy Server

ISP VPS, routing traffic

Hi guys I need to setup server/router in my firm. We got from our ISP dedicated server in their data center. It has a static IP and it servers as replacement for out DSL connection. I configured our internal server to be border gateway and to connects to data center. "Remote" admin installed... (0 Replies)
Discussion started by: solaris_user
0 Replies

10. IP Networking

I would like to monitor network traffic for a computer on my network

My son does homework on a school laptop. I was thinking about setting up a gateway on my home network, so that I can monitor web traffic and know if he is doing his homework without standing over his shoulder. Ideally I would like to use the Raspberry Pi Model b that I already have. However, I... (15 Replies)
Discussion started by: gandolf989
15 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)
All times are GMT -4. The time now is 02:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy