DISREGARD THIS THREAD; IT WAS MY FAULT:
OK, so I realised what it was. I completely forgot I had setup a convoluted NAT (to test something out a few weeks ago) on the internal router that NAT'd the destination host to a test DoH client in the DMZ. My bad! Tested from another non-172.16.150.0/24 host and expected result looks good:
Apr 7 15:55:12 kernel: [BLOCKED - OUTBOUND] IN=br0 OUT= SRC=192.168.150.178 DST=213.181.166.26 LEN=60 TOS=0)
Thanks for looking if you did
--
Hi,
I'm currently running Skynet v7.2.4 (19/03/2021) and have a question regarding it blocking connections. The router's LAN IP is 172.16.150.254 and there are multiple other networks (behind an internal router) that don't appear to have traffic blocked when a new IP block is applied via Skynet. I can confirm that one other host on the 172.16.150.0/24 network is blocked on Skynet but all other non-172.16.150.0/24 nets are allowed thru.
Router Model; RT-AC88U
Skynet Version; v7.2.4 (19/03/2021) (0380669c11572e222d1fd2f7531d7bfa)
iptables v1.4.15 - (eth0 @ 172.16.150.254)
ipset v6.32, protocol version: 6
IP Address; (aaa.bbb.c.d)
Any ideas on how to address this please?
Thanks
--
Edit: thought I'll paste what I typed a little further down for ease of first-time readers:
Hopefully this explains it a bit better:
When attempting connection to a blocked network/IP from the same network as the router's internal interface network (172.16.150.0/24)
Host on same net:
user@172.16.150.234:~$ telnet 213.181.166.26 53
Trying 213.181.166.26...
^C
Skynet logs:
Apr 6 20:31:47 kernel: [BLOCKED - OUTBOUND] IN=br0 OUT= SRC=172.16.150.234 DST=213.181.166.26 LEN=60 TOS=0)
Works as expected.
Host on a diff internal net:
user@192.168.150.50:~$ telnet 213.181.166.26 53
Trying 213.181.166.26...
Connected to 213.181.166.26.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
Does not work as expected.
See what I mean?
OK, so I realised what it was. I completely forgot I had setup a convoluted NAT (to test something out a few weeks ago) on the internal router that NAT'd the destination host to a test DoH client in the DMZ. My bad! Tested from another non-172.16.150.0/24 host and expected result looks good:
Apr 7 15:55:12 kernel: [BLOCKED - OUTBOUND] IN=br0 OUT= SRC=192.168.150.178 DST=213.181.166.26 LEN=60 TOS=0)
Thanks for looking if you did
--
Hi,
I'm currently running Skynet v7.2.4 (19/03/2021) and have a question regarding it blocking connections. The router's LAN IP is 172.16.150.254 and there are multiple other networks (behind an internal router) that don't appear to have traffic blocked when a new IP block is applied via Skynet. I can confirm that one other host on the 172.16.150.0/24 network is blocked on Skynet but all other non-172.16.150.0/24 nets are allowed thru.
Router Model; RT-AC88U
Skynet Version; v7.2.4 (19/03/2021) (0380669c11572e222d1fd2f7531d7bfa)
iptables v1.4.15 - (eth0 @ 172.16.150.254)
ipset v6.32, protocol version: 6
IP Address; (aaa.bbb.c.d)
Any ideas on how to address this please?
Thanks
--
Edit: thought I'll paste what I typed a little further down for ease of first-time readers:
Hopefully this explains it a bit better:
When attempting connection to a blocked network/IP from the same network as the router's internal interface network (172.16.150.0/24)
Host on same net:
user@172.16.150.234:~$ telnet 213.181.166.26 53
Trying 213.181.166.26...
^C
Skynet logs:
Apr 6 20:31:47 kernel: [BLOCKED - OUTBOUND] IN=br0 OUT= SRC=172.16.150.234 DST=213.181.166.26 LEN=60 TOS=0)
Works as expected.
Host on a diff internal net:
user@192.168.150.50:~$ telnet 213.181.166.26 53
Trying 213.181.166.26...
Connected to 213.181.166.26.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
Does not work as expected.
See what I mean?
Last edited: