Unusual source address issue with Apache on WinNT

telecomsman

Hi

Unusual problem that Ive been encountering.
Basically I have Apache 1.3 running as a proxy server on a Windows Server NT machine. This machine has two NICs ,say 192.168.10.1 and 192.168.10.2. I have Apache bound to one address ,192.168.10.1, to receive traffic. But for DNS queries and outgoing traffic, the proxy is using the other source address 192.168.10.2. This is causing issues as only 192.168.10.1 is configured on the Fw to send DNS and HTTP traffic. Anyone got any ideas?? Other than amend the ACL to include the other address (although this means involving another dept so Im hoping for a local work-around).Currently I have the other NIC switched off to allow the proxy to function correctly.

Cheers

WizZard

Which NIC has the default gateway setup?

Windows will use that to route all non-local traffic. If both have a DG set up then Windows becomes weird.

i71jskz5xu42pb

I assume you are using mod_proxy? There is a patch floating around to add a ProxySourceAddress directive to allow you specify. Does not sound like you're in an environment where patching Apache is an option though. There's also a patch that will just use the listen address as the source address (sounds like exactly what you are looking for).

All that said I think what you are trying to do should/could be done by the routing system in the OS. Moving routing into the Apache process just seems wrong to me. Have you though of accomplishing what you want to do using the route command?

telecomsman

PaschalNee wrote:

I assume you are using mod_proxy? There is a patch floating around to add a ProxySourceAddress directive to allow you specify. Does not sound like you're in an environment where patching Apache is an option though. There's also a patch that will just use the listen address as the source address (sounds like exactly what you are looking for).

All that said I think what you are trying to do should/could be done by the routing system in the OS. Moving routing into the Apache process just seems wrong to me. Have you though of accomplishing what you want to do using the route command?

To be honest, Im open to all suggestions....its only a small part of a trial network for a product we're developing. Im not familiar with the route command in WinNT, if its straightforward though I will give it a wee google.
Which do you reckon is the best way to resolve this...ie to make sure Apache uses a specific source address?

Which NIC has the default gateway setup?

I had configured both with the DG in their IP config, did this as I was using the Apache on one NIC and had another unrelated server bound to the other.

Capt'n Midnight

BTW
NT only uses the first default gateway listed - even though you can add several to each card.