08-08-2003
multiple interfaces with apache?
I'm having some problems here, and was wondering whether it was an Apache problem. We have two firewalls where I'm at, Apache is installed on the second one. The first firewall is setup to forward all outside requests to port 80 on the second firewall. Apache is only working on the lan, not the internet. What I was wondering is whether Apache binds to the first network card by default, and if so, how to enable Apache to bind to the second interface as well. I've tried Virtual Hosts, to no avail. Apache 1.3.28 if that helps.
7 More Discussions You Might Find Interesting
1. IP Networking
I have a Unix box with 2 network interfaces on the same IP subnet and would like to add a host route via a specific interface. Any assistance would be greatly appreciated. (3 Replies)
Discussion started by: diemos
3 Replies
2. IP Networking
I have an OpenBSD 3.7 firewall with five network interfaces on it, one of which is connected to the Internet. I'd like to use the remaining four interfaces as a network switch for a single internal subnet. The main problem I have is that the DHCP daemon doesn't like multiple interfaces matching... (0 Replies)
Discussion started by: vertigo23
0 Replies
3. AIX
Is there a way to add routes using the add route command in AIX to add different routes and bind them to different NICS installed in the box? (2 Replies)
Discussion started by: Docboyeee
2 Replies
4. 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
5. Solaris
Hello,
I have a machine with Solaris 8, and it has multiple interfaces that are connected to the same network which means they all have metric 0 (1 hop) to the default gateway.
assume:
* e1000g0: 10.1.1.70
* e1000g2: 10.1.1.72
* e1000g4: 10.1.1.74
* e1000g5: 10.1.1.76
* gateway:... (11 Replies)
Discussion started by: aeg
11 Replies
6. AIX
Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket.
Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B.
Box B has two network interfaces, X and Y. Interface X has the... (4 Replies)
Discussion started by: RonBowater
4 Replies
7. 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
LEARN ABOUT OSX
apache::testrun
Apache::TestRun(3) User Contributed Perl Documentation Apache::TestRun(3)
NAME
Apache::TestRun - Run the test suite
SYNOPSIS
DESCRIPTION
The "Apache::TestRun" package controls the configuration and running of the test suite.
METHODS
Several methods are sub-classable, if the default behavior should be changed.
"bug_report"
The "bug_report()" method is executed when "t/TEST" was executed with the "-bugreport" option, and "make test" (or "t/TEST") fail. Normally
this is callback which you can use to tell the user how to deal with the problem, e.g. suggesting to read some document or email some
details to someone who can take care of it. By default nothing is executed.
The "-bugreport" option is needed so this feature won't become annoying to developers themselves. It's automatically added to the
"run_tests" target in Makefile. So if you repeateadly have to test your code, just don't use "make test" but run "t/TEST" directly. Here is
an example of a custom "t/TEST"
My::TestRun->new->run(@ARGV);
package My::TestRun;
use base 'Apache::TestRun';
sub bug_report {
my $self = shift;
print <<EOI;
+--------------------------------------------------------+
| Please file a bug report: http://perl.apache.org/bugs/ |
+--------------------------------------------------------+
EOI
}
"pre_configure"
The "pre_configure()" method is executed before the configuration for "Apache::Test" is generated. So if you need to adjust the setup
before httpd.conf and other files are autogenerated, this is the right place to do so.
For example if you don't want to inherit a LoadModule directive for mod_apreq.so but to make sure that the local version is used, you can
sub-class "Apache::TestRun" and override this method in t/TEST.PL:
package My::TestRun;
use base 'Apache::TestRun';
use Apache::TestConfig;
__PACKAGE__->new->run(@ARGV);
sub pre_configure {
my $self = shift;
# Don't load an installed mod_apreq
Apache::TestConfig::autoconfig_skip_module_add('mod_apreq.c');
$self->SUPER::pre_configure();
}
Notice that the extension is .c, and not .so.
Don't forget to run the super class' c<pre_configure()> method.
"new_test_config"
META: to be completed
perl v5.16.2 2011-02-07 Apache::TestRun(3)