<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.os.solaris.opensolaris.networking">
    <title>gmane.os.solaris.opensolaris.networking</title>
    <link>http://blog.gmane.org/gmane.os.solaris.opensolaris.networking</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14292"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14283"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14278"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14275"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14269"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14268"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14267"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14261"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14256"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14254"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14252"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14250"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14244"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14241"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14235"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14232"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14225"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14224"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14221"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14216"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14292">
    <title>ipf increase NAT table</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14292</link>
    <description>&lt;pre&gt;Hello all.
How to increase a NAT table, for example for 300000 sessions? I have tried

#ipf -D -T ipf_nattable_sz=10009,ipf_nattable_max=300000 -E

but after this NAT hangup and doesn't work.

$ uname -a
SunOS router 5.11 11.1 sun4v sparc SUNW,Sun-Fire-T1000

On FreeBSD i recompile kernel with bigger values and it works fine, but 
in Solaris - i doesn't want to recompile kernel/ipf.

Thanks.
&lt;/pre&gt;</description>
    <dc:creator>skeletor</dc:creator>
    <dc:date>2013-02-22T09:26:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14283">
    <title>IPMP - Programmatic interface</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14283</link>
    <description>&lt;pre&gt;Hi,

I read about libipmp library which provides programmatic (ioctl/system calls) interface to configure and monitor IPMP groups.

However I am not able to find any documentation or library itself for use.

Please provide more info on libipmp.

Thanks and Regards,
Paresh Bafna

&lt;/pre&gt;</description>
    <dc:creator>Paresh Bafna</dc:creator>
    <dc:date>2012-07-20T06:54:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14278">
    <title>scalability and memory consumption of the DCEcache</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14278</link>
    <description>&lt;pre&gt;Hi,

I am analyzing issues on some s11 (151.0.1.12) production systems used as
Varnish web caches with a high number of concurrent connections from a high
number of tcp clients where client-side statistics/benchmarks would show long
connect times at times, e.g. 2.7 seconds connect maximum reported in ApacheBench
compared to normal .6 seconds (which already was far too bad, see below)

I would very much appreciate if I could discuss my current understanding with
someone.

* The issue is related to the DCE cache

  Using

  dtrace -n 'profile-1001 { &amp;lt; at &amp;gt;s[stack(),ustack()] = count();} END {trunc(&amp;lt; at &amp;gt;s,5)}'

  i noticed that the top stacks were

CPU     ID                    FUNCTION:NAME
  2      2                             :END


              ip`ip_snmp_get_mib2_ip_dce+0xbe
              ip`ip_snmp_get+0x267
              ip`snmpcom_req+0x293
              ip`ip_wput_nondata+0xd5
              unix`putnext+0x21e
              unix`putnext+0x21e
              unix`putnext+0x21e
              unix`putnext+0x21e
  &lt;/pre&gt;</description>
    <dc:creator>Nils Goroll</dc:creator>
    <dc:date>2012-02-06T17:36:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14275">
    <title>etherstub - backup interface?</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14275</link>
    <description>&lt;pre&gt;Hi,

is it possible to tell etherstub, that one link is the backup for
another?

What I have in mind is simplifying/uniform zone setup/connectivity -&amp;gt;
zone management:


  CampusA ||       || CampusB
      +------------------+       2x10G       +--------------------+
      | Cisco 6509/3560X |&amp;lt;=================&amp;gt;|   Cisco Nexus 5010 |
      +------------------+                   +--------------------+
Uplinks:     ^ ^                                 ^ ^
  _________  | | 2x1G _________________________  | | 2x10G ______________
 /           \V/                                 \V/                    /
/             T                                   T                    /
\             | aggr0                             | aggr1              \
 \            v                                   v                     \
  \       +---------------------------------------------+                \
  /       |             etherstub es0                   |                /
 /        +-------------------------------------&lt;/pre&gt;</description>
    <dc:creator>Jens Elkner</dc:creator>
    <dc:date>2011-10-26T14:11:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14269">
    <title>igb becomes sender only on Intel 82576 [kawela] (X8DTH-6F motherboard)</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14269</link>
    <description>&lt;pre&gt;We have a system with a SuperMicro X8DTH-6F dual socket motherboard with dual Xeon X5680 processors. The X8DTH-6F motherboard has dual GigE NIC powered by the Intel 82576 (kawela) chipset [attached by igb driver]. We've got S10u9 installed:

