Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Settings DNS server adds a static route
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-06-28
01:05 AM
2015-06-28
01:05 AM
Settings DNS server adds a static route
Using ReadyNas 6.2.4 (latest as of today)
We have the ReadyNas box on a LAN
- RN = 10.1.1.10/24
- router = 10.1.1.1
We access from time to time, settings etc... the box from a VPN:
- VPN server = 10.1.1.2
- TUN network = 10.0.100.0/24
- TUN host (other end) = 10.0.100.100 (and also DNS server at times)
In order for the RN to "see" the TUN on VPN server, we add a static route via the RN interface Network/Routes to ensure routing from RN to VPN for the TUN network works
- 10.0.100.0/24 => via VPN server (10.1.1.2)
Then remotely, from the other end of the VPN, we can see the RN successfully, and reversely the RN see the other end of the VPN.
Great!
However to perform some tests and other configurations, we had to set a DNS server on the TUN host (the other end), 10.0.100.100, and then set that DNS server on the RN:
- in Network/Links/eth0 (only one interface), DNS
But for some mysterious reasons, the RN added automatically a static route to 10.0.100.100 via 10.1.1.1 (the LAN router!), being more specific, made the RN try to reach the TUN host via the LAN router (10.1.1.1) instead of via the VPN server (10.1.1.2) as it did before, and the LAN router doesn't know (and must not know) the VPN network (10.0.100.0/24).
Before adding the DNS server, the RN routing table showed
and after
Bug or feature?
We have the ReadyNas box on a LAN
- RN = 10.1.1.10/24
- router = 10.1.1.1
We access from time to time, settings etc... the box from a VPN:
- VPN server = 10.1.1.2
- TUN network = 10.0.100.0/24
- TUN host (other end) = 10.0.100.100 (and also DNS server at times)
In order for the RN to "see" the TUN on VPN server, we add a static route via the RN interface Network/Routes to ensure routing from RN to VPN for the TUN network works
- 10.0.100.0/24 => via VPN server (10.1.1.2)
Then remotely, from the other end of the VPN, we can see the RN successfully, and reversely the RN see the other end of the VPN.
Great!
However to perform some tests and other configurations, we had to set a DNS server on the TUN host (the other end), 10.0.100.100, and then set that DNS server on the RN:
- in Network/Links/eth0 (only one interface), DNS
But for some mysterious reasons, the RN added automatically a static route to 10.0.100.100 via 10.1.1.1 (the LAN router!), being more specific, made the RN try to reach the TUN host via the LAN router (10.1.1.1) instead of via the VPN server (10.1.1.2) as it did before, and the LAN router doesn't know (and must not know) the VPN network (10.0.100.0/24).
Before adding the DNS server, the RN routing table showed
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
10.0.100.0 10.1.1.2 255.255.255.0 UG 0 0 0 eth0
10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
and after
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
10.0.100.0 10.1.1.2 255.255.255.0 UG 0 0 0 eth0
10.0.100.100 10.1.1.1 255.255.255.255 UGH 0 0 0 eth0
10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
Bug or feature?
Message 1 of 1