Need howto for opensolaris host / win guest networking

[SamCN2]

I am unable to configure a windows guest to offer a network service to the
lan at large. I am sure it is a user error/omission. But I cannot for the life
of me figure things out by reading the user docs or forums.

I believe that I should use bridged neworking on a previously plumbed nic.

Should I also give that nic on the host OS side of things the same ipaddr
as I assign it in the guest? Or do I give it an address only in the guest?
Or do I give it an address only on the host and use NAT for the guest?

If this is already a FAQ, I'd appreciate a pointer to it.

Cheers!
-sam

[renato.morano]

Hi

on opensolaris

ifconfig rge0 plumb
ifconfig rge0 192.168.0.33 netmask 255.255.255.0
ifconfig rge0 up

ifconfig rge0
idefix@morano:~ $ ifconfig rge0
rge0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.0.33 netmask ffffff00 broadcast 192.168.0.255

on windows modify the nic address and netmask 192.168.0.44/255.255.255.0

now host and guest are on the same network and you can try to ping one host fron other.

let me know
Renato
are you working with crossbow ?

[SamCN2]

Thanks, and Happy New Year.

I went through your notes, and I think we're doing
basically the same thing. I am using crossbow.

Here's what I'm doing:

host opensolaris: snv_111b

dladm create-vnic -l e1000g1 -m auto vnet0
ifconfig vnet0 plumb 198.98.1.2/24 up

virtualbox network 0 setup for guest:
Intel PRO/1000 T Server (Bridged adapter, vnet0 - Ethernet)

win2k3 guest: Local Area Network
Intel PRO 1000 T Server Adapter
Connected
198.98.1.4
255.255.255.0


Get a cmd or shell prompt on either and try to ping the other gives no joy.

I'm using the exact same setup for zones and they work fine.

Ideas or corrections would be most welcome!

Cheers!
-sam

[SamCN2]

Silly me.

It was indeed a case of user omission.

User Manual, Section 6.4 Bridged Networking

The last sentence:

The VNIC and the guest network interface that uses the VNIC must be assigned identical MAC addresses.

Pay attention to that and all works.

FYI, I have often found with Crossbow that an initial outbound packet is often needed
to get things going. My zone startup scripts ping the default router. I'll probably create
a similar Windows start script.

Cheers!
-sam

[renato.morano]

vnic and vbox nic have to the same mac to work

host667-1@morano:~ $ dladm show-vnic
LINK OVER SPEED MACADDRESS MACADDRTYPE VID
radius0 left1 0 2:8:20:99:ac:52 fixed 0
ldap0 left1 0 2:8:20:5c:87:ba fixed 0
zs0 left1 0 2:8:20:ef:2e:18 fixed 0
zs1 rigth1 0 2:8:20:41:19:2d fixed 0
ws0 wireless1 0 2:8:20:f1:6e:9f fixed 0
pc1 wireless1 0 2:8:20:c1:b1:f0 fixed 0

host667-1@morano:~ $ VBoxManage showvminfo radius | grep NIC
NIC 1: MAC: 02082099AC52, Attachment: Bridged Interface 'radius0 - Ethernet', Cable connected: on, Trace: off (file: none), Type: 82543GC, Reported speed: 0 Mbps

Renato