Very Computer

>says...
>> I'm setting up a Linux firewall with demand dialing and ipmasq.  I can
>> access the Internet through the firewall, but I can't connect to a PPTP
>> server.  If I try the same PPTP connection from the same computer over a
>> direct dial-up to the isp, it works fine.

>> Any ideas?

>Yes... look here
>ftp://ftp.rubyriver.com/pub/jhardin/masquerade/ip_masq_vpn.html
>--

> Thanks, that looks like what I need.  Of course, I have been able to avoid
> recompiling the kernel until now, oh well.

> Since the default Slackware 2.0.36 Kernel has worked for everything else
> I've done, is there any way to know what settings were used so I can make
> only the minimum required changes to the settings before recompiling?

> >says...
> >> I'm setting up a Linux firewall with demand dialing and ipmasq.  I can
> >> access the Internet through the firewall, but I can't connect to a PPTP
> >> server.  If I try the same PPTP connection from the same computer over a
> >> direct dial-up to the isp, it works fine.

> >> Any ideas?

> >Yes... look here
> >ftp://ftp.rubyriver.com/pub/jhardin/masquerade/ip_masq_vpn.html
> >--

>says...
>> Thanks, that looks like what I need.  Of course, I have been able to
avoid
>> recompiling the kernel until now, oh well.

>> Since the default Slackware 2.0.36 Kernel has worked for everything else
>> I've done, is there any way to know what settings were used so I can make
>> only the minimum required changes to the settings before recompiling?

>> >says...
>> >> I'm setting up a Linux firewall with demand dialing and ipmasq.  I can
>> >> access the Internet through the firewall, but I can't connect to a
PPTP
>> >> server.  If I try the same PPTP connection from the same computer over
a
>> >> direct dial-up to the isp, it works fine.

>> >> Any ideas?

>> >Yes... look here
>> >ftp://ftp.rubyriver.com/pub/jhardin/masquerade/ip_masq_vpn.html
>> >--

>Don't know. Don't use RedHat. Like Debian better.
>--

>>says...
>>> Thanks, that looks like what I need.  Of course, I have been able to
>avoid
>>> recompiling the kernel until now, oh well.

>>> Since the default Slackware 2.0.36 Kernel has worked for everything
else
>>> I've done, is there any way to know what settings were used so I can
make
>>> only the minimum required changes to the settings before recompiling?

>>>says...
>>>> Thanks, that looks like what I need.  Of course, I have been able to
>>avoid
>>>> recompiling the kernel until now, oh well.

>>>> Since the default Slackware 2.0.36 Kernel has worked for everything
>else
>>>> I've done, is there any way to know what settings were used so I can
>make
>>>> only the minimum required changes to the settings before recompiling?

>Before you change your kernel, run "make menuconfig" or "make xconfig"
>(whichever you prefer) and use the "save configuration" option to save your
>current configuration in a file. You can then later read in this
>configuration, make small changes, save it again...

>It saves you starting from scratch every time.

>--

> pgpk -a finger://gonzo.wolfenet.com/jhardin    PGP key ID: 0x41EA94F5
> PGP key fingerprint: A3 0C 5B C2 EF 0D 2C E5  E9 BF C8 33 A7 A9 CE 76
>-----------------------------------------------------------------------
>  In the Lion
>  the Mighty Lion
>  the Zebra sleeps tonight...
>  Dee de-ee-ee-ee-ee de de de we um umma way!