🚀 go-pugleaf

Are you allowing inbound port 80 in your ipchains rules?  If you enable
logging on your ipchains rules and then run "tail -f /var/log/messages"
you should be able to see where you are being denied.  Again, sounds
like you aren't allowing inbound port 80.

In article <38A7C93C.B6CC7780@c031.aone.net.au>,
  movielink@c031.aone.net.au wrote:
> This is getting to much...
>
> 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.
>
> Kernel is 2.2.13 with a lot of un-nescesary stuff
> removed (SCSI support, some file systems etc.)
>
> This works great for MASQ to the Internet from my
> internal network.
>
> Trying to get access from the Internet to a WWW server
> running on one of the boxes on the internal network is
> impossible!  Or so it seems.
>
> I have recompiled the kernel more times than I care to
> mention due to overlooking some of the switches to
> enable "portfw" so that "ipmasqadm" could work.
>
> Now all is set up according to the man pages but it
> still will not run.
>
> I have tried to use PING to test it, pointed a www browser
> at it - nothing, no response.
>
> 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
>
> This should forward the Internet IP, port 80 to the internal machine
on
> 192.168.5.9, port 80.
>
> What am I doing wrong here????
>
> Anthony
>

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


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