I'm not sure if this is the best solution,
but it works for me in brief testing (on Ubuntu 7.10).
Here is my test configuration:
eth0 - 10.1.151.108
eth0:0 - 10.1.151.109
I'm using wireshark to capture network
Before adding any iptables rules, a
ping to 10.1.100.132 shows traffic coming from 10.1.151.108.
After adding the following rule, pinging
10.1.100.132 reveals traffic coming from 10.1.151.109.
# iptables -A OUTPUT --destination 10.1.100.132
Using iptables, you should be able to
achieve what you're looking for.
Hope this helps,
Academy Sports & Outdoors
Systems Engineer - Linux & Windows
12/12/2007 08:53 AM
Re: [Pound Mailing List] Pound use real
IP instead of virtual IP to call with backends server
Unfortunately I have no choice. In fact, I must use
the virtual IP address to
avoid duplication of rules in my firewall and of course securities flaw.
I try to telnet BackendIPServer port_xx but of course, telnet use the address
eth0 (the real) and not the address on eth0:0 (the virtual)
But, there is an option with telnet to use specific address :
telnet -b VirtualIP BackendIP BackendPort who works fine.
So, I imagine it's possible to configure OS to do that but how ????
I works on Ubuntu 7.10 server Edition and pound 2.xxx,
I don't exactly remember
To unsubscribe send an email with subject unsubscribe to firstname.lastname@example.org.
Please contact email@example.com for questions.