I did this, but it seems to have no effect.What seems to have an effect is turning this routing rule on or off:
So "locally", instead of:
vlan50-HOME <-> public IP (input)
I want:
vlan50-HOME <-> 192.168.1.1 <-forward-> CGNAT IP <-> pppoe-WAN <-> Internet <-> LTE-WAN <-> public IP (input)
Code:
routing rule add action=lookup-only-in-table src-address=███.███.███.███/32 table=wan-public- When it's off, the WireGuard connection works locally but not remotely, and it doesn't even use pppoe-WAN or LTE-WAN interfaces. The router gets a packet from vlan50-HOME and responds directly to vlan50-HOME as the public IP. This is not what I want.
- When it's on, The WireGuard connection works remotely but not locally. This is acceptable and was the situation until now, but I want to get it to work both remotely and (semi) locally, with the communication passing through the LTE connection in both cases.
So "locally", instead of:
vlan50-HOME <-> public IP (input)
I want:
vlan50-HOME <-> 192.168.1.1 <-forward-> CGNAT IP <-> pppoe-WAN <-> Internet <-> LTE-WAN <-> public IP (input)
Statistics: Posted by goscickiw — Sun Jan 21, 2024 8:14 pm