RRAS to connect VLAN to physical LAN?

I need to connect a 2003 VLAN to a 2003 physical LAN.
They are on different subnets, both LANs use static IP addresses.
Both are AD domains, are small (< 10 users), and at 2003 funtionality at the
Forest(?) level.

I'm a SQL guy, not a networking guy, so please bear that in mind.

RRAS seems like a good solution, but I'm having trouble finding details on
how
to accomplish this task. Any pointers to a good resource would be most
welcome.

TIA!

"dj" <(E-Mail Removed)> wrote in message
news:2B15CB10-249D-419E-8EE4-(E-Mail Removed)...
> I need to connect a 2003 VLAN to a 2003 physical LAN.
> They are on different subnets, both LANs use static IP addresses.
> Both are AD domains, are small (< 10 users), and at 2003 funtionality at
> the
> Forest(?) level.
>
> I'm a SQL guy, not a networking guy, so please bear that in mind.
>
> RRAS seems like a good solution, but I'm having trouble finding details on
> how
> to accomplish this task. Any pointers to a good resource would be most
> welcome.
>
> TIA!

Simply installing a router, RRAS or anything else, doesn't mean that
the networks can talk to each other. Unfortunately it is not as simple as
that. You may need an extensive change to your network, or it may be fairly
simple. There is no way to tell without a lot more info on how the networks
are currently configured.

The only time IP routing "just works" is if both subnets use the router
as their default gateway and there is no connection to other networks. eg

192.168.1.x dg 192.168.1.1
|
192.168.1.1 dg blank
router
192.168.21.1 dg blank
|
192.168.21.x dg 192.168.21.1

If either network connects to other networks such as the Internet it
needs more work to get it going.

Thanks for the replies.

Here's the current configuration:
(hope the formatting is retained in the post)
VLAN
Name IP Mask DG DNS Remarks
VM1 10.1.1.1 255.255.255.0 10.1.1.1 10.1.1.1 Domain Controller (2003)
VM2 10.1.1.2 255.255.255.0 10.1.1.1 10.1.1.1 Member server
VM3 10.1.1.3 255.255.255.0 10.1.1.1 10.1.1.1 Member server


Physical LAN
Name IP Mask DG DNS Remarks
PServer 10.0.0.200 255.255.255.0 10.0.0.1 10.0.0.200 Domain Controller
(2003)
Desk1 10.0.0.20 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
Desk2 10.0.0.22 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
....
Desk10 10.0.0.40 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop

Other details:
Router to connect to internet is 10.0.0.1

PServer has one (physical) NIC installed.
All VMs have one logical NIC installed.

Objective: allow network traffic between VLAN and physical LAN.
No network traffic restrictions between the two are needed.

Thank you.


"Bob Lin (MS-MVP)" wrote:

> We need more information to help. Do you have a multihomed computer as RRAS
> server? If yes, sure you can enable RRAS to router between two LANs.
>
> However, since this is VLAN, you don't need a RRAS server to connect these
> two LANs. In our school, we have 3 VLANs, public, student and staff. We
> connect them by doing port forwarding accordingly.
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "dj" <(E-Mail Removed)> wrote in message
> news:2B15CB10-249D-419E-8EE4-(E-Mail Removed)...
> >I need to connect a 2003 VLAN to a 2003 physical LAN.
> > They are on different subnets, both LANs use static IP addresses.
> > Both are AD domains, are small (< 10 users), and at 2003 funtionality at
> > the
> > Forest(?) level.
> >
> > I'm a SQL guy, not a networking guy, so please bear that in mind.
> >
> > RRAS seems like a good solution, but I'm having trouble finding details on
> > how
> > to accomplish this task. Any pointers to a good resource would be most
> > welcome.
> >
> > TIA!
>

