Hopefully this is the right branch of the forum for this discussion.
Backstory: I'm a former AT&T customer who recently upgraded to sonic 10G fiber (woohoo!) In my old setup, I had a residential gateway, in addition to my tplink router which is less than two years old. I also had a pi-hole set up on the residential gateway's network, and pointed my tplink router to it to filter ad requests, etc. It worked great.
Transition to sonic, and the residential gateway went away, and got replaced with a modem. My tplink router won't allow me to specify a device on the lan as the DNS server. It also doesn't have any capability to set up a subnet. As a result the pi-hole is out of business.
I discovered that the modem has two ethernet ports on it. I have hardened my pi-hole, changed the default ssh port, and set up a firewall to ONLY talk to the public IP address of the other port on the modem. (IP address resolved via dynamic dns available through tplink.) I also verified that the pi-hole was completely functional on my lan by manually setting the DNS sever setting on one of my machines.
So, here's the rub. I can connect to the box via ssh (on the non-standard port.) I can see the pi-hole administration page (port 80.) I can not get a response from the box on port 53 on tcp or udp. SO, my question is, is sonic filtering inbound traffic on port 53?
I know I could resolve this by moving the pi-hole inside my router and setting it up as the DHCP server, but I lose some router functions by doing that, and I'm resisting.![Smile :)](images/smilies/xicon_e_smile.gif.pagespeed.ic.JIwIjWOCfZ.png)
Thanks!
Duane
Backstory: I'm a former AT&T customer who recently upgraded to sonic 10G fiber (woohoo!) In my old setup, I had a residential gateway, in addition to my tplink router which is less than two years old. I also had a pi-hole set up on the residential gateway's network, and pointed my tplink router to it to filter ad requests, etc. It worked great.
Transition to sonic, and the residential gateway went away, and got replaced with a modem. My tplink router won't allow me to specify a device on the lan as the DNS server. It also doesn't have any capability to set up a subnet. As a result the pi-hole is out of business.
I discovered that the modem has two ethernet ports on it. I have hardened my pi-hole, changed the default ssh port, and set up a firewall to ONLY talk to the public IP address of the other port on the modem. (IP address resolved via dynamic dns available through tplink.) I also verified that the pi-hole was completely functional on my lan by manually setting the DNS sever setting on one of my machines.
So, here's the rub. I can connect to the box via ssh (on the non-standard port.) I can see the pi-hole administration page (port 80.) I can not get a response from the box on port 53 on tcp or udp. SO, my question is, is sonic filtering inbound traffic on port 53?
I know I could resolve this by moving the pi-hole inside my router and setting it up as the DHCP server, but I lose some router functions by doing that, and I'm resisting.
![Smile :)](images/smilies/xicon_e_smile.gif.pagespeed.ic.JIwIjWOCfZ.png)
Thanks!
Duane