[ILUG] really being specific with iptables.

[John Allen]

Darragh wrote:
> I think I now know what the problem is.
>
> The iptables are set up to route packets going to the server to port 3128
> then from there, to squid and then over to the router at 192.168.2.1 on
> port 80.
>
> I was unsure as to why all traffic on port 80 was giving me the router
> configuration page but that would make sense.  I'll therefore have to
> remove the rules and write them again.
>
> I'm still not sure though how I can acess the server internally.  It's not
> unlogical to think that if this assumption is correct, the server wouldn't
> forward all traffic to port 80 over to the router after it had been delt
> with by squid.
>
> I'll give it a go today sometime when I have a few minutes.
>
> Thanks again for the suggestions.
> BTW, if anyone has an alternative way of looking at iptables -L output I'd
> really appreciate knowing about it.  I'm unable to make any sense of it's
> output.  I understand the rules.  but what I understand just doesn't match
> up to what the list is showing me.
>
>   
All joking aside, Darragh, just stop dealing with iptables directly, and 
switch to shorewall, once you get the hang of it, you will never want to 
deal with iptables directly again :)
> Thanks agian
>
>
>
> Darragh
>
>   


-- 
John Allen                          mailto:john.allen at codemountain.net
CodeMountain                        http://www.codemountain.net

Ubuntu 7.10, kernel 2.6.22-14-generic
up 4 days, 19:51,  8 users,  load average: 0.24, 0.32, 0.76