"dj" <(E-Mail Removed)> wrote in message
news:006AFD84-365C-42B0-98CB-(E-Mail Removed)...
> Thanks for the replies.
>
> Here's the current configuration:
> (hope the formatting is retained in the post)
> VLAN
> Name IP Mask DG DNS Remarks
> VM1 10.1.1.1 255.255.255.0 10.1.1.1 10.1.1.1 Domain Controller (2003)
> VM2 10.1.1.2 255.255.255.0 10.1.1.1 10.1.1.1 Member server
> VM3 10.1.1.3 255.255.255.0 10.1.1.1 10.1.1.1 Member server
>
>
> Physical LAN
> Name IP Mask DG DNS Remarks
> PServer 10.0.0.200 255.255.255.0 10.0.0.1 10.0.0.200 Domain
> Controller
> (2003)
> Desk1 10.0.0.20 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
> Desk2 10.0.0.22 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
> ...
> Desk10 10.0.0.40 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
>
> Other details:
> Router to connect to internet is 10.0.0.1
>
> PServer has one (physical) NIC installed.
> All VMs have one logical NIC installed.
>
> Objective: allow network traffic between VLAN and physical LAN.
> No network traffic restrictions between the two are needed.
>
> Thank you.
>
>
> "Bob Lin (MS-MVP)" wrote:
>
>> We need more information to help. Do you have a multihomed computer as
>> RRAS
>> server? If yes, sure you can enable RRAS to router between two LANs.
>>
>> However, since this is VLAN, you don't need a RRAS server to connect
>> these
>> two LANs. In our school, we have 3 VLANs, public, student and staff. We
>> connect them by doing port forwarding accordingly.
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "dj" <(E-Mail Removed)> wrote in message
>> news:2B15CB10-249D-419E-8EE4-(E-Mail Removed)...
>> >I need to connect a 2003 VLAN to a 2003 physical LAN.
>> > They are on different subnets, both LANs use static IP addresses.
>> > Both are AD domains, are small (< 10 users), and at 2003 funtionality
>> > at
>> > the
>> > Forest(?) level.
>> >
>> > I'm a SQL guy, not a networking guy, so please bear that in mind.
>> >
>> > RRAS seems like a good solution, but I'm having trouble finding details
>> > on
>> > how
>> > to accomplish this task. Any pointers to a good resource would be most
>> > welcome.
>> >
>> > TIA!
>>


First up, do you really mean VLAN? VLAN has a specific meaning and I
don't think that you have any. I think you are talking about virtual
machines on a virtual network.

The simplest way to do what you want is to use a virtual machine (not
the DC) as a router between the two subnets. You would give it a second NIC
and put that NIC in the network linked to the host's physical NIC. It will
be in the same IP subnet as the physical LAN machines.

I would set it up as a NAT router. (I have a setup running this way).
This allows the virtual machines access to the physical LAN and to the
Internet without changing the routing on the physical LAN. If you really
need the machines on the physical LAN to be able to initiate a connection to
a machine in the virtual network, the routing is a bit more complex. Your
gateway router needs extra info so that it knows about the new subnet and
how to get traffic to it.

Here is how it looks with a NAT router.

Internet
|
gateway
10.0.0.1
|
physical LAN
10.0.0.x dg 10.0.0.1
|
10.0.0.254 dg 10.0.0.1
RRAS NAT router (vm)
10.1.1.1 dg blank
|
virtual LAN
10.1.1.x dg 10.1.1.1

For full routing between subnets and Internet access, it looks like
this.

Internet
|
gateway (static route 10.1.1.0 255.255.255.0 10.0.0.254)
|
10.0.0.x dg 10.0.0.1
|
10.0.0.254 dg 10.0.0.1
RRAS LAN router (vm)
10.1.1.1 dg blank
|
10.1.1.x dg 10.1.1.1

I appreciate the detailed and helpful reply.
You are correct about the VLAN; I should have know this was a specific term.
My environment is simply a domain of 3 virtual machines.

After configuring the NICs as you suggest in the first scenario, I attempted
to configure RRAS on the virtual DC, but became confused by the options
offered. I chose the 'Custom' configuration, guessing it would allow the
most flexibility, but I'm still missing something as the two domains still
cannot see/ping one another. Do I need to do something with routing tables?

"Bill Grant" wrote:

