> I've a openwrt box that handle an openvpn tunnel between two branch offices.
> The router have a ''public'' ip address in 10.0.0.0/24, and route via
> openvpn the internal network in 10.172.0.0/16.
> I've also added wireless access via WPA2 enterprise, using a radius sever in
> the main (internal) network.
> All work flawlessy, apart that when router reboot, for some reason hostapd
> ''bound'' the public 10.0.0.X addess and make radius request to the radius
> server using that IP (and clearly never go to the radius server).
> If i simply restart wireless, all things goes well.
> AFAIK the culprit come from hostapd that start before openvpn. There's some
> way to cure, or circumvent this?
No one reply to my email, but still i need feedback on this.
I've tried to create an openvpn 'up' script with inside:
/sbin/wifi down
/bin/sleep 1
/sbin/wifi up
but does nothing; i've also added that instruction on /etc/rc.local, but
nothing changed.
The trouble is that everytime the router reboot (for a power outgage, ...) i
cannot autheticate apart if i manually logon into the router and restart
wireless.
It is very annoying... someone can help me? Thanks.
PS: seems also that a simple:
HOSTAPD_PID=`cat /var/run/wifi-phy0.pid`
kill -HUP $HOSTAPD_PID
does not work, eg wirelss/hostapd have to be restarted...
--
E i professori dell'altroieri stanno affrettandosi a cambiare altare
hanno indossato le nuove maschere
e rincominciano a respirare (F. De Gregori)
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
