"James (Jim) Hatridge" wrote:
---------------------------------------- Opus:/root # ipfwadm -Fln IP firewall forward rules, default policy: accept type prot source destination ports acc/m all 192.168.17.0/24 0.0.0.0/0 n/a ------------------------------------
Yes and no, when I use lynx or netscrape it hangs with the looking up error. But when I ping I got two differet errors. At first I was getting something like "net not accessable" (I didn't keep the error, sorry) each time it pinged. Then after I messed around with the files some (I've been on this for about 2 weeks now.) I stopped getting anything. I would run ping xxx.xx.xxx.xxx and it would just sit there. When I ^c out of ping it would say something about x packages sent 0 returned 100% lost. I would then do the same ping command on Opus and it worked.
Well, this sounds like it is managing to send packets out (or at least it thinks it is) but is not receiving any back. (Hmm. Seems like I'm stating the obvious here...). You're not using any other firewalling package other than your own 'hand roled' ipfwadm rules are you? I'm afraid I've never used ipfwadm before, only ipchains. You would happen to have an input or output rule that could be blocking the ICMP (ping) packets would you? (Assuming you have such a thing with ipfwadm - I don't know). Another thing to check for is whether or not you're running a firewall on the client (non-firewall) box. Oh well. I though I had something useful to say. Hopefully you can find something useful out of all that, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/