> My configuration is as follows. > > EXTERN_IP=111.222.333.444 > EXTERN_IF =eth0 > INTERNAL_IP=10.24.33.224 > INTERNAL_IF =eth1 > INT_NET = 10.0.0.0/8 > IPFWDING_KERNEL= FILTER_ON > IPALWAYSDEFRAG_KERNEL = YES > CONFIG_HOSTNAME = YES > CONFIG_HOSTSFILE = YES > CONFIG_DNS = NO > IPFILTER_SWITCH = firewall > SNMP_BLOCK = YES > EXTERN_DHCP = NO > EXTERN_DHCP = NO > EXTERN_TCP_PORT0="0/0 www 111.222.333.444" > INTERN_SERVERS="tcp_111.222.333.444_www_10.24.33.150_www" > > My IPCHAINS RULES looks like they are accepting the connection at > 111.222.333.444. But could not find the solution. Could anybody help me in > that regard. > When I see in weblet through brouser I'm seeing this. > but no byte(packet) in Chain port forward policy. > > > :: Masqueraded Connections :: > IP masquerading entries > prot expire source destination ports > tcp 0:58.64 10.24.33.150 203.163.160.2 80 2678 (80)
> Will Charls reply. You won't see any port-80 packets going through the forward ipchain. Inbound port 80 requests will either be answered by the local weblet server, or sent via port-forwarding rules to your internal web-server. If you're running weblet on port 80, it's probably getting all the port 80 requests, as I don't think inetd can differentiate services by IP address...if inetd is listening on port 80 for weblet, it's listening on *ALL* interfaces. Try disabling webet (or moving it to a different port), and see if your external port-forward begins to work. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
