From 73620a6590f32d0626c766435be98a5eaf7be617 Mon Sep 17 00:00:00 2001 From: Erik Conijn Date: Thu, 14 May 2026 10:27:20 +0200 Subject: [PATCH] docs-pbr-1.2.2:Add warning for unknown gateway on device Added a warning about unknown gateway for devices when the uplink/WAN interface is down, explaining that it is usually transient and can be ignored if PBR restarts successfully. Signed-off-by: Erik Conijn --- pbr/1.2.2/README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/pbr/1.2.2/README.md b/pbr/1.2.2/README.md index b47796e..967b31f 100644 --- a/pbr/1.2.2/README.md +++ b/pbr/1.2.2/README.md @@ -103,6 +103,7 @@ - [Warning: Please set 'dhcp.lan.force=1'](#warning-please-set-dhcplanforce1) - [Warning: Internal Version Mismatch](#warning-internal-version-mismatch) - [Warning: Incompatible DHCP Option 6](#warning-incompatible-dhcp-option-6) + - [Warning: Unknown Gateway for device 'XX'](#warning-unknown-gateway-for-device-xx) - [Thanks](#thanks) @@ -1179,6 +1180,12 @@ If you have the matching versions of the `pbr` and `luci-app-pbr` installed you The `pbr` package now checks for incompatible DHCP Option 6 on start if resolver_set is used. +### Warning: Unknown Gateway for device 'XX' + +This usually is a transient warning and related to `WARNING: Uplink/WAN interface is still down, going back to boot mode`. +When an interface is not up there is no gateway, normally PBR will restart if the interface is up and the warning should be gone. +So you can ignore this warning if PBR restarts afterwards and the warning is gone. + ## Thanks I'd like to thank everyone who helped by providing testing and feedback on this service. Without contributions from [@hnyman](https://github.com/hnyman), [@dibdot](https://github.com/dibdot), [@danrl](https://github.com/danrl), [@tohojo](https://github.com/tohojo), [@cybrnook](https://github.com/cybrnook), [@nidstigator](https://github.com/nidstigator), [@AndreBL](https://github.com/AndreBL), [@dz0ny](https://github.com/dz0ny), [@tew42](https://github.com/tew42), [bogorad](https://forum.openwrt.org/u/bogorad), rigorous testing/bugreporting by [@dziny](https://github.com/dziny), [@bluenote73](https://github.com/bluenote73), [@buckaroo](https://github.com/pgera), [@Alexander-r](https://github.com/Alexander-r), [@n8v8R](https://github.com/n8v8R), [psherman](https://forum.openwrt.org/u/psherman), [@Vale-max](https://github.com/Vale-max), [@aliicex](https://github.com/aliicex), [dscpl](https://forum.openwrt.org/u/dscpl), [pesa1234](https://forum.openwrt.org/u/pesa1234) and multiple contributions from [@egc112](https://github.com/egc112), [@bigsmile74](https://github.com/bigsmile74), [@dl12345](https://github.com/dl12345) and [trendy](https://forum.openwrt.org/u/trendy) and feedback from other OpenWrt users it wouldn't have been possible. WireGuard/IPv6 support is courtesy of [IVPN](https://www.ivpn.net/).