F5F Stay Refreshed Power Users Networks Set up your home network, Pi-hole and VPN connections smoothly.

Set up your home network, Pi-hole and VPN connections smoothly.

Set up your home network, Pi-hole and VPN connections smoothly.

Pages (2): 1 2 Next
B
Burritozilla
Junior Member
17
11-22-2016, 09:02 PM
#1
I adjusted my network setup this way to cover the entire house: Modem at 192.168.0.1 connects via cable to WAN Router1, which then links to LAN Router2 at 192.168.1.2. Both routers share the same SSID and everything functions properly. However...

1. Pi-hole is currently set on the 192.168.1.0 network and acts as DNS for both routers, while the modem relies on the ISP DNS. Would linking Pi-hole directly to the modem be beneficial? It shouldn’t change much.
2. The ISP modem supports an ISP VPN that works well, but with the present setup I’m limited to 192.168.0.0 via the modem and can’t reach the router’s LAN (192.168.1.0). Should I configure the modem and Router1 to access the 192.168.1.1 network through the VPN? Thanks!
B
Burritozilla
11-22-2016, 09:02 PM #1

I adjusted my network setup this way to cover the entire house: Modem at 192.168.0.1 connects via cable to WAN Router1, which then links to LAN Router2 at 192.168.1.2. Both routers share the same SSID and everything functions properly. However...

1. Pi-hole is currently set on the 192.168.1.0 network and acts as DNS for both routers, while the modem relies on the ISP DNS. Would linking Pi-hole directly to the modem be beneficial? It shouldn’t change much.
2. The ISP modem supports an ISP VPN that works well, but with the present setup I’m limited to 192.168.0.0 via the modem and can’t reach the router’s LAN (192.168.1.0). Should I configure the modem and Router1 to access the 192.168.1.1 network through the VPN? Thanks!

M
MLGGirl54
Senior Member
258
11-22-2016, 10:11 PM
#2
You might want to give it a shot and see what happens. You could also experiment with other values. A double ending seems unnecessary to me. Because the part behind DNS isn't routable, it probably won't matter much. 169.244…? I don’t recall that number.
M
MLGGirl54
11-22-2016, 10:11 PM #2

You might want to give it a shot and see what happens. You could also experiment with other values. A double ending seems unnecessary to me. Because the part behind DNS isn't routable, it probably won't matter much. 169.244…? I don’t recall that number.

M
mrpig89
Junior Member
4
11-23-2016, 06:03 AM
#3
You're wondering if using a pihole as your DNS for your internal network instead of the ISP's DNS would affect blocking or tracking, and why switching network numbers might help. The benefit lies in choosing a more private DNS server that isn't tied to your ISP, potentially improving privacy and avoiding certain restrictions.
M
mrpig89
11-23-2016, 06:03 AM #3

You're wondering if using a pihole as your DNS for your internal network instead of the ISP's DNS would affect blocking or tracking, and why switching network numbers might help. The benefit lies in choosing a more private DNS server that isn't tied to your ISP, potentially improving privacy and avoiding certain restrictions.

_
_SiebePlayz_
Junior Member
40
11-24-2016, 02:41 PM
#4
It doesn't really matter much (as long as your ISP's DNS is included in your pihole), though visiting sites might be slower. A DNS lookup will first reach your pihole and then your ISP.
_
_SiebePlayz_
11-24-2016, 02:41 PM #4

It doesn't really matter much (as long as your ISP's DNS is included in your pihole), though visiting sites might be slower. A DNS lookup will first reach your pihole and then your ISP.

Y
YouseyHD
Member
154
11-24-2016, 04:41 PM
#5
You set up your modem routing to allow the network 192.168.1.0/24 via the wan router's IP in the 192.168.0.0/24 range. When you connect through a VPN, packets reach 192.168.0.0 and function properly because the modem recognizes it. However, if you send a packet to 192.168.1.0, the modem questions its origin and drops the packet.
Y
YouseyHD
11-24-2016, 04:41 PM #5

You set up your modem routing to allow the network 192.168.1.0/24 via the wan router's IP in the 192.168.0.0/24 range. When you connect through a VPN, packets reach 192.168.0.0 and function properly because the modem recognizes it. However, if you send a packet to 192.168.1.0, the modem questions its origin and drops the packet.

D
Donald_Trumpz
Member
246
11-24-2016, 04:57 PM
#6
You can use a static route, but make sure the target network is correctly configured and the router IP matches the device you want to reach. Double-check that the forwarding mode is set properly and there are no conflicting rules.
D
Donald_Trumpz
11-24-2016, 04:57 PM #6

You can use a static route, but make sure the target network is correctly configured and the router IP matches the device you want to reach. Double-check that the forwarding mode is set properly and there are no conflicting rules.

L
181
12-13-2016, 06:23 AM
#7
You're looking to set up a static IP using CMD. Do you have a fixed IP from your ISP? If not, both your modem and router will assign DHCP addresses. You should be able for clients to communicate through the router, which isn't the modem.
L
LePoteDuQuebec
12-13-2016, 06:23 AM #7

You're looking to set up a static IP using CMD. Do you have a fixed IP from your ISP? If not, both your modem and router will assign DHCP addresses. You should be able for clients to communicate through the router, which isn't the modem.

C
celiphia
Junior Member
22
12-14-2016, 08:02 AM
#8
You need to instruct your device to route traffic destined for 192.168.1.0 via the VPN to the 192.168.0.0 network. It appears your computer is discarding packets because it doesn’t understand the destination address.
C
celiphia
12-14-2016, 08:02 AM #8

You need to instruct your device to route traffic destined for 192.168.1.0 via the VPN to the 192.168.0.0 network. It appears your computer is discarding packets because it doesn’t understand the destination address.

T
traucht13
Junior Member
45
12-14-2016, 04:46 PM
#9
I don’t have a fixed IP address from my internet provider, though I’m using DynDNS together with a VPN that’s functioning. Yes, devices can communicate with one another, but when trying to connect through the VPN, I’m only able to see the modem network and not reach other clients.
T
traucht13
12-14-2016, 04:46 PM #9

I don’t have a fixed IP address from my internet provider, though I’m using DynDNS together with a VPN that’s functioning. Yes, devices can communicate with one another, but when trying to connect through the VPN, I’m only able to see the modem network and not reach other clients.

H
howitis1
Member
55
12-15-2016, 09:10 PM
#10
Check if it's feasible to reach all clients through VPN connections on the two routers.
H
howitis1
12-15-2016, 09:10 PM #10

Check if it's feasible to reach all clients through VPN connections on the two routers.

Pages (2): 1 2 Next