Does yours also rewrite the source IP of the outgoing GRE packets? Here's example output from snoop -d sppp0 -r, using the same IP scheme as in my original email:
192.168.0.45 -> 12.12.12.12 IP D=12.12.12.12 S=192.168.0.45 LEN=56, ID=46568, TOS=0x0, TTL=63 192.168.0.45 -> 12.12.12.12 IP D=12.12.12.12 S=192.168.0.45 LEN=56, ID=46569, TOS=0x0, TTL=63 192.168.0.45 -> 12.12.12.12 IP D=12.12.12.12 S=192.168.0.45 LEN=56, ID=46570, TOS=0x0, TTL=63 64.64.64.64 -> 12.12.12.12 TCP D=1723 S=23809 Push Ack=3741653503 Seq=372925543 Len=16 Win=6432 Options=<nop,nop,tstamp 49663 3230013> 12.12.12.12 -> 64.64.64.64 TCP D=23809 S=1723 Push Ack=372925559 Seq=3741653503 Len=148 Win=65195 Options=<nop,nop,tstamp 3230312 49663> Does this happen with your setup? Is there a specific rule to tell ipnat or ipf to rewrite the source IP? Or is this a bug in 3.4.33pre1? I suppose I could diagnose further by rebooting my PC into Windows and trying it from there... to isolate a possible Linux PPTP client bug. On Wed, Jan 14, 2004 at 05:06:10PM +1100, Adam Summerfield put into existance: ] I have a similar setup to yours, except ADSL not dialup. ] ] I don't think you need to have a rdr statement for the GRE unless you ] are running a pptp server on another internal box (I don't have it and ] what you want works fine for me). ] ] I allow everything out by default and I have a rule that allows GRE from ] any to any back in. ] ] This allows me to connect from my two windows pc's to a pptp server at ] work. ] ] Regards, ] ] Adam ] ] -----Original Message----- ] From: [EMAIL PROTECTED] ] [mailto:[EMAIL PROTECTED] On Behalf Of ] [EMAIL PROTECTED] ] Sent: Wednesday, 14 January 2004 11:42 AM ] To: [EMAIL PROTECTED] ] Subject: IPFilter 3.4.33pre1, GRE/PPTP client behind firewall ] ] I understand this issue has been hashed again and again and again ] hundreds of times... but after ] searching the archives, I am still stumped. ] ] Situation: ] I have a Sun Ultra 5 (Solaris 9) as a dialup ] router/firewall/server/kitchen sink/etc. at home, which ] maintains a dialup modem connection to my ISP. We'll say its Internet ] address is 64.64.64.64 (dev sppp0) at the moment. ] I also have an internal LAN, 192.168.0.0/24. My Sun box's IP on this ] LAN is 192.168.0.1 (dev hme0), and it is the default ] route for all internal LAN boxes (it also runs Sun's DHCP server). ] ] I have a laptop on this LAN. My laptop has RedHat Linux 9 with ] PPTP software installed, and that works great (when it's given a real ] Internet address). ] It is the ONLY client in my LAN which needs to do ANYTHING with PPTP or ] GRE. It needs to connect to the ] corporate VPN server (which is on a public Internet IP), we'll call it ] 12.12.12.12. ] My laptop's IP is 192.168.0.45. ] ] I understand I can set up a rdr using IPNat so GRE packets coming from ] 12.12.12.12 to my dialup modem can be ] redirected to my laptop's IP (192.168.0.45) using a rule like: ] rdr sppp0 0.0.0.0/0 port 0 -> 192.168.0.45 port 0 gre ] ] I am not sure if this works, because the following scenario exists when ] I try to make a PPTP connection: ] ] My laptop sends packets to the corporate VPN server (12.12.12.12) with ] protocol=47 (GRE), however ] Source IP=192.168.0.45, Dest IP=12.12.12.12. That's fine, except my Sun ] box continues to send that packet ] out the modem as Source=192.168.0.45, Dest=12.12.12.12 ! ] It does not rewrite the Source IP of the outbound GRE packet. Are there ] any rules I should add to enable this? ] ] Note that I determined this by use of Solaris's "snoop" program. I ] noticed that TCP NAT'ed packets for the port 1723 ] connection appeared in "snoop" as bearing the destination/source IP of ] the Sun box's dialup modem IP, rather than the ] laptop's internal IP. The IP packets bearing protocol "47" all said ] source IP of 192.168.0.45, so I assume that means ] it sent the packet out the modem as such. ] ] ] ] Also for the record, I have basic TCP/UDP NAT'ing for all boxes in my ] internal LAN, using the following IPNat rule: ] map sppp0 192.168.0.0/24 -> 0.0.0.0/32 portmap tcp/udp 20000:30000 ] ] ] Thank you very much!
