www.zeroshell.org

[houkouonchi]

It looks like the netbalancer seems to over-ride what interface/IP the packets are showing as their source even when it is specifically set with the 'bind' option.

Here is an example:

[ppalias]

As you can see here the LOCAL PROCESS is before the routing decission, MANGLE OUTPUT, MANGLE POSTROUTING and NAT POSTROUTING, so the content of the packet can change easily before the packet starts its journey on the wires.
In order to achieve what you want, you can do it the same way you do it in your other linux box. Set mark of 0x66 (this is an example, see what are the marks available in "ip rule ls") to the application you want to send over a specific interface and the netbalancer will do the rest.

[houkouonchi]

Ok, so if I am understanding you correctly from this output (my two connections 67/65):

admin@zeroshell: 06:01 PM :~# ip rule ls
0: from all lookup local
32764: from all fwmark 0x67 lookup 103
32765: from all fwmark 0x65 lookup 101
32766: from all lookup main
32767: from all lookup default
admin@zeroshell: 06:01 PM :~#

I can just add rules like I have on my box for 101/103?

IE:

ip rule add from $LINE1_IP table 101
ip rule add from $LINE2_IP table 103

and I should be able to reliably bind a specific program to a specific IP?

If so I assume with dynamic IPs I would need to write a script that grabbed the IP of the interface. Where would the best place to put this script in Startup/Cron?

[ppalias]

I don't know if that will work. Maybe you should try the iptables to mark the packet, depending on the source IP.

[houkouonchi]

[houkouonchi]

And that did work, just how I wanted:

[houkouonchi]

This is what I added to 'Firewall Chain in:

Startup/Cron: