1 |
Grant <emailgrant@×××××.com> writes: |
2 |
|
3 |
>> > iptables -P INPUT DROP |
4 |
>> > iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT |
5 |
>> > iptables -A FORWARD -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT |
6 |
>> |
7 |
>> This line is only needed if you want to forward packets to another |
8 |
>> iface/device (i.e. when your laptop is acting as a router and the input |
9 |
>> interface is eth0). |
10 |
> |
11 |
> Alright I guess I'll just set up shorewall on the laptop with a config |
12 |
> similar to the router's. Maybe I'll set up shorewall on the other |
13 |
> system in my local network while I'm at it. |
14 |
|
15 |
Wait... I'm pretty sure there are a few lines of IPTABLES code that |
16 |
will do what you want. |
17 |
|
18 |
I remember using something with IPTABLES that made any connections |
19 |
from internet only happen in response to requests from your localhost. |
20 |
I don't remember the lines now but someone might post it. |
21 |
|
22 |
Wouldn't the above and not running any unnecessary services be pretty |
23 |
good protection for what your after? |
24 |
|
25 |
I've hooked up to many networks while traveling without anything at |
26 |
all (Except not running any unnecessary services) with windows based |
27 |
laptop and never had a bit of trouble. So I'd expect a linux based |
28 |
host to do even better. |
29 |
|
30 |
-- |
31 |
gentoo-user@g.o mailing list |