"Steven T. Hatton" wrote:
Nick,
Thanks for all the pointers. I still haven't gotten the kernel part working. I decided to use the rp_pppoe for now. I wanted to get someting working. I found it to be EXTREMLY difficult. I attempted to use SuSE's firewall defaluts and ended up hurting myself! I used the sample off http://members.home.net/ipmasq/ and got it working as soon as I ran it. The only problem was SuSE's script griped about not knowing what the external interface is. I put that in the rc.firewall from the above site and the SuSE script stopped complaining. Unfortunately it also stopped working. When I look at /var/log/messages I see that all the stuff from my traceroutes and etc., are being blocked by the firewall. I went over this and over this. I can't figure it out. I don't like running on a system that tells me the "firewall startup failed". Here's my ifconfig
Personally I'm not using the SuSE firewall scripts. I built one using: http://linux-firewall-tools.com/linux/firewall/index.html It's aimed at Redhat users so you need to do a little editing but it's actually easier then when I first used. Pick static IP and then add something like: EXTERNAL_INTERFACE="ppp0" export IPADDR=$(ifconfig ${EXTERNAL_INTERFACE}|sed -ne '/addr:/{s/.*addr:\([^ ]*\).*/\1/;p;}') echo $IPADDR I just looked at the website again and it's been updated to handle ppp0 connections so you won't need to change the interface line. I don't know if it's smart enough now to get the IPADDR on it's own. If so you won't need the IPADDR line either. The stuff you need to comment out should be at the bottom of the created script. I just added # and ignored it. If nothings changed then it's all the stuff after "echo done"
Here's the doodoo from /var/log/messages:
Mar 11 18:53:49 heimdall kernel: Packet log: input DENY ppp0 PROTO=17 207.217.77.82:53 138.88.44.31:61000 L=156 S=0x00 I=12029 F=0 x0000 T=240 (#3)
Do you have any idea what is going on here? I went through the SuSE rc.firewall and opened that thing up to absolute vulnerablility on every port and still had the same problem.
53 is DNS. It looks to me like the DNS server is trying to talk to you. Personally I get my ISPs newserver [port 119] doing the same thing. Since everything works I just ignore it. Nick -- 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/