ER707-M2 upgrade to 1.4.1 Build 20260325 Rel.78146 can't see remote site, WireGuard VPN broken

ER707-M2 upgrade to 1.4.1 Build 20260325 Rel.78146 can't see remote site, WireGuard VPN broken

ER707-M2 upgrade to 1.4.1 Build 20260325 Rel.78146 can't see remote site, WireGuard VPN broken
ER707-M2 upgrade to 1.4.1 Build 20260325 Rel.78146 can't see remote site, WireGuard VPN broken
5 hours ago - last edited 3 hours ago
Model: ER707-M2  
Hardware Version: V1
Firmware Version: 1.4.1 Build 20260325 Rel.78146

Hello,

 

I have an ER707-M2 router setup with a site to site vpn to a ER7412-M2.  I upgraded to the latest stable firmware on the ER707 (ER7412-M2).  The VPN has stopped working.  

 

Interestingly, I have 2 software controllers setup.  One at each site.  They can no longer see the other site at all.  This is probably the issue. I haven't changed anythig except the firmware.  Any ideas where to start to fix this?

 

Thanks!

  0      
  0      
#1
Options
1 Accepted Solution
Re:ER707-M2 upgrade to 1.4.1 Build 20260325 Rel.78146 can't see remote site, WireGuard VPN broken-Solution
4 hours ago - last edited 3 hours ago

Ok, i believe I have solved the problem.  

 

  • It looks like the ability to have spaces in any name field, peers included, has been removed.  First thing I had to do was replace all the spaces with underscores.
  • On the side with the ER707-M2, there is now a setting in the Site-to-site VPN called "Network".  This was set to 0.0.0.0/0.  Changing this from "Custom IP" to "Network" seems to have fixed the problem.

 

Hope this helps someone.

 

 

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:ER707-M2 upgrade to 1.4.1 Build 20260325 Rel.78146 can't see remote site, WireGuard VPN broken-Solution
4 hours ago - last edited 3 hours ago

Ok, i believe I have solved the problem.  

 

  • It looks like the ability to have spaces in any name field, peers included, has been removed.  First thing I had to do was replace all the spaces with underscores.
  • On the side with the ER707-M2, there is now a setting in the Site-to-site VPN called "Network".  This was set to 0.0.0.0/0.  Changing this from "Custom IP" to "Network" seems to have fixed the problem.

 

Hope this helps someone.

 

 

Recommended Solution
  0  
  0  
#2
Options