[Openswan Users] Issues with L2TPNS and Openswan on Fedora Core 4

[Tim P]

I fixed this issue because I needed to set my bind address to either
the outside address or a new address that resided on my internal
subnet (forget which, dont have the machine accessible right now).

I have a new problem in that the L2TP server never seems to do
anything with the vpn request for l2tp authentication.  I have a good
ipsec tunnel (you said it looked good when you saw the output) and the
radius authentication works fine but I can't seem to get L2TP to show
anything in the logs when a request comes through.  Essentially ipsec
kills the tunnel after a minute or so when no authentication is
completed.

On 8/2/05, Jacco de Leeuw <jacco2 at dds.nl> wrote:
> Tim P wrote:
> 
> > I am using L2TPNS for my L2TP server and when it brings up the tun0
> > interface (actually when I start the service/executable) it seems to
> > kill my second nic in the box.  I have eth0 as my "outside" nic and
> > eth1 as my "inside" nic.  When tun0 becomes active I am no longer able
> > to ping on the inside network.
> 
> It "kills" your internal interface? What does that mean?
> You are pinging from what to what? The IPsec connection is not even up
> at that stage?
> 
> 
> > set bind_address 192.168.0.1
> >
> > I am hosting freeradius on the vpn box, I can use 127.0.0.1 correct?
> 
> AFAIK, yes.
> 
> > Bind_address I have set to my eth1 (inside) nic address, is that correct?
> 
> What if you use your 'outside' nic address?
> 
> Jacco
> --
> Jacco de Leeuw                         mailto:jacco2 at dds.nl
> Zaandam, The Netherlands           http://www.jacco2.dds.nl
> _______________________________________________
> Users mailing list
> Users at openswan.org
> http://lists.openswan.org/mailman/listinfo/users
>