> > > I was looking at installing PoPToP (PPTP server) on a RedHat server on
> my
> > > internal network so users at home, mobile etc. can access our Samba
> shares
> > > using a dialup connection.
> > >
> > > I know I need to open ports 1723 (tcp) and protocol 47 to allow the
PPTP
> > > protocol to work, and I can do this with my LRP box. I assume I will
> need to
> > > portforward 1723 to the internal server. But how can I
> 'protocolforward'?
>
> > /usr/sbin/ipfwd my_server_ip 47 &
>
> Thanks all for the help on this - I now have my Windows machine able to
> connect to my internal RedHat box. I haven't yet installed the new kernel
> and modules to my LRP (ES2B) box, since I don't want to risk screwing
> everything up when I'm not in the office (I'm using SSH currently..)
>
> Checking the logs on the RedHat box reveal that the connection is dying
due
> to a reason (from the PoPToP faq) that is fixed by applying the
> 'ip_masq_vpn.patch' to my kernel. Now, I know I'm getting off topic here,
> but which kernel? The internal RedHat box, or my LRP box? Or both? Or will
> it be fixed by installing the new kernel on my LRP box plus the relevant
> ip_masq_pptpd.o module?
The ip_masq_* modules are known as IP Masquerade helper modules, and exist
to 'help' or fix protocols that generally don't like going through a router
that mangles their IP headers. Therefore, if you need the ip_masq_vpn
patch, or any ip_masq_* modules, they should go on your firewall/router box,
which I'm assuming is the LRP machine.
I have some LRP kernels compiled with the VPN patches available:
http://lrp.steinkuehler.net/files/kernels/Eiger-VPNMasq/
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
