Andrew
Andrew Gray (Gil) wrote:
Andrew Gray (Gil) wrote:
..
Yes the modem connects and nats to 192.168.1.0 network then the firewall sits
behind that. Everything else works fine this way and the modem takes care of
the connection to the ISP for me. The firewall is in the dmz of the modem so
all incoming traffic goes straight to the firewall and there are no other
devices connected to the modem with the firewall.
Mhhh... OK another try then...
On the server side, this does not make much sense...
server 10.8.0.0 255.255.255.0
and
push "route 10.8.0.0 255.255.255.0"
The server will use th 10.8.0.0 subnet for its tunnels and will set the
routes on the clients anyway, you can see this in the last log entry
before the error
Feb 24 21:52:50 FIREWALLESP openvpn[22746]:
FIREWALLPIA/203.94.34.34:32769 PUSH:
Received control message: 'PUSH_REQUEST'
Feb 24 21:52:50 FIREWALLESP openvpn[22746]:
FIREWALLPIA/203.94.34.34:32769 SENT
CONTROL [FIREWALLPIA]: 'PUSH_REPLY,route 10.8.0.0 255.255.255.0,route
192.168.2.0 255.255.255.0,route 10.8.0.0 255.255.255.0,ping 10,ping-restart
120,ifconfig 10.8.0.6 10.8.0.5' (status=1)
Feb 24 21:53:45 FIREWALLESP openvpn[22746]: FIREWALLPIA/203.94.34.34:32769
MULTI: bad source address from client [192.168.3.31], packet dropped
try to fix this and then treport back
cheers
Erich
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
