Tag Info

New answers tagged

0

so i have managed to get this working: First of all NAT is not required as suggested by Michael. Now to allow SIP at port 5060 I used following rules: iptables -D FORWARD -j delegate_forward; iptables -D FORWARD -j DROP iptables -I FORWARD -i eth0.120 -o eth0.200 -m state --state RELATED,ESTABLISHED -j ACCEPT; iptables -I FORWARD -i eth0.200 -o eth0.120 ...


0

Well, given that you told us: Because I'm not able to easily force the process in question to bind to a specific interface, I am trying to achieve the same outcome via routing. Is this possible? we can start helping you from this very point. Once upon a time in FreeBSD jail system call appeared with the purpose to restrict a process, or group of ...


0

Sadly the iptables extensions manpage (http://ipset.netfilter.org/iptables-extensions.man.html) states no module to fullfill your requirements. I would suggest the same as Mauricio López. You could setuid or setgid the target application to a specific user or group, so that no matter who originally started the application, it will always run as a specific ...


1

Your routing the packets through either eth1 or eth0. tables mangle should address this. To do so, I had to mark packets and set up rules for handling it. First, add a rule that make the kernel route packets marked with 2 through table ip rule add fwmark 2 table 3 Add a route for redirecting traffic over a different interface, assuming the gateway being ...



Top 50 recent answers are included