Here is what works for me:
Given that the network I want my remote users to be able to connect to
is accessible via eth0 and I am creating a TAP device called tap0, I
create a bridge once per boot of the OpenVPN server:
brctl addbr br0
brctl addif br0 eth0
I hard-code eth0 with IP address info instead of using DHCP.
These commands are run every time OpenVPN starts:
brctl addif br0 tap0
ip link set tap0 up
After this is done remote clients are able to get IP addresses via the
DHCP server on my internal network.
These commands are also scripted to run again every time OpenVPN
restarts due to ping-restart.
IPRO Tech, Inc.
[mailto:openvpn-users-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike
Sent: Wednesday, January 12, 2005 7:20 PM
Subject: [Openvpn-users] How to initialize bridge at boot time?
What is the proper way to initialize or create a bridge on a
linux box at
boot time? I currently initialize both ethernet interfaces,
and eth1 internal in the "normal" way via the init scripts. Then in
rc.local I run the equivalent of the bridge-start script from the 2.0
This seems to work intermittently. When it doesn't work, the
I have is that IP addresses are never assigned via dhcp. If
I look in
/var/log/messages I see the dhcp requests on eth0. When it
does work I
see dhcp requests on br0.
My guess is that dhcpd is not sure which interface to listen on after
bridge-start yanks eth1 out from underneath it(?).
-- Thanks, Mike
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
Openvpn-users mailing list