Hello!
I have a small home network:
my ISP
|
Cable Modem connection to my ISP
|
eth3
get an IP address
from dhcp server of my ISP
10.91.0.xxx
|
PC box-1 firewall/gateway
======================= |
|
eth1 eth2
192.168.1.1 192.168.2.1
| |
LAN DMZ
| |
eth0 eth0
192.168.1.98 192.168.2.100
| |
PC box-2 PC box-3
desktop server
Debian Etch Debian Etch
=========== ==========
Shorewall run on all boxes, and started successfully. :)
I can''t to connect with SSH from
box-2 IP: eth1: 192.168.1.98
to
box-3 IP: 192.168.2.100
Any advices will be appreciated!
--
Regards, Paul Csanyi
http://www.freewebs.com/csanyi-pal/index.htm
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
Paul Csanyi wrote:> > Shorewall run on all boxes, and started successfully. :)So why did you only send the status from the firewall?> > I can''t to connect with SSH from > box-2 IP: eth1: 192.168.1.98 > to > box-3 IP: 192.168.2.100 > > > Any advices will be appreciated!I''m guessing that the problem is on box-3 -- I don''t see anything on the firewall. I suggest that you "shorewall clear" on all three boxes; you should be able to connect (if not, the problem has nothing to do with Shorewall). Then start Shorewall on one box at a time until you can''t connect -- then look at the last box that you did the "shorewall start" on. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
Sun, 11 Nov 2007 14:01:43 -0800 keltezéssel Tom Eastep azt írta:> Paul Csanyi wrote: > >> >> Shorewall run on all boxes, and started successfully. :) > > So why did you only send the status from the firewall?Sorry, I thought that that it is not important, because the shorewall configuration on box-2 and box-3 is simple and right.>> I can't to connect with SSH from >> box-2 IP: eth1: 192.168.1.98 >> to >> box-3 IP: 192.168.2.100 >> >> >> Any advices will be appreciated! > > I'm guessing that the problem is on box-3 -- I don't see anything on the > firewall. I suggest that you "shorewall clear" on all three boxes; you > should be able to connect (if not, the problem has nothing to do with > Shorewall). Then start Shorewall on one box at a time until you can't > connect -- then look at the last box that you did the "shorewall start" on.Thank you for help. The problem was that that the dhcp3-server give for the box-2 the wrong IP address: 192.168.1.95. When I set up it correctly, and box-2 get the right IP address: 192.168.1.98, then I can made successfully the SSH connection to the box-3 from box-2. -- Regards, Paul Csanyi http://www.freewebs.com/csanyi-pal/index.htm ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users