search for: vnic0

..._108, I''m playing with creating a vnic over an etherstub, and I > might not be doing it right, but the behaviour I''m seeing doesn''t look > right either. > > So this is what I did... > > # dladm create-etherstub estub0 > # dladm create-vnic -l estub0 vnic0 > # ifconfig vnic0 plumb > # ifconfig vnic0 192.168.128.1 netmask 255.255.255.0 broadcast + up > # > > That seems to work, and I had virtualbox also attach to vnic0 and > traffic passes through vnic0 OK. > > Then I reboot. I wasn''t expecting the interfaced to be pl...

So, just to play with vnics with 106, I have... e1000g2 plumb''d with 192.168.85.10 vnic0 is created on top of e1000g2 with 192.168.85.22 I snoop on e1000g2 to see the traffic. I ping 192.168.85.22 and it works. I stop the snoop on e1000g2. I ping 192.168.85.22 and it doesn''t work. I start the snoop on e1000g2. I ping 192.168.85.22 and ping works. Is this a new feature with cr...

How come snoop doesn''t find the vnic0, by default: root at pine:~# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 vnic0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.9.59.56 netmask ffffffe0 broad...

After googling around and reading the material on the opensolaris.org xvm community site, I still do not understanding the configuration of networking and would appreciate some assistance. Problem: I have successfully installed an hvm domU running Windows XP on opensolaris 2005.11 (build 94), and when the laptop (lenovo t61, core2 9300) is connected via the e1000g0 interface networking works

Actually, it is not a list.. but just something that''ll be very useful to me in my business. If crossbow/virtual interfaces can provide a flow that can capture bandwidth usage over a period of time (including 95 percentile), that''ll be great! Is this possible? -- This message posted from opensolaris.org

Greetings, I've setup an vm with openwrt in it, defined a isolated lan between the vm and the host and booted the vm up. I see the vm is up, made sure the vnic is visible in both the host and guest and added it to the br in the guest. I've issued an dhcpd call on the vnic (labeled vnic0) in the host and got an ip, see: dagg@NCC-5001D ~ $ dhcpcd vnet0 DUID 00:01:00:01:23:dd:d8:5b:e0:d5:5e:d9:f2:e2 vnet0: IAID 00:10:20:bf vnet0: rebinding lease of 192.168.1.130 vnet0: probing address 192.168.1.130/24 vnet0: soliciting an IPv6 router vnet0: leased 192.168.1.130 for 43200 seconds vnet...

...> > I've setup an vm with openwrt in it, defined a isolated lan between the vm and the host and booted the vm up. > I see the vm is up, made sure the vnic is visible in both the host and guest and added it to the br in the guest. > I've issued an dhcpd call on the vnic (labeled vnic0) in the host and got an ip, see: > dagg@NCC-5001D ~ $ dhcpcd vnet0 You didn't run "dhcpd" (which is a dhcp server) on the host, you ran "dhcpcd", which is a dhcp *client*. So you've ended up assigning an IP address to the tap device on the host. I guess the dhcp se...

System config:- bash-3.2# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 rge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 index 2 inet 192.168.1.53 netmask ffffff00 broadcast 192.168.1.255 ether 0:1e:8c:25:cc:a5 lo0:

...of these protocols is dropped. ------------------------------------------------------------------------ ACLs may be modified at any time but they only take effect if the corresponding protection type is set. Below are some examples on how to use the *-acl subcommands: # dladm add-acl -l vnic0 -a 10.0.0.1,10.0.0.2,10.0.0.3 ipnospoof # dladm remove-acl -l vnic0 -a ipv6 whitelist-in # dladm show-acl -l vnic0 ACL ATTR POSSIBLE ipnospoof 10.0.0.1, 10.0.0.2, ipv4 or ipv6 address 10.0.0.3 whitelist-in ipv4, arp ipv4, ipv6, arp whitelist-out ipv4, ipv6, arp ipv4, ipv6, arp Other consi...

Folks, I just posted an updated Crossbow virtualization architecture document. The new revision is available at: http://opensolaris.org/os/project/crossbow/Docs/crossbow-virt.pdf The main changes are the addition of support for multiple MAC addresses per client, and an explicit separation between consolidation private and project private MAC API entry points. See in particular the