This morning I re-installed a pi-hole and I'm trying to set up my raspberry as a Linux router.
Here's my home network:
[InternetRouter] <--------------------------> [PiHole] <--------------------------> [Wifi-Router]
[192.168.1.1/24] [wan: 192.168.1.2/24] -------- [lan: 192.168.2.1/24] [192.168.2.2]
The Pi has 3 network interfaces, eth0, wlan0 and the USB ethernet adapter eth1.
I disabled the wlan0 interface, because I don't need it. In order to do so, edit the /boot/config.txt and add a line: dtoverlay=disable-wifi. You may also disable bluetooth radio by adding: dtoverlay=disable-bt
Then, in order to help identifying those NICs, I created this file: /etc/udev/rules.d/10-network.rules
I thought you had your Pi listening and routing on the same port and address.
So what you did was lie to the Pi and tell it the LAN side of your ISP gateway/router was WAN then told your pi-Router to treat that traffic as WAN?
I'm, fairly, sure if you switch the wireless router to AP mode, it will allow you to assign an IP address. Especially since the device in front of it is, essentially, the gateway as it sees the network.
Yeah, but you labeled it as wan and I noticed it was a local IP address and I assumed ETH1 was just for the WIFI router and I did not understand you had isolated the two; I thought you had somehow gotten the PI to see all that with one connection because I was caught up with another thread that was trying to do the same thing on one port and their wifi on Starlink.
I still do not understand how DNS requests from 192.168.2.x are getting routed by 192.168.1.0 but after reading your posts, a few times, I'm guessing you are using MASQUERADE and PREROUTING to make it happen.
I get the concept, but my Linux is not that good.
I linked to your post and just started asking questions.