I'm new to shorewall or any ip-config/network type configuration, so I applogize ahead for any misstakes in terms.
I've decsided that I will turn an old desktop of mine into a wireless router and torrent box. I installed shorewall and looked as the documentation and the sample two-interface configuration. The wireless card is a madwifi one (ath_pci) and I can connect to it and get an ip from it from dnsmasq. An ethernet port gets the internet. Now, when I wireless connect to my desktop router, I have complete access to the local network. I can ping the box and ssh into it. The box gets internet and can torrent (I made the suggested modifications from the guide). However when I try to ping anything, say google.com, I get rejected and lines like this in my log: > Shorewall:loc2fw:REJECT:IN=ath0 OUT= MAC=..... SRC=10.0.0.2 DST=10.0.0.1 .... So something is misconfigured because its looking in $FW for google. When I change the policy line from: > loc $FW REJECT info to > loc $FW ACCEPT Suddenly the machine can get google's ip, but it still can't ping it. I don't know what files would be important to post here, or what would be helpful, but I'm confused as to why its doing things this way. I'm using Arch Linux with Shorewall version 4.0.13. My configuration files are the two-interface ones with eth0 (net) becoming eth1 and eth1 (net) becoming ath0. -- - Simon Gomizelj ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
