I’m connecting a repeater to the Internet-connected Opal. Because the Opal is already doing NAT (masquerading) I shouldn’t need to do another NAT on the repeater, therefore I did the wireless connection and created static routes pointing to each other’s LAN (and I can successfully ping each other’s LAN). In fact, I used to do the same with an old OpenWrt router and it worked fine, but now I’m using the SFT1200, my log get filled with warnings:
Wed Feb 21 06:25:00 2024 cron.info crond[2212]: USER root pid 18708 cmd . /lib/functions/modem.sh;check_ip
Wed Feb 21 06:25:00 2024 cron.info crond[2212]: USER root pid 18709 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Wed Feb 21 06:25:01 2024 kern.warn kernel: [32417.491521] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 853f0700
Wed Feb 21 06:25:01 2024 kern.warn kernel: [32417.979615] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 853f0800
Wed Feb 21 06:25:10 2024 kern.warn kernel: [32427.296240] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 853f0a00
Wed Feb 21 06:25:13 2024 kern.warn kernel: [32430.262763] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 83416700
Wed Feb 21 06:25:21 2024 kern.warn kernel: [32437.744894] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 853f0900
Wed Feb 21 06:25:26 2024 kern.warn kernel: [32443.295158] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24900
Wed Feb 21 06:25:28 2024 kern.warn kernel: [32444.583440] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24c00
Wed Feb 21 06:25:28 2024 kern.warn kernel: [32444.646844] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 83416300
Wed Feb 21 06:25:30 2024 kern.warn kernel: [32447.267198] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24200
Wed Feb 21 06:25:34 2024 kern.warn kernel: [32450.697491] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24400
Wed Feb 21 06:25:34 2024 kern.warn kernel: [32450.794092] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24f00
Wed Feb 21 06:25:34 2024 kern.warn kernel: [32450.801700] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24e00
Wed Feb 21 06:25:34 2024 kern.warn kernel: [32451.035040] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24300
Wed Feb 21 06:25:36 2024 kern.warn kernel: [32452.678476] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24000
Wed Feb 21 06:25:36 2024 kern.warn kernel: [32452.686074] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24900
Wed Feb 21 06:25:43 2024 kern.warn kernel: [32459.374498] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 853f0700
Wed Feb 21 06:25:43 2024 kern.warn kernel: [32460.007449] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24400
Wed Feb 21 06:25:48 2024 kern.warn kernel: [32464.393571] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24f00
Wed Feb 21 06:25:56 2024 kern.warn kernel: [32472.684365] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 853f0700
Wed Feb 21 06:25:57 2024 kern.warn kernel: [32473.581264] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24f00
Wed Feb 21 06:25:58 2024 kern.warn kernel: [32475.265243] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 83416100
Wed Feb 21 06:26:00 2024 cron.info crond[2212]: USER root pid 21074 cmd . /lib/functions/modem.sh;check_ip
Wed Feb 21 06:26:00 2024 cron.info crond[2212]: USER root pid 21076 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Wed Feb 21 06:26:08 2024 kern.warn kernel: [32484.426636] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24d00
Wed Feb 21 06:26:17 2024 daemon.info dnscrypt-proxy[1892]: dnscrypt-proxy Refetching server certificates
Wed Feb 21 06:26:21 2024 kern.warn kernel: [32497.683715] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24200
Wed Feb 21 06:26:21 2024 kern.warn kernel: [32497.691427] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24e00
Wed Feb 21 06:26:29 2024 kern.warn kernel: [32505.656902] [hnat error]SUBNET error, sip 192.168.10.132 bypass flow 85f24000
I think the NAT or Firewall on the Opal is complaining about Source IP addresses (192.168.10.x) not part of the IP segment defined for its LAN (192.168.8.x), which shouldn’t be reported as a warning. I think the rule should check the source interface, not the source IP, unless the User specifically ask for it.
The workaround is to do double NAT, but I would prefer to do routing instead of that. Is there something you could do about it? In the meantime, is there something I could do to avoid rising these messages?