Hi bls
I'm afraid I can't remember the exact details now as I've done so much debugging the initial attempt seems like an age ago now. Needless to say I checked all the conf files for any references to the orginal ip address. I have them all as sym links in a 'working directory', because I've got unbound tied in and I'm making pihole available over wifi with hostapt and dnsmasq etc. After that I changed the interface file and moved the pi box to the new subnet. Then I ran 'pihole -r' and it failed first time, which I eventually discovered was due to the strange ip assignment.
It took me a while to do the packet trace and find the problem because I had ssh'ed onto the Pi box to run the 'pihole -r' and so would hardly suspect such a strange problem when my ssh connection was working fine. It still strikes me as strange that the return packets to an externally initiated connection are addressed correctly but packet associated with out going connections initiated from the Pi box have the wrong address. It seems like the Pi has a split stack. I did wonder if network namespaces might be involved? But why non-related traffic would be routed through a namespace initiated by, presumably pihole, is anyones guess.
Apart from checking all the relevent conf files and network related files I've also run grep against everything within /etc/, including the contents of all subdirectories. The only hit I got was against the binary file /etc/pihole/pihole-FTL.db. I assume this file gets rebuilt at the end of a successful run of 'pihole -r'.
This is an assumption but I need something like this to explan the tie-in between pihole and the network behaviour. Obvously it also requires some tying into a part of the network layer/interface by pihole. Given there is no obvious reason why a string embeded within /etc/pihole/pihole-FTL.db would affect the assignment of ip values to outgoing traffic.
Anyway I've now raised the issue with on pihole.net:
https://discourse.pi-hole.net/t/cannot- ... bnet/70414
Maybe they can shed some light on this.
I've checked 'ip route' and it returns:
default via 192.168.0.1 dev eth0 onlink
10.42.0.0/24 dev wlan0 proto kernel scope link src 10.42.0.10
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.117
Thanks for all your time and help.
I'm afraid I can't remember the exact details now as I've done so much debugging the initial attempt seems like an age ago now. Needless to say I checked all the conf files for any references to the orginal ip address. I have them all as sym links in a 'working directory', because I've got unbound tied in and I'm making pihole available over wifi with hostapt and dnsmasq etc. After that I changed the interface file and moved the pi box to the new subnet. Then I ran 'pihole -r' and it failed first time, which I eventually discovered was due to the strange ip assignment.
It took me a while to do the packet trace and find the problem because I had ssh'ed onto the Pi box to run the 'pihole -r' and so would hardly suspect such a strange problem when my ssh connection was working fine. It still strikes me as strange that the return packets to an externally initiated connection are addressed correctly but packet associated with out going connections initiated from the Pi box have the wrong address. It seems like the Pi has a split stack. I did wonder if network namespaces might be involved? But why non-related traffic would be routed through a namespace initiated by, presumably pihole, is anyones guess.
Apart from checking all the relevent conf files and network related files I've also run grep against everything within /etc/, including the contents of all subdirectories. The only hit I got was against the binary file /etc/pihole/pihole-FTL.db. I assume this file gets rebuilt at the end of a successful run of 'pihole -r'.
This is an assumption but I need something like this to explan the tie-in between pihole and the network behaviour. Obvously it also requires some tying into a part of the network layer/interface by pihole. Given there is no obvious reason why a string embeded within /etc/pihole/pihole-FTL.db would affect the assignment of ip values to outgoing traffic.
Anyway I've now raised the issue with on pihole.net:
https://discourse.pi-hole.net/t/cannot- ... bnet/70414
Maybe they can shed some light on this.
I've checked 'ip route' and it returns:
default via 192.168.0.1 dev eth0 onlink
10.42.0.0/24 dev wlan0 proto kernel scope link src 10.42.0.10
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.117
Thanks for all your time and help.
Statistics: Posted by 101charlie — Wed May 29, 2024 4:24 am