06-18-2009
Problems with 2 NICS and Apache
I have a Solaris 10 box that has 2 Ethernet connections. One is 172.21.0.150, this is on the main internal LAN. The other is 172.16.0.50 this is the DMZ. I have Apache 2.0.59, I do not care which it Listens to but the main one for it is 172.16.0.50 (DMZ) which I have been explicit (Listen 172.16.0.50:80) and tried bind all (Listen *:80). When I have the system all setup everything works fine from the Internet going to
Server.com or external IP (which goes to DMZ 172.16.0.50). But it DOES NOT work when sitting on the 172.21.0.X network (LAN). This tells me that there is a problem in the firewall preventing network 21 getting to port 80 on the 16 network. But if I totally disable the interface that has 172.21.0.150, then everything works fine from the Internet AND from the 21 network going to
Server.com.
Any suggestions?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everyone. Okay here are a couple of my problems and hopefully you
guys can help me out.
Problem 1: i have 2 website that are being hosted on a webserver. The
webserver is running redhat 8x and running apache 1.3.20. To make it a
little clearer, lets say website A and website B. Both... (1 Reply)
Discussion started by: crazycelicagts
1 Replies
2. UNIX for Dummies Questions & Answers
I downloaded Apache 1.3.27.tar.gz into my SCO u/install directory.
However, to begin with, I couldn't untar the file using the " tar xvf apache-1.3.27.tar.gz" command, so I used winzip from a windows computer on our network. Winzip untarred the file and I transferred the files to the SCO... (2 Replies)
Discussion started by: cstovall
2 Replies
3. UNIX for Dummies Questions & Answers
I posted a problem with the forum on 11/18/02. Unfortunately, I
have been out of town. Today is the first chance I've had to try
the suggestions that were made.
Here is the output from the ls -l configure* command:
-rw-r--r-- 1root sys 58230 May 21 2002 configure
When I type " sh... (2 Replies)
Discussion started by: cstovall
2 Replies
4. Solaris
I have a Solaris 8 box and need to install Apache 2.0.55 on it. First thing I tried was compiling from source code. During the make phase, I got the following errors:
Then I tried downloading the binaries. I tried the one available from Apache's site and the one from sunfreeware.com, with... (3 Replies)
Discussion started by: GKnight
3 Replies
5. Solaris
I've been working on a project to replace one of the my group's primary NIS servers. It also runs mysql and apache, as it is the host for the our team's hardware tracking database and website. Its running apache 1.3, and for some odd reason, I can't get apache to start on system boot. The... (1 Reply)
Discussion started by: godspunk32
1 Replies
6. Solaris
Hi, is there a way in Solaris 8 to determine how many total NIC's say a Sun Sparc box has installed - plumbed or unplumbed - and find out its capable network speeds and MAC address?
I know ifconfig -a but that only shows the plumbed and used interfaces.
thx
cc (2 Replies)
Discussion started by: bigapple100
2 Replies
7. Web Development
When I upload a file 32M or larger to fails.
I can see the file being uploaded into the /tmp directory but when it gets to ~32M it dissapears.
This is from phpinfo:
upload_max_filesize 100M 100MB
post_max_size 100M 100MB
enable_dl On On
I dont get an error in the log saying im... (9 Replies)
Discussion started by: Ikon
9 Replies
8. Web Development
Hello guys
I have been running a LAMP stack for awhile now but have never really explored the server side end of things. What I am trying to do is have a python script on a website run a bash command. This will accomplish a system so someone can create an account for proxy access via a webpage.... (45 Replies)
Discussion started by: darkphaux
45 Replies
9. Web Development
Hi,
I just installed Apache 2.0.54 and when I try and start httpd I get
mohit@mohit-desktop:/sw/pkg/apache/bin$ ./httpd -k start
httpd: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
(13): make_sock: could not bind to address :80
no listening... (1 Reply)
Discussion started by: mojoman
1 Replies
10. Web Development
I am attempting to add virtual hosts to an apache web server, which has this current configuration:
<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot /var/www
<Directory />
Options FollowSymLinks
AllowOverride None
... (27 Replies)
Discussion started by: Corona688
27 Replies
LEARN ABOUT DEBIAN
ovs-vlan-test
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)