Allow access to Omada Controller Management portal from all VPN computers.

Allow access to Omada Controller Management portal from all VPN computers.

Allow access to Omada Controller Management portal from all VPN computers.
Allow access to Omada Controller Management portal from all VPN computers.
2024-03-03 17:45:58 - last edited 2024-03-07 01:59:17
Model: ER7212PC  
Hardware Version: V1
Firmware Version: ER7212PC(UN)_V1_1.1.2 Build 20240102


Here is the configuration:

VPN Server
- Protocol P2TP
- Public IP x.x.x.x
- VPN Private Network 10.222.0.0/16

ER7212pc Omada Controller as VPN Client (A place)
- Protocol P2TP
- Public IP 192.168.1.100 (Behind providers NAT Router)
- VPN Private Network 10.222.48.0/24
- VPN Interface IP 10.222.0.100 (From VPN Server DHCP)
- Controller IP 10.222.48.1
- Other Device IP 10.222.48.20

Place B
- VPN Private IPs 10.222.4.0/24
- Other Device IP 10.222.4.1

HTTP and Ping from 10.222.48.20 --> 10.222.4.1 (Place A to Place B) is working, the opposite direction (10.222.4.1 -> 10.222.48.1) is not working.
I have try to create a "Policy Routing" using as interface the [vpn in] and allowing Any IP Group to Any IP Group but without success.

Does any body have success to a similar configuration?

  0      
  0      
#1
Options
1 Accepted Solution
Re:Allow access to Omada Controller Management portal from all VPN computers.-Solution
2024-03-06 14:51:26 - last edited 2024-03-07 01:59:17

  @Clive_A 

Hi,


I believe I have figured out where the problem lies.
Just for the record, the VPN server I connect to is based on Layer 2 packets and not Layer 3. Probably, I need L2TPv3, which is currently not supported by the router.
 

Thank you anyway.

Recommended Solution
  0  
  0  
#3
Options
2 Reply
Re:Allow access to Omada Controller Management portal from all VPN computers.
2024-03-04 05:46:41

Hi @Techfreak 

Thanks for posting in our business forum.

A to B works which already implies the tunnel is up and running and communication works. This means nothing wrong with the router or the VPN(tunnel).

B to A does not work which indicates you might ping the wrong IP address or firewall blocks it.

If you can ping the gateway IP address over the tunnel, that means a successful connection. And that's the conclusion to your issue. You need to move on and check your firewall of the IP you tried to ping.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  0  
  0  
#2
Options
Re:Allow access to Omada Controller Management portal from all VPN computers.-Solution
2024-03-06 14:51:26 - last edited 2024-03-07 01:59:17

  @Clive_A 

Hi,


I believe I have figured out where the problem lies.
Just for the record, the VPN server I connect to is based on Layer 2 packets and not Layer 3. Probably, I need L2TPv3, which is currently not supported by the router.
 

Thank you anyway.

Recommended Solution
  0  
  0  
#3
Options