Enable ethernet bridging through your firewall using iptables or sysctl.conf

Posted in hmmm , security

Avoid the iptables firewall rules or edit sysctl.conf?

Which is better? Which is faster? For a desktop system, I don’t think it really matters if you have to process a bunch of rules. How many can there be, and how much network traffic are you seeing anyway? It’s probably more efficient to modify your sysctl.conf, but it seems more organized to do it all with iptables.

dewey-bridge-fire-2008

The sysctl.conf method

Add these lines to sysctl.conf

net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0

# sysctl -p /etc/sysctl.conf

net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0

The iptables method

# iptables -I FORWARD -m physdev –physdev-is-bridged -j ACCEPT
# /etc/init.d/iptables save

iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]

Posted by admica   @   23 November 2009

Related Posts

0 Comments

No comments yet. Be the first to leave a comment !
Leave a Comment

Name

Email

Website

Previous Post
« Modern Warfare 2 aim bots and wall hacks
Next Post
Batch add users to the cc list for all components in the bugzilla database directly »
Powered by Wordpress   |   Lunated designed by ZenVerse