[SOLVED] VPN Server on PPPoE interface

[alxbzm]

I'm using Zentyal 2.0.17 core. I have 3 interfaces:
eth0 - internal
eth1 - external PPPoe (provider gives static "white" IP on it)
eth2 - external static

VPN server is configured to listen on all interfaces. So when i'm trying to connect on eth2 IP adress - everything works fine, but when i'm trying to connect on PPPoE IP adress - it doesn't work. Client hangs on "UDPv4 link remote: <IP>:<PORT>" step.
I think the firewall doesn't work properly on this interface: i see dropped packets on interface PPPoE in syslog file.
So the question is how properly tune up the firewall or is there any other ways of solution?

Thanks in advance!

[jquintao]

Hi,

I had the same problem in the past... I believe that this problem was fixed in the recent versions from ebox modules... Are your ebox-openvpn and ebox-network updated?

Thanks,
Jorge Quintao

[alxbzm]

Thanks for reply!
But I have latest updates of all modules:

Zentyal Core - 2.0.17
VPN Service - 2.0.9
Firewall - 2.0.3
Network Configuration - 2.0.8
Network Services - 2.0
Certification Authority - 2.0.3

and all the updates installed by apt-get.

Unfortunately I have little experience in configuring firewall: is there a way to manually change the firewall settings?

Thanks in advance!

UPD: I mean the firewall settings from the command line, as in the web interface I can not set rules for the ppp0 interface - that it is packet filtering judging by the logs.

[jquintao]

Hi,

You can put rules manually editing the file "/etc/ebox/hooks/firewall.postservice"... Example:

Code: [Select]

if [ "$1" -eq "1" ]
then
    #add custom rules here
    sudo iptables -I FORWARD -s x.x.x.x/24 -d 0/0 -j ACCEPT
    true
fi

exit 0

In the past, i have problems with openvpn using "proto udp"... Maybe you can choose for "proto tcp-server" in the server side and "proto tcp-client" in the client side to test too... You can do this editing the files inside "/usr/share/ebox/stubs/openvpn/" and restarting with "/etc/init.d/ebox openvpn restart"...

Thanks,
Jorge Quintao

Thanks,
Jorge Quintao

[alxbzm]

Thanks for the tip! Indeed, the transition to the protocol TCP solved the problem. In the case of the UDP protocol connection still can not be established. I do not presume to say exactly this bug or normal behavior, but this topic can be marked as [SOLVED].