Lost my link between the units after upgrading to 7.1.2, anyone else seen that?
I checked my WAN IPs and public keys, nothing changed.
Both sides have a public ip address directly assigned to them ?
If not, try to toggle the peer from disabled to enabled.
Thanks but that did not help.
Both side are sending data
What is odd is that torch on wireguard1 on the remote router shows a non existent IP, 192.168.100.240, trying to reach one of my PCs.
My printer use to be 192.168.100.240 but I changed all IPs at my remote site to 192.168.200.xxx so wireguard would work.
The ARP table does not show 192.168.100.240, it’s not in the lease table and I can’t ping it
Wireguard will always try to send.
It is only when it receives, then you’ll know it works.
It worked before, right ?
What happens if you go back to previous version ?
What else did you change (since you mention change of IP subnet) ? What was changed to what ?
I don’t recall changing anything, it did work before, I was able to use file explorer from the main site and see the NAS at the remote by using
\192.168.200.25 from the 192.168.100.0 network.
I’m at the remote site and will revert back but will wait and do the main site when I get back next week. I did a brief glance at the backup file I made before the upgrade and don’t see any differences. I removed and reinstalled the wireguard interface and still don’t connect.
/export hide-sensitive file=anynameyouwish
Post current config for both sites between code quotes.
Make sure to review those configs so no public info slips through.
This rule was blocking wireguard from working.
;;; defconf: drop all from WAN not DSTNATed
chain=forward action=drop connection-state=new connection-nat-state=!dstnat in-interface-list=WAN log=no log-prefix=“”
so I put this in just above it
chain=forward action=accept src-address=10.0.0.0/24 in-interface=wireguard1 log=no log-prefix=“”
It’s working now, are they any negatives to doing this?
Can work like that.
What interface list is your wg connection in ?