search for: nge0

...into ZFS. It makes sense to me because of the integration of NFS and iSCSI with the sharenfs and shareiscsi properties. Since these are both dependent on an IP it would be pretty cool if there was also a virtual IP that would automatically move with the pool. Maybe something like "zfs set ip.nge0=x.x.x.x mypool" Or since we may have different interfaces on the nodes where we want to move the zpool... zfs set ip.server1.nge0=x.x.x.x mypool zfs set ip.server2.bge0=x.x.x.x mypool I know this could be handled with Sun Cluster but if I am only building a simple storage appliance to serve...

...This DTrace script uses the ip provider to show packets as they pass in and out of tunnels: # ./ipio.d CPU DELTA(us) SOURCE DEST INT BYTES 1 598913 10.1.100.123 -> 192.168.10.75 ip.tun0 68 1 73 192.168.1.108 -> 192.168.5.1 nge0 140 1 18325 192.168.1.108 <- 192.168.5.1 nge0 140 1 69 10.1.100.123 <- 192.168.10.75 ip.tun0 68 0 102921 10.1.100.123 -> 192.168.10.75 ip.tun0 20 0 79 192.168.1.108 -> 192.168.5.1 nge0 92 This DTrace...

...g timeouts that the emulated realtek does. So long if I dump the xml configuration of my hvm domU it says (I had to swap <> with {} or this forum didn''t let me post the config, but it''s the same): {interface type=''bridge''} {source bridge=''nge0 ''/} {target dev=''vif-1.0''/} {mac address=''00:16:3e:17:f4:46''/} {script path=''vif-vnic''/} {/interface} if I try to add the model=ne2k_pci here in any way it doesn''t want to reimport the xml, otherwise it w...

...started to play with IP Instances. I''m having trouble making my zone happy: root at aeon zones$ zoneadm -z testing1 boot zoneadm: zone ''testing1'': WARNING: unable to hold network interface ''skge0''.: Invalid argument root at aeon zones$ dladm show-dev nge0 link: up speed: 100Mb duplex: full skge0 link: unknown speed: 0Mb duplex: unknown Here are the relevant bits from the zone config: ip-type: exclusive net: address not specified physical: skge0 I''ve tried variations, such as plumb'...

Hi all, I'm currently in the process of testing Samba 3.2.1.x compiled for Solaris 10 x86, because there are some issues I have found with the default Sun supported 3.0.28a that I am trying to resolve. In the process of attempting to run up 3.2.1.x, I have found that when I issue an /opt/local/sbin/smbd -D, my samba log file results in: [2008/10/04 21:29:15, 0, pid=3059]

I''m following the example provided in the type reference under ''zone'', i.e.: zone{myzone: autoboot=>true, create_args=>"-b", ip=>"nge0:10:130.55.201", path=>"/zoneds/%s", realhostname=>"myzone.example.com", sysidcfg=>template(sysidcfg) } with the following template: system_locale=en_AU timezone=Australia/NSW terminal=xterms security_policy=...

...t600A0B800029D69A000013CA4B00E1ABd0''/> <target dev=''hdb'' bus=''ide''/> </disk> <interface type=''bridge''> <mac address=''00:16:3e:00:03:04''/> <source bridge=''nge0''/> <script path=''/usr/lib/xen/scripts/vif-vnic''/> <target dev=''vif16.0''/> </interface> <serial type=''pty''> <source path=''/dev/pts/1''/> <target port=...

...the host OS, we do see them showing up, but all all records are 0. Can someone tell me how to get the correct network info via snmp on the Vbox Host?? Thanks in advance. IF-MIB::ifDescr.1 = STRING: lo0 IF-MIB::ifDescr.2 = STRING: ibd0 IF-MIB::ifDescr.3 = STRING: ibd1 IF-MIB::ifDescr.4 = STRING: nge0 IF-MIB::ifDescr.5 = STRING: nge1 IF-MIB::ifDescr.6 = STRING: vboxnet0 IF-MIB::ifDescr.7 = STRING: m121_vnic1 IF-MIB::ifDescr.8 = STRING: m121_vnic2 IF-MIB::ifDescr.9 = STRING: m115_vnic1 IF-MIB::ifDescr.10 = STRING: m115_vnic2 IF-MIB::ifDescr.11 = STRING: m119_vnic1 IF-MIB::ifDescr.12 = STRING: m11...

I recently updated to snv_125 and now bridged networks for my VirtualBox guests can''t move any network traffic. I''ve tried both VirtualBox 3.0.4 and 3.0.8 with no success. Any ideas? Thanks, Gordon -- This message posted from opensolaris.org

I opened a bug report earlier today but it doesn''t seem to have been added to the bugs database. I''m posting here in case one of the Crossbow developers might see it and confirm this behavior. Description Duplicate packets are generated whenever an aggregate is introduced into the network configuration. We''ve ruled out switch ports and physical bge interfaces as

Hi all! I am running SXCE 121 on a dual quad-core X2200M2 (64 bit of course). During an installation of a NetBSD 5.0.1 PVM domU, the entire machine crashed with a kernel panic. Here''s what I managed to salvage from the LOM console of the machine: Sep 2 18:55:19 glaurung genunix: /xpvd/xdb@41,51712 (xdb5) offline Sep 2 18:55:19 glaurung genunix: /xpvd/xdb@41,51728 (xdb6) offline

...AL> mtu 8252 index 1 inet6 ::1/128 lo0:1: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 zone adriatic inet6 ::1/128 and output of "dladm show-link", showing a vnic created for xvm: LINK CLASS MTU STATE OVER nge0 phys 1500 unknown -- nge1 phys 1500 unknown -- bge0 phys 1500 up -- bge1 phys 1500 unknown -- xvm1_0 vnic 1500 up bge0 Thanks in advance, L. -- This message posted from opensolaris.org

I''m running snv93. I''m trying to install a windows hvm domU using the virt-install command: /usr/bin/virt-install -n windowsts -r 2048 -s 20 -f /data/domU/windowsts --hvm --vnc -c /dev/dsk/c0t0d0s2 The vncviewer is unable to open a connection to the xend VNC server and is failing with the Connection refused (146) error message. xend is set up with the following properties:

...DomU config: - ZFS based disk (zvol) =============== disk = [ ''phy:/dev/zvol/dsk/p4/w2k3r2s,hdc,w''] memory = 1024 name = "w2k3r2s" kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' vif = [ ''type=ioemu, mac=00:14:b1:ab:e2:b7, bridge=nge0'' ] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''preserve'' boot=''c'' vnc=1 vnclisten="0.0.0.0" vncpasswd=''secret'' vncunused=0 vncdisplay=3 apic=1 acpi=1 vcpu=1 usb=1 localtim...

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start