- User Since
- Mar 22 2019, 7:24 PM (246 w, 2 d)
Feb 13 2023
Feb 6 2023
Jan 28 2023
Dec 3 2022
Nov 22 2022
@trae32566 My apologies for the inconveniences. You are right. The criteria for triggering this action shall be narrowed down further.
It would be necessary to issue the warning if and only if such colliding peers also specify the exact same remote endpoint addresses (with empty endpoints also being accounted as to be the same).
In other words, we need to identify incoming peers and apply the rule only to them, not the outgoing ones which already have specific remote endpoint addresses statically defined.
Oct 27 2022
Oct 26 2022
Oct 20 2022
Apr 17 2021
Oct 21 2020
Oct 19 2020
This is an example scenario in which this comes handy:
You have three ethernet interfaces
Two are connected to different LANs
The third is connected to WAN (another router)
All networks offer DHCP and def gw
The LANs offer it for internet access
The WAN offers it for branch access
We want to keep def gw received for WAN and ignore internet access offered by those LANs