$ uname -a
SunOS r10.atl.efoldering.com 5.10 Generic_144489-06 i86pc i386 i86pc

The symptoms are very similar to what was reported here:
http://opensolaris.org/jive/thread.jspa?threadID=124411

Since the chipset is completely different in this case (igb instead of e1000g) I'm posting to a new thread.

The system is under a constant incoming load between 40 Mbit/sec to 240 Mbit/sec. At random times (usually about once per day, sometimes twice per day, sometimes not at all), the system disappears off the network (it can't ping other systems, and other systems can't ping it) for between 60 seconds to up to 30 minutes, after which it will mysteriously appear on the network again all without intervention.

We actually have both igb0 and igb1 interfaces wired with separate IP&lt;/pre&gt;</description>
    <dc:creator>khoffman-9trlstd70hfR7s880joybQ&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2011-09-14T04:35:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14268">
    <title>solaris11 static IP setup</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14268</link>
    <description>&lt;pre&gt;Hello,

I am using snv171. I am often confused by its NWAM: all IP ports before net0, net1....., I am wondering how do I know which one is mother board NIC which I usually set as default access port? 

Also, how do I disable nwam and set NIC static IP address manually? I used to disable nwam and then set static IP manually. However, 
 svcadm disable svc:/network/physical:nwam
 svcadm enable svc:/network/physical:default
do not work on recent version of S11 x86, though they still work on Sparc. 

Any idea how to set static IP on recent S11 x86 release?

Tom

root&amp;lt; at &amp;gt;aryabhata:~# cat /etc/release
                          Oracle Solaris 11 snv_171 X86
  Copyright (c) 1983, 2011, Oracle and/or its affiliates.  All rights reserved.
                             Assembled 29 July 2011
root&amp;lt; at &amp;gt;aryabhata:~# ifconfig -a
lo0: flags=2001000849&amp;lt;UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL&amp;gt; mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
net0: flags=1004843&amp;lt;UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4&amp;gt; mtu 1500 index 2
    &lt;/pre&gt;</description>
    <dc:creator>Tom Chen</dc:creator>
    <dc:date>2011-09-08T20:42:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14267">
    <title>ConnectX-2 Support</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14267</link>
    <description>&lt;pre&gt;I'm building out a new open solaris box (maybe open indiana) and there is one thing that concerns me. The IB card. I spent about a year futzing with the previous card in the other OS machine and now it is working. My vendor wants to install a MHQH19B as his first choice which seems to run ConnectX®-2 VPI chipset. I think I may have found one report of it working here:
http://opensolaris.org/jive/thread.jspa?messageID=493088&amp;amp;#493088

"its IB functionality
is already supported by hermon driver: PSARC/2008/497"

Can anyone help me out? Does it work?
&lt;/pre&gt;</description>
    <dc:creator>Phillip V</dc:creator>
    <dc:date>2011-08-29T22:54:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14261">
    <title>svccfg apply profile.xml - network addressesdo not change</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14261</link>
    <description>&lt;pre&gt;Is there something below that I'm doing wrong?

Darren

Boot device: /pci&amp;lt; at &amp;gt;7c0/pci&amp;lt; at &amp;gt;0/pci&amp;lt; at &amp;gt;8/scsi&amp;lt; at &amp;gt;2/disk&amp;lt; at &amp;gt;0,0:a  File and args:
SunOS Release 5.11 Version on-hg_ob2 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
DEBUG enabled
misc/forthdebug (170417 bytes) loaded
Hostname: netvirt-b1
Aug 22 06:01:11 svc.startd[100002]: svc:/system/ocm:default: Method 
"/lib/svc/method/svc-ocm start" failed with exit status 95.
Aug 22 06:01:11 svc.startd[100002]: system/ocm:default failed fatally: 
transitioned to maintenance (see 'svcs -xv' for details)

netvirt-b1 console login: root
Password:
Last login: Mon Aug 22 05:54:42 on console
Oracle Corporation      SunOS 5.11      on-hg_ob2       Aug. 16, 2011
SunOS Internal Development: dr146992 2011-Aug-16 [on-hg_ob2]
root&amp;lt; at &amp;gt;netvirt-b1:~# ifconfig -a
lo0: flags=2001000849&amp;lt;UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL&amp;gt; mtu 
8232 index 1
         inet 127.0.0.1 netmask ff000000
