| 1 |
On 05/22/2013 01:36 PM, Michael Orlitzky wrote: |
| 2 |
> On 05/22/13 12:36, Samuraiii wrote: |
| 3 |
>> Hello, |
| 4 |
>> |
| 5 |
>> I am trying to get hostname address resolution on my LAN and VPN with |
| 6 |
>> one serious problem: |
| 7 |
>> I have two "networks" eg. 10.1.1.0 and 10.2.2.0 which are representing |
| 8 |
>> local address space for LAN (10.1.1.0/8) and VPN address space (10.2.2.0/8). |
| 9 |
> This isn't two networks, it's one network and you've got the VPN space |
| 10 |
> overlapping the LAN space. To oversimplify a little, Don't Do That. |
| 11 |
> |
| 12 |
> Use a separate subnet for the VPN. Then traffic to the VPN will be |
| 13 |
> routed over the VPN interface as intended, but traffic to the LAN will |
| 14 |
> be routed over the LAN interface. This is what you want, but right now |
| 15 |
> the VPN and the LAN are the same network, so "routing to the LAN" is the |
| 16 |
> same as "routing to the VPN", and your network stack doesn't know what |
| 17 |
> to do with it. |
| 18 |
> |
| 19 |
> |
| 20 |
|
| 21 |
To be clear, replacing /8 with /24 would do this: |
| 22 |
|
| 23 |
10.1.1.0/8, as a "network", is really just 10.0.0.0/8. This is also true |
| 24 |
of 10.2.2.0/8. The bits after the first 8 are irrelevant, since a /8 is |
| 25 |
being used. Use /24 instead, in this case. |
| 26 |
|
| 27 |
It would be good for Samuraiii to read up: |
| 28 |
|
| 29 |
http://www.tcpipguide.com/free/t_IPAddressing.htm |
Archives