Problem with Local Bridge (Debian 7)

[milanolarry]

I set up a server in my Debian 7; it runs smoothly on SecureNAT. Last week, I switched it to local bridge; sometimes, not always, the following error message appears after reboot:

SIOCSIFADDR: No Such Device
tap_XXX: ERROR while getting interface flags : no such device

Anyone has the same problem? It really puzzles me. If there is something wrong with the setting, the error message should appear every time after reboot, but it does not. Sometimes the vpn server works without any problems.

[Petrol]

Do you have a script in /etc/init.d/ that launches softether vpn?

if yes, you should have a line that sets your local bridge ip address (ifconfig tap_something <anipaddress>) just after you start your vpn server. :

1. Start vpn server
2. Set local bridge ip

I think that the error message you sometime have is because your script don't wait enough time after the vpn starts to configure the local bridge ip address. The vpn server takes time to actually create the local bridge.

So you should modify your script to do something like this :

1. Start the vpn server
2. Wait for a moment ("sleep 1" works great for me)
3. Assign an IP to the local bridge.

[milanolarry]

Thanks. Let me give it a try. I'll change it to sleep 3.

[milanolarry]

Petrol wrote:
> Do you have a script in /etc/init.d/ that launches softether vpn?
>
> if yes, you should have a line that sets your local bridge ip address (ifconfig
> tap_something <anipaddress>) just after you start your vpn server. :
>
> 1. Start vpn server
> 2. Set local bridge ip
>
> I think that the error message you sometime have is because your script don't wait
> enough time after the vpn starts to configure the local bridge ip address. The vpn
> server takes time to actually create the local bridge.
>
> So you should modify your script to do something like this :
>
> 1. Start the vpn server
> 2. Wait for a moment ("sleep 1" works great for me)
> 3. Assign an IP to the local bridge.



It seems to work. However, another problem arises. The dnsmasq does not assign IP correctly unless I open my firewall,
ie, removing -A INPUT -j DROP .

When I used SecureNAT, I only needed to open port 443 and everything worked fine. Do I need to do some forwarding in the firewall in order to making the dnsmasq work correctly? Thanks in advance.

[Petrol]

Yes you should open Port UDP 67 on the server to allow dhcp

[milanolarry]

Allow udp 67 INPUT or FORWARD ? I am a newbie in Linux

[hatimux]

DHCP requests will arrive in the INPUT chain of the server.