Try this link for a start. http://home.attbi.com/~srlohman/linux/firewall/es-remoteacc.html
His putty instructions worked but his sshd instructions did not. I am using Dachstein CD 1.0.1 and connect from one windows machine on the LAN to the LRP box. To get sshd to work I had to load sshd.lrp, libz.lrp, and makekey.lrp. After all that is loaded, default to a system prompt on the LRP box and run makekey. Be patient, it takes a while. Write down the fingerprint just in case you might find it useful later. Makekey only needs to be run once. After that you don't need to load makekey.lrp again. Now follow the instructions for putty and try to log in. OH, forgot, you also need to come up with a password for root using the passwd command. This is done on the LRP machine. When putty comes up, you will see a screen showing the fingerprint, and it will ask you if you want to accept this connection as a secure connection. Say yes, and you will get the LRP box logon screen. Enter the root password you set up on the LRP box and you are in. Regards, Frank Kamp Ray Olszewski wrote: > > At 03:05 PM 3/3/2003 -0500, [EMAIL PROTECTED] wrote: > >Hi, > > > >i trying to get the following situation to work: > >Windows pc with Putty connecting to Bering Firewall. > > > >When i make the connection via Putty i get the following reply: > >* Network error. Connection Refused. > > > >I have read the online Bering Openssh documentation. > > > >I have the Bering 1.1 firewall. > > > >I have the standard policy and rules of the bering firewall. > > > >I don't understand what i'm doing wrong. > > > >Any comments. > > That is the putty message you get when there is no server running on the > target host. I don't know (and cannot readily test) if it is also the > message you get in response to an icmp reject (the kind of REJECT an > iptables firewall generates) or a DENY (probably not for a DENY, though ... > for that, I'd expect a wait, followed by "Network error: connection timed > out", same as if that IP address was not in use). So ... > > 1. You should confirm that sshd is running on the Bering firewall. > > 2. Are you trying to connect to the router from the LAN side or the > external side? Are you certain you are using the right IP address in either > case? If the connection is external, is it possible that your ISP > interferes with traffic to port 22 (ssh)? > > 3. Just in case ... the default in putty is a telnet connection. You are > changing that to ssh, right? > > 4. "the standard policy and rules of the bering firewall" is not really all > that well-defined; there is a lot of customizing you can, and sometimes > need to, do to make Shorewall work with "standard" Bering settings. You > might find it worthwhile to review the output of "/sbin/shorewall status" > ... or to post it here if you need help interpreting it. > > 5. Is your Windows host set up properly in general, with respect to its IP > address, routing table, and gateway address? One test: can you ping the > Bering firewall (do it from a DOS prompt if you don't have a GUI ping app > installed)? If not, how does a ping attempt fail? > > Sorry to be offering such bland advice, but when you don't provide the > standard details on your setup (see the SQ FAQ), it's hard to do more. > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
