On Tue, 2004-02-24 at 01:02, Gunnar vS Kramm wrote: > Hmm, it sure might be the linksys. I'm actually got a similar setup. > Fedora Core 1 behind a linksys befw11 router. do you allow other inbound > connections to your server; email or ftp? If so do they work? Can you get this test page: http://linux4me.dyndns.org/ > The connection refused message makes me think your linksys is denying the > connection, also I see your coming from tampabay.rr.com, which I believe it > A Road Runner cable modem connection. > > Road Runner is notorious for not allowing "server" on their network and > _might_ be not allowing any inbound connections to your IP. I know tampabay.rr does not block 80, p2p, etc. Though I am not sure of SSH. > Could you check you linksys configuration? look at the forwarding tab > (assuming your linksys is like mine) and see if it is allowing inbound > connections on port 21 I have ports 21, 80 and 500 forwarding to 192.168.1.101. Port 500 is for the Netlock VPN client. > On a totally different note I see you said you got your Netlock Linux VPN > client working. I've been trying to get it working my self. I'd love to > talk to you about how you got it to work with Fedora Core 1. I downloaded the latest RH9 kernel and kernel source and installed that. I then booted into FC1 with the RH9 kernel and installed the client with that. It works like a champ. There is some issue with the FC1 kernel that the Netlock client has not been coded to work with. So until Netlock does that, I just boot into the RH9 kernel when needed. You could also just run the RH9 kernel full-time since I did not notice any differences over the stock FC1 kernel concerning functionality/performance. > Gunnar vS Kramm Jim Drabb -- --------------------------------------------------------- The box said: "Requires Windows 98/2000/NT/XP or better." So, I installed LINUX! --------------------------------------------------------- James Drabb JR Senior Programmer Analyst Davenport, FL USA
