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