On Wed, 2010-01-13 at 13:59 -0500, Christopher Barry wrote:
> Greets everyone,
>
> googlage produced nothing applicable, so asking here.
>
> I'm trying to do some network discovery testing, and I need a bunch of
> systems on different networks. Not only that, but I need to have some of
> the systems with IP aliases on some of these nets, (i.e. multi-netted)
> as they purposely will not have the total amount of NICs required to
> have a single NIC per network. This is essentially the point of my
> testing.
>
> So, for example:
>
> vbox_A: has three NICs.
> vbox_B: has two NICs
> vbox_C has one NIC.
>
> I'll have three test networks:
> net_A: 192.168.111.0/24 (bridged to host eth0)
> net_B: 10.1.0.0/24
> net_C: 172.16.0.111/0/24
>
> I do not care if net_{B,C} can route outbound or not. I'll just need to
> see other vbox hosts on these networks.
>
> vbox_A: will have eth0:net_A, eth1:net_B, eth2:net_C
> vbox_B: will have eth0:net_A, eth1:net_B & net_C
> vbox_C: will have eth0:net_A & net_B & net_C
>
> The crux of the biscuit is I want aliases on separate subnets, and not
> sure how to configure the VM network to do this - especially on the
> single NIC vbox_C.
>
> Would a single internal network work, and just do the normal ip aliasing
> with ip addr add ... stuff in Linux? What about interacting with the
> bridge?
>
> Any clarification would be great.
>
>
> Thanks,
> -Christopher
>
>
Nevermind all - I was over-thinking it. Just put everything on the
internal, and it's just a big switch.
Thanks,
-C
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