net0: flags=1000843&amp;lt;UP,BROADCAST,RUNNING,MULTICAST,IPv4&amp;gt; mtu 1500 index 2
 &lt;/pre&gt;</description>
    <dc:creator>Darren Reed</dc:creator>
    <dc:date>2011-08-22T13:34:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14256">
    <title>Internet shuts down. Bug in e1000 driver?</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14256</link>
    <description>&lt;pre&gt;Sometimes my internet connection just dies. I can not ping anything or do anything. This carries on for half an hour or so, then everything suddenly works again. What is going on? Is there a bug in the e1000 driver? Can I type some Solaris commands that show what is going on? The strange thing is that Windows PC / iPad works fine, I can surf the web without problems. So the problem is somewhere on the Solaris 11 Express PC. Here is some output when the Solaris 11 Express PC just hangs:



$ ping 192.168.1.1     //this is my router
ping: sendto No route to host



$ ipadm show-addr
ADDROBJ           TYPE     STATE        ADDR
lo0/v4            static   ok           127.0.0.1/8
e1000g0/_a        static   duplicate    192.168.1.3/24
vboxnet0/_a       static   ok           192.168.56.1/24
lo0/v6            static   ok           ::1/128



$ ipadm show-ifprop
IFNAME      PROPERTY        PROTO PERM CURRENT    PERSISTENT DEFAULT    POSSIBLE
lo0         arp             ipv4  rw   on         --         on         on,&lt;/pre&gt;</description>
    <dc:creator>Orvar Korvar</dc:creator>
    <dc:date>2011-08-14T09:15:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14254">
    <title>bridging two ixgbe interfaces to one logicalbridge with one ip</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14254</link>
    <description>&lt;pre&gt;i would like to bridge two ixgbe interfaces to one logical bridge with one ip. is this possible?

so far I've only done that ip is bound to only one interface. this ip is active on both interfaces. ?!?! in linux you can bind the ip to a bridge interface (br0)

what I need is a solaris box with two ixgbe interfaces which are directly connected to two esx servers. both esx servers can communicate to one destination ip adderss (192.168.0.1)

thanks for you help
&lt;/pre&gt;</description>
    <dc:creator>Daniel Wagner</dc:creator>
    <dc:date>2011-07-07T17:18:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14252">
    <title>build NIC drivers for snv166+</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14252</link>
    <description>&lt;pre&gt;Hi,

I just tried to replace a NIC driver on OpenSolaris snv166 and 167. The driver can not be installed. Even inbox driver from earlier version of OpenSolaris OS, snv155, also can not run:
 "WARNING: mac_register failed for port 0"

I guess there are some modificaiton in header files and I need a rebuild. However, even after I download the latest ON bits yesterday, the new driver still unable to run. I think the ON bits files posted to OpenSolaris.org have not been updated. Any body encountered this issue?

Tom
&lt;/pre&gt;</description>
    <dc:creator>Tom Chen</dc:creator>
    <dc:date>2011-07-06T22:41:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14250">
    <title>ipadm buggy?</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14250</link>
    <description>&lt;pre&gt;Hi,

Hmm, what is the propper way to bring up an IP IF, which is admin. down?


ENVIRONMENT: Solaris Express snv_151a incl. all avail support updates

admin.home ~ &amp;gt;dladm show-phys
LINK         MEDIA                STATE      SPEED  DUPLEX    DEVICE
ext0         Ethernet             up         100    full      rge0
vboxnet0     Ethernet             unknown    0      unknown   vboxnet0
int0         Ethernet             up         100    full      rge1

admin.home ~ &amp;gt;dladm show-vnic
LINK         OVER         SPEED  MACADDRESS        MACADDRTYPE
VID
home0        ext0         100    0:80:41:10:d:1     fixed               0
home1        int0         100    0:80:41:20:d:1     fixed               0

