linksys wrt54gl, tomato firmware, iptables problem denying access from ip2ip
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
linksys wrt54gl, tomato firmware, iptables problem denying access from ip2ip
Hello all,
I have rather silly problem here. I have successfully flashed my brand new linksys wrt54gl router with the latest tomato firmware.
Now I need to make ips 192.168.1.2-192.168.1.99 to NOT have access to ips 192.168.1.100-192.168.1.199 on my local network. I know it's something with the FORWARD chain in the iptables rules, but I do not have the knowledge of iptables to make it yet.
Can someone help me out?
Something like that maybe?:
iptables -A FORWARD -s 192.168.1.2-192.168.1.99 -d 192.168.1.100-192.168.1.199 -j DROP
Acctualy, I'm not sure if that will work on a WRT54G. I think that the 4 ethernet ports are actually on an internal switch. If that is the case then you will not be able to filter port to port packets as the traffic will not go through netfilter/iptables.
The switch may get confused if you try software bridge the VLAN, it depends on if it has separate forwarding tables for each VLAN. That will also be slow.
WRT54Gs typically run Linux 2.4 due to the historic lack of an open source wifi driver, bridge netfilter support was introduced later. I believe the wifi driver bridges packet internally, so that would be another problem.
You should however be able to use it as a routing firewall.
Edit:Software bridging does in fact work on my WRT54GS v4, and wire to wire bridging firewall works, wireless to wireless fire-walling doesn't work in dd-wrt.
Last edited by TimothyEBaldwin; 04-27-2010 at 06:16 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.