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

[Tim P]

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.

My l2tpns startup-config is as follows:

set debug 3
set log_file "/var/log/l2tpns"
set pid_file "/var/run/l2tpns.pid"
set l2tp_secret "secret"
set primary_dns 192.168.1.1
set secondary_dns 198.110.24.14
set save_state yes
set primary_radius 127.0.0.1
set secondary_radius 1.2.3.7
set radius_accounting yes
set radius_secret "mysecret"
set bind_address 192.168.0.1
set throttle_speed 64
set accounting_dir "/var/run/l2tpns/acct"
set setuid 0
set dump_speed no
#load plugin "garden"
load plugin "throttlectl"
load plugin "autothrottle"
load plugin "snoopctl"
load plugin "autosnoop"


I am hosting freeradius on the vpn box, I can use 127.0.0.1 correct?
Bind_address I have set to my eth1 (inside) nic address, is that correct?