>
>
> "dj" <(E-Mail Removed)> wrote in message
> news:006AFD84-365C-42B0-98CB-(E-Mail Removed)...
> > Thanks for the replies.
> >
> > Here's the current configuration:
> > (hope the formatting is retained in the post)
> > VLAN
> > Name IP Mask DG DNS Remarks
> > VM1 10.1.1.1 255.255.255.0 10.1.1.1 10.1.1.1 Domain Controller (2003)
> > VM2 10.1.1.2 255.255.255.0 10.1.1.1 10.1.1.1 Member server
> > VM3 10.1.1.3 255.255.255.0 10.1.1.1 10.1.1.1 Member server
> >
> >
> > Physical LAN
> > Name IP Mask DG DNS Remarks
> > PServer 10.0.0.200 255.255.255.0 10.0.0.1 10.0.0.200 Domain
> > Controller
> > (2003)
> > Desk1 10.0.0.20 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
> > Desk2 10.0.0.22 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
> > ...
> > Desk10 10.0.0.40 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
> >
> > Other details:
> > Router to connect to internet is 10.0.0.1
> >
> > PServer has one (physical) NIC installed.
> > All VMs have one logical NIC installed.
> >
> > Objective: allow network traffic between VLAN and physical LAN.
> > No network traffic restrictions between the two are needed.
> >
> > Thank you.
> >
> >
> > "Bob Lin (MS-MVP)" wrote:
> >
> >> We need more information to help. Do you have a multihomed computer as
> >> RRAS
> >> server? If yes, sure you can enable RRAS to router between two LANs.
> >>
> >> However, since this is VLAN, you don't need a RRAS server to connect
> >> these
> >> two LANs. In our school, we have 3 VLANs, public, student and staff. We
> >> connect them by doing port forwarding accordingly.
> >>
> >> --
> >> Bob Lin, MS-MVP, MCSE & CNE
> >> Networking, Internet, Routing, VPN Troubleshooting on
> >> http://www.ChicagoTech.net
> >> How to Setup Windows, Network, VPN & Remote Access on
> >> http://www.HowToNetworking.com
> >> "dj" <(E-Mail Removed)> wrote in message
> >> news:2B15CB10-249D-419E-8EE4-(E-Mail Removed)...
> >> >I need to connect a 2003 VLAN to a 2003 physical LAN.
> >> > They are on different subnets, both LANs use static IP addresses.
> >> > Both are AD domains, are small (< 10 users), and at 2003 funtionality
> >> > at
> >> > the
> >> > Forest(?) level.
> >> >
> >> > I'm a SQL guy, not a networking guy, so please bear that in mind.
> >> >
> >> > RRAS seems like a good solution, but I'm having trouble finding details
> >> > on
> >> > how
> >> > to accomplish this task. Any pointers to a good resource would be most
> >> > welcome.
> >> >
> >> > TIA!
> >>
>
>
> First up, do you really mean VLAN? VLAN has a specific meaning and I
> don't think that you have any. I think you are talking about virtual
> machines on a virtual network.
>
> The simplest way to do what you want is to use a virtual machine (not
> the DC) as a router between the two subnets. You would give it a second NIC
> and put that NIC in the network linked to the host's physical NIC. It will
> be in the same IP subnet as the physical LAN machines.
>
> I would set it up as a NAT router. (I have a setup running this way).
> This allows the virtual machines access to the physical LAN and to the
> Internet without changing the routing on the physical LAN. If you really
> need the machines on the physical LAN to be able to initiate a connection to
> a machine in the virtual network, the routing is a bit more complex. Your
> gateway router needs extra info so that it knows about the new subnet and
> how to get traffic to it.
>
> Here is how it looks with a NAT router.
>
> Internet
> |
> gateway
> 10.0.0.1
> |
> physical LAN
> 10.0.0.x dg 10.0.0.1
> |
> 10.0.0.254 dg 10.0.0.1
> RRAS NAT router (vm)
> 10.1.1.1 dg blank
> |
> virtual LAN
> 10.1.1.x dg 10.1.1.1
>
> For full routing between subnets and Internet access, it looks like
> this.
>
> Internet
> |
> gateway (static route 10.1.1.0 255.255.255.0 10.0.0.254)
> |
> 10.0.0.x dg 10.0.0.1
> |
> 10.0.0.254 dg 10.0.0.1
> RRAS LAN router (vm)
> 10.1.1.1 dg blank
> |
> 10.1.1.x dg 10.1.1.1
>
>
>
>
>
>

The first scenario will not work unless you configure RRAS as a NAT
router. That is one of the options in the setup wizard.

When it asks which interface is to be the public interface to be
shared, select the 10.0.0. interface.

"dj" <(E-Mail Removed)> wrote in message
news:59B94868-1293-4062-AD1C-(E-Mail Removed)...
> I appreciate the detailed and helpful reply.
> You are correct about the VLAN; I should have know this was a specific
> term.
> My environment is simply a domain of 3 virtual machines.
>
> After configuring the NICs as you suggest in the first scenario, I
> attempted
> to configure RRAS on the virtual DC, but became confused by the options
> offered. I chose the 'Custom' configuration, guessing it would allow the
> most flexibility, but I'm still missing something as the two domains still
> cannot see/ping one another. Do I need to do something with routing
> tables?
>
> "Bill Grant" wrote:
>
>>
>>
>> "dj" <(E-Mail Removed)> wrote in message
>> news:006AFD84-365C-42B0-98CB-(E-Mail Removed)...
>> > Thanks for the replies.
>> >
>> > Here's the current configuration:
>> > (hope the formatting is retained in the post)
>> > VLAN
>> > Name IP Mask DG DNS Remarks
>> > VM1 10.1.1.1 255.255.255.0 10.1.1.1 10.1.1.1 Domain Controller
>> > (2003)
>> > VM2 10.1.1.2 255.255.255.0 10.1.1.1 10.1.1.1 Member server
>> > VM3 10.1.1.3 255.255.255.0 10.1.1.1 10.1.1.1 Member server
>> >
>> >
>> > Physical LAN
>> > Name IP Mask DG DNS Remarks
>> > PServer 10.0.0.200 255.255.255.0 10.0.0.1 10.0.0.200 Domain
>> > Controller
>> > (2003)
>> > Desk1 10.0.0.20 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
>> > Desk2 10.0.0.22 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
>> > ...
>> > Desk10 10.0.0.40 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
>> >
>> > Other details:
>> > Router to connect to internet is 10.0.0.1
>> >
>> > PServer has one (physical) NIC installed.
>> > All VMs have one logical NIC installed.
>> >
>> > Objective: allow network traffic between VLAN and physical LAN.
>> > No network traffic restrictions between the two are needed.
>> >
>> > Thank you.
>> >
>> >
>> > "Bob Lin (MS-MVP)" wrote:
>> >
>> >> We need more information to help. Do you have a multihomed computer as
>> >> RRAS
>> >> server? If yes, sure you can enable RRAS to router between two LANs.
>> >>
>> >> However, since this is VLAN, you don't need a RRAS server to connect
>> >> these
>> >> two LANs. In our school, we have 3 VLANs, public, student and staff.
>> >> We
>> >> connect them by doing port forwarding accordingly.
>> >>
>> >> --
>> >> Bob Lin, MS-MVP, MCSE & CNE
>> >> Networking, Internet, Routing, VPN Troubleshooting on
>> >> http://www.ChicagoTech.net
>> >> How to Setup Windows, Network, VPN & Remote Access on
>> >> http://www.HowToNetworking.com
>> >> "dj" <(E-Mail Removed)> wrote in message
>> >> news:2B15CB10-249D-419E-8EE4-(E-Mail Removed)...
>> >> >I need to connect a 2003 VLAN to a 2003 physical LAN.
>> >> > They are on different subnets, both LANs use static IP addresses.
>> >> > Both are AD domains, are small (< 10 users), and at 2003
>> >> > funtionality
>> >> > at
>> >> > the
>> >> > Forest(?) level.
>> >> >
>> >> > I'm a SQL guy, not a networking guy, so please bear that in mind.
>> >> >
>> >> > RRAS seems like a good solution, but I'm having trouble finding
>> >> > details
>> >> > on
>> >> > how
>> >> > to accomplish this task. Any pointers to a good resource would be
>> >> > most
>> >> > welcome.
>> >> >
>> >> > TIA!
>> >>
>>
>>
>> First up, do you really mean VLAN? VLAN has a specific meaning and
>> I
>> don't think that you have any. I think you are talking about virtual
>> machines on a virtual network.
>>
>> The simplest way to do what you want is to use a virtual machine (not
>> the DC) as a router between the two subnets. You would give it a second
>> NIC
>> and put that NIC in the network linked to the host's physical NIC. It
>> will
>> be in the same IP subnet as the physical LAN machines.
>>
>> I would set it up as a NAT router. (I have a setup running this way).
>> This allows the virtual machines access to the physical LAN and to the
>> Internet without changing the routing on the physical LAN. If you really
>> need the machines on the physical LAN to be able to initiate a connection
>> to
>> a machine in the virtual network, the routing is a bit more complex. Your
>> gateway router needs extra info so that it knows about the new subnet and
>> how to get traffic to it.
>>
>> Here is how it looks with a NAT router.
>>
>> Internet
>> |
>> gateway
>> 10.0.0.1
>> |
>> physical LAN
>> 10.0.0.x dg 10.0.0.1
>> |
>> 10.0.0.254 dg 10.0.0.1
>> RRAS NAT router (vm)
>> 10.1.1.1 dg blank
>> |
>> virtual LAN
>> 10.1.1.x dg 10.1.1.1
>>
>> For full routing between subnets and Internet access, it looks like
>> this.
>>
>> Internet
>> |
>> gateway (static route 10.1.1.0 255.255.255.0 10.0.0.254)
>> |
>> 10.0.0.x dg 10.0.0.1
>> |
>> 10.0.0.254 dg 10.0.0.1
>> RRAS LAN router (vm)
>> 10.1.1.1 dg blank
>> |
>> 10.1.1.x dg 10.1.1.1
>>
>>
>>
>>
>>
>>

The solution, in my case, turned out to b emuch simpler.
In VS Admin, for the second network adapter, I simply chose the existing
External Network adapter and bingo! Working great.

I appreciate your help, nonetheless.


"Bill Grant" wrote:

> The first scenario will not work unless you configure RRAS as a NAT
> router. That is one of the options in the setup wizard.
>
> When it asks which interface is to be the public interface to be
> shared, select the 10.0.0. interface.
>
> "dj" <(E-Mail Removed)> wrote in message
> news:59B94868-1293-4062-AD1C-(E-Mail Removed)...
> > I appreciate the detailed and helpful reply.
> > You are correct about the VLAN; I should have know this was a specific
> > term.
> > My environment is simply a domain of 3 virtual machines.
> >
> > After configuring the NICs as you suggest in the first scenario, I
> > attempted
> > to configure RRAS on the virtual DC, but became confused by the options
> > offered. I chose the 'Custom' configuration, guessing it would allow the
> > most flexibility, but I'm still missing something as the two domains still
> > cannot see/ping one another. Do I need to do something with routing
> > tables?
> >
> > "Bill Grant" wrote:
> >
> >>
> >>
> >> "dj" <(E-Mail Removed)> wrote in message
> >> news:006AFD84-365C-42B0-98CB-(E-Mail Removed)...
> >> > Thanks for the replies.
> >> >
> >> > Here's the current configuration:
> >> > (hope the formatting is retained in the post)
> >> > VLAN
> >> > Name IP Mask DG DNS Remarks
> >> > VM1 10.1.1.1 255.255.255.0 10.1.1.1 10.1.1.1 Domain Controller
> >> > (2003)
> >> > VM2 10.1.1.2 255.255.255.0 10.1.1.1 10.1.1.1 Member server
> >> > VM3 10.1.1.3 255.255.255.0 10.1.1.1 10.1.1.1 Member server
> >> >
> >> >
> >> > Physical LAN
> >> > Name IP Mask DG DNS Remarks
> >> > PServer 10.0.0.200 255.255.255.0 10.0.0.1 10.0.0.200 Domain
> >> > Controller
> >> > (2003)
> >> > Desk1 10.0.0.20 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
> >> > Desk2 10.0.0.22 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
> >> > ...
> >> > Desk10 10.0.0.40 255.255.255.0 10.0.0.1 10.0.0.200 XP desktop
> >> >
> >> > Other details:
> >> > Router to connect to internet is 10.0.0.1
> >> >
> >> > PServer has one (physical) NIC installed.
> >> > All VMs have one logical NIC installed.
> >> >
> >> > Objective: allow network traffic between VLAN and physical LAN.
> >> > No network traffic restrictions between the two are needed.
> >> >
> >> > Thank you.
> >> >
> >> >
> >> > "Bob Lin (MS-MVP)" wrote:
> >> >
> >> >> We need more information to help. Do you have a multihomed computer as
> >> >> RRAS
> >> >> server? If yes, sure you can enable RRAS to router between two LANs.
> >> >>
> >> >> However, since this is VLAN, you don't need a RRAS server to connect
> >> >> these
> >> >> two LANs. In our school, we have 3 VLANs, public, student and staff.
> >> >> We
> >> >> connect them by doing port forwarding accordingly.
> >> >>
> >> >> --
> >> >> Bob Lin, MS-MVP, MCSE & CNE
> >> >> Networking, Internet, Routing, VPN Troubleshooting on
> >> >> http://www.ChicagoTech.net
> >> >> How to Setup Windows, Network, VPN & Remote Access on
> >> >> http://www.HowToNetworking.com
> >> >> "dj" <(E-Mail Removed)> wrote in message
> >> >> news:2B15CB10-249D-419E-8EE4-(E-Mail Removed)...
> >> >> >I need to connect a 2003 VLAN to a 2003 physical LAN.
> >> >> > They are on different subnets, both LANs use static IP addresses.
> >> >> > Both are AD domains, are small (< 10 users), and at 2003
> >> >> > funtionality
> >> >> > at
> >> >> > the
> >> >> > Forest(?) level.
> >> >> >
> >> >> > I'm a SQL guy, not a networking guy, so please bear that in mind.
> >> >> >
> >> >> > RRAS seems like a good solution, but I'm having trouble finding
> >> >> > details
> >> >> > on
> >> >> > how
> >> >> > to accomplish this task. Any pointers to a good resource would be
> >> >> > most
> >> >> > welcome.
> >> >> >
> >> >> > TIA!
> >> >>
> >>
> >>
> >> First up, do you really mean VLAN? VLAN has a specific meaning and
> >> I
> >> don't think that you have any. I think you are talking about virtual
> >> machines on a virtual network.
> >>
> >> The simplest way to do what you want is to use a virtual machine (not
> >> the DC) as a router between the two subnets. You would give it a second
> >> NIC
> >> and put that NIC in the network linked to the host's physical NIC. It
> >> will
> >> be in the same IP subnet as the physical LAN machines.
> >>
> >> I would set it up as a NAT router. (I have a setup running this way).
> >> This allows the virtual machines access to the physical LAN and to the
> >> Internet without changing the routing on the physical LAN. If you really
> >> need the machines on the physical LAN to be able to initiate a connection
> >> to
> >> a machine in the virtual network, the routing is a bit more complex. Your
> >> gateway router needs extra info so that it knows about the new subnet and
> >> how to get traffic to it.
> >>
> >> Here is how it looks with a NAT router.
> >>
> >> Internet
> >> |
> >> gateway
> >> 10.0.0.1
> >> |
> >> physical LAN
> >> 10.0.0.x dg 10.0.0.1
> >> |
> >> 10.0.0.254 dg 10.0.0.1
> >> RRAS NAT router (vm)
> >> 10.1.1.1 dg blank
> >> |
> >> virtual LAN
> >> 10.1.1.x dg 10.1.1.1
> >>
> >> For full routing between subnets and Internet access, it looks like
> >> this.
> >>
> >> Internet
> >> |
> >> gateway (static route 10.1.1.0 255.255.255.0 10.0.0.254)
> >> |
> >> 10.0.0.x dg 10.0.0.1
> >> |
> >> 10.0.0.254 dg 10.0.0.1
> >> RRAS LAN router (vm)
> >> 10.1.1.1 dg blank
> >> |
> >> 10.1.1.x dg 10.1.1.1
> >>
> >>
> >>
> >>
> >>
> >>
>