routes are killing me - how to?

[Stefan Jeglinski]

>  > So, my understanding is weak. I thought I first had to get the
>>  routing table configured to pass packets from the private network
>>  through the Linux box to the outside world, then set up iptables as
>>  an add-on. IOW, since I first want to pass all traffic (get it
>>  working), I thought I didn't need iptables as a first step. You're
>>  saying there's an interrelationship that is unavoidable, eh?
>>
>
>Well I wouldn't go so far as to say unavoidable - as Robert pointed out, all
>you *really* need to do is to enable IP forwarding...

I tried his suggestion, and just posted back that it did not appear to work.

>   however, IMO you're
>simply nuts if you don't provide some level of firewalling for your internal
>hosts... so, I guess you could say they really go hand in hand - one
>compliments the other.  Just a matter of your point of view.

Oh I quite agree. Firewall is the next step. I thought I would be 
well on to that by now, but I got stuck trying to get the simplest of 
operations to work. There's no sense creating a firewall when I can't 
even get non-firewalled packets through! Right?


>It sounds like you're on the right track here.  I'd go ahead & start working
>on your IPTABLES rules & take it from there.  There are quite a few good
>tutorials regarding IPTABLES, so you shouldn't have much trouble figuring it
>out.

OK, since the ip_forward did not appear to work, again it seems to me 
that my configuration has no chance of working at all unless iptables 
is actually implemented and running. IOW, there's no way for me to 
just pass packets, even if I wanted to be insecure. I'll hit the 
tutorials. Thanks for your comments.


Stefan Jeglinski