🚀 go-pugleaf

Without seeing your entire firewall script I guess I can't tell you
where it's being blocked.  Either post the whole script or enable
logging and post that or both.

In article <38A7DD65.DB0D2A49@c031.aone.net.au>,
  movielink@c031.aone.net.au wrote:
> Anthony White wrote:
> >
> > This is getting to much...
>
> Please read on...I have more info to the following.
>
> >
> > After 17 kernel re-compiles, numerous tests,
> > trial and error I can still not get people on
> > the Internet onto my internal network:-(((
> >
> > Here is the system:
> > -------------------
> >
> > A standard RedHat box set up as a firewall between
> > an internal network (192.168.x.x) and an Internet
> > IP address, using the "PmFirewall" scripts.
>
> [...most snipped...]
>
> > The "/lib/modules/2.2.13/ipv4/ip_masq_portfw.o" file does
> > exist and can be loaded - is loaded.
> >
> > This is the command used:
> >
> >  /sbin/ipmasqadm portfw -f
> >  /sbin/ipmasqadm portfw -a -P tcp -L inet_ip_addr 80 -R 192.168.5.9
80
>
> When changing the above to
>
>    /sbin/ipmasqadm portfw -a -P tcp -L inet_ip_addr 4000 -R
192.168.5.9
> 80
>
>  and then point my browser to "inet_ip_addr" all works!!!
>
> In other words when using port 4000 to request www pages the thing
gets
> forwarded just fine.  This means that there must be a problem with
> blocking
> port 80 in my IpChains rules - but where???
>
> >
> > This should forward the Internet IP, port 80 to the internal
machine on
> > 192.168.5.9, port 80.
>
> It does not, see above...
>

--
Tim Fischer
MCSE,MCP+Internet
COMPAQ/DEC ASE


Sent via Deja.com http://www.deja.com/
Before you buy.