Martinez, Mike (MHS-ACS)
2002-Jan-09 21:25 UTC
[Shorewall-users] IpSec problem from local box to company ser ver
Les, We also run a nortel vpn and use the Extranet Client. All of our clients connect to everything on our network without any problems. It sits in our DMZ on our network. In addition to Tom''s rules you also need to add another rule for the Encapsulating Security Payload (esp) protocol. On our firewall we have entries like this for the Extranet client on our rules file. ACCEPT net dmz udp 500 ACCEPT net dmz esp Hope this helps Mike -----Original Message----- From: Tom Eastep [mailto:teastep@shorewall.net] Sent: Wednesday, January 09, 2002 2:46 PM To: Les Hazelton; shorewall-users@shorewall.net Subject: Re: [Shorewall-users] IpSec problem from local box to company server Les, On Wednesday 09 January 2002 12:39 pm, Les Hazelton wrote:> I have a problem with my IpSec tunnels. They work for a few minutes and > then die. My firewall is running shorewall 1.2.2. The connection to the > net is via ppp0 dial. The local network interface is eth0 which connectsto> a LinkSys 10/100 switch. Most of the systems in the house are for personal > use and don''t use IpSec. They all work just fine. > > The work system is a Thinkpad running Win98-SE and a Nortell ExtranetIpSec> client. This all worked without a problem while I was using an olderLinux> kernel and Seawall for the firewall. When I switched to a 2.4.17 kernel > and shorewall the IpSec problem started. > > The message log shows an incomming udp packet rejected at ablut the same > time as the tunnel failure. See below: > > Shorewall:net2all:DROP:IN=ppp0 OUT= MAC= SRC=192.128.133.43 > DST=32.226.176.107 LEN=104 TOS=0x00 PREC=0x00 TTL=55 ID=21414 PROTO=UDP > SPT=500 DPT=500 LEN=84 Shorewall:net2all:DROP:IN=ppp0 OUT= MAC> SRC=192.128.133.43 DST=32.226.176.107 LEN=104 TOS=0x00 PREC=0x00 TTL=55 > ID=25250 PROTO=UDP SPT=500 DPT=500 LEN=84 .... and many more ... > > I have not placed any entries in the /etc/shorewall/tunnels file becauseit> looked to me like that was to define tunnels with endpoints on thefirewall> system. All my tunnels should be masked from local through the firewallto> a company server somewhere in the ether. > > I would greatly appreciate any pointers - i.e., what am I doing wrong???I would try adding a couple of rules: ACCEPT net 192.128.133.43 loc:<thinkpad ip> 50 - - all ACCEPT net 192.128.133.43 loc:<thinkpad ip> udp 500 0 all See if that helps. -Tom -- Tom Eastep \ A Firewall for Linux 2.4.* AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net ------------------------------------------- _______________________________________________ Shorewall-users mailing list Shorewall-users@shorewall.net http://www.shorewall.net/mailman/listinfo/shorewall-users