06-22-2023, 02:58 AM
Good day,
I have been testing the L2TP setup for the Yealink.
Our firewall (fortigate) is hosting the L2TP services.
From the firewall we have the L2T.Root interface using IP 172.24.0.1 and DHCP enabled which adds the Option 121 feature and 33 with the same 10.2.0.0/24 172.24.0.1 route (which works perfectly on Windows)
but when the Yealink uses the same VPN and same account. It cannot see 10.2.0.0/24.
I can ping 172.24.0.1 but cannot ping the PBX located on 10.2.0.0/24
Firewall wise I know is setup correct as we can use it with our windows machine without problems. When I do route print in the command prompt it shows the route added by the vpn tunnel to 10.2.0.0/24 and I can ping any of the systems on the network and vice versa.
I also opened a ticket with Yealink originally about this but couldn't figure out.
I have been testing the L2TP setup for the Yealink.
Our firewall (fortigate) is hosting the L2TP services.
From the firewall we have the L2T.Root interface using IP 172.24.0.1 and DHCP enabled which adds the Option 121 feature and 33 with the same 10.2.0.0/24 172.24.0.1 route (which works perfectly on Windows)
but when the Yealink uses the same VPN and same account. It cannot see 10.2.0.0/24.
I can ping 172.24.0.1 but cannot ping the PBX located on 10.2.0.0/24
Firewall wise I know is setup correct as we can use it with our windows machine without problems. When I do route print in the command prompt it shows the route added by the vpn tunnel to 10.2.0.0/24 and I can ping any of the systems on the network and vice versa.
I also opened a ticket with Yealink originally about this but couldn't figure out.