admin.home ~ &amp;gt;dladm show-link
LINK        CLASS     MTU    STATE    BRIDGE     OVER
ext0        phys      1500   up       --         --
vboxnet0    phys      1500   unknown  --         --
int0        phys      1500   up       --         --
home0       vnic      1500   up       --         ext0
home1       vnic      15&lt;/pre&gt;</description>
    <dc:creator>Jens Elkner</dc:creator>
    <dc:date>2011-06-25T20:46:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14244">
    <title>mac_link state</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14244</link>
    <description>&lt;pre&gt;Hello,

1) Is it true that even after specifying mac_link_update(adapter-&amp;gt;mach, LINK_STATE_UNKNOWN), ethernet driver xmit routine can still get packets from stack. Application I am using is netperf. 
2) Will it not create any problem for OS like creating backpressure in its Queues because I keep getting mbufs even after indicating LINK_STATE_UNKOWN and I return those mbufs from xmit. All these packets may end up in OS  Queues.
3) Is there any thing more to stop getting packets apart from doing LINK_STATE_UNKNOWN/DOWN.

Thanks
Raghu.
&lt;/pre&gt;</description>
    <dc:creator>raghu</dc:creator>
    <dc:date>2011-06-24T03:03:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14241">
    <title>dtrace script for CLOSE_WAIT leaks ?</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14241</link>
    <description>&lt;pre&gt;
Hi all,

Does anyone have a dtrace script for observing connection/socket leaks ? 
I.e. when application does not do shutdown()/close() on a socket which 
it previously accept()'ed ? Ideally with IP address/port pairs printed 
in the output.


v.
&lt;/pre&gt;</description>
    <dc:creator>Vladimir Kotal</dc:creator>
    <dc:date>2011-06-23T17:56:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14235">
    <title>JUmpStart Installation and ZFS flarinstallation</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14235</link>
    <description>&lt;pre&gt;Can anybody please explain what is mean by JumpStart Installation. As far as I know Solaris installation with ZFS flar can be done only with JUmpStart installation. Is that correct? If that is correct, what is Jumpstart installation, how can we do?, Is JUmpstart installation can be done from any server or any bootable CD?

Please do the needfull
&lt;/pre&gt;</description>
    <dc:creator>Praneeth Ravikanti</dc:creator>
    <dc:date>2011-06-01T08:44:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14232">
    <title>bridges and vlans...</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14232</link>
    <description>&lt;pre&gt;Hello.
On FreeBSD host system I have the following configuration:
on physical interface I created vlan, connected it to bridge, created epair and added it end to bridge. In such way I can connect several jailed systems (VNET) to one vlan, providing one virtual interface to each jail.
I'm trying to achieve this functionality on OpenIndiana system (oi_151) so that severals zones could be connected to one vlan with own vnic, but I didn't managed yet. I can't create  vnic based on vlan and can't bridge vlan...
&lt;/pre&gt;</description>
    <dc:creator>Alexander</dc:creator>
    <dc:date>2011-05-30T12:06:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14225">
    <title>Bizarre code in dladm</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14225</link>
    <description>&lt;pre&gt;Whilst trying to compile dladm with "-g", I received this error:
...
Undefined                       first referenced
  symbol                             in file
brlsum_t_is_too_large               dladm.o
brsum_t_is_too_large                dladm.o
ld: fatal: symbol referencing errors. No output written to dladm

Looking in dladm.c, I find this:

+#ifndef lint
+        /* This is a compile-time assertion; optimizer normally fixes this */
+        extern void brlsum_t_is_too_large(void);
+
+        if (sizeof (*brlsum)&amp;gt;  sizeof (state-&amp;gt;ls_prevstats))
+                brlsum_t_is_too_large();
+#endif

... given that this prohibits compiling with -g,
can someone explain why this belongs in dladm.c?

Darren


&lt;/pre&gt;</description>
    <dc:creator>Darren Reed</dc:creator>
    <dc:date>2011-05-21T01:48:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14224">
    <title>Can not get static IP in S11E</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14224</link>
    <description>&lt;pre&gt;I can not get static IP on my S11E. I am trying to follow the manual, which says (copied from [1]):

# ipadm create-if e1000g3
# ipadm show-if e1000g3
IFNAME STATE CURRENT PERSISTENT
e1000g3 down bm--------46 -46
# ifconfig e1000g3
e1000g3: flags=1000842&amp;lt;BROADCAST,RUNNING,MULTICAST,IPv4&amp;gt; mtu 1500 index 3
inet 0.0.0.0 netmask 0
ether 0:15:17:af:e5:ea
# ipadm create-addr -T static -a 192.168.17.1/24 e1000g3/v4
# ifconfig e1000g3
e1000g3: flags=1000843&amp;lt;UP,BROADCAST,RUNNING,MULTICAST,IPv4&amp;gt; mtu 1500 index 3
inet 192.168.17.1 netmask ffffff00 broadcast 192.168.17.255
ether 0:15:17:af:e5:ea
# ipadm show-addr e1000g3/v4
ADDROBJ TYPE STATE ADDR
e1000g3/v4 static ok 192.168.17.1/24




I followed the instructions, but I have e1000g0. So I tried the first line on my e1000g0 but that does not work.

Also, I get this error message. The manual is not correct.
root&amp;lt; at &amp;gt;Frasse:~# ipadm create-addr -T static -a 192.168.1.4/24 e1000g0/v4
ipadm: Could not create address: Persistent operation on temporary object

And now:
root&amp;lt; at &amp;gt;Fras&lt;/pre&gt;</description>
    <dc:creator>Orvar Korvar</dc:creator>
    <dc:date>2011-05-19T21:44:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14221">
    <title>Link aggregation ignoring policy</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14221</link>
    <description>&lt;pre&gt;I'm having trouble getting my server to spread the transmit data over an
aggregated link (Sun Fire X2250) create from its two on-board
interfaces. Below is the configuration of the aggregation:

# dladm show-aggr
LINK            POLICY   ADDRPOLICY           LACPACTIVITY  LACPTIMER
FLAGS
aggr1           L2,L3,L4 auto                 active        short
-----

# dladm show-aggr -x aggr1
LINK        PORT           SPEED DUPLEX   STATE     ADDRESS
PORTSTATE
aggr1       --             1000Mb full    up        0:23:8b:ce:45:c2   --
            e1000g0        1000Mb full    up        0:23:8b:ce:45:c2
attached
            e1000g1        1000Mb full    up        0:23:8b:ce:45:c3
attached

The other end is an Extreme Network X450a switch stack and everything is
configured correctly on its end of the link aggregation. I'm streaming
video over this link to a few dozen clients over UDP and given the
transmit policy, I should see at least some transmit utilization on
either link. However, for some reason, the system does&lt;/pre&gt;</description>
    <dc:creator>Sašo Kiselkov</dc:creator>
    <dc:date>2011-05-17T21:29:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14216">
    <title>FIN segment with piggybacked data</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14216</link>
    <description>&lt;pre&gt;
Hi all,

I'd like to test a path in Solaris TCP stack where FIN segment with 
piggybacked data is processed (server side).

My first issue is how to effectively/easily generate such connection 
(3WHS + optionally some data segments + FIN with data) on the client 
side. Is there easier way than using raw sockets ?

Secondly, and this is tied to the first question, is what can make TCP 
stack (primarily interested in client side) to emit FIN+data segment, 
both on Solaris and other systems.

Any insights will be appreciated,


v.
&lt;/pre&gt;</description>
    <dc:creator>Vladimir Kotal</dc:creator>
    <dc:date>2011-05-12T13:53:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14203">
    <title>SO_LINGER option behavior</title>
    <link>http://comments.gmane.org/gmane.os.solaris.opensolaris.networking/14203</link>
    <description>&lt;pre&gt;I want to gather some info about what apps expect from setting
the SO_LINGER option with a non-zero linger time on a TCP socket.
Suppose after the specified linger timeout, some data still cannot
be sent or some data has not been ack'ed by the peer.  In this
case, the close() will return an error as documented.  But what do
apps expect the underlying TCP connection will behave?  AFAIK,
there is no Solaris document which states what will happen to
the underlying TCP connection.  Do apps expect that the connection
will be aborted after the timeout, the same behavior if a zero linger
time is set?


&lt;/pre&gt;</description>
    <dc:creator>Kacheong Poon</dc:creator>
    <dc:date>2011-05-06T15:44:17</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.os.solaris.opensolaris.networking">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.os.solaris.opensolaris.networking</link>
  </textinput>
</rdf:RDF>
