Setting up the device out of the box is really easy if you're going for a simple SFP to IPv4 Switched Network, the template takes care of everything. Offcourse the pfSense config is corresponding with the config bellow as the connection worked. Solution - (hyphen): The VPN tunnel is active, and the VPN monitor optional feature is not configured. I initially bought the EdgeRouter X SFP to replace my Bell Home Hub 3000, as I was trying to setup an IPv6in4 tunnel, and the Bell router has a habit of locking itself up when attempting to do so. Whats the cause and how can i solve this? We need reliable VPN connections and if they are disconnected for really short period that they at least need to reconnect automatically! Use the CLI from the Edgerouter to configure the OpenVPN with the following commands Your VPN configured on network 192.168.200.0/24. Reconfiguring the IPSec connection in pfSense (No reboot yet as this will pull down our whole network.įor now we have around 3 "broken" connections of the 30-35 connections. Because the Edgerouter webconsole is alo on 443, i will change the webconsole to port 4443.Deleting the IPSec settings on the Edgerouter and re-configure IPsec on the edgerouter followed by a reboot as it still didn't work.Hard restart by unplug the power and reconnect it.Restart Ubitquiti Edgerouter via UNMS (centralized management tool).Nothing has changed to the config, neither on the Edgerouter X nor in pfSense Also no firmware updates are installed or reboots happened. I don't understand what happens here as this specific connection worked fine and stable for months. I can see in pfSense (System logs / IPsec) that the Edgerouter tries to connect to pfSense. In general the connections are stable and everything is working fine and like expected, though some times a connection is lost "randomly" and doensn't come back. It does this by pinging a internal ip on our office site once every minute. then Network Options and check Allow Teredo tunnels Filtering Teredo Teredo is an. The Edgerouter X always establishes the connection as we not always have the possibility to forward ports on the customer network(s). Then check to see if Server connectivity no longer shows Blocked. Configure outbound NAT For site B to reach the Internet, site A must perform outbound NAT on the traffic from the site B LAN ( 10.5.0.0/24) as it leaves the WAN.
At the office we use pfSense V2.4.5 as VPN gateway and placing Ubiquiti Edgerouter X devices with the latest firmware on the customer sites to establish the connection with. We have tens of IPSec connections between our office and customer sites.
0 kommentar(er)
