Welcome, Guest. Please login or register.
Did you miss your activation email?
Tuesday 20 April 2021, 01:51:00 am

Login with username, password and session length

CLICK HERE for the The official Endian Roadmap and Issue tracker
14085 Posts in 4293 Topics by 6184 Members
Latest Member: nivaldo
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  VPN Support
| | |-+  [Endian 3.2.2] Machines on Green network not accessible.
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: [Endian 3.2.2] Machines on Green network not accessible.  (Read 4481 times)
Jr. Member
Offline Offline

Posts: 1

« on: Tuesday 23 May 2017, 06:42:16 am »


I have just upgraded a 2.5.1 installation that has been working well for 3 years to 3.2.2 on different equipment.
The only issue I have left is getting OpenVPN to work.  Under 2.5.1 it was simple and it "Just Worked", with 3.2.2, frustration!!

I am able to connect, via the red interface to the firewall, log in and I get an IP address from the firewall in the range expected.
BUT I cannot ping any machine inside on the Green interface.

With one login I have set the "Direct all client traffic through the VPN server" override and using tracert I can see that a request to google.com goes via that interface rather than directly from the connecting ISP.

The server is set as:-
- Authentication type: PSK
- Port: 1194
- Device Type: TAP
- Protocol: UDP
- Bridged: Selected
- Bridged to: GREEN
- Dynamic IP pool start address:
- Dynamic IP pool end address:
- Push these nameservers: selected
- Nameservers:
- Push these networks: selected
- Networks:

Client Config settings:-
dev tap
proto udp
remote my-external-ip 1194
resolv-retry infinite
ca cacert.pem

After connection in the Network Connection Details (Win7):-
- Description: TAP-Windows Adapater V9
- DHCP Enabled: Yes
- IPv4 Address:
- IPv4 Subnet Mask:
- IPv4 Default Gateway: (blank)
- IPv4 DHCP Server:
- IPv4 DNS Servers:

Reading other things on the net, I have not tried using the VPN firewall (should not be needed with bridged), but have tried the Source NAT rule suggested by kdouglas in the smalldragon post.

Full Member
Offline Offline

Posts: 42

« Reply #1 on: Wednesday 29 November 2017, 11:21:02 am »

Prueba con esto:


Jr. Member
Offline Offline

Posts: 5

« Reply #2 on: Thursday 20 February 2020, 06:58:16 am »

just the answer i needed  Cheesy . only setting up a vopenvpn client gw2gw is not enough to communicate with a endian vpn server, the source nat rule is nessesary .
Jr. Member
Offline Offline

Posts: 5

« Reply #3 on: Thursday 20 February 2020, 06:59:29 am »

Prueba con esto:


thank you
Full Member
Offline Offline

Posts: 11

« Reply #4 on: Monday 02 March 2020, 12:44:40 am »

Prueba con esto:


Thanks a lot!
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.062 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com