A. John Peters
2003-May-19 06:47 UTC
[Shorewall-users] Unable to access outside ISP system
S Version 1.4.2 Kernal 2.4.20-6 Redhat 9 Internal Network 192.168.2. Internal Router 192.168.2.1 ppp0 address after dialup 205.243.25.210 Remote address 205.243.25.10>From any system on in local net I can ping192.168.2.1 192.168.2.20 192.168.2.25 205.243.25.210 205.243.25.10 Whenever I ping a site on the other side of 205.243.25.10 I get destination unreachable. Example is 209.32.151.4 No messages in my log when I get this. Is this normally a configuration problem, or do I have a problem with my ISP?
On Mon, 19 May 2003 08:47:34 -0500, A. John Peters <ajpeters@otg-dss.com> wrote:> S Version 1.4.2 > Kernal 2.4.20-6 Redhat 9 > > Internal Network 192.168.2. > > Internal Router 192.168.2.1 > > ppp0 address after dialup 205.243.25.210 > > Remote address 205.243.25.10 > > >> From any system on in local net I can ping > 192.168.2.1 > 192.168.2.20 > 192.168.2.25 > 205.243.25.210 > 205.243.25.10 > > > Whenever I ping a site on the other side of 205.243.25.10 I get > destination > unreachable. Example is 209.32.151.4 > > No messages in my log when I get this. > > Is this normally a configuration problem, or do I have a problem with my > ISP?It normally means that you haven''t set the default gateway properly on your internal systems. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net
On Mon, 19 May 2003 09:13:58 -0500, A. John Peters <ajpeters@otg-dss.com> wrote:> > > On my local Systems I have it set at 192.168.2.1 which is my shorewall > server. >Then the problem is most likely with the entry in the /etc/shorewall/masq file. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net