<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<id>tag:old.nabble.com,2006:forum-6602</id>
	<title>Nabble - freebsd-net</title>
	<updated>2009-11-28T09:04:38Z</updated>
	<link rel="self" type="application/atom+xml" href="http://old.nabble.com/freebsd-net-f6602.xml" />
	<link rel="alternate" type="text/html" href="http://old.nabble.com/freebsd-net-f6602.html" />
	<subtitle type="html">Networking and TCP/IP with FreeBSD</subtitle>
	
<entry>
	<id>tag:old.nabble.com,2006:post-26554902</id>
	<title>Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock</title>
	<published>2009-11-28T09:04:38Z</published>
	<updated>2009-11-28T09:04:38Z</updated>
	<author>
		<name>Glen Barber-2</name>
	</author>
	<content type="html">Hi,
&lt;br&gt;&lt;br&gt;On Mon, Nov 23, 2009 at 9:30 PM, Benjamin Kaduk &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26554902&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;kaduk@...&lt;/a&gt;&amp;gt; &amp;gt;  &amp;gt;
&lt;br&gt;On Sun, 22 Nov 2009, Bernhard Schmidt wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt;  &amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;  &amp;gt;&amp;gt; Can you verify that the LOR is gone with the latest checkout of my
&lt;br&gt;&amp;gt;  &amp;gt;&amp;gt; repository?
&lt;br&gt;&amp;gt;  &amp;gt;&amp;gt; Compile instructions:
&lt;br&gt;&amp;gt;  &amp;gt;&amp;gt; &lt;a href=&quot;http://forums.freebsd.org/showpost.php?p=47627&amp;postcount=16&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://forums.freebsd.org/showpost.php?p=47627&amp;postcount=16&lt;/a&gt;&lt;br&gt;&amp;gt;  &amp;gt;
&lt;br&gt;&amp;gt;  &amp;gt; I upgraded to today's current (which picked up a number of probably-unrelated
&lt;br&gt;&amp;gt;  &amp;gt; changes), and then installed the driver from
&lt;br&gt;&amp;gt;  &amp;gt; your tree on top of it.
&lt;br&gt;&amp;gt;  &amp;gt; No LOR on boot, and I'll let you know if I see any lockups.
&lt;/div&gt;&lt;br&gt;I am seeing this LOR on 8-STABLE (with the latest iwn(4) patches from
&lt;br&gt;the site above).
&lt;br&gt;&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;  I got a &amp;quot;lockup&amp;quot; (no idea what actually was happening) while in X tonight;
&lt;br&gt;&amp;gt;  nothing useful is in the logs.
&lt;br&gt;&lt;br&gt;Do you mean &amp;quot;lockup&amp;quot; as in the system becomes non-responsive? &amp;nbsp;If so,
&lt;br&gt;I am experiencing this as well.
&lt;br&gt;&lt;br&gt;I recently switched my filesystem to ZFS because of the time fsck_ufs
&lt;br&gt;takes, and added the following options to GENERIC to try to track this
&lt;br&gt;down:
&lt;br&gt;&lt;br&gt;KDB
&lt;br&gt;DDB
&lt;br&gt;BREAK_TO_DEBUGGER
&lt;br&gt;ALT_BREAK_TO_DEBUGGER
&lt;br&gt;INVARIANTS
&lt;br&gt;INVARIANT_SUPPORT
&lt;br&gt;WITNESS
&lt;br&gt;WITNESS_SKIPSPIN
&lt;br&gt;SOCKBUF_DEBUG
&lt;br&gt;DIAGNOSTIC
&lt;br&gt;SW_WATCHDOG
&lt;br&gt;DEBUG_VFS_LOCKS
&lt;br&gt;&lt;br&gt;&lt;br&gt;&amp;gt;  I'm not even sure if I can blame iwn for it ...
&lt;br&gt;&lt;br&gt;The last time the system locked, I wasn't in X. &amp;nbsp;I saw the following
&lt;br&gt;on the console before it became unusable:
&lt;br&gt;&lt;br&gt;&lt;br&gt;firmware error log:
&lt;br&gt;error type &amp;nbsp; &amp;nbsp; &amp;nbsp;= &amp;quot;SYSASSERT&amp;quot; (0x00000005)
&lt;br&gt;program counter = 0x0000C920
&lt;br&gt;source line &amp;nbsp; &amp;nbsp; = 0x00000619
&lt;br&gt;error data &amp;nbsp; &amp;nbsp; &amp;nbsp;= 0x000000FE00000000
&lt;br&gt;branch link &amp;nbsp; &amp;nbsp; = 0x0000C8420000C842
&lt;br&gt;interrupt link &amp;nbsp;= 0x0000090E00000000
&lt;br&gt;time &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;= 1182627
&lt;br&gt;driver status:
&lt;br&gt;tx ring &amp;nbsp;0: qid=0 &amp;nbsp;cur=1 &amp;nbsp; queued=1
&lt;br&gt;tx ring &amp;nbsp;1: qid=1 &amp;nbsp;cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring &amp;nbsp;2: qid=2 &amp;nbsp;cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring &amp;nbsp;3: qid=3 &amp;nbsp;cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring &amp;nbsp;4: qid=4 &amp;nbsp;cur=12 &amp;nbsp;queued=0
&lt;br&gt;tx ring &amp;nbsp;5: qid=5 &amp;nbsp;cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring &amp;nbsp;6: qid=6 &amp;nbsp;cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring &amp;nbsp;7: qid=7 &amp;nbsp;cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring &amp;nbsp;8: qid=8 &amp;nbsp;cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring &amp;nbsp;9: qid=9 &amp;nbsp;cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 10: qid=10 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 11: qid=11 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 12: qid=12 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 13: qid=13 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 14: qid=14 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 15: qid=15 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 16: qid=16 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 17: qid=17 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 18: qid=18 cur=0 &amp;nbsp; queued=0
&lt;br&gt;tx ring 19: qid=19 cur=0 &amp;nbsp; queued=0
&lt;br&gt;rx ring: cur=59
&lt;br&gt;iwn0: iwn_apm_stop_master: timeout waiting for master
&lt;br&gt;&lt;br&gt;If there is more information I can provide, please let me know.
&lt;br&gt;&lt;br&gt;&lt;br&gt;-- 
&lt;br&gt;Glen Barber
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26554902&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26554902&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-kern-140036%3A--iwn---lor--lock-order-reversal-with-iwn0_com_lock-and-iwn0-softc-lock-tp26473675p26554902.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26554085</id>
	<title>Re: kern/140970: [bce] The two NetXtreme II BCM5709S NICs on our HP Bl460c G1 Blade can't be accessed on FreeBSD 7.2 and 8 [regression]</title>
	<published>2009-11-28T07:27:50Z</published>
	<updated>2009-11-28T07:27:50Z</updated>
	<author>
		<name>linimon</name>
	</author>
	<content type="html">Old Synopsis: [bce] The two NetXtreme II BCM5709S NICs on our HP Bl460c G1 Blade can't be accessed on FreeBSD 7.2 and 8
&lt;br&gt;New Synopsis: [bce] The two NetXtreme II BCM5709S NICs on our HP Bl460c G1 Blade can't be accessed on FreeBSD 7.2 and 8 [regression]
&lt;br&gt;&lt;br&gt;Responsible-Changed-From-To: freebsd-bugs-&amp;gt;freebsd-net
&lt;br&gt;Responsible-Changed-By: linimon
&lt;br&gt;Responsible-Changed-When: Sat Nov 28 15:26:24 UTC 2009
&lt;br&gt;Responsible-Changed-Why: 
&lt;br&gt;Over to maintainer(s).
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.freebsd.org/cgi/query-pr.cgi?pr=140970&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.freebsd.org/cgi/query-pr.cgi?pr=140970&lt;/a&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26554085&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26554085&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-kern-140970%3A--bce--The-two-NetXtreme-II-BCM5709S-NICs-on-our-HP-Bl460c-G1-Blade-can%27t-be-accessed-on-FreeBSD-7.2-and-8--regression--tp26554085p26554085.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26551735</id>
	<title>Fix available for run driver</title>
	<published>2009-11-28T02:06:07Z</published>
	<updated>2009-11-28T02:06:07Z</updated>
	<author>
		<name>PseudoCylon</name>
	</author>
	<content type="html">Hello,
&lt;br&gt;&lt;br&gt;There are some fixes for run driver for 8.0 release and current. It can be downloaded from freebsd forums at
&lt;br&gt;&lt;a href=&quot;http://forums.freebsd.org/showpost.php?s=87e376cf71273061f7de5aaf258132a1&amp;p=44110&amp;postcount=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://forums.freebsd.org/showpost.php?s=87e376cf71273061f7de5aaf258132a1&amp;p=44110&amp;postcount=1&lt;/a&gt;&lt;br&gt;&lt;br&gt;Some packet loss/drop and memory leak have been identified and fixed. (It improved some performance, too)
&lt;br&gt;&lt;br&gt;Also, 40 more vender/device IDs have been added.
&lt;br&gt;&lt;br&gt;Details are on RELEASE_NOTES included.
&lt;br&gt;&lt;br&gt;Please update before the driver causing any troubles.
&lt;br&gt;&lt;br&gt;Akinori
&lt;br&gt;&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; __________________________________________________________________
&lt;br&gt;Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at &lt;a href=&quot;http://downloads.yahoo.com/ca/internetexplorer/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://downloads.yahoo.com/ca/internetexplorer/&lt;/a&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26551735&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26551735&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Fix-available-for-run-driver-tp26551735p26551735.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26551141</id>
	<title>Re: interface FIB</title>
	<published>2009-11-28T00:03:53Z</published>
	<updated>2009-11-28T00:03:53Z</updated>
	<author>
		<name>Igor Sysoev</name>
	</author>
	<content type="html">On Fri, Nov 27, 2009 at 09:12:37PM -0800, Julian Elischer wrote:
&lt;br&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; Igor Sysoev wrote:
&lt;br&gt;&amp;gt; &amp;gt; Currently only packets generated during encapsulation can use
&lt;br&gt;&amp;gt; &amp;gt; interface's FIB stored during interface creation:
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; setfib 1 ifconfig gif0 ...
&lt;br&gt;&amp;gt; &amp;gt; setfib 1 ifconfig tun0 ...
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; not sure if tun actually does this (in fac tit shouldn't)
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; but for gre and gif (and stf) these are tunnelling other things into 
&lt;br&gt;&amp;gt; IP and thus it makes sense to be able to connect a routing table with 
&lt;br&gt;&amp;gt; the generated envelopes.
&lt;/div&gt;&lt;br&gt;I've got this from 8.0 release notes:
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;A packet generated on tunnel interfaces such as gif(4) and tun(4) will
&lt;br&gt;&amp;nbsp; &amp;nbsp;be encapsulated using the FIB of the process which set up the tunnel.
&lt;br&gt;&lt;br&gt;However, sys/net/if_tun.c is really has no FIB related changes.
&lt;br&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; &amp;gt; is it possible to implement this feature for any interface:
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; setfib 1 ifconfig vlan0 ...
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; or
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; ifconfig vlan0 setfib 1 ...
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; these two things would mean differnt things.
&lt;br&gt;&amp;gt; and one of them wouldn't mean anything.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; setfig 1 ifconfig vlan0 woudl mean &amp;quot;what&amp;quot; exactly?
&lt;br&gt;&amp;gt; VLAN tagging is an L2/L1 operation and FIBS have no effect on this.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; as for ifconfig vlan0 setfib 1, or &amp;nbsp;ifconfig em0 setfib 1
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; this will (shortly) mean that incoming packets through this interface 
&lt;br&gt;&amp;gt; will be default be connected with fib 1 so the any return packets 
&lt;br&gt;&amp;gt; (resets, icmp etc.) will use FIB1 to go back to the sender.
&lt;/div&gt;&lt;br&gt;This is exactly what I meant.
&lt;br&gt;&lt;br&gt;&amp;gt; That patch is in the works.
&lt;br&gt;&lt;br&gt;I'm ready to test the patch in production on 7/8-STABLE if the patch
&lt;br&gt;can be applied to it.
&lt;br&gt;&lt;br&gt;&lt;br&gt;-- 
&lt;br&gt;Igor Sysoev
&lt;br&gt;&lt;a href=&quot;http://sysoev.ru/en/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://sysoev.ru/en/&lt;/a&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26551141&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26551141&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/interface-FIB-tp26539495p26551141.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26550581</id>
	<title>Re: interface FIB</title>
	<published>2009-11-27T21:12:37Z</published>
	<updated>2009-11-27T21:12:37Z</updated>
	<author>
		<name>Julian Elischer</name>
	</author>
	<content type="html">Igor Sysoev wrote:
&lt;br&gt;&amp;gt; Currently only packets generated during encapsulation can use
&lt;br&gt;&amp;gt; interface's FIB stored during interface creation:
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; setfib 1 ifconfig gif0 ...
&lt;br&gt;&amp;gt; setfib 1 ifconfig tun0 ...
&lt;br&gt;&lt;br&gt;not sure if tun actually does this (in fac tit shouldn't)
&lt;br&gt;&lt;br&gt;but for gre and gif (and stf) these are tunnelling other things into 
&lt;br&gt;IP and thus it makes sense to be able to connect a routing table with 
&lt;br&gt;the generated envelopes.
&lt;br&gt;&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; is it possible to implement this feature for any interface:
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; setfib 1 ifconfig vlan0 ...
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; or
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; ifconfig vlan0 setfib 1 ...
&lt;br&gt;&lt;br&gt;these two things would mean differnt things.
&lt;br&gt;and one of them wouldn't mean anything.
&lt;br&gt;&lt;br&gt;setfig 1 ifconfig vlan0 woudl mean &amp;quot;what&amp;quot; exactly?
&lt;br&gt;VLAN tagging is an L2/L1 operation and FIBS have no effect on this.
&lt;br&gt;&lt;br&gt;as for ifconfig vlan0 setfib 1, or &amp;nbsp;ifconfig em0 setfib 1
&lt;br&gt;&lt;br&gt;this will (shortly) mean that incoming packets through this interface 
&lt;br&gt;will be default be connected with fib 1 so the any return packets 
&lt;br&gt;(resets, icmp etc.) will use FIB1 to go back to the sender.
&lt;br&gt;&lt;br&gt;That patch is in the works.
&lt;br&gt;&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; 
&lt;br&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26550581&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26550581&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/interface-FIB-tp26539495p26550581.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26545794</id>
	<title>Re: ipw driver on FreeBSD 8.0</title>
	<published>2009-11-27T09:33:13Z</published>
	<updated>2009-11-27T09:33:13Z</updated>
	<author>
		<name>Guido Falsi</name>
	</author>
	<content type="html">On Thu, Nov 26, 2009 at 09:31:58PM -0500, Chris wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; Hello,
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Months ago there was some chatter about the ipw driver (For Centrino Intel
&lt;br&gt;&amp;gt; 2100 wireless) being broken in 8.0 but that was when 8.0 was still under the
&lt;br&gt;&amp;gt; CURRENT branch. Can anyone tell me if it has been fixed? I'm having a heck
&lt;br&gt;&amp;gt; of a time trying to get it to work with the new VAP stuff. Here's the thread
&lt;br&gt;&amp;gt; I'm referring to:
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/wpa_supplicant-can%27t-associate-with-WPA2-AP-td22687633.html&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://old.nabble.com/wpa_supplicant-can%27t-associate-with-WPA2-AP-td22687633.html&lt;/a&gt;&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; I'm seeing exactly the same problem shown in the thread when trying to
&lt;br&gt;&amp;gt; associate with a regular WPA access point.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Any info would be appreciated!
&lt;/div&gt;&lt;br&gt;That was me having thet problem on my old laptop. Still using that same 
&lt;br&gt;laptop(I'd like to buy the latest hardware for my home setup, but at &amp;nbsp; &amp;nbsp;
&lt;br&gt;this time of the year I like spending my money to go to sky!).
&lt;br&gt;&lt;br&gt;I have not tried ipw driver anymore, I have &amp;quot;fixed&amp;quot; the problem by using
&lt;br&gt;ndis. Works like a charm, so if you have this problem I suggest you do
&lt;br&gt;the same. I have not seen any major commit to the ipw driver, so my take
&lt;br&gt;is it is as it was then. Please correct me if I'm wrong.
&lt;br&gt;&lt;br&gt;Some time ago I also had a look at the driver source, but it really
&lt;br&gt;requires some major knowledge of wlan protocols and device interface,
&lt;br&gt;and I lack both.
&lt;br&gt;&lt;br&gt;BTW, at present my biggest problem with WiFi is the one described in PR
&lt;br&gt;kern/139117: [lagg] + wlan boot timing (EBUSY).
&lt;br&gt;&lt;br&gt;I encountered it while trying to configure a wlan(with WPA2) failsafe
&lt;br&gt;lagg with the cabled ethernet.
&lt;br&gt;&lt;br&gt;Any news on that front?
&lt;br&gt;&lt;br&gt;Sorry if I could not be of any more help and thanks for any answers to
&lt;br&gt;my query.
&lt;br&gt;&lt;br&gt;P.S. I'm also CCing freebsd-net@, since the problems seems to be
&lt;br&gt;appropriate there.
&lt;br&gt;&lt;br&gt;-- 
&lt;br&gt;Guido Falsi &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26545794&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;mad@...&lt;/a&gt;&amp;gt;
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26545794&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26545794&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-ipw-driver-on-FreeBSD-8.0-tp26545794p26545794.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26540431</id>
	<title>Re: svn commit: r198994 - in stable/6/sys/dev: bce mii</title>
	<published>2009-11-27T02:22:14Z</published>
	<updated>2009-11-27T02:22:14Z</updated>
	<author>
		<name>pluknet</name>
	</author>
	<content type="html">2009/11/6 Doug Ambrisko &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26540431&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;ambrisko@...&lt;/a&gt;&amp;gt;:
&lt;div class='shrinkable-quote'&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; Author: ambrisko
&lt;br&gt;&amp;gt; Date: Fri Nov  6 17:58:44 2009
&lt;br&gt;&amp;gt; New Revision: 198994
&lt;br&gt;&amp;gt; URL: &lt;a href=&quot;http://svn.freebsd.org/changeset/base/198994&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://svn.freebsd.org/changeset/base/198994&lt;/a&gt;&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Log:
&lt;br&gt;&amp;gt;  MFC: Merge in minimal 5709/5716 support into 6.X extracted from current.
&lt;br&gt;&amp;gt;  This is not a direct merge since I tried to only extra the changes to
&lt;br&gt;&amp;gt;  support the 5709 from all of the other changes that have happened in
&lt;br&gt;&amp;gt;  head.  This should not introduce any issues that the other changes may
&lt;br&gt;&amp;gt;  have caused.  We have been running this code for months on Dell r710's.
&lt;br&gt;&amp;gt;  It has been lightly tested on systems with 5716's.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;  This is to allow people to run newer hardware on 6.X.
&lt;/div&gt;&lt;/div&gt;&lt;br&gt;Very nice. Thank you.
&lt;br&gt;&lt;br&gt;I'm afraid not all the chunks were merged since I cannot run on 6.x
&lt;br&gt;with my BCM5709.
&lt;br&gt;&lt;br&gt;FreeBSD 7.2 - works
&lt;br&gt;FreeBSD 6.4-stable - does not
&lt;br&gt;&lt;br&gt;It locks up somewhere in the late stage of multiuser (usually in a
&lt;br&gt;random step of rc.d) and getty cannot take the control.
&lt;br&gt;Here it still pings via network, I can achieve ssh stage where ssh
&lt;br&gt;warns me &amp;quot;The authenticity of host '$HOST' can't be established.&amp;quot;
&lt;br&gt;If I type &amp;quot;yes&amp;quot;, then it stops here and no go. After return from ddb
&lt;br&gt;it stops even ping until next reboot.
&lt;br&gt;&lt;br&gt;I use boot via NFS/PXE, so it may interfere there, since rc.d usually
&lt;br&gt;write something to disk, which is NFS-mounted here.
&lt;br&gt;So it probably could run fine if booting from a local disk (I can't
&lt;br&gt;test this setup).
&lt;br&gt;&lt;br&gt;I've attached dmesg (doesn't differs much from 7.2) and some ddb output below.
&lt;br&gt;Looking in alltrace I see no obvious lockups, no nfs stuck. But
&lt;br&gt;sometimes sh stucks somewhere in nfsreq.
&lt;br&gt;&lt;br&gt;The same box boots fine via NFS on different NFS setup with 7.2,
&lt;br&gt;a different (in h/w) box boots fine on these NFS setup and NFS root,
&lt;br&gt;so no mistakes in setup part.
&lt;br&gt;&lt;br&gt;I remember that back to August I tried to boot 6.4 with what is in bce
&lt;br&gt;of RELENG_7 on this box and it booted fine and I xmitted some traffic
&lt;br&gt;with it.
&lt;br&gt;So I guess the problem is in NFS-boot.
&lt;br&gt;&lt;br&gt;I'll try to find ways to boot the system locally and report back..
&lt;br&gt;&lt;br&gt;-- 
&lt;br&gt;wbr,
&lt;br&gt;pluknet
&lt;br&gt;&lt;br /&gt; &lt;br /&gt; &lt;br /&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26540431&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26540431&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;&lt;div class=&quot;small&quot;&gt;&lt;br/&gt;&lt;img src=&quot;http://old.nabble.com/images/icon_attachment.gif&quot; &gt; &lt;strong&gt;dmesg.x3650m2-6.4-patched-verbose-bce&lt;/strong&gt; (1K) &lt;a href=&quot;http://old.nabble.com/attachment/26540431/0/dmesg.x3650m2-6.4-patched-verbose-bce&quot; target=&quot;_top&quot;&gt;Download Attachment&lt;/a&gt;&lt;br/&gt;&lt;img src=&quot;http://old.nabble.com/images/icon_attachment.gif&quot; &gt; &lt;strong&gt;dmesg.x3650m2-6.4-patched&lt;/strong&gt; (91K) &lt;a href=&quot;http://old.nabble.com/attachment/26540431/1/dmesg.x3650m2-6.4-patched&quot; target=&quot;_top&quot;&gt;Download Attachment&lt;/a&gt;&lt;/div&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-svn-commit%3A-r198994---in-stable-6-sys-dev%3A-bce-mii-tp26540431p26540431.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26539495</id>
	<title>interface FIB</title>
	<published>2009-11-27T00:55:04Z</published>
	<updated>2009-11-27T00:55:04Z</updated>
	<author>
		<name>Igor Sysoev</name>
	</author>
	<content type="html">Currently only packets generated during encapsulation can use
&lt;br&gt;interface's FIB stored during interface creation:
&lt;br&gt;&lt;br&gt;setfib 1 ifconfig gif0 ...
&lt;br&gt;setfib 1 ifconfig tun0 ...
&lt;br&gt;&lt;br&gt;is it possible to implement this feature for any interface:
&lt;br&gt;&lt;br&gt;setfib 1 ifconfig vlan0 ...
&lt;br&gt;&lt;br&gt;or
&lt;br&gt;&lt;br&gt;ifconfig vlan0 setfib 1 ...
&lt;br&gt;&lt;br&gt;&lt;br&gt;-- 
&lt;br&gt;Igor Sysoev
&lt;br&gt;&lt;a href=&quot;http://sysoev.ru/en/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://sysoev.ru/en/&lt;/a&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26539495&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26539495&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/interface-FIB-tp26539495p26539495.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26534723</id>
	<title>GRED on queue or pipe</title>
	<published>2009-11-26T12:34:04Z</published>
	<updated>2009-11-26T12:34:04Z</updated>
	<author>
		<name>Jon Otterholm</name>
	</author>
	<content type="html">Doing some test of gred in dummynet. My ruleset consists of a number of 
&lt;br&gt;queues connected to the same pipe. Queues have different weight and I 
&lt;br&gt;want to make use of gred instead of taildrop.
&lt;br&gt;&lt;br&gt;Should i define gred on the queues or on the pipe? To me it seems 
&lt;br&gt;reasonable to set it on the pipe and let the pipe handle the weight from 
&lt;br&gt;the queues.
&lt;br&gt;&lt;br&gt;How do I define the queue-depth on queues and pipes? If the pipe has 
&lt;br&gt;2000 slots should queues have the same number on queues or should the 
&lt;br&gt;total number of slots in all queues sum up to the number defined in the 
&lt;br&gt;pipe?
&lt;br&gt;&lt;br&gt;Example:
&lt;br&gt;&lt;br&gt;ipfw queue 1000 config pipe 1000 weight 5
&lt;br&gt;ipfw queue 2000 config pipe 2000 weight 5
&lt;br&gt;ipfw queue 1001 config pipe 1000 weight 80
&lt;br&gt;ipfw queue 2001 config pipe 2000 weight 80
&lt;br&gt;ipfw pipe 1000 config bw 100Mbit/s buckets 65535 queue 2000 gred 
&lt;br&gt;0.002/1800/2000/0.1
&lt;br&gt;ipfw pipe 2000 config bw 100Mbit/s buckets 65535 queue 2000 gred 
&lt;br&gt;0.002/1800/2000/0.1
&lt;br&gt;&lt;br&gt;ipfw add 10 queue 1000 ip from any to table(10) dst-port 25 out xmit em1 &amp;nbsp;
&lt;br&gt;ipfw add 10 queue 2000 ip from table(10) to any dst-port 25 out xmit em0
&lt;br&gt;ipfw add 20 queue 1001 ip from any to table(20) out xmit em1 &amp;nbsp; &amp;nbsp; 
&lt;br&gt;ipfw add 20 queue 2001 ip from table(20) to any out xmit em0
&lt;br&gt;&lt;br&gt;//JO
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26534723&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26534723&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/GRED-on-queue-or-pipe-tp26534723p26534723.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26524536</id>
	<title>Re: What is better? Use a SMP kernel or amd64 for network?</title>
	<published>2009-11-25T21:28:36Z</published>
	<updated>2009-11-25T21:28:36Z</updated>
	<author>
		<name>Julian Elischer</name>
	</author>
	<content type="html">Han Hwei Woo wrote:
&lt;br&gt;&amp;gt; It used to be that UP i386 was the way to go for best routing performance.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; I'm not sure if this has changed more recently, due to the changes in
&lt;br&gt;&amp;gt; the network stack.
&lt;br&gt;&lt;br&gt;In all seriousness, try it and let us know.
&lt;br&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Wes Morgan wrote:
&lt;br&gt;&amp;gt;&amp;gt; On Wed, 25 Nov 2009, Rafael Ganascim wrote:
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt; Hi list,
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt; I have a doubt (don't encountered on google) about what is better for a
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt; FreeBSD Router: use a 32bits SMP kernel or an amd64? I know that
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt; exists some
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt; differences, but generaly, what is better and why?
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt; I have a hardware with Xeon Dual processor.
&lt;br&gt;&amp;gt;&amp;gt; Why not an SMP amd64 kernel? SMP is not exclusive to i386.
&lt;br&gt;&amp;gt;&amp;gt; _______________________________________________
&lt;br&gt;&amp;gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26524536&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;gt;&amp;gt; &lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;&amp;gt;&amp;gt; To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26524536&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; _______________________________________________
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26524536&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;&amp;gt; To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26524536&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;/div&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26524536&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26524536&amp;i=5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/What-is-better--Use-a-SMP-kernel-or-amd64-for-network--tp26518375p26524536.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26522534</id>
	<title>Re: What is better? Use a SMP kernel or amd64 for network?</title>
	<published>2009-11-25T15:32:35Z</published>
	<updated>2009-11-25T15:32:35Z</updated>
	<author>
		<name>Han Hwei Woo</name>
	</author>
	<content type="html">It used to be that UP i386 was the way to go for best routing performance.
&lt;br&gt;&lt;br&gt;I'm not sure if this has changed more recently, due to the changes in
&lt;br&gt;the network stack.
&lt;br&gt;&lt;br&gt;&lt;br&gt;Wes Morgan wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; On Wed, 25 Nov 2009, Rafael Ganascim wrote:
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; Hi list,
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; I have a doubt (don't encountered on google) about what is better for a
&lt;br&gt;&amp;gt;&amp;gt; FreeBSD Router: use a 32bits SMP kernel or an amd64? I know that
&lt;br&gt;&amp;gt;&amp;gt; exists some
&lt;br&gt;&amp;gt;&amp;gt; differences, but generaly, what is better and why?
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; I have a hardware with Xeon Dual processor.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Why not an SMP amd64 kernel? SMP is not exclusive to i386.
&lt;br&gt;&amp;gt; _______________________________________________
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26522534&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;&amp;gt; To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26522534&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;/div&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26522534&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26522534&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/What-is-better--Use-a-SMP-kernel-or-amd64-for-network--tp26518375p26522534.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26522123</id>
	<title>netstat -an shows me an open &quot;phantom&quot; tcp6 port</title>
	<published>2009-11-25T15:08:10Z</published>
	<updated>2009-11-25T15:08:10Z</updated>
	<author>
		<name>Thomas Vogt-3</name>
	</author>
	<content type="html">Hi
&lt;br&gt;&lt;br&gt;I'm confused. I've a new installed FreeBSD system. I'm running NFS, 
&lt;br&gt;http, ntpd and a ftp server. If i look for open ports netstat shows me 
&lt;br&gt;something on port 1000 (ipv6)
&lt;br&gt;&lt;br&gt;netstat -an | grep 1000
&lt;br&gt;tcp6 &amp;nbsp; &amp;nbsp; &amp;nbsp; 0 &amp;nbsp; &amp;nbsp; &amp;nbsp;0 *.1000 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; *.* &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;LISTEN
&lt;br&gt;&lt;br&gt;But sockstat shows me nothing:
&lt;br&gt;&lt;br&gt;sockstat -6 | grep tcp6
&lt;br&gt;root &amp;nbsp; &amp;nbsp; sshd &amp;nbsp; &amp;nbsp; &amp;nbsp; 704 &amp;nbsp; 3 &amp;nbsp;tcp6 &amp;nbsp; *:22 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;*:*
&lt;br&gt;root &amp;nbsp; &amp;nbsp; rpc.statd &amp;nbsp;599 &amp;nbsp; 6 &amp;nbsp;tcp6 &amp;nbsp; *:912 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; *:*
&lt;br&gt;root &amp;nbsp; &amp;nbsp; rpcbind &amp;nbsp; &amp;nbsp;597 &amp;nbsp; 8 &amp;nbsp;tcp6 &amp;nbsp; *:111 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; *:*
&lt;br&gt;&lt;br&gt;&lt;br&gt;Also lsof -i 6 -a -P shows me nothing on port 1000.
&lt;br&gt;&lt;br&gt;Any idea who i can figure out whats running on port 1000 with ipv6? Only 
&lt;br&gt;the loopback interface has an ipv6 address.
&lt;br&gt;&lt;br&gt;System:
&lt;br&gt;FreeBSD 7.2-RELEASE-p4 amd64
&lt;br&gt;&lt;br&gt;Regards,
&lt;br&gt;Thomas
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26522123&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26522123&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/netstat--an-shows-me-an-open-%22phantom%22-tcp6-port-tp26522123p26522123.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26521564</id>
	<title>Re: What is better? Use a SMP kernel or amd64 for network?</title>
	<published>2009-11-25T14:42:20Z</published>
	<updated>2009-11-25T14:42:20Z</updated>
	<author>
		<name>Wes Morgan-2</name>
	</author>
	<content type="html">On Wed, 25 Nov 2009, Rafael Ganascim wrote:
&lt;br&gt;&lt;br&gt;&amp;gt; Hi list,
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; I have a doubt (don't encountered on google) about what is better for a
&lt;br&gt;&amp;gt; FreeBSD Router: use a 32bits SMP kernel or an amd64? I know that exists some
&lt;br&gt;&amp;gt; differences, but generaly, what is better and why?
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; I have a hardware with Xeon Dual processor.
&lt;br&gt;&lt;br&gt;Why not an SMP amd64 kernel? SMP is not exclusive to i386.
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26521564&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26521564&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/What-is-better--Use-a-SMP-kernel-or-amd64-for-network--tp26518375p26521564.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26518375</id>
	<title>What is better? Use a SMP kernel or amd64 for network?</title>
	<published>2009-11-25T10:34:26Z</published>
	<updated>2009-11-25T10:34:26Z</updated>
	<author>
		<name>Rafael Ganascim</name>
	</author>
	<content type="html">Hi list,
&lt;br&gt;&lt;br&gt;I have a doubt (don't encountered on google) about what is better for a
&lt;br&gt;FreeBSD Router: use a 32bits SMP kernel or an amd64? I know that exists some
&lt;br&gt;differences, but generaly, what is better and why?
&lt;br&gt;&lt;br&gt;I have a hardware with Xeon Dual processor.
&lt;br&gt;&lt;br&gt;&lt;br&gt;Thanks,
&lt;br&gt;&lt;br&gt;Rafael
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26518375&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26518375&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/What-is-better--Use-a-SMP-kernel-or-amd64-for-network--tp26518375p26518375.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26518353</id>
	<title>Wireless PCI recommendations for CURRENT</title>
	<published>2009-11-25T10:34:11Z</published>
	<updated>2009-11-25T10:34:11Z</updated>
	<author>
		<name>ebw</name>
	</author>
	<content type="html">I'd like suggestions for a PCI wifi. Vanilla tower with -CURRENT.
&lt;br&gt;&lt;br&gt;Thanks in advance,
&lt;br&gt;Eric
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26518353&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26518353&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/bce%284%29-BCM5907-CTX-write-errors-on-7.2-driver-tp26081795p26518353.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26517858</id>
	<title>Getting creation and modification time of an IPv6 interface address</title>
	<published>2009-11-25T10:22:09Z</published>
	<updated>2009-11-25T10:22:09Z</updated>
	<author>
		<name>Harti Brandt</name>
	</author>
	<content type="html">&lt;br&gt;Hi,
&lt;br&gt;&lt;br&gt;I'm working on the IpAddressTable for bsnmpd. This table has two rows ipAddressCreated and ipAddressLastUpdated which seem to
&lt;br&gt;correspond to the created and changed fields of the struct in6_ifaddr. Because there seems no way (except for poking in the
&lt;br&gt;kernel memory) to get at these values I have added an ioctl to get them much in the spirit of the other ioctls for IPv6 addresses.
&lt;br&gt;&lt;br&gt;I'm not sure how the ioctl codes are allocated so I just took the next available one. If this looks ok and there are no principal problems,
&lt;br&gt;I would like to commit that.
&lt;br&gt;&lt;br&gt;harti
&lt;br&gt;&lt;br&gt;Index: in6.c
&lt;br&gt;===================================================================
&lt;br&gt;RCS file: /usr/cvsup/src/sys/netinet6/in6.c,v
&lt;br&gt;retrieving revision 1.121.2.8
&lt;br&gt;diff -u -r1.121.2.8 in6.c
&lt;br&gt;--- in6.c	28 Oct 2009 21:45:25 -0000	1.121.2.8
&lt;br&gt;+++ in6.c	25 Nov 2009 17:41:40 -0000
&lt;br&gt;@@ -312,6 +312,7 @@
&lt;br&gt;&amp;nbsp;	case SIOCSIFALIFETIME_IN6:
&lt;br&gt;&amp;nbsp;	case SIOCGIFSTAT_IN6:
&lt;br&gt;&amp;nbsp;	case SIOCGIFSTAT_ICMP6:
&lt;br&gt;+	case SIOCGIFATIMES_IN6:
&lt;br&gt;&amp;nbsp;		sa6 = &amp;ifr-&amp;gt;ifr_addr;
&lt;br&gt;&amp;nbsp;		break;
&lt;br&gt;&amp;nbsp;	default:
&lt;br&gt;@@ -383,6 +384,7 @@
&lt;br&gt;&amp;nbsp;	case SIOCGIFNETMASK_IN6:
&lt;br&gt;&amp;nbsp;	case SIOCGIFDSTADDR_IN6:
&lt;br&gt;&amp;nbsp;	case SIOCGIFALIFETIME_IN6:
&lt;br&gt;+	case SIOCGIFATIMES_IN6:
&lt;br&gt;&amp;nbsp;		/* must think again about its semantics */
&lt;br&gt;&amp;nbsp;		if (ia == NULL) {
&lt;br&gt;&amp;nbsp;			error = EADDRNOTAVAIL;
&lt;br&gt;@@ -652,6 +654,11 @@
&lt;br&gt;&amp;nbsp;			prelist_remove(pr);
&lt;br&gt;&amp;nbsp;		EVENTHANDLER_INVOKE(ifaddr_event, ifp);
&lt;br&gt;&amp;nbsp;		break;
&lt;br&gt;+
&lt;br&gt;+	case SIOCGIFATIMES_IN6:
&lt;br&gt;+		ifr-&amp;gt;ifr_ifru.ifru_times[0] = ia-&amp;gt;ia6_createtime;
&lt;br&gt;+		ifr-&amp;gt;ifr_ifru.ifru_times[1] = ia-&amp;gt;ia6_updatetime;
&lt;br&gt;+		break;
&lt;br&gt;&amp;nbsp;	}
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	default:
&lt;br&gt;Index: in6_var.h
&lt;br&gt;===================================================================
&lt;br&gt;RCS file: /usr/cvsup/src/sys/netinet6/in6_var.h,v
&lt;br&gt;retrieving revision 1.45.2.1
&lt;br&gt;diff -u -r1.45.2.1 in6_var.h
&lt;br&gt;--- in6_var.h	3 Aug 2009 08:13:06 -0000	1.45.2.1
&lt;br&gt;+++ in6_var.h	25 Nov 2009 17:07:34 -0000
&lt;br&gt;@@ -277,6 +277,7 @@
&lt;br&gt;&amp;nbsp;		struct in6_ifstat ifru_stat;
&lt;br&gt;&amp;nbsp;		struct icmp6_ifstat ifru_icmp6stat;
&lt;br&gt;&amp;nbsp;		u_int32_t ifru_scope_id[16];
&lt;br&gt;+		time_t	ifru_times[2];
&lt;br&gt;&amp;nbsp;	} ifr_ifru;
&lt;br&gt;&amp;nbsp;};
&lt;br&gt;&amp;nbsp;
&lt;br&gt;@@ -463,6 +464,8 @@
&lt;br&gt;&amp;nbsp;#define SIOCAADDRCTL_POLICY	_IOW('u', 108, struct in6_addrpolicy)
&lt;br&gt;&amp;nbsp;#define SIOCDADDRCTL_POLICY	_IOW('u', 109, struct in6_addrpolicy)
&lt;br&gt;&amp;nbsp;
&lt;br&gt;+#define	SIOCGIFATIMES_IN6	_IOWR('i', 110, struct in6_ifreq)
&lt;br&gt;+
&lt;br&gt;&amp;nbsp;#define IN6_IFF_ANYCAST		0x01	/* anycast address */
&lt;br&gt;&amp;nbsp;#define IN6_IFF_TENTATIVE	0x02	/* tentative address */
&lt;br&gt;&amp;nbsp;#define IN6_IFF_DUPLICATED	0x04	/* DAD detected duplicate */
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26517858&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26517858&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Getting-creation-and-modification-time-of-an-IPv6-interface-address-tp26517858p26517858.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26515367</id>
	<title>Re: [CFR] unified rc.firewall</title>
	<published>2009-11-25T08:01:16Z</published>
	<updated>2009-11-25T08:01:16Z</updated>
	<author>
		<name>Hajimu UMEMOTO</name>
	</author>
	<content type="html">Hi,
&lt;br&gt;&lt;br&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; On Mon, 23 Nov 2009 12:55:25 -0500
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; John Baldwin &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26515367&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;jhb@...&lt;/a&gt;&amp;gt; said:
&lt;br&gt;&lt;br&gt;I updated the patch.
&lt;br&gt;&lt;br&gt;jhb&amp;gt; I had missed the me vs any. &amp;nbsp;It is true that the equivalent rule would use
&lt;br&gt;jhb&amp;gt; me6. &amp;nbsp;I would rather figure out the IPv6 bug so that TCP is treated the
&lt;br&gt;jhb&amp;gt; same for both protocols instead of having a weaker firewall for IPv6 than
&lt;br&gt;jhb&amp;gt; IPV4.
&lt;br&gt;&lt;br&gt;Yes, it is better, definitely. &amp;nbsp;I thought that we could change to use
&lt;br&gt;dynamic rule, once it was fixed.
&lt;br&gt;Since the PR kern/117234 fixed it, I changed to use dynamic rule for
&lt;br&gt;IPv6 as well. &amp;nbsp;So, it requires the patch in the PR.
&lt;br&gt;&lt;br&gt;jhb&amp;gt; I do find the shorter version easier to read, and it matches the existing
&lt;br&gt;jhb&amp;gt; style as well as the examples in the manual page, handbook, etc.
&lt;br&gt;&lt;br&gt;Okay, I changed 'ip6' to 'all' where we can use it, and stopped use of
&lt;br&gt;'proto xxx'' as possible.
&lt;br&gt;&lt;br&gt;I reconsidered oif vs oif6 and iif vs iif6 issue. &amp;nbsp;Now, if
&lt;br&gt;$firewall_simple_oif_ipv6 is not set, $firewall_simple_oif is assumed
&lt;br&gt;for oif6, and, $firewall_simple_iif_ipv6 is not set,
&lt;br&gt;$firewall_simple_iif is assumed for iif6.
&lt;br&gt;Further, I think we don't assign a global IPv6 address to oif in
&lt;br&gt;usual. &amp;nbsp;So, I made $firewall_simple_onet_ipv6 optional.
&lt;br&gt;One more change is that DHCPv6 is allowed as well as IPv4 DHCP for
&lt;br&gt;WORKSTATION type. &amp;nbsp;I'm using DHCPv6 in usual; L2TP + DHCPv6 PD, DHCPv6
&lt;br&gt;DNS option ...
&lt;br&gt;&lt;br&gt;Sincerely,
&lt;br&gt;&lt;br&gt;&lt;br /&gt;&lt;hr align=&quot;left&quot; width=&quot;300&quot; /&gt;&lt;tt&gt;Index: etc/Makefile
&lt;br&gt;diff -u etc/Makefile.orig etc/Makefile
&lt;br&gt;--- etc/Makefile.orig	2009-10-25 10:10:29.000000000 +0900
&lt;br&gt;+++ etc/Makefile	2009-11-22 22:07:19.840275808 +0900
&lt;br&gt;@@ -15,7 +15,7 @@
&lt;br&gt;&amp;nbsp;	inetd.conf libalias.conf login.access login.conf mac.conf motd \
&lt;br&gt;&amp;nbsp;	netconfig network.subr networks newsyslog.conf nsswitch.conf \
&lt;br&gt;&amp;nbsp;	phones profile protocols \
&lt;br&gt;-	rc rc.bsdextended rc.firewall rc.firewall6 rc.initdiskless \
&lt;br&gt;+	rc rc.bsdextended rc.firewall rc.initdiskless \
&lt;br&gt;&amp;nbsp;	rc.sendmail rc.shutdown \
&lt;br&gt;&amp;nbsp;	rc.subr remote rpc services shells \
&lt;br&gt;&amp;nbsp;	sysctl.conf syslog.conf \
&lt;br&gt;Index: etc/defaults/rc.conf
&lt;br&gt;diff -u etc/defaults/rc.conf.orig etc/defaults/rc.conf
&lt;br&gt;--- etc/defaults/rc.conf.orig	2009-10-25 10:10:29.000000000 +0900
&lt;br&gt;+++ etc/defaults/rc.conf	2009-11-22 21:25:22.343296205 +0900
&lt;br&gt;@@ -118,7 +118,10 @@
&lt;br&gt;&amp;nbsp;firewall_quiet=&amp;quot;NO&amp;quot;		# Set to YES to suppress rule display
&lt;br&gt;&amp;nbsp;firewall_logging=&amp;quot;NO&amp;quot;		# Set to YES to enable events logging
&lt;br&gt;&amp;nbsp;firewall_flags=&amp;quot;&amp;quot;		# Flags passed to ipfw when type is a file
&lt;br&gt;-firewall_client_net=&amp;quot;192.0.2.0/24&amp;quot; # Network address for &amp;quot;client&amp;quot; firewall.
&lt;br&gt;+firewall_client_net=&amp;quot;192.0.2.0/24&amp;quot; # IPv4 Network address for &amp;quot;client&amp;quot;
&lt;br&gt;+				# firewall.
&lt;br&gt;+#firewall_client_net_ipv6=&amp;quot;2001:db8:2:1::/64&amp;quot; # IPv6 network prefix for
&lt;br&gt;+				# &amp;quot;client&amp;quot; firewall.
&lt;br&gt;&amp;nbsp;firewall_simple_iif=&amp;quot;ed1&amp;quot;	# Inside network interface for &amp;quot;simple&amp;quot;
&lt;br&gt;&amp;nbsp;				# firewall.
&lt;br&gt;&amp;nbsp;firewall_simple_inet=&amp;quot;192.0.2.16/28&amp;quot; # Inside network address for &amp;quot;simple&amp;quot;
&lt;br&gt;@@ -127,12 +130,22 @@
&lt;br&gt;&amp;nbsp;				# firewall.
&lt;br&gt;&amp;nbsp;firewall_simple_onet=&amp;quot;192.0.2.0/28&amp;quot; # Outside network address for &amp;quot;simple&amp;quot;
&lt;br&gt;&amp;nbsp;				# firewall.
&lt;br&gt;+#firewall_simple_iif_ipv6=&amp;quot;ed1&amp;quot;	# Inside IPv6 network interface for &amp;quot;simple&amp;quot;
&lt;br&gt;+				# firewall.
&lt;br&gt;+#firewall_simple_inet_ipv6=&amp;quot;2001:db8:2:800::/56&amp;quot; # Inside IPv6 network prefix
&lt;br&gt;+				# for &amp;quot;simple&amp;quot; firewall.
&lt;br&gt;+#firewall_simple_oif_ipv6=&amp;quot;ed0&amp;quot;	# Outside IPv6 network interface for &amp;quot;simple&amp;quot;
&lt;br&gt;+				# firewall.
&lt;br&gt;+#firewall_simple_onet_ipv6=&amp;quot;2001:db8:2:0::/56&amp;quot; # Outside IPv6 network prefix
&lt;br&gt;+				# for &amp;quot;simple&amp;quot; firewall.
&lt;br&gt;&amp;nbsp;firewall_myservices=&amp;quot;&amp;quot;		# List of TCP ports on which this host
&lt;br&gt;&amp;nbsp;				# offers services for &amp;quot;workstation&amp;quot; firewall.
&lt;br&gt;&amp;nbsp;firewall_allowservices=&amp;quot;&amp;quot;	# List of IPs which have access to
&lt;br&gt;&amp;nbsp;				# $firewall_myservices for &amp;quot;workstation&amp;quot;
&lt;br&gt;&amp;nbsp;				# firewall.
&lt;br&gt;-firewall_trusted=&amp;quot;&amp;quot;		# List of IPs which have full access to this
&lt;br&gt;+firewall_trusted=&amp;quot;&amp;quot;		# List of IPv4s which have full access to this
&lt;br&gt;+				# host for &amp;quot;workstation&amp;quot; firewall.
&lt;br&gt;+firewall_trusted_ipv6=&amp;quot;&amp;quot;	# List of IPv6s which have full access to this
&lt;br&gt;&amp;nbsp;				# host for &amp;quot;workstation&amp;quot; firewall.
&lt;br&gt;&amp;nbsp;firewall_logdeny=&amp;quot;NO&amp;quot;		# Set to YES to log default denied incoming
&lt;br&gt;&amp;nbsp;				# packets for &amp;quot;workstation&amp;quot; firewall.
&lt;br&gt;@@ -470,13 +483,18 @@
&lt;br&gt;&amp;nbsp;				# faithd(8) setup.
&lt;br&gt;&amp;nbsp;ipv6_ipv4mapping=&amp;quot;NO&amp;quot;		# Set to &amp;quot;YES&amp;quot; to enable IPv4 mapped IPv6 addr
&lt;br&gt;&amp;nbsp;				# communication. (like ::ffff:a.b.c.d)
&lt;br&gt;-ipv6_firewall_enable=&amp;quot;NO&amp;quot;	# Set to YES to enable IPv6 firewall
&lt;br&gt;-				# functionality
&lt;br&gt;-ipv6_firewall_script=&amp;quot;/etc/rc.firewall6&amp;quot; # Which script to run to set up the IPv6 firewall
&lt;br&gt;-ipv6_firewall_type=&amp;quot;UNKNOWN&amp;quot;	# IPv6 Firewall type (see /etc/rc.firewall6)
&lt;br&gt;-ipv6_firewall_quiet=&amp;quot;NO&amp;quot;	# Set to YES to suppress rule display
&lt;br&gt;-ipv6_firewall_logging=&amp;quot;NO&amp;quot;	# Set to YES to enable events logging
&lt;br&gt;-ipv6_firewall_flags=&amp;quot;&amp;quot;		# Flags passed to ip6fw when type is a file
&lt;br&gt;+#ipv6_firewall_enable=&amp;quot;NO&amp;quot;	# Set to YES to enable IPv6 firewall
&lt;br&gt;+				# functionality (DEPRECAED)
&lt;br&gt;+#ipv6_firewall_script=&amp;quot;/etc/rc.firewall6&amp;quot; # Which script to run to set up the
&lt;br&gt;+				# IPv6 firewall (DEPRECAED)
&lt;br&gt;+#ipv6_firewall_type=&amp;quot;UNKNOWN&amp;quot;	# IPv6 Firewall type (see /etc/rc.firewall6)
&lt;br&gt;+				# (DEPRECAED)
&lt;br&gt;+#ipv6_firewall_quiet=&amp;quot;NO&amp;quot;	# Set to YES to suppress rule display
&lt;br&gt;+				# (DEPRECAED)
&lt;br&gt;+#ipv6_firewall_logging=&amp;quot;NO&amp;quot;	# Set to YES to enable events logging
&lt;br&gt;+				# (DEPRECAED)
&lt;br&gt;+#ipv6_firewall_flags=&amp;quot;&amp;quot;		# Flags passed to ip6fw when type is a file
&lt;br&gt;+				# (DEPRECAED)
&lt;br&gt;&amp;nbsp;ipv6_ipfilter_rules=&amp;quot;/etc/ipf6.rules&amp;quot;	# rules definition file for ipfilter,
&lt;br&gt;&amp;nbsp;					# see /usr/src/contrib/ipfilter/rules
&lt;br&gt;&amp;nbsp;					# for examples
&lt;br&gt;Index: etc/rc.d/Makefile
&lt;br&gt;diff -u etc/rc.d/Makefile.orig etc/rc.d/Makefile
&lt;br&gt;--- etc/rc.d/Makefile.orig	2009-10-25 10:10:29.000000000 +0900
&lt;br&gt;+++ etc/rc.d/Makefile	2009-11-22 20:42:16.398311126 +0900
&lt;br&gt;@@ -15,7 +15,7 @@
&lt;br&gt;&amp;nbsp;	hcsecd \
&lt;br&gt;&amp;nbsp;	hostapd hostid hostid_save hostname \
&lt;br&gt;&amp;nbsp;	inetd initrandom \
&lt;br&gt;-	ip6addrctl ip6fw ipfilter ipfs ipfw ipmon \
&lt;br&gt;+	ip6addrctl ipfilter ipfs ipfw ipmon \
&lt;br&gt;&amp;nbsp;	ipnat ipsec ipxrouted \
&lt;br&gt;&amp;nbsp;	jail \
&lt;br&gt;&amp;nbsp;	kadmind kerberos keyserv kldxref kpasswdd \
&lt;br&gt;Index: etc/rc.d/ipfw
&lt;br&gt;diff -u etc/rc.d/ipfw.orig etc/rc.d/ipfw
&lt;br&gt;--- etc/rc.d/ipfw.orig	2009-11-22 20:43:59.000000000 +0900
&lt;br&gt;+++ etc/rc.d/ipfw	2009-11-23 19:29:05.426333161 +0900
&lt;br&gt;@@ -61,7 +61,13 @@
&lt;br&gt;&amp;nbsp;	# Enable the firewall
&lt;br&gt;&amp;nbsp;	#
&lt;br&gt;&amp;nbsp;	if ! ${SYSCTL_W} net.inet.ip.fw.enable=1 1&amp;gt;/dev/null 2&amp;gt;&amp;1; then
&lt;br&gt;-		warn &amp;quot;failed to enable firewall&amp;quot;
&lt;br&gt;+		warn &amp;quot;failed to enable IPv4 firewall&amp;quot;
&lt;br&gt;+	fi
&lt;br&gt;+	if afexists inet6; then
&lt;br&gt;+		if ! ${SYSCTL_W} net.inet6.ip6.fw.enable=1 1&amp;gt;/dev/null 2&amp;gt;&amp;1
&lt;br&gt;+		then
&lt;br&gt;+			warn &amp;quot;failed to enable IPv6 firewall&amp;quot;
&lt;br&gt;+		fi
&lt;br&gt;&amp;nbsp;	fi
&lt;br&gt;&amp;nbsp;}
&lt;br&gt;&amp;nbsp;
&lt;br&gt;@@ -70,6 +76,9 @@
&lt;br&gt;&amp;nbsp;	# Disable the firewall
&lt;br&gt;&amp;nbsp;	#
&lt;br&gt;&amp;nbsp;	${SYSCTL_W} net.inet.ip.fw.enable=0
&lt;br&gt;+	if afexists inet6; then
&lt;br&gt;+		${SYSCTL_W} net.inet6.ip6.fw.enable=0
&lt;br&gt;+	fi
&lt;br&gt;&amp;nbsp;	if [ -f /etc/rc.d/natd ] ; then
&lt;br&gt;&amp;nbsp;		/etc/rc.d/natd quietstop
&lt;br&gt;&amp;nbsp;	fi
&lt;br&gt;Index: etc/rc.firewall
&lt;br&gt;diff -u etc/rc.firewall.orig etc/rc.firewall
&lt;br&gt;--- etc/rc.firewall.orig	2009-10-25 10:10:29.000000000 +0900
&lt;br&gt;+++ etc/rc.firewall	2009-11-25 03:18:14.568870172 +0900
&lt;br&gt;@@ -85,12 +85,42 @@
&lt;br&gt;&amp;nbsp;	${fwcmd} add 100 pass all from any to any via lo0
&lt;br&gt;&amp;nbsp;	${fwcmd} add 200 deny all from any to 127.0.0.0/8
&lt;br&gt;&amp;nbsp;	${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
&lt;br&gt;+	if [ $ipv6_available -eq 0 ]; then
&lt;br&gt;+		${fwcmd} add 400 deny all from any to ::1
&lt;br&gt;+		${fwcmd} add 500 deny all from ::1 to any
&lt;br&gt;+	fi
&lt;br&gt;+}
&lt;br&gt;+
&lt;br&gt;+setup_ipv6_mandatory () {
&lt;br&gt;+	[ $ipv6_available -eq 0 ] || return 0
&lt;br&gt;+
&lt;br&gt;+	############
&lt;br&gt;+	# Only in rare cases do you want to change these rules
&lt;br&gt;+	#
&lt;br&gt;+	# ND
&lt;br&gt;+	#
&lt;br&gt;+	# DAD
&lt;br&gt;+	${fwcmd} add pass ipv6-icmp from :: to ff02::/16
&lt;br&gt;+	# RS, RA, NS, NA, redirect...
&lt;br&gt;+	${fwcmd} add pass ipv6-icmp from fe80::/10 to fe80::/10
&lt;br&gt;+	${fwcmd} add pass ipv6-icmp from fe80::/10 to ff02::/16
&lt;br&gt;+
&lt;br&gt;+	# Allow ICMPv6 destination unreach
&lt;br&gt;+	${fwcmd} add pass ipv6-icmp from any to any icmp6types 1
&lt;br&gt;+
&lt;br&gt;+	# Allow NS/NA/toobig (don't filter it out)
&lt;br&gt;+	${fwcmd} add pass ipv6-icmp from any to any icmp6types 2,135,136
&lt;br&gt;&amp;nbsp;}
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;if [ -n &amp;quot;${1}&amp;quot; ]; then
&lt;br&gt;&amp;nbsp;	firewall_type=&amp;quot;${1}&amp;quot;
&lt;br&gt;&amp;nbsp;fi
&lt;br&gt;&amp;nbsp;
&lt;br&gt;+. /etc/rc.subr
&lt;br&gt;+. /etc/network.subr
&lt;br&gt;+afexists inet6
&lt;br&gt;+ipv6_available=$?
&lt;br&gt;+
&lt;br&gt;&amp;nbsp;############
&lt;br&gt;&amp;nbsp;# Set quiet mode if requested
&lt;br&gt;&amp;nbsp;#
&lt;br&gt;@@ -109,6 +139,7 @@
&lt;br&gt;&amp;nbsp;${fwcmd} -f flush
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;setup_loopback
&lt;br&gt;+setup_ipv6_mandatory
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;############
&lt;br&gt;&amp;nbsp;# Network Address Translation. &amp;nbsp;All packets are passed to natd(8)
&lt;br&gt;@@ -166,11 +197,13 @@
&lt;br&gt;&amp;nbsp;	# against people from outside your own network.
&lt;br&gt;&amp;nbsp;	#
&lt;br&gt;&amp;nbsp;	# Configuration:
&lt;br&gt;-	# &amp;nbsp;firewall_client_net:		Network address of local network.
&lt;br&gt;+	# &amp;nbsp;firewall_client_net:		Network address of local IPv4 network.
&lt;br&gt;+	# &amp;nbsp;firewall_client_net_ipv6:	Network address of local IPv6 network.
&lt;br&gt;&amp;nbsp;	############
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# set this to your local network
&lt;br&gt;&amp;nbsp;	net=&amp;quot;$firewall_client_net&amp;quot;
&lt;br&gt;+	net6=&amp;quot;$firewall_client_net_ipv6&amp;quot;
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Allow limited broadcast traffic from my own net.
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass all from ${net} to 255.255.255.255
&lt;br&gt;@@ -178,6 +211,16 @@
&lt;br&gt;&amp;nbsp;	# Allow any traffic to or from my own net.
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass all from me to ${net}
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass all from ${net} to me
&lt;br&gt;+	if [ -n &amp;quot;$net6&amp;quot; ]; then
&lt;br&gt;+		${fwcmd} add pass all from me6 to ${net6}
&lt;br&gt;+		${fwcmd} add pass all from ${net6} to me6
&lt;br&gt;+	fi
&lt;br&gt;+
&lt;br&gt;+	if [ -n &amp;quot;$net6&amp;quot; ]; then
&lt;br&gt;+		# Allow any link-local multicast traffic
&lt;br&gt;+		${fwcmd} add pass all from fe80::/10 to ff02::/16
&lt;br&gt;+		${fwcmd} add pass all from ${net6} to ff02::/16
&lt;br&gt;+	fi
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Allow TCP through if setup succeeded
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass tcp from any to any established
&lt;br&gt;@@ -212,23 +255,38 @@
&lt;br&gt;&amp;nbsp;	# on the inside at this machine for those services.
&lt;br&gt;&amp;nbsp;	#
&lt;br&gt;&amp;nbsp;	# Configuration:
&lt;br&gt;-	# &amp;nbsp;firewall_simple_iif:		Inside network interface.
&lt;br&gt;-	# &amp;nbsp;firewall_simple_inet:	Inside network address.
&lt;br&gt;-	# &amp;nbsp;firewall_simple_oif:		Outside network interface.
&lt;br&gt;-	# &amp;nbsp;firewall_simple_onet:	Outside network address.
&lt;br&gt;+	# &amp;nbsp;firewall_simple_iif:		Inside IPv4 network interface.
&lt;br&gt;+	# &amp;nbsp;firewall_simple_inet:	Inside IPv4 network address.
&lt;br&gt;+	# &amp;nbsp;firewall_simple_oif:		Outside IPv4 network interface.
&lt;br&gt;+	# &amp;nbsp;firewall_simple_onet:	Outside IPv4 network address.
&lt;br&gt;+	# &amp;nbsp;firewall_simple_iif_ipv6:	Inside IPv6 network interface.
&lt;br&gt;+	# &amp;nbsp;firewall_simple_inet_ipv6:	Inside IPv6 network prefix.
&lt;br&gt;+	# &amp;nbsp;firewall_simple_oif_ipv6:	Outside IPv6 network interface.
&lt;br&gt;+	# &amp;nbsp;firewall_simple_onet_ipv6:	Outside IPv6 network prefix.
&lt;br&gt;&amp;nbsp;	############
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# set these to your outside interface network
&lt;br&gt;&amp;nbsp;	oif=&amp;quot;$firewall_simple_oif&amp;quot;
&lt;br&gt;&amp;nbsp;	onet=&amp;quot;$firewall_simple_onet&amp;quot;
&lt;br&gt;+	oif6=&amp;quot;${firewall_simple_oif_ipv6:-$firewall_simple_oif}&amp;quot;
&lt;br&gt;+	onet6=&amp;quot;$firewall_simple_onet_ipv6&amp;quot;
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# set these to your inside interface network
&lt;br&gt;&amp;nbsp;	iif=&amp;quot;$firewall_simple_iif&amp;quot;
&lt;br&gt;&amp;nbsp;	inet=&amp;quot;$firewall_simple_inet&amp;quot;
&lt;br&gt;+	iif6=&amp;quot;${firewall_simple_iif_ipv6:-$firewall_simple_iif}&amp;quot;
&lt;br&gt;+	inet6=&amp;quot;$firewall_simple_inet_ipv6&amp;quot;
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Stop spoofing
&lt;br&gt;&amp;nbsp;	${fwcmd} add deny all from ${inet} to any in via ${oif}
&lt;br&gt;&amp;nbsp;	${fwcmd} add deny all from ${onet} to any in via ${iif}
&lt;br&gt;+	if [ -n &amp;quot;$inet6&amp;quot; ]; then
&lt;br&gt;+		${fwcmd} add deny all from ${inet6} to any in via ${oif6}
&lt;br&gt;+		if [ -n &amp;quot;$onet6&amp;quot; ]; then
&lt;br&gt;+			${fwcmd} add deny all from ${onet6} to any in \
&lt;br&gt;+			 &amp;nbsp; &amp;nbsp;via ${iif6}
&lt;br&gt;+		fi
&lt;br&gt;+	fi
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Stop RFC1918 nets on the outside interface
&lt;br&gt;&amp;nbsp;	${fwcmd} add deny all from any to 10.0.0.0/8 via ${oif}
&lt;br&gt;@@ -254,7 +312,7 @@
&lt;br&gt;&amp;nbsp;	case ${natd_enable} in
&lt;br&gt;&amp;nbsp;	[Yy][Ee][Ss])
&lt;br&gt;&amp;nbsp;		if [ -n &amp;quot;${natd_interface}&amp;quot; ]; then
&lt;br&gt;-			${fwcmd} add divert natd all from any to any via ${natd_interface}
&lt;br&gt;+			${fwcmd} add divert natd ip4 from any to any via ${natd_interface}
&lt;br&gt;&amp;nbsp;		fi
&lt;br&gt;&amp;nbsp;		;;
&lt;br&gt;&amp;nbsp;	esac
&lt;br&gt;@@ -273,6 +331,55 @@
&lt;br&gt;&amp;nbsp;	${fwcmd} add deny all from 224.0.0.0/4 to any via ${oif}
&lt;br&gt;&amp;nbsp;	${fwcmd} add deny all from 240.0.0.0/4 to any via ${oif}
&lt;br&gt;&amp;nbsp;
&lt;br&gt;+	if [ -n &amp;quot;$inet6&amp;quot; ]; then
&lt;br&gt;+		# Stop unique local unicast address on the outside interface
&lt;br&gt;+		${fwcmd} add deny all from fc00::/7 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to fc00::/7 via ${oif6}
&lt;br&gt;+
&lt;br&gt;+		# Stop site-local on the outside interface
&lt;br&gt;+		${fwcmd} add deny all from fec0::/10 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to fec0::/10 via ${oif6}
&lt;br&gt;+
&lt;br&gt;+		# Disallow &amp;quot;internal&amp;quot; addresses to appear on the wire.
&lt;br&gt;+		${fwcmd} add deny all from ::ffff:0.0.0.0/96 to any \
&lt;br&gt;+		 &amp;nbsp; &amp;nbsp;via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to ::ffff:0.0.0.0/96 \
&lt;br&gt;+		 &amp;nbsp; &amp;nbsp;via ${oif6}
&lt;br&gt;+
&lt;br&gt;+		# Disallow packets to malicious IPv4 compatible prefix.
&lt;br&gt;+		${fwcmd} add deny all from ::224.0.0.0/100 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to ::224.0.0.0/100 via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from ::127.0.0.0/104 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to ::127.0.0.0/104 via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from ::0.0.0.0/104 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to ::0.0.0.0/104 via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from ::255.0.0.0/104 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to ::255.0.0.0/104 via ${oif6}
&lt;br&gt;+
&lt;br&gt;+		${fwcmd} add deny all from ::0.0.0.0/96 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to ::0.0.0.0/96 via ${oif6}
&lt;br&gt;+
&lt;br&gt;+		# Disallow packets to malicious 6to4 prefix.
&lt;br&gt;+		${fwcmd} add deny all from 2002:e000::/20 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to 2002:e000::/20 via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from 2002:7f00::/24 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to 2002:7f00::/24 via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from 2002:0000::/24 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to 2002:0000::/24 via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from 2002:ff00::/24 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to 2002:ff00::/24 via ${oif6}
&lt;br&gt;+
&lt;br&gt;+		${fwcmd} add deny all from 2002:0a00::/24 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to 2002:0a00::/24 via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from 2002:ac10::/28 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to 2002:ac10::/28 via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from 2002:c0a8::/32 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to 2002:c0a8::/32 via ${oif6}
&lt;br&gt;+
&lt;br&gt;+		${fwcmd} add deny all from ff05::/16 to any via ${oif6}
&lt;br&gt;+		${fwcmd} add deny all from any to ff05::/16 via ${oif6}
&lt;br&gt;+	fi
&lt;br&gt;+
&lt;br&gt;&amp;nbsp;	# Allow TCP through if setup succeeded
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass tcp from any to any established
&lt;br&gt;&amp;nbsp;
&lt;br&gt;@@ -291,7 +398,11 @@
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass tcp from any to me 80 setup
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Reject&amp;Log all setup of incoming connections from the outside
&lt;br&gt;-	${fwcmd} add deny log tcp from any to any in via ${oif} setup
&lt;br&gt;+	${fwcmd} add deny log ip4 from any to any in via ${oif} setup proto tcp
&lt;br&gt;+	if [ -n &amp;quot;$inet6&amp;quot; ]; then
&lt;br&gt;+		${fwcmd} add deny log ip6 from any to any in via ${oif6} \
&lt;br&gt;+		 &amp;nbsp; &amp;nbsp;setup proto tcp
&lt;br&gt;+	fi
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Allow setup of any other TCP connection
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass tcp from any to any setup
&lt;br&gt;@@ -313,7 +424,7 @@
&lt;br&gt;&amp;nbsp;	#			 	 offers services.
&lt;br&gt;&amp;nbsp;	# &amp;nbsp;firewall_allowservices:	List of IPs which has access to
&lt;br&gt;&amp;nbsp;	#				 $firewall_myservices.
&lt;br&gt;-	# &amp;nbsp;firewall_trusted:		List of IPs which has full access 
&lt;br&gt;+	# &amp;nbsp;firewall_trusted:		List of IPv4s which has full access 
&lt;br&gt;&amp;nbsp;	#				 to this host. Be very carefull 
&lt;br&gt;&amp;nbsp;	#				 when setting this. This option can
&lt;br&gt;&amp;nbsp;	#				 seriously degrade the level of 
&lt;br&gt;@@ -324,25 +435,44 @@
&lt;br&gt;&amp;nbsp;	# &amp;nbsp;firewall_nologports:		List of TCP/UDP ports for which
&lt;br&gt;&amp;nbsp;	#				 denied incomming packets are not
&lt;br&gt;&amp;nbsp;	#				 logged.
&lt;br&gt;-	
&lt;br&gt;+	# &amp;nbsp;firewall_trusted_ipv6:	List of IPv6s which has full access 
&lt;br&gt;+	#				 to this host. Be very carefull 
&lt;br&gt;+	#				 when setting this. This option can
&lt;br&gt;+	#				 seriously degrade the level of 
&lt;br&gt;+	#				 protection provided by the firewall.
&lt;br&gt;+
&lt;br&gt;&amp;nbsp;	# Allow packets for which a state has been built.
&lt;br&gt;&amp;nbsp;	${fwcmd} add check-state
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# For services permitted below.
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass tcp &amp;nbsp;from me to any established
&lt;br&gt;+	if [ $ipv6_available -eq 0 ]; then
&lt;br&gt;+		${fwcmd} add pass tcp from me6 to any established
&lt;br&gt;+	fi
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Allow any connection out, adding state for each.
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass tcp &amp;nbsp;from me to any setup keep-state
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass udp &amp;nbsp;from me to any &amp;nbsp; &amp;nbsp; &amp;nbsp; keep-state
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass icmp from me to any &amp;nbsp; &amp;nbsp; &amp;nbsp; keep-state
&lt;br&gt;+	if [ $ipv6_available -eq 0 ]; then
&lt;br&gt;+		${fwcmd} add pass tcp from me6 to any setup keep-state
&lt;br&gt;+		${fwcmd} add pass udp from me6 to any keep-state
&lt;br&gt;+		${fwcmd} add pass ipv6-icmp from me6 to any keep-state
&lt;br&gt;+	fi
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Allow DHCP.
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass udp &amp;nbsp;from 0.0.0.0 68 to 255.255.255.255 67 out
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass udp &amp;nbsp;from any 67 &amp;nbsp; &amp;nbsp; to me 68 in
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass udp &amp;nbsp;from any 67 &amp;nbsp; &amp;nbsp; to 255.255.255.255 68 in
&lt;br&gt;+	if [ $ipv6_available -eq 0 ]; then
&lt;br&gt;+		${fwcmd} add pass udp from fe80::/10 to me6 546 in
&lt;br&gt;+	fi
&lt;br&gt;&amp;nbsp;	# Some servers will ping the IP while trying to decide if it's 
&lt;br&gt;&amp;nbsp;	# still in use.
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass icmp from any to any icmptype 8
&lt;br&gt;+	if [ $ipv6_available -eq 0 ]; then
&lt;br&gt;+		${fwcmd} add pass ipv6-icmp from any to any icmp6type 128,129
&lt;br&gt;+	fi
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Allow &amp;quot;mandatory&amp;quot; ICMP in.
&lt;br&gt;&amp;nbsp;	${fwcmd} add pass icmp from any to any icmptype 3,4,11
&lt;br&gt;@@ -361,6 +491,9 @@
&lt;br&gt;&amp;nbsp;	for i in ${firewall_allowservices} ; do
&lt;br&gt;&amp;nbsp;	 &amp;nbsp;for j in ${firewall_myservices} ; do
&lt;br&gt;&amp;nbsp;	 &amp;nbsp; &amp;nbsp;${fwcmd} add pass tcp from $i to me $j
&lt;br&gt;+	 &amp;nbsp; &amp;nbsp;if [ $ipv6_available -eq 0 ]; then
&lt;br&gt;+	 &amp;nbsp; &amp;nbsp; &amp;nbsp;${fwcmd} add pass tcp from $i to me6 $j
&lt;br&gt;+	 &amp;nbsp; &amp;nbsp;fi
&lt;br&gt;&amp;nbsp;	 &amp;nbsp;done
&lt;br&gt;&amp;nbsp;	done
&lt;br&gt;&amp;nbsp;
&lt;br&gt;@@ -370,7 +503,10 @@
&lt;br&gt;&amp;nbsp;	for i in ${firewall_trusted} ; do
&lt;br&gt;&amp;nbsp;	 &amp;nbsp;${fwcmd} add pass ip from $i to me
&lt;br&gt;&amp;nbsp;	done
&lt;br&gt;-	
&lt;br&gt;+	for i in ${firewall_trusted_ipv6} ; do
&lt;br&gt;+	 &amp;nbsp;${fwcmd} add pass all from $i to me6
&lt;br&gt;+	done
&lt;br&gt;+
&lt;br&gt;&amp;nbsp;	${fwcmd} add 65000 count ip from any to any
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	# Drop packets to ports where we don't want logging
&lt;br&gt;&lt;/tt&gt;&lt;hr align=&quot;left&quot; width=&quot;300&quot; /&gt;&lt;br /&gt;&lt;br&gt;--
&lt;br&gt;Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26515367&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;ume@...&lt;/a&gt; &amp;nbsp;ume@{,jp.}FreeBSD.org
&lt;br&gt;&lt;a href=&quot;http://www.imasy.org/~ume/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.imasy.org/~ume/&lt;/a&gt;&lt;br&gt;&lt;br /&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26515367&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26515367&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/-CFR--unified-rc.firewall-tp26466319p26515367.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26515342</id>
	<title>Re: Need help on IPv6 prefixes and interface addresses</title>
	<published>2009-11-25T08:00:45Z</published>
	<updated>2009-11-25T08:00:45Z</updated>
	<author>
		<name>hrs</name>
	</author>
	<content type="html">&amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26515342&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;Hartmut.Brandt@...&lt;/a&gt;&amp;gt; wrote
&lt;br&gt;&amp;nbsp; in &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26515342&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;E086A96846579E4F932C168218DB1E55024129@...&lt;/a&gt;&amp;gt;:
&lt;br&gt;&lt;br&gt;Ha&amp;gt; To answer my own question :-) These strange link local addresses are
&lt;br&gt;Ha&amp;gt; explained in the developers handbook section 8.1.1.3 and are called
&lt;br&gt;Ha&amp;gt; embedded
&lt;br&gt;Ha&amp;gt; link local addresses. These are not standard IPv6 addresses, but a way
&lt;br&gt;Ha&amp;gt; to encode the interface index (aka zone index) into the IPv6
&lt;br&gt;Ha&amp;gt; address. This must be undone by the user program before using these
&lt;br&gt;Ha&amp;gt; addresses.
&lt;br&gt;&lt;br&gt;&amp;nbsp;I think &amp;quot;1.3.1 Kernel internal&amp;quot; in /usr/share/doc/IPv6/IMPLEMENTATION
&lt;br&gt;&amp;nbsp;would also help.
&lt;br&gt;&lt;br&gt;-- Hiroki
&lt;br&gt;&lt;br /&gt; &lt;div class=&quot;small&quot;&gt;&lt;br/&gt;&lt;img src=&quot;http://old.nabble.com/images/icon_attachment.gif&quot; &gt; &lt;strong&gt;attachment0&lt;/strong&gt; (202 bytes) &lt;a href=&quot;http://old.nabble.com/attachment/26515342/0/attachment0&quot; target=&quot;_top&quot;&gt;Download Attachment&lt;/a&gt;&lt;/div&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Need-help-on-IPv6-prefixes-and-interface-addresses-tp26511667p26515342.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26514382</id>
	<title>RE: Need help on IPv6 prefixes and interface addresses</title>
	<published>2009-11-25T07:07:45Z</published>
	<updated>2009-11-25T07:07:45Z</updated>
	<author>
		<name>Harti Brandt</name>
	</author>
	<content type="html">To answer my own question :-) These strange link local addresses are explained in the developers handbook section 8.1.1.3 and are called embedded
&lt;br&gt;link local addresses. These are not standard IPv6 addresses, but a way to encode the interface index (aka zone index) into the IPv6 address. This must be undone by the user program before using these addresses.
&lt;br&gt;&lt;br&gt;harti 
&lt;br&gt;&lt;br&gt;&lt;br&gt;-----Original Message-----
&lt;br&gt;From: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26514382&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;owner-freebsd-net@...&lt;/a&gt; on behalf of &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26514382&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;Hartmut.Brandt@...&lt;/a&gt;
&lt;br&gt;Sent: Wed 11/25/2009 1:15 PM
&lt;br&gt;To: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26514382&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt;
&lt;br&gt;Subject: Need help on IPv6 prefixes and interface addresses
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&lt;br&gt;Hi all,
&lt;br&gt;&lt;br&gt;I try to make bsnmpd IPv6 aware and need some help here. I've set up a small IPv6 network for testing between a couple of VMs.
&lt;br&gt;&lt;br&gt;For IPv6 interface addresses there are two tables: ipAddressPrefix table and ipAddressTable (containing pointers to the prefix table). Now I see something on my system I cannot grasp. ndp -pn gives me:
&lt;br&gt;&lt;br&gt;2001:638:101:ff::/64 if=le0
&lt;br&gt;flags=LO vltime=infinity, pltime=infinity, expire=Never, ref=1
&lt;br&gt;&amp;nbsp; No advertising router
&lt;br&gt;fe80::%le0/64 if=le0
&lt;br&gt;flags=LAO vltime=infinity, pltime=infinity, expire=Never, ref=0
&lt;br&gt;&amp;nbsp; No advertising router
&lt;br&gt;fe80::%lo0/64 if=lo0
&lt;br&gt;flags=LAO vltime=infinity, pltime=infinity, expire=Never, ref=0
&lt;br&gt;&amp;nbsp; No advertising router
&lt;br&gt;&lt;br&gt;ifconfig -a inet6 gives:
&lt;br&gt;&lt;br&gt;le0: flags=8843&amp;lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&amp;gt; metric 0 mtu 1500
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; options=8&amp;lt;VLAN_MTU&amp;gt;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet6 fe80::20c:29ff:fe90:dd1b%le0 prefixlen 64 scopeid 0x1 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet6 2001:638:101:ff::8:ffff prefixlen 64 
&lt;br&gt;lo0: flags=8049&amp;lt;UP,LOOPBACK,RUNNING,MULTICAST&amp;gt; metric 0 mtu 16384
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; options=3&amp;lt;RXCSUM,TXCSUM&amp;gt;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet6 ::1 prefixlen 128 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
&lt;br&gt;&lt;br&gt;So far, so nice.
&lt;br&gt;&lt;br&gt;When I ask for the interface addresses via sysctl([0, NET_RT_IFLIST, 0], ...) I get strange RTM_NEWADDR messages:
&lt;br&gt;&lt;br&gt;msglen=76 version=5 type=RTM_NEWADDR
&lt;br&gt;&amp;nbsp; &amp;nbsp; flags=0
&lt;br&gt;&amp;nbsp; &amp;nbsp; index=1 metric=0
&lt;br&gt;&amp;nbsp; &amp;nbsp; netmask=INET6,28,{0,0,ffff:ffff:ffff:ffff::,0}
&lt;br&gt;&amp;nbsp; &amp;nbsp; ifa=INET6,28,{0,0,fe80:1::20c:29ff:fe90:dd1b,0}
&lt;br&gt;&lt;br&gt;Which means a prefix of fe80:1::/64 instead of fe80::%le0/64. Note, the :1: there and note the zero missing scope_id
&lt;br&gt;(the last 0 inside the {}). Same for lo0:
&lt;br&gt;&lt;br&gt;msglen=80 version=5 type=RTM_NEWADDR
&lt;br&gt;&amp;nbsp; &amp;nbsp; flags=0
&lt;br&gt;&amp;nbsp; &amp;nbsp; index=2 metric=0
&lt;br&gt;&amp;nbsp; &amp;nbsp; netmask=INET6,28,{0,0,ffff:ffff:ffff:ffff::,0}
&lt;br&gt;&amp;nbsp; &amp;nbsp; ifa=INET6,28,{0,0,fe80:2::1,0}
&lt;br&gt;&amp;nbsp; &amp;nbsp; brd=UNSPEC,0,{}
&lt;br&gt;&lt;br&gt;So my questions:
&lt;br&gt;&amp;nbsp; - are the routing message really that inconsistent and broken? Or do I read them somehow incorrect?
&lt;br&gt;&amp;nbsp; - is it possible to rely on the prefix table? In other words: Does *each* prefix used
&lt;br&gt;&amp;nbsp; &amp;nbsp; in a INET6 interface address appear in the prefix list?
&lt;br&gt;&lt;br&gt;harti
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26514382&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26514382&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;&lt;br&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26514382&amp;i=5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26514382&amp;i=6&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Need-help-on-IPv6-prefixes-and-interface-addresses-tp26511667p26514382.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26511667</id>
	<title>Need help on IPv6 prefixes and interface addresses</title>
	<published>2009-11-25T04:15:01Z</published>
	<updated>2009-11-25T04:15:01Z</updated>
	<author>
		<name>Harti Brandt</name>
	</author>
	<content type="html">&lt;br&gt;Hi all,
&lt;br&gt;&lt;br&gt;I try to make bsnmpd IPv6 aware and need some help here. I've set up a small IPv6 network for testing between a couple of VMs.
&lt;br&gt;&lt;br&gt;For IPv6 interface addresses there are two tables: ipAddressPrefix table and ipAddressTable (containing pointers to the prefix table). Now I see something on my system I cannot grasp. ndp -pn gives me:
&lt;br&gt;&lt;br&gt;2001:638:101:ff::/64 if=le0
&lt;br&gt;flags=LO vltime=infinity, pltime=infinity, expire=Never, ref=1
&lt;br&gt;&amp;nbsp; No advertising router
&lt;br&gt;fe80::%le0/64 if=le0
&lt;br&gt;flags=LAO vltime=infinity, pltime=infinity, expire=Never, ref=0
&lt;br&gt;&amp;nbsp; No advertising router
&lt;br&gt;fe80::%lo0/64 if=lo0
&lt;br&gt;flags=LAO vltime=infinity, pltime=infinity, expire=Never, ref=0
&lt;br&gt;&amp;nbsp; No advertising router
&lt;br&gt;&lt;br&gt;ifconfig -a inet6 gives:
&lt;br&gt;&lt;br&gt;le0: flags=8843&amp;lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&amp;gt; metric 0 mtu 1500
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; options=8&amp;lt;VLAN_MTU&amp;gt;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet6 fe80::20c:29ff:fe90:dd1b%le0 prefixlen 64 scopeid 0x1 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet6 2001:638:101:ff::8:ffff prefixlen 64 
&lt;br&gt;lo0: flags=8049&amp;lt;UP,LOOPBACK,RUNNING,MULTICAST&amp;gt; metric 0 mtu 16384
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; options=3&amp;lt;RXCSUM,TXCSUM&amp;gt;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet6 ::1 prefixlen 128 
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
&lt;br&gt;&lt;br&gt;So far, so nice.
&lt;br&gt;&lt;br&gt;When I ask for the interface addresses via sysctl([0, NET_RT_IFLIST, 0], ...) I get strange RTM_NEWADDR messages:
&lt;br&gt;&lt;br&gt;msglen=76 version=5 type=RTM_NEWADDR
&lt;br&gt;&amp;nbsp; &amp;nbsp; flags=0
&lt;br&gt;&amp;nbsp; &amp;nbsp; index=1 metric=0
&lt;br&gt;&amp;nbsp; &amp;nbsp; netmask=INET6,28,{0,0,ffff:ffff:ffff:ffff::,0}
&lt;br&gt;&amp;nbsp; &amp;nbsp; ifa=INET6,28,{0,0,fe80:1::20c:29ff:fe90:dd1b,0}
&lt;br&gt;&lt;br&gt;Which means a prefix of fe80:1::/64 instead of fe80::%le0/64. Note, the :1: there and note the zero missing scope_id
&lt;br&gt;(the last 0 inside the {}). Same for lo0:
&lt;br&gt;&lt;br&gt;msglen=80 version=5 type=RTM_NEWADDR
&lt;br&gt;&amp;nbsp; &amp;nbsp; flags=0
&lt;br&gt;&amp;nbsp; &amp;nbsp; index=2 metric=0
&lt;br&gt;&amp;nbsp; &amp;nbsp; netmask=INET6,28,{0,0,ffff:ffff:ffff:ffff::,0}
&lt;br&gt;&amp;nbsp; &amp;nbsp; ifa=INET6,28,{0,0,fe80:2::1,0}
&lt;br&gt;&amp;nbsp; &amp;nbsp; brd=UNSPEC,0,{}
&lt;br&gt;&lt;br&gt;So my questions:
&lt;br&gt;&amp;nbsp; - are the routing message really that inconsistent and broken? Or do I read them somehow incorrect?
&lt;br&gt;&amp;nbsp; - is it possible to rely on the prefix table? In other words: Does *each* prefix used
&lt;br&gt;&amp;nbsp; &amp;nbsp; in a INET6 interface address appear in the prefix list?
&lt;br&gt;&lt;br&gt;harti
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26511667&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26511667&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Need-help-on-IPv6-prefixes-and-interface-addresses-tp26511667p26511667.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26510237</id>
	<title>possible memory leak in em_dma_free?</title>
	<published>2009-11-25T01:56:50Z</published>
	<updated>2009-11-25T01:56:50Z</updated>
	<author>
		<name>beezarliu</name>
	</author>
	<content type="html">Hi all, 
&lt;br&gt;&lt;br&gt;I saw em driver, and found a possible memory leak.
&lt;br&gt;dma-&amp;gt;dma_map may be NULL, so the dma memory will not be freed.
&lt;br&gt;I think the condition will it be beter if &amp;nbsp;it is &amp;quot;(dma-&amp;gt;dma_vaddr != NULL) {&amp;quot;
&lt;br&gt;&lt;br&gt;Thanks
&lt;br&gt;&lt;br&gt;static void
&lt;br&gt;em_dma_free(struct adapter *adapter, struct em_dma_alloc *dma)
&lt;br&gt;{
&lt;br&gt;&amp;nbsp;if (dma-&amp;gt;dma_tag == NULL)
&lt;br&gt;&amp;nbsp; return;
&lt;br&gt;&amp;nbsp;if (dma-&amp;gt;dma_map != NULL) { &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; --&amp;gt; if (dma-&amp;gt;dma_vaddr != NULL) {
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; bus_dmamap_sync(dma-&amp;gt;dma_tag, dma-&amp;gt;dma_map,
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; BUS_DMASYNC_POSTREAD | BUS_DMASYNC_POSTWRITE);
&lt;br&gt;&amp;nbsp; bus_dmamap_unload(dma-&amp;gt;dma_tag, dma-&amp;gt;dma_map);
&lt;br&gt;&amp;nbsp; bus_dmamem_free(dma-&amp;gt;dma_tag, dma-&amp;gt;dma_vaddr, dma-&amp;gt;dma_map);
&lt;br&gt;&amp;nbsp; dma-&amp;gt;dma_map = NULL;
&lt;br&gt;&amp;nbsp;}
&lt;br&gt;&amp;nbsp;bus_dma_tag_destroy(dma-&amp;gt;dma_tag);
&lt;br&gt;&amp;nbsp;dma-&amp;gt;dma_tag = NULL;
&lt;br&gt;}
&lt;br&gt;&lt;br&gt;2009-11-25 
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;beezarliu 
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26510237&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26510237&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/possible-memory-leak-in-em_dma_free--tp26510237p26510237.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26507701</id>
	<title>Re: Performance issue with new pipe profile feature in FreeBSD 8.0 RELEASE</title>
	<published>2009-11-24T21:21:17Z</published>
	<updated>2009-11-24T21:21:17Z</updated>
	<author>
		<name>Luigi Rizzo-5</name>
	</author>
	<content type="html">Hi,
&lt;br&gt;there is no bug, the 'pipe profile' code is working correctly.
&lt;br&gt;&lt;br&gt;In your mail below you are comparing two different things.
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;&amp;quot;pipe config bw 10Mbit/s delay 25ms&amp;quot;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; means that _after shaping_ at 10Mbps, all traffic will
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; be subject to an additional delay of 25ms.
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Each packet (1470 bytes) will take Length/Bandwidth sec
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; to come out or 1470*8/10M = 1.176ms , but you won't
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; see them until you wait another 25ms (7500km at the speed
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; of light).
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp;&amp;quot;pipe config bw 10Mbit/s profile &amp;quot;test&amp;quot; ...&amp;quot;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; means that in addition to the Length/Bandwidth,
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; _each packet transmission_ will consume
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; some additional air-time as specified in the profile
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (25ms in your case)
&lt;br&gt;&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; So, in your case with 1470bytes/pkt each transmission
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; will take len/bw (1.176ms) + 25ms (extra air time) = 26.76ms
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; That is 25 times more than the previous case and explains
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; the reduced bandwidth you see.
&lt;br&gt;&lt;br&gt;The 'delay profile' is effectively extra air time used for each
&lt;br&gt;transmission. The name is probably confusing, i should have called
&lt;br&gt;it 'extra-time' or 'overhead' and not 'delay'
&lt;br&gt;&lt;br&gt;cheers
&lt;br&gt;luigi
&lt;br&gt;&lt;br&gt;On Tue, Nov 24, 2009 at 12:40:31PM -0500, Charles Henri de Boysson wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; Hi,
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; I have a simple setup with two computer connected via a FreeBSD bridge
&lt;br&gt;&amp;gt; running 8.0 RELEASE.
&lt;br&gt;&amp;gt; I am trying to use dummynet to simulate a wireless network between the
&lt;br&gt;&amp;gt; two and for that I wanted to use the pipe profile feature of FreeBSD
&lt;br&gt;&amp;gt; 8.0.
&lt;br&gt;&amp;gt; But as I was experimenting with the pipe profile feature I ran into some issues.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; I have setup ipfw to send traffic coming for either interface of the
&lt;br&gt;&amp;gt; bridge to a respective pipe as follow:
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; # ipfw show
&lt;br&gt;&amp;gt; 00100 ?? ?? 0 ?? ?? ?? ?? 0 allow ip from any to any via lo0
&lt;br&gt;&amp;gt; 00200 ?? ?? 0 ?? ?? ?? ?? 0 deny ip from any to 127.0.0.0/8
&lt;br&gt;&amp;gt; 00300 ?? ?? 0 ?? ?? ?? ?? 0 deny ip from 127.0.0.0/8 to any
&lt;br&gt;&amp;gt; 01000 ?? ?? 0 ?? ?? ?? ?? 0 pipe 1 ip from any to any via vr0 layer2
&lt;br&gt;&amp;gt; 01100 ?? ?? 0 ?? ?? ?? ?? 0 pipe 101 ip from any to any via vr4 layer2
&lt;br&gt;&amp;gt; 65000 ??7089 ?? ??716987 allow ip from any to any
&lt;br&gt;&amp;gt; 65535 ?? ?? 0 ?? ?? ?? ?? 0 deny ip from any to any
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; When I setup my pipes as follow:
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; # ipfw pipe 1 config bw 10Mbit delay 25 mask proto 0
&lt;br&gt;&amp;gt; # ipfw pipe 101 config bw 10Mbit delay 25 mask proto 0
&lt;br&gt;&amp;gt; # ipfw pipe show
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; 00001: ??10.000 Mbit/s ?? 25 ms ?? 50 sl. 0 queues (1 buckets) droptail
&lt;br&gt;&amp;gt; burst: 0 Byte
&lt;br&gt;&amp;gt; 00101: ??10.000 Mbit/s ?? 25 ms ?? 50 sl. 0 queues (1 buckets) droptail
&lt;br&gt;&amp;gt; burst: 0 Byte
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; With this setup, when I try to pass traffic through the bridge with
&lt;br&gt;&amp;gt; iperf, I obtain the desired speed: iperf reports about 9.7Mbits/sec in
&lt;br&gt;&amp;gt; UDP mode and 9.5 in TCP mode (I copied and pasted the iperf runs at
&lt;br&gt;&amp;gt; the end of this email).
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; The problem arise when I setup pipe 1 (the downlink) with an
&lt;br&gt;&amp;gt; equivalent profile (I tried to simplify it as much as possible).
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; # ipfw pipe 1 config profile test.pipeconf &amp;nbsp; mask proto 0
&lt;br&gt;&amp;gt; # ipfw pipe show
&lt;br&gt;&amp;gt; 00001: &amp;nbsp;10.000 Mbit/s &amp;nbsp; &amp;nbsp;0 ms &amp;nbsp; 50 sl. 0 queues (1 buckets) droptail
&lt;br&gt;&amp;gt; 	 burst: 0 Byte
&lt;br&gt;&amp;gt; 	 profile: name &amp;quot;test&amp;quot; loss 1.000000 samples 2
&lt;br&gt;&amp;gt; 00101: &amp;nbsp;10.000 Mbit/s &amp;nbsp; 25 ms &amp;nbsp; 50 sl. 0 queues (1 buckets) droptail
&lt;br&gt;&amp;gt; 	 burst: 0 Byte
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; # cat test.pipeconf
&lt;br&gt;&amp;gt; name &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;test
&lt;br&gt;&amp;gt; bw &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;10Mbit
&lt;br&gt;&amp;gt; loss-level &amp;nbsp;1.0
&lt;br&gt;&amp;gt; samples &amp;nbsp; &amp;nbsp; 2
&lt;br&gt;&amp;gt; prob &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;delay
&lt;br&gt;&amp;gt; 0.0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 25
&lt;br&gt;&amp;gt; 1.0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 25
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; The same iperf TCP tests then collapse to about 500Kbit/s with the
&lt;br&gt;&amp;gt; same settings (copy and pasted the output of iperf bellow)
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; I can't figure out what is going on. There is no visible load on the bridge.
&lt;br&gt;&amp;gt; I have an unmodified GENERIC kernel with the following sysctl.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; net.link.bridge.ipfw: 1
&lt;br&gt;&amp;gt; kern.hz: 1000
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; The bridge configuration is as follow:
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; bridge0: flags=8843&amp;lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&amp;gt; metric 0 mtu 1500
&lt;br&gt;&amp;gt; ether 1a:1f:2e:42:74:8d
&lt;br&gt;&amp;gt; id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
&lt;br&gt;&amp;gt; maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
&lt;br&gt;&amp;gt; root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
&lt;br&gt;&amp;gt; member: vr4 flags=143&amp;lt;LEARNING,DISCOVER,AUTOEDGE,AUTOPTP&amp;gt;
&lt;br&gt;&amp;gt; ?? ?? ?? ??ifmaxaddr 0 port 6 priority 128 path cost 200000
&lt;br&gt;&amp;gt; member: vr0 flags=143&amp;lt;LEARNING,DISCOVER,AUTOEDGE,AUTOPTP&amp;gt;
&lt;br&gt;&amp;gt; ?? ?? ?? ??ifmaxaddr 0 port 2 priority 128 path cost 200000
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; iperf runs without the profile set:
&lt;br&gt;&amp;gt; % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15
&lt;br&gt;&amp;gt; ------------------------------------------------------------
&lt;br&gt;&amp;gt; Client connecting to 10.0.0.254, TCP port 5001
&lt;br&gt;&amp;gt; Binding to local address 10.1.0.1
&lt;br&gt;&amp;gt; TCP window size: 16.0 KByte (default)
&lt;br&gt;&amp;gt; ------------------------------------------------------------
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001
&lt;br&gt;&amp;gt; [ ID] Interval &amp;nbsp; &amp;nbsp; &amp;nbsp; Transfer &amp;nbsp; &amp;nbsp; Bandwidth
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] &amp;nbsp;0.0-15.0 sec &amp;nbsp;17.0 MBytes &amp;nbsp;9.49 Mbits/sec
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 -u -b 10Mbit
&lt;br&gt;&amp;gt; ------------------------------------------------------------
&lt;br&gt;&amp;gt; Client connecting to 10.0.0.254, UDP port 5001
&lt;br&gt;&amp;gt; Binding to local address 10.1.0.1
&lt;br&gt;&amp;gt; Sending 1470 byte datagrams
&lt;br&gt;&amp;gt; UDP buffer size: &amp;nbsp; 110 KByte (default)
&lt;br&gt;&amp;gt; ------------------------------------------------------------
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001
&lt;br&gt;&amp;gt; [ ID] Interval &amp;nbsp; &amp;nbsp; &amp;nbsp; Transfer &amp;nbsp; &amp;nbsp; Bandwidth
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] &amp;nbsp;0.0-15.0 sec &amp;nbsp;18.8 MBytes &amp;nbsp;10.5 Mbits/sec
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] Sent 13382 datagrams
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] Server Report:
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] &amp;nbsp;0.0-15.1 sec &amp;nbsp;17.4 MBytes &amp;nbsp;9.72 Mbits/sec &amp;nbsp;0.822 ms &amp;nbsp;934/13381 (7%)
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] &amp;nbsp;0.0-15.1 sec &amp;nbsp;1 datagrams received out-of-order
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; iperf runs with the profile set:
&lt;br&gt;&amp;gt; % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15
&lt;br&gt;&amp;gt; ------------------------------------------------------------
&lt;br&gt;&amp;gt; Client connecting to 10.0.0.254, TCP port 5001
&lt;br&gt;&amp;gt; Binding to local address 10.1.0.1
&lt;br&gt;&amp;gt; TCP window size: 16.0 KByte (default)
&lt;br&gt;&amp;gt; ------------------------------------------------------------
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001
&lt;br&gt;&amp;gt; [ ID] Interval &amp;nbsp; &amp;nbsp; &amp;nbsp; Transfer &amp;nbsp; &amp;nbsp; Bandwidth
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] &amp;nbsp;0.0-15.7 sec &amp;nbsp; &amp;nbsp;968 KBytes &amp;nbsp; &amp;nbsp;505 Kbits/sec
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 -u -b 10Mbit
&lt;br&gt;&amp;gt; ------------------------------------------------------------
&lt;br&gt;&amp;gt; Client connecting to 10.0.0.254, UDP port 5001
&lt;br&gt;&amp;gt; Binding to local address 10.1.0.1
&lt;br&gt;&amp;gt; Sending 1470 byte datagrams
&lt;br&gt;&amp;gt; UDP buffer size: &amp;nbsp; 110 KByte (default)
&lt;br&gt;&amp;gt; ------------------------------------------------------------
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001
&lt;br&gt;&amp;gt; [ ID] Interval &amp;nbsp; &amp;nbsp; &amp;nbsp; Transfer &amp;nbsp; &amp;nbsp; Bandwidth
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] &amp;nbsp;0.0-15.0 sec &amp;nbsp;18.8 MBytes &amp;nbsp;10.5 Mbits/sec
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] Sent 13382 datagrams
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] Server Report:
&lt;br&gt;&amp;gt; [ &amp;nbsp;3] &amp;nbsp;0.0-16.3 sec &amp;nbsp; &amp;nbsp;893 KBytes &amp;nbsp; &amp;nbsp;449 Kbits/sec &amp;nbsp;1.810 ms 12757/13379 (95%)
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Let me know what other information you would need to help me debugging this.
&lt;br&gt;&amp;gt; In advance, thank you for your help
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; --
&lt;br&gt;&amp;gt; Charles-Henri de Boysson
&lt;br&gt;&amp;gt; _______________________________________________
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26507701&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-ipfw@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw&lt;/a&gt;&lt;br&gt;&amp;gt; To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26507701&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-ipfw-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;/div&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26507701&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26507701&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Performance-issue-with-new-pipe-profile-feature-in-FreeBSD-8.0--RELEASE-tp26500647p26507701.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26505927</id>
	<title>Re: bce(4) BCM5907 CTX write errors on 7.2 driver</title>
	<published>2009-11-24T16:57:31Z</published>
	<updated>2009-11-24T16:57:31Z</updated>
	<author>
		<name>Tom Judge</name>
	</author>
	<content type="html">David Christensen wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt;&amp;gt;&amp;gt; For the record we also have not been able to reproduce the issue on 
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt; the R710 only the R610.
&lt;br&gt;&amp;gt;&amp;gt; I got hold of an R610 system and I now understand why the 
&lt;br&gt;&amp;gt;&amp;gt; issue was difficult to replicate on R710. &amp;nbsp;The R610 ships 
&lt;br&gt;&amp;gt;&amp;gt; without Enterprise iDRAC while the R710 ship with the add-in 
&lt;br&gt;&amp;gt;&amp;gt; Enterprise iDRAC module. &amp;nbsp;When the module is present the 
&lt;br&gt;&amp;gt;&amp;gt; system is managed through the additional RJ45 port but when 
&lt;br&gt;&amp;gt;&amp;gt; the module is absent iDRAC traffic will flow through the 
&lt;br&gt;&amp;gt;&amp;gt; on-board 5709 adpaters.
&lt;br&gt;&amp;gt;&amp;gt; The error will only occur when management firmware is loaded 
&lt;br&gt;&amp;gt;&amp;gt; on the 5709 AND when NC-SI management functionality is enabled.
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; You should be able to confirm this by adding or removing the 
&lt;br&gt;&amp;gt;&amp;gt; Enterprise iDRAC module on your systems. &amp;nbsp;Now that I have a 
&lt;br&gt;&amp;gt;&amp;gt; failure again I have some ideas to test which might help.
&lt;br&gt;&amp;gt;&amp;gt; Stay tuned.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Does the attached patch make a difference for you?
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; FYI, I'll be out next week on vacation.
&lt;br&gt;&amp;gt; 
&lt;/div&gt;&lt;br&gt;Hi David,
&lt;br&gt;&lt;br&gt;This patch seems to do the trick, on at least one of the R610's that we 
&lt;br&gt;have.
&lt;br&gt;&lt;br&gt;Just did cold boot, 5 warm boots, cold boot, 5 warm boots and have not 
&lt;br&gt;had any issues.
&lt;br&gt;&lt;br&gt;&lt;br&gt;Thanks
&lt;br&gt;&lt;br&gt;Tom
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505927&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505927&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/bce%284%29-BCM5907-CTX-write-errors-on-7.2-driver-tp26081795p26505927.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26505528</id>
	<title>Re: bin/118987: commit references a PR</title>
	<published>2009-11-24T16:10:02Z</published>
	<updated>2009-11-24T16:10:02Z</updated>
	<author>
		<name>dfilter service</name>
	</author>
	<content type="html">The following reply was made to PR bin/118987; it has been noted by GNATS.
&lt;br&gt;&lt;br&gt;From: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505528&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;dfilter@...&lt;/a&gt; (dfilter service)
&lt;br&gt;To: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505528&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;bug-followup@...&lt;/a&gt;
&lt;br&gt;Cc: &amp;nbsp;
&lt;br&gt;Subject: Re: bin/118987: commit references a PR
&lt;br&gt;Date: Wed, 25 Nov 2009 00:01:12 +0000 (UTC)
&lt;br&gt;&lt;br&gt;&amp;nbsp;Author: will
&lt;br&gt;&amp;nbsp;Date: Wed Nov 25 00:00:57 2009
&lt;br&gt;&amp;nbsp;New Revision: 199770
&lt;br&gt;&amp;nbsp;URL: &lt;a href=&quot;http://svn.freebsd.org/changeset/base/199770&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://svn.freebsd.org/changeset/base/199770&lt;/a&gt;&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;Log:
&lt;br&gt;&amp;nbsp; &amp;nbsp;Make ``ifconfig -l ether'' only list interfaces that speak Ethernet.
&lt;br&gt;&amp;nbsp; &amp;nbsp;
&lt;br&gt;&amp;nbsp; &amp;nbsp;PR:		118987
&lt;br&gt;&amp;nbsp; &amp;nbsp;Approved by:	ken (mentor)
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;Modified:
&lt;br&gt;&amp;nbsp; &amp;nbsp;head/sbin/ifconfig/ifconfig.c
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;Modified: head/sbin/ifconfig/ifconfig.c
&lt;br&gt;&amp;nbsp;==============================================================================
&lt;br&gt;&amp;nbsp;--- head/sbin/ifconfig/ifconfig.c	Tue Nov 24 22:37:04 2009	(r199769)
&lt;br&gt;&amp;nbsp;+++ head/sbin/ifconfig/ifconfig.c	Wed Nov 25 00:00:57 2009	(r199770)
&lt;br&gt;&amp;nbsp;@@ -147,7 +147,7 @@ main(int argc, char *argv[])
&lt;br&gt;&amp;nbsp; 	struct ifaddrs *ifap, *ifa;
&lt;br&gt;&amp;nbsp; 	struct ifreq paifr;
&lt;br&gt;&amp;nbsp; 	const struct sockaddr_dl *sdl;
&lt;br&gt;&amp;nbsp;-	char options[1024], *cp;
&lt;br&gt;&amp;nbsp;+	char options[1024], *cp, *namecp = NULL;
&lt;br&gt;&amp;nbsp; 	const char *ifname;
&lt;br&gt;&amp;nbsp; 	struct option *p;
&lt;br&gt;&amp;nbsp; 	size_t iflen;
&lt;br&gt;&amp;nbsp;@@ -294,7 +294,7 @@ main(int argc, char *argv[])
&lt;br&gt;&amp;nbsp; 			sdl = (const struct sockaddr_dl *) ifa-&amp;gt;ifa_addr;
&lt;br&gt;&amp;nbsp; 		else
&lt;br&gt;&amp;nbsp; 			sdl = NULL;
&lt;br&gt;&amp;nbsp;-		if (cp != NULL &amp;&amp; strcmp(cp, ifa-&amp;gt;ifa_name) == 0)
&lt;br&gt;&amp;nbsp;+		if (cp != NULL &amp;&amp; strcmp(cp, ifa-&amp;gt;ifa_name) == 0 &amp;&amp; !namesonly)
&lt;br&gt;&amp;nbsp; 			continue;
&lt;br&gt;&amp;nbsp; 		iflen = strlcpy(name, ifa-&amp;gt;ifa_name, sizeof(name));
&lt;br&gt;&amp;nbsp; 		if (iflen &amp;gt;= sizeof(name)) {
&lt;br&gt;&amp;nbsp;@@ -308,16 +308,32 @@ main(int argc, char *argv[])
&lt;br&gt;&amp;nbsp; 			continue;
&lt;br&gt;&amp;nbsp; 		if (uponly &amp;&amp; (ifa-&amp;gt;ifa_flags &amp; IFF_UP) == 0)
&lt;br&gt;&amp;nbsp; 			continue;
&lt;br&gt;&amp;nbsp;-		ifindex++;
&lt;br&gt;&amp;nbsp; 		/*
&lt;br&gt;&amp;nbsp; 		 * Are we just listing the interfaces?
&lt;br&gt;&amp;nbsp; 		 */
&lt;br&gt;&amp;nbsp; 		if (namesonly) {
&lt;br&gt;&amp;nbsp;+			if (namecp == cp)
&lt;br&gt;&amp;nbsp;+				continue;
&lt;br&gt;&amp;nbsp;+			if (afp != NULL) {
&lt;br&gt;&amp;nbsp;+				/* special case for &amp;quot;ether&amp;quot; address family */
&lt;br&gt;&amp;nbsp;+				if (!strcmp(afp-&amp;gt;af_name, &amp;quot;ether&amp;quot;)) {
&lt;br&gt;&amp;nbsp;+					if (sdl == NULL ||
&lt;br&gt;&amp;nbsp;+					 &amp;nbsp; &amp;nbsp;sdl-&amp;gt;sdl_type != IFT_ETHER ||
&lt;br&gt;&amp;nbsp;+					 &amp;nbsp; &amp;nbsp;sdl-&amp;gt;sdl_alen != ETHER_ADDR_LEN)
&lt;br&gt;&amp;nbsp;+						continue;
&lt;br&gt;&amp;nbsp;+				} else {
&lt;br&gt;&amp;nbsp;+					if (ifa-&amp;gt;ifa_addr-&amp;gt;sa_family != afp-&amp;gt;af_af)
&lt;br&gt;&amp;nbsp;+						continue;
&lt;br&gt;&amp;nbsp;+				}
&lt;br&gt;&amp;nbsp;+			}
&lt;br&gt;&amp;nbsp;+			namecp = cp;
&lt;br&gt;&amp;nbsp;+			ifindex++;
&lt;br&gt;&amp;nbsp; 			if (ifindex &amp;gt; 1)
&lt;br&gt;&amp;nbsp; 				printf(&amp;quot; &amp;quot;);
&lt;br&gt;&amp;nbsp; 			fputs(name, stdout);
&lt;br&gt;&amp;nbsp; 			continue;
&lt;br&gt;&amp;nbsp; 		}
&lt;br&gt;&amp;nbsp;+		ifindex++;
&lt;br&gt;&amp;nbsp; 
&lt;br&gt;&amp;nbsp; 		if (argc &amp;gt; 0)
&lt;br&gt;&amp;nbsp; 			ifconfig(argc, argv, 0, afp);
&lt;br&gt;&amp;nbsp;_______________________________________________
&lt;br&gt;&amp;nbsp;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505528&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;svn-src-all@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;nbsp;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/svn-src-all&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/svn-src-all&lt;/a&gt;&lt;br&gt;&amp;nbsp;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505528&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;svn-src-all-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;&amp;nbsp;
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505528&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505528&amp;i=5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-bin-118987%3A-commit-references-a-PR-tp26505528p26505528.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26505494</id>
	<title>Re: bin/118987: ifconfig(8): ifconfig -l (address_family) does not work correctly on RELENG-7</title>
	<published>2009-11-24T16:06:26Z</published>
	<updated>2009-11-24T16:06:26Z</updated>
	<author>
		<name>Will Andrews-2</name>
	</author>
	<content type="html">Synopsis: ifconfig(8): ifconfig -l (address_family) does not work correctly on RELENG-7
&lt;br&gt;&lt;br&gt;State-Changed-From-To: analyzed-&amp;gt;closed
&lt;br&gt;State-Changed-By: will
&lt;br&gt;State-Changed-When: Wed Nov 25 00:05:19 UTC 2009
&lt;br&gt;State-Changed-Why: 
&lt;br&gt;Fixed in r199770 (HEAD).
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.freebsd.org/cgi/query-pr.cgi?pr=118987&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.freebsd.org/cgi/query-pr.cgi?pr=118987&lt;/a&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505494&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26505494&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-bin-118987%3A-ifconfig%288%29%3A-ifconfig--l-%28address_family%29-does-not-work-correctly-on-RELENG-7-tp26505494p26505494.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26504939</id>
	<title>Re: [PATCH] Remove if_watchdog and if_timer</title>
	<published>2009-11-24T15:07:20Z</published>
	<updated>2009-11-24T15:07:20Z</updated>
	<author>
		<name>Robert Watson</name>
	</author>
	<content type="html">&lt;br&gt;On Tue, 24 Nov 2009, John Baldwin wrote:
&lt;br&gt;&lt;br&gt;&amp;gt; Now that no drivers in the tree use if_watchdog and if_timer, this patch 
&lt;br&gt;&amp;gt; just removes them completely. &amp;nbsp;Since if_timer was a short that was adjacent 
&lt;br&gt;&amp;gt; to if_index, removing if_timer would have still left a padding hole in the 
&lt;br&gt;&amp;gt; form of a short on all of our current architectures. &amp;nbsp;After discussing this 
&lt;br&gt;&amp;gt; briefly with Brooks I changed if_index to be an int rather than leaving the 
&lt;br&gt;&amp;gt; padding hole. &amp;nbsp;Comments?
&lt;br&gt;&lt;br&gt;The if_watchdog/if_timer changes sound good to me, but let's do the if_index 
&lt;br&gt;change separately, and just add padding in this change. &amp;nbsp;The if_index -&amp;gt; 
&lt;br&gt;32-bit chnge is one that's been overdue for a long time, but it's going to 
&lt;br&gt;have a lot of side effects, so keeping it to its own changesets (which can be 
&lt;br&gt;backed out if needed more easily) is probably a good idea. &amp;nbsp;Thanks for taking 
&lt;br&gt;on the watchdog changes!
&lt;br&gt;&lt;br&gt;Robert N M Watson
&lt;br&gt;Computer Laboratory
&lt;br&gt;University of Cambridge
&lt;br&gt;&lt;br&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; --- //depot/vendor/freebsd/src/sys/net/if.c	2009/11/12 19:05:14
&lt;br&gt;&amp;gt; +++ //depot/user/jhb/cleanup/sys/net/if.c	2009/11/19 22:35:58
&lt;br&gt;&amp;gt; @@ -125,10 +125,8 @@
&lt;br&gt;&amp;gt; static void	if_freemulti(struct ifmultiaddr *);
&lt;br&gt;&amp;gt; static void	if_init(void *);
&lt;br&gt;&amp;gt; static void	if_grow(void);
&lt;br&gt;&amp;gt; -static void	if_check(void *);
&lt;br&gt;&amp;gt; static void	if_route(struct ifnet *, int flag, int fam);
&lt;br&gt;&amp;gt; static int	if_setflag(struct ifnet *, int, int, int *, int);
&lt;br&gt;&amp;gt; -static void	if_slowtimo(void *);
&lt;br&gt;&amp;gt; static int	if_transmit(struct ifnet *ifp, struct mbuf *m);
&lt;br&gt;&amp;gt; static void	if_unroute(struct ifnet *, int flag, int fam);
&lt;br&gt;&amp;gt; static void	link_rtrequest(int, struct rtentry *, struct rt_addrinfo *);
&lt;br&gt;&amp;gt; @@ -185,11 +183,6 @@
&lt;br&gt;&amp;gt; static	if_com_alloc_t *if_com_alloc[256];
&lt;br&gt;&amp;gt; static	if_com_free_t *if_com_free[256];
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; -/*
&lt;br&gt;&amp;gt; - * System initialization
&lt;br&gt;&amp;gt; - */
&lt;br&gt;&amp;gt; -SYSINIT(interface_check, SI_SUB_PROTO_IF, SI_ORDER_FIRST, if_check, NULL);
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; MALLOC_DEFINE(M_IFNET, &amp;quot;ifnet&amp;quot;, &amp;quot;interface internals&amp;quot;);
&lt;br&gt;&amp;gt; MALLOC_DEFINE(M_IFADDR, &amp;quot;ifaddr&amp;quot;, &amp;quot;interface address&amp;quot;);
&lt;br&gt;&amp;gt; MALLOC_DEFINE(M_IFMADDR, &amp;quot;ether_multi&amp;quot;, &amp;quot;link-level multicast address&amp;quot;);
&lt;br&gt;&amp;gt; @@ -375,18 +368,6 @@
&lt;br&gt;&amp;gt; 	V_ifindex_table = e;
&lt;br&gt;&amp;gt; }
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; -static void
&lt;br&gt;&amp;gt; -if_check(void *dummy __unused)
&lt;br&gt;&amp;gt; -{
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; -	/*
&lt;br&gt;&amp;gt; -	 * If at least one interface added during boot uses
&lt;br&gt;&amp;gt; -	 * if_watchdog then start the timer.
&lt;br&gt;&amp;gt; -	 */
&lt;br&gt;&amp;gt; -	if (slowtimo_started)
&lt;br&gt;&amp;gt; -		if_slowtimo(0);
&lt;br&gt;&amp;gt; -}
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; /*
&lt;br&gt;&amp;gt; &amp;nbsp;* Allocate a struct ifnet and an index for an interface. &amp;nbsp;A layer 2
&lt;br&gt;&amp;gt; &amp;nbsp;* common structure will also be allocated if an allocation routine is
&lt;br&gt;&amp;gt; @@ -670,18 +651,6 @@
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; 	/* Announce the interface. */
&lt;br&gt;&amp;gt; 	rt_ifannouncemsg(ifp, IFAN_ARRIVAL);
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; -	if (!vmove &amp;&amp; ifp-&amp;gt;if_watchdog != NULL) {
&lt;br&gt;&amp;gt; -		if_printf(ifp,
&lt;br&gt;&amp;gt; -		 &amp;nbsp; &amp;nbsp;&amp;quot;WARNING: using obsoleted if_watchdog interface\n&amp;quot;);
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; -		/*
&lt;br&gt;&amp;gt; -		 * Note that we need if_slowtimo(). &amp;nbsp;If this happens after
&lt;br&gt;&amp;gt; -		 * boot, then call if_slowtimo() directly.
&lt;br&gt;&amp;gt; -		 */
&lt;br&gt;&amp;gt; -		if (atomic_cmpset_int(&amp;slowtimo_started, 0, 1) &amp;&amp; !cold)
&lt;br&gt;&amp;gt; -			if_slowtimo(0);
&lt;br&gt;&amp;gt; -	}
&lt;br&gt;&amp;gt; }
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; static void
&lt;br&gt;&amp;gt; @@ -1973,39 +1942,6 @@
&lt;br&gt;&amp;gt; }
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; /*
&lt;br&gt;&amp;gt; - * Handle interface watchdog timer routines. &amp;nbsp;Called
&lt;br&gt;&amp;gt; - * from softclock, we decrement timers (if set) and
&lt;br&gt;&amp;gt; - * call the appropriate interface routine on expiration.
&lt;br&gt;&amp;gt; - *
&lt;br&gt;&amp;gt; - * XXXRW: Note that because timeouts run with Giant, if_watchdog() is called
&lt;br&gt;&amp;gt; - * holding Giant.
&lt;br&gt;&amp;gt; - */
&lt;br&gt;&amp;gt; -static void
&lt;br&gt;&amp;gt; -if_slowtimo(void *arg)
&lt;br&gt;&amp;gt; -{
&lt;br&gt;&amp;gt; -	VNET_ITERATOR_DECL(vnet_iter);
&lt;br&gt;&amp;gt; -	struct ifnet *ifp;
&lt;br&gt;&amp;gt; -	int s = splimp();
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; -	VNET_LIST_RLOCK_NOSLEEP();
&lt;br&gt;&amp;gt; -	IFNET_RLOCK_NOSLEEP();
&lt;br&gt;&amp;gt; -	VNET_FOREACH(vnet_iter) {
&lt;br&gt;&amp;gt; -		CURVNET_SET(vnet_iter);
&lt;br&gt;&amp;gt; -		TAILQ_FOREACH(ifp, &amp;V_ifnet, if_link) {
&lt;br&gt;&amp;gt; -			if (ifp-&amp;gt;if_timer == 0 || --ifp-&amp;gt;if_timer)
&lt;br&gt;&amp;gt; -				continue;
&lt;br&gt;&amp;gt; -			if (ifp-&amp;gt;if_watchdog)
&lt;br&gt;&amp;gt; -				(*ifp-&amp;gt;if_watchdog)(ifp);
&lt;br&gt;&amp;gt; -		}
&lt;br&gt;&amp;gt; -		CURVNET_RESTORE();
&lt;br&gt;&amp;gt; -	}
&lt;br&gt;&amp;gt; -	IFNET_RUNLOCK_NOSLEEP();
&lt;br&gt;&amp;gt; -	VNET_LIST_RUNLOCK_NOSLEEP();
&lt;br&gt;&amp;gt; -	splx(s);
&lt;br&gt;&amp;gt; -	timeout(if_slowtimo, (void *)0, hz / IFNET_SLOWHZ);
&lt;br&gt;&amp;gt; -}
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; -/*
&lt;br&gt;&amp;gt; &amp;nbsp;* Map interface name to interface structure pointer, with or without
&lt;br&gt;&amp;gt; &amp;nbsp;* returning a reference.
&lt;br&gt;&amp;gt; &amp;nbsp;*/
&lt;br&gt;&amp;gt; --- //depot/vendor/freebsd/src/sys/net/if_dead.c	2009/04/23 11:55:13
&lt;br&gt;&amp;gt; +++ //depot/user/jhb/cleanup/sys/net/if_dead.c	2009/11/19 22:35:58
&lt;br&gt;&amp;gt; @@ -70,12 +70,6 @@
&lt;br&gt;&amp;gt; 	return (ENXIO);
&lt;br&gt;&amp;gt; }
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; -static void
&lt;br&gt;&amp;gt; -ifdead_watchdog(struct ifnet *ifp)
&lt;br&gt;&amp;gt; -{
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; -}
&lt;br&gt;&amp;gt; -
&lt;br&gt;&amp;gt; static int
&lt;br&gt;&amp;gt; ifdead_resolvemulti(struct ifnet *ifp, struct sockaddr **llsa,
&lt;br&gt;&amp;gt; &amp;nbsp; &amp;nbsp; struct sockaddr *sa)
&lt;br&gt;&amp;gt; @@ -107,7 +101,6 @@
&lt;br&gt;&amp;gt; 	ifp-&amp;gt;if_input = ifdead_input;
&lt;br&gt;&amp;gt; 	ifp-&amp;gt;if_start = ifdead_start;
&lt;br&gt;&amp;gt; 	ifp-&amp;gt;if_ioctl = ifdead_ioctl;
&lt;br&gt;&amp;gt; -	ifp-&amp;gt;if_watchdog = ifdead_watchdog;
&lt;br&gt;&amp;gt; 	ifp-&amp;gt;if_resolvemulti = ifdead_resolvemulti;
&lt;br&gt;&amp;gt; 	ifp-&amp;gt;if_qflush = ifdead_qflush;
&lt;br&gt;&amp;gt; 	ifp-&amp;gt;if_transmit = ifdead_transmit;
&lt;br&gt;&amp;gt; --- //depot/vendor/freebsd/src/sys/net/if_var.h	2009/11/12 19:05:14
&lt;br&gt;&amp;gt; +++ //depot/user/jhb/cleanup/sys/net/if_var.h	2009/11/19 22:35:58
&lt;br&gt;&amp;gt; @@ -140,8 +140,7 @@
&lt;br&gt;&amp;gt; 	int	if_pcount;		/* number of promiscuous listeners */
&lt;br&gt;&amp;gt; 	struct	carp_if *if_carp;	/* carp interface structure */
&lt;br&gt;&amp;gt; 	struct	bpf_if *if_bpf;		/* packet filter structure */
&lt;br&gt;&amp;gt; -	u_short	if_index;		/* numeric abbreviation for this if &amp;nbsp;*/
&lt;br&gt;&amp;gt; -	short	if_timer;		/* time 'til if_watchdog called */
&lt;br&gt;&amp;gt; +	u_int	if_index;		/* numeric abbreviation for this if &amp;nbsp;*/
&lt;br&gt;&amp;gt; 	struct &amp;nbsp;ifvlantrunk *if_vlantrunk; /* pointer to 802.1q data */
&lt;br&gt;&amp;gt; 	int	if_flags;		/* up/down, broadcast, etc. */
&lt;br&gt;&amp;gt; 	int	if_capabilities;	/* interface features &amp; capabilities */
&lt;br&gt;&amp;gt; @@ -161,8 +160,6 @@
&lt;br&gt;&amp;gt; 		(struct ifnet *);
&lt;br&gt;&amp;gt; 	int	(*if_ioctl)		/* ioctl routine */
&lt;br&gt;&amp;gt; 		(struct ifnet *, u_long, caddr_t);
&lt;br&gt;&amp;gt; -	void	(*if_watchdog)		/* timer routine */
&lt;br&gt;&amp;gt; -		(struct ifnet *);
&lt;br&gt;&amp;gt; 	void	(*if_init)		/* Init routine */
&lt;br&gt;&amp;gt; 		(void *);
&lt;br&gt;&amp;gt; 	int	(*if_resolvemulti)	/* validate/resolve multicast */
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; -- 
&lt;br&gt;&amp;gt; John Baldwin
&lt;br&gt;&amp;gt; _______________________________________________
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26504939&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;&amp;gt; To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26504939&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;&amp;gt;
&lt;/div&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26504939&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26504939&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/-PATCH--Remove-if_watchdog-and-if_timer-tp26501432p26504939.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26502317</id>
	<title>Re: Reducing number of interrupts from intel pro 1000 et adapter</title>
	<published>2009-11-24T11:59:21Z</published>
	<updated>2009-11-24T11:59:21Z</updated>
	<author>
		<name>Jack Vogel</name>
	</author>
	<content type="html">There are significant changes to igb forthcoming, I believe I have fixed the
&lt;br&gt;multiqueue problems that exist in it now, and I am working to improve the
&lt;br&gt;AIM code so it handles TX and RX (this is still experimental right now
&lt;br&gt;though).
&lt;br&gt;I hope it addresses your problems.
&lt;br&gt;&lt;br&gt;Jack
&lt;br&gt;&lt;br&gt;&lt;br&gt;On Tue, Nov 24, 2009 at 11:40 AM, Pyun YongHyeon &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26502317&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;pyunyh@...&lt;/a&gt;&amp;gt; wrote:
&lt;br&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; On Mon, Nov 23, 2009 at 07:42:20PM +0200, Yuriy A. Korobko wrote:
&lt;br&gt;&amp;gt; &amp;gt; Hi,
&lt;br&gt;&amp;gt; &amp;gt;
&lt;br&gt;&amp;gt; &amp;gt; I'd like to know a way to control tx interrupts on intel pro 1000 et
&lt;br&gt;&amp;gt; &amp;gt; adapter with igb driver. Just installed one in the router and systat
&lt;br&gt;&amp;gt; &amp;gt; shows 8-9k rx interrupts and 20k tx interrupts from igb0 and igb1
&lt;br&gt;&amp;gt; &amp;gt; adapters. Box is a router running freebsd 7.2 release, I've tried
&lt;br&gt;&amp;gt; &amp;gt; default driver from kernel source and latest from intel site, effect is
&lt;br&gt;&amp;gt; &amp;gt; the same with automatic interrupt moderation enabled and disabled. I
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; I'm also aware of this issue. Here is patch I'm currently
&lt;br&gt;&amp;gt; experimenting. It seems igb(4) wants to dynamically adjust
&lt;br&gt;&amp;gt; interrupt moderation on Rx traffic such that this seems to cause
&lt;br&gt;&amp;gt; lots of Tx interrupts under heavy Rx traffic. I simply disabled
&lt;br&gt;&amp;gt; that feature and fixed Rx handler not to generate more interrupts.
&lt;br&gt;&amp;gt; Without Rx handler fix the igb(4) took all CPU cycles under heady
&lt;br&gt;&amp;gt; load(64 bytes UDP torture test) I couldn't even type a character
&lt;br&gt;&amp;gt; on console. You can get my patch at the following URL.
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://people.freebsd.org/~yongari/igb/igb.buf.patch5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://people.freebsd.org/~yongari/igb/igb.buf.patch5&lt;/a&gt;&amp;lt;&lt;a href=&quot;http://people.freebsd.org/%7Eyongari/igb/igb.buf.patch5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://people.freebsd.org/%7Eyongari/igb/igb.buf.patch5&lt;/a&gt;&amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; The patch also includes other changes I made so it's somewhat big.
&lt;br&gt;&amp;gt; Note, please don't apply the patch on production servers it needs
&lt;br&gt;&amp;gt; more testing.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; &amp;gt; have the same box with intel pro 1000 pt adapter which have
&lt;br&gt;&amp;gt; &amp;gt; tx(rx)_int_delay sysctls in em driver, I was able to reduce number of
&lt;br&gt;&amp;gt; &amp;gt; tx/rx interrupts to 7-8k per interface and got much more cpu idle
&lt;br&gt;&amp;gt; &amp;gt; because of less context switches with same pps.
&lt;br&gt;&amp;gt; &amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; I guess you sacrificed latencies.
&lt;br&gt;&amp;gt; _______________________________________________
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26502317&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;&amp;gt; To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26502317&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;&amp;gt;
&lt;/div&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26502317&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26502317&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Reducing-number-of-interrupts-from-intel-pro-1000-et-adapter-tp26483054p26502317.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26502080</id>
	<title>Re: Reducing number of interrupts from intel pro 1000 et adapter</title>
	<published>2009-11-24T11:40:25Z</published>
	<updated>2009-11-24T11:40:25Z</updated>
	<author>
		<name>Pyun YongHyeon</name>
	</author>
	<content type="html">On Mon, Nov 23, 2009 at 07:42:20PM +0200, Yuriy A. Korobko wrote:
&lt;br&gt;&amp;gt; Hi,
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; I'd like to know a way to control tx interrupts on intel pro 1000 et
&lt;br&gt;&amp;gt; adapter with igb driver. Just installed one in the router and systat
&lt;br&gt;&amp;gt; shows 8-9k rx interrupts and 20k tx interrupts from igb0 and igb1
&lt;br&gt;&amp;gt; adapters. Box is a router running freebsd 7.2 release, I've tried
&lt;br&gt;&amp;gt; default driver from kernel source and latest from intel site, effect is
&lt;br&gt;&amp;gt; the same with automatic interrupt moderation enabled and disabled. I
&lt;br&gt;&lt;br&gt;I'm also aware of this issue. Here is patch I'm currently
&lt;br&gt;experimenting. It seems igb(4) wants to dynamically adjust
&lt;br&gt;interrupt moderation on Rx traffic such that this seems to cause
&lt;br&gt;lots of Tx interrupts under heavy Rx traffic. I simply disabled
&lt;br&gt;that feature and fixed Rx handler not to generate more interrupts.
&lt;br&gt;Without Rx handler fix the igb(4) took all CPU cycles under heady
&lt;br&gt;load(64 bytes UDP torture test) I couldn't even type a character
&lt;br&gt;on console. You can get my patch at the following URL.
&lt;br&gt;&lt;a href=&quot;http://people.freebsd.org/~yongari/igb/igb.buf.patch5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://people.freebsd.org/~yongari/igb/igb.buf.patch5&lt;/a&gt;&lt;br&gt;&lt;br&gt;The patch also includes other changes I made so it's somewhat big.
&lt;br&gt;Note, please don't apply the patch on production servers it needs
&lt;br&gt;more testing.
&lt;br&gt;&lt;br&gt;&amp;gt; have the same box with intel pro 1000 pt adapter which have
&lt;br&gt;&amp;gt; tx(rx)_int_delay sysctls in em driver, I was able to reduce number of
&lt;br&gt;&amp;gt; tx/rx interrupts to 7-8k per interface and got much more cpu idle
&lt;br&gt;&amp;gt; because of less context switches with same pps.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&lt;br&gt;I guess you sacrificed latencies.
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26502080&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26502080&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Reducing-number-of-interrupts-from-intel-pro-1000-et-adapter-tp26483054p26502080.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26501432</id>
	<title>[PATCH] Remove if_watchdog and if_timer</title>
	<published>2009-11-24T10:56:05Z</published>
	<updated>2009-11-24T10:56:05Z</updated>
	<author>
		<name>John Baldwin</name>
	</author>
	<content type="html">Now that no drivers in the tree use if_watchdog and if_timer, this patch just 
&lt;br&gt;removes them completely. &amp;nbsp;Since if_timer was a short that was adjacent to 
&lt;br&gt;if_index, removing if_timer would have still left a padding hole in the form 
&lt;br&gt;of a short on all of our current architectures. &amp;nbsp;After discussing this briefly 
&lt;br&gt;with Brooks I changed if_index to be an int rather than leaving the padding 
&lt;br&gt;hole. &amp;nbsp;Comments?
&lt;br&gt;&lt;br&gt;--- //depot/vendor/freebsd/src/sys/net/if.c	2009/11/12 19:05:14
&lt;br&gt;+++ //depot/user/jhb/cleanup/sys/net/if.c	2009/11/19 22:35:58
&lt;br&gt;@@ -125,10 +125,8 @@
&lt;br&gt;&amp;nbsp;static void	if_freemulti(struct ifmultiaddr *);
&lt;br&gt;&amp;nbsp;static void	if_init(void *);
&lt;br&gt;&amp;nbsp;static void	if_grow(void);
&lt;br&gt;-static void	if_check(void *);
&lt;br&gt;&amp;nbsp;static void	if_route(struct ifnet *, int flag, int fam);
&lt;br&gt;&amp;nbsp;static int	if_setflag(struct ifnet *, int, int, int *, int);
&lt;br&gt;-static void	if_slowtimo(void *);
&lt;br&gt;&amp;nbsp;static int	if_transmit(struct ifnet *ifp, struct mbuf *m);
&lt;br&gt;&amp;nbsp;static void	if_unroute(struct ifnet *, int flag, int fam);
&lt;br&gt;&amp;nbsp;static void	link_rtrequest(int, struct rtentry *, struct rt_addrinfo *);
&lt;br&gt;@@ -185,11 +183,6 @@
&lt;br&gt;&amp;nbsp;static	if_com_alloc_t *if_com_alloc[256];
&lt;br&gt;&amp;nbsp;static	if_com_free_t *if_com_free[256];
&lt;br&gt;&amp;nbsp;
&lt;br&gt;-/*
&lt;br&gt;- * System initialization
&lt;br&gt;- */
&lt;br&gt;-SYSINIT(interface_check, SI_SUB_PROTO_IF, SI_ORDER_FIRST, if_check, NULL);
&lt;br&gt;-
&lt;br&gt;&amp;nbsp;MALLOC_DEFINE(M_IFNET, &amp;quot;ifnet&amp;quot;, &amp;quot;interface internals&amp;quot;);
&lt;br&gt;&amp;nbsp;MALLOC_DEFINE(M_IFADDR, &amp;quot;ifaddr&amp;quot;, &amp;quot;interface address&amp;quot;);
&lt;br&gt;&amp;nbsp;MALLOC_DEFINE(M_IFMADDR, &amp;quot;ether_multi&amp;quot;, &amp;quot;link-level multicast address&amp;quot;);
&lt;br&gt;@@ -375,18 +368,6 @@
&lt;br&gt;&amp;nbsp;	V_ifindex_table = e;
&lt;br&gt;&amp;nbsp;}
&lt;br&gt;&amp;nbsp;
&lt;br&gt;-static void
&lt;br&gt;-if_check(void *dummy __unused)
&lt;br&gt;-{
&lt;br&gt;-
&lt;br&gt;-	/*
&lt;br&gt;-	 * If at least one interface added during boot uses
&lt;br&gt;-	 * if_watchdog then start the timer.
&lt;br&gt;-	 */
&lt;br&gt;-	if (slowtimo_started)
&lt;br&gt;-		if_slowtimo(0);
&lt;br&gt;-}
&lt;br&gt;-
&lt;br&gt;&amp;nbsp;/*
&lt;br&gt;&amp;nbsp; * Allocate a struct ifnet and an index for an interface. &amp;nbsp;A layer 2
&lt;br&gt;&amp;nbsp; * common structure will also be allocated if an allocation routine is
&lt;br&gt;@@ -670,18 +651,6 @@
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;	/* Announce the interface. */
&lt;br&gt;&amp;nbsp;	rt_ifannouncemsg(ifp, IFAN_ARRIVAL);
&lt;br&gt;-
&lt;br&gt;-	if (!vmove &amp;&amp; ifp-&amp;gt;if_watchdog != NULL) {
&lt;br&gt;-		if_printf(ifp,
&lt;br&gt;-		 &amp;nbsp; &amp;nbsp;&amp;quot;WARNING: using obsoleted if_watchdog interface\n&amp;quot;);
&lt;br&gt;-
&lt;br&gt;-		/*
&lt;br&gt;-		 * Note that we need if_slowtimo(). &amp;nbsp;If this happens after
&lt;br&gt;-		 * boot, then call if_slowtimo() directly.
&lt;br&gt;-		 */
&lt;br&gt;-		if (atomic_cmpset_int(&amp;slowtimo_started, 0, 1) &amp;&amp; !cold)
&lt;br&gt;-			if_slowtimo(0);
&lt;br&gt;-	}
&lt;br&gt;&amp;nbsp;}
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;static void
&lt;br&gt;@@ -1973,39 +1942,6 @@
&lt;br&gt;&amp;nbsp;}
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;/*
&lt;br&gt;- * Handle interface watchdog timer routines. &amp;nbsp;Called
&lt;br&gt;- * from softclock, we decrement timers (if set) and
&lt;br&gt;- * call the appropriate interface routine on expiration.
&lt;br&gt;- *
&lt;br&gt;- * XXXRW: Note that because timeouts run with Giant, if_watchdog() is called
&lt;br&gt;- * holding Giant.
&lt;br&gt;- */
&lt;br&gt;-static void
&lt;br&gt;-if_slowtimo(void *arg)
&lt;br&gt;-{
&lt;br&gt;-	VNET_ITERATOR_DECL(vnet_iter);
&lt;br&gt;-	struct ifnet *ifp;
&lt;br&gt;-	int s = splimp();
&lt;br&gt;-
&lt;br&gt;-	VNET_LIST_RLOCK_NOSLEEP();
&lt;br&gt;-	IFNET_RLOCK_NOSLEEP();
&lt;br&gt;-	VNET_FOREACH(vnet_iter) {
&lt;br&gt;-		CURVNET_SET(vnet_iter);
&lt;br&gt;-		TAILQ_FOREACH(ifp, &amp;V_ifnet, if_link) {
&lt;br&gt;-			if (ifp-&amp;gt;if_timer == 0 || --ifp-&amp;gt;if_timer)
&lt;br&gt;-				continue;
&lt;br&gt;-			if (ifp-&amp;gt;if_watchdog)
&lt;br&gt;-				(*ifp-&amp;gt;if_watchdog)(ifp);
&lt;br&gt;-		}
&lt;br&gt;-		CURVNET_RESTORE();
&lt;br&gt;-	}
&lt;br&gt;-	IFNET_RUNLOCK_NOSLEEP();
&lt;br&gt;-	VNET_LIST_RUNLOCK_NOSLEEP();
&lt;br&gt;-	splx(s);
&lt;br&gt;-	timeout(if_slowtimo, (void *)0, hz / IFNET_SLOWHZ);
&lt;br&gt;-}
&lt;br&gt;-
&lt;br&gt;-/*
&lt;br&gt;&amp;nbsp; * Map interface name to interface structure pointer, with or without
&lt;br&gt;&amp;nbsp; * returning a reference.
&lt;br&gt;&amp;nbsp; */
&lt;br&gt;--- //depot/vendor/freebsd/src/sys/net/if_dead.c	2009/04/23 11:55:13
&lt;br&gt;+++ //depot/user/jhb/cleanup/sys/net/if_dead.c	2009/11/19 22:35:58
&lt;br&gt;@@ -70,12 +70,6 @@
&lt;br&gt;&amp;nbsp;	return (ENXIO);
&lt;br&gt;&amp;nbsp;}
&lt;br&gt;&amp;nbsp;
&lt;br&gt;-static void
&lt;br&gt;-ifdead_watchdog(struct ifnet *ifp)
&lt;br&gt;-{
&lt;br&gt;-
&lt;br&gt;-}
&lt;br&gt;-
&lt;br&gt;&amp;nbsp;static int
&lt;br&gt;&amp;nbsp;ifdead_resolvemulti(struct ifnet *ifp, struct sockaddr **llsa,
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;struct sockaddr *sa)
&lt;br&gt;@@ -107,7 +101,6 @@
&lt;br&gt;&amp;nbsp;	ifp-&amp;gt;if_input = ifdead_input;
&lt;br&gt;&amp;nbsp;	ifp-&amp;gt;if_start = ifdead_start;
&lt;br&gt;&amp;nbsp;	ifp-&amp;gt;if_ioctl = ifdead_ioctl;
&lt;br&gt;-	ifp-&amp;gt;if_watchdog = ifdead_watchdog;
&lt;br&gt;&amp;nbsp;	ifp-&amp;gt;if_resolvemulti = ifdead_resolvemulti;
&lt;br&gt;&amp;nbsp;	ifp-&amp;gt;if_qflush = ifdead_qflush;
&lt;br&gt;&amp;nbsp;	ifp-&amp;gt;if_transmit = ifdead_transmit;
&lt;br&gt;--- //depot/vendor/freebsd/src/sys/net/if_var.h	2009/11/12 19:05:14
&lt;br&gt;+++ //depot/user/jhb/cleanup/sys/net/if_var.h	2009/11/19 22:35:58
&lt;br&gt;@@ -140,8 +140,7 @@
&lt;br&gt;&amp;nbsp;	int	if_pcount;		/* number of promiscuous listeners */
&lt;br&gt;&amp;nbsp;	struct	carp_if *if_carp;	/* carp interface structure */
&lt;br&gt;&amp;nbsp;	struct	bpf_if *if_bpf;		/* packet filter structure */
&lt;br&gt;-	u_short	if_index;		/* numeric abbreviation for this if &amp;nbsp;*/
&lt;br&gt;-	short	if_timer;		/* time 'til if_watchdog called */
&lt;br&gt;+	u_int	if_index;		/* numeric abbreviation for this if &amp;nbsp;*/
&lt;br&gt;&amp;nbsp;	struct &amp;nbsp;ifvlantrunk *if_vlantrunk; /* pointer to 802.1q data */
&lt;br&gt;&amp;nbsp;	int	if_flags;		/* up/down, broadcast, etc. */
&lt;br&gt;&amp;nbsp;	int	if_capabilities;	/* interface features &amp; capabilities */
&lt;br&gt;@@ -161,8 +160,6 @@
&lt;br&gt;&amp;nbsp;		(struct ifnet *);
&lt;br&gt;&amp;nbsp;	int	(*if_ioctl)		/* ioctl routine */
&lt;br&gt;&amp;nbsp;		(struct ifnet *, u_long, caddr_t);
&lt;br&gt;-	void	(*if_watchdog)		/* timer routine */
&lt;br&gt;-		(struct ifnet *);
&lt;br&gt;&amp;nbsp;	void	(*if_init)		/* Init routine */
&lt;br&gt;&amp;nbsp;		(void *);
&lt;br&gt;&amp;nbsp;	int	(*if_resolvemulti)	/* validate/resolve multicast */
&lt;br&gt;&lt;br&gt;-- 
&lt;br&gt;John Baldwin
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26501432&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26501432&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/-PATCH--Remove-if_watchdog-and-if_timer-tp26501432p26501432.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26500647</id>
	<title>Performance issue with new pipe profile feature in FreeBSD 8.0  RELEASE</title>
	<published>2009-11-24T09:40:31Z</published>
	<updated>2009-11-24T09:40:31Z</updated>
	<author>
		<name>Charles Henri de Boysson</name>
	</author>
	<content type="html">Hi,
&lt;br&gt;&lt;br&gt;I have a simple setup with two computer connected via a FreeBSD bridge
&lt;br&gt;running 8.0 RELEASE.
&lt;br&gt;I am trying to use dummynet to simulate a wireless network between the
&lt;br&gt;two and for that I wanted to use the pipe profile feature of FreeBSD
&lt;br&gt;8.0.
&lt;br&gt;But as I was experimenting with the pipe profile feature I ran into some issues.
&lt;br&gt;&lt;br&gt;I have setup ipfw to send traffic coming for either interface of the
&lt;br&gt;bridge to a respective pipe as follow:
&lt;br&gt;&lt;br&gt;# ipfw show
&lt;br&gt;00100     0         0 allow ip from any to any via lo0
&lt;br&gt;00200     0         0 deny ip from any to 127.0.0.0/8
&lt;br&gt;00300     0         0 deny ip from 127.0.0.0/8 to any
&lt;br&gt;01000     0         0 pipe 1 ip from any to any via vr0 layer2
&lt;br&gt;01100     0         0 pipe 101 ip from any to any via vr4 layer2
&lt;br&gt;65000  7089    716987 allow ip from any to any
&lt;br&gt;65535     0         0 deny ip from any to any
&lt;br&gt;&lt;br&gt;When I setup my pipes as follow:
&lt;br&gt;&lt;br&gt;# ipfw pipe 1 config bw 10Mbit delay 25 mask proto 0
&lt;br&gt;# ipfw pipe 101 config bw 10Mbit delay 25 mask proto 0
&lt;br&gt;# ipfw pipe show
&lt;br&gt;&lt;br&gt;00001:  10.000 Mbit/s   25 ms   50 sl. 0 queues (1 buckets) droptail
&lt;br&gt;burst: 0 Byte
&lt;br&gt;00101:  10.000 Mbit/s   25 ms   50 sl. 0 queues (1 buckets) droptail
&lt;br&gt;burst: 0 Byte
&lt;br&gt;&lt;br&gt;With this setup, when I try to pass traffic through the bridge with
&lt;br&gt;iperf, I obtain the desired speed: iperf reports about 9.7Mbits/sec in
&lt;br&gt;UDP mode and 9.5 in TCP mode (I copied and pasted the iperf runs at
&lt;br&gt;the end of this email).
&lt;br&gt;&lt;br&gt;The problem arise when I setup pipe 1 (the downlink) with an
&lt;br&gt;equivalent profile (I tried to simplify it as much as possible).
&lt;br&gt;&lt;br&gt;# ipfw pipe 1 config profile test.pipeconf &amp;nbsp; mask proto 0
&lt;br&gt;# ipfw pipe show
&lt;br&gt;00001: &amp;nbsp;10.000 Mbit/s &amp;nbsp; &amp;nbsp;0 ms &amp;nbsp; 50 sl. 0 queues (1 buckets) droptail
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;burst: 0 Byte
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;profile: name &amp;quot;test&amp;quot; loss 1.000000 samples 2
&lt;br&gt;00101: &amp;nbsp;10.000 Mbit/s &amp;nbsp; 25 ms &amp;nbsp; 50 sl. 0 queues (1 buckets) droptail
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;burst: 0 Byte
&lt;br&gt;&lt;br&gt;# cat test.pipeconf
&lt;br&gt;name &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;test
&lt;br&gt;bw &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;10Mbit
&lt;br&gt;loss-level &amp;nbsp;1.0
&lt;br&gt;samples &amp;nbsp; &amp;nbsp; 2
&lt;br&gt;prob &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;delay
&lt;br&gt;0.0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 25
&lt;br&gt;1.0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 25
&lt;br&gt;&lt;br&gt;The same iperf TCP tests then collapse to about 500Kbit/s with the
&lt;br&gt;same settings (copy and pasted the output of iperf bellow)
&lt;br&gt;&lt;br&gt;I can't figure out what is going on. There is no visible load on the bridge.
&lt;br&gt;I have an unmodified GENERIC kernel with the following sysctl.
&lt;br&gt;&lt;br&gt;net.link.bridge.ipfw: 1
&lt;br&gt;kern.hz: 1000
&lt;br&gt;&lt;br&gt;The bridge configuration is as follow:
&lt;br&gt;&lt;br&gt;bridge0: flags=8843&amp;lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&amp;gt; metric 0 mtu 1500
&lt;br&gt;ether 1a:1f:2e:42:74:8d
&lt;br&gt;id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
&lt;br&gt;maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
&lt;br&gt;root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
&lt;br&gt;member: vr4 flags=143&amp;lt;LEARNING,DISCOVER,AUTOEDGE,AUTOPTP&amp;gt;
&lt;br&gt;       ifmaxaddr 0 port 6 priority 128 path cost 200000
&lt;br&gt;member: vr0 flags=143&amp;lt;LEARNING,DISCOVER,AUTOEDGE,AUTOPTP&amp;gt;
&lt;br&gt;       ifmaxaddr 0 port 2 priority 128 path cost 200000
&lt;br&gt;&lt;br&gt;&lt;br&gt;iperf runs without the profile set:
&lt;br&gt;% iperf -B 10.1.0.1 -c 10.0.0.254 -t 15
&lt;br&gt;------------------------------------------------------------
&lt;br&gt;Client connecting to 10.0.0.254, TCP port 5001
&lt;br&gt;Binding to local address 10.1.0.1
&lt;br&gt;TCP window size: 16.0 KByte (default)
&lt;br&gt;------------------------------------------------------------
&lt;br&gt;[ &amp;nbsp;3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001
&lt;br&gt;[ ID] Interval &amp;nbsp; &amp;nbsp; &amp;nbsp; Transfer &amp;nbsp; &amp;nbsp; Bandwidth
&lt;br&gt;[ &amp;nbsp;3] &amp;nbsp;0.0-15.0 sec &amp;nbsp;17.0 MBytes &amp;nbsp;9.49 Mbits/sec
&lt;br&gt;&lt;br&gt;% iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 -u -b 10Mbit
&lt;br&gt;------------------------------------------------------------
&lt;br&gt;Client connecting to 10.0.0.254, UDP port 5001
&lt;br&gt;Binding to local address 10.1.0.1
&lt;br&gt;Sending 1470 byte datagrams
&lt;br&gt;UDP buffer size: &amp;nbsp; 110 KByte (default)
&lt;br&gt;------------------------------------------------------------
&lt;br&gt;[ &amp;nbsp;3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001
&lt;br&gt;[ ID] Interval &amp;nbsp; &amp;nbsp; &amp;nbsp; Transfer &amp;nbsp; &amp;nbsp; Bandwidth
&lt;br&gt;[ &amp;nbsp;3] &amp;nbsp;0.0-15.0 sec &amp;nbsp;18.8 MBytes &amp;nbsp;10.5 Mbits/sec
&lt;br&gt;[ &amp;nbsp;3] Sent 13382 datagrams
&lt;br&gt;[ &amp;nbsp;3] Server Report:
&lt;br&gt;[ &amp;nbsp;3] &amp;nbsp;0.0-15.1 sec &amp;nbsp;17.4 MBytes &amp;nbsp;9.72 Mbits/sec &amp;nbsp;0.822 ms &amp;nbsp;934/13381 (7%)
&lt;br&gt;[ &amp;nbsp;3] &amp;nbsp;0.0-15.1 sec &amp;nbsp;1 datagrams received out-of-order
&lt;br&gt;&lt;br&gt;&lt;br&gt;iperf runs with the profile set:
&lt;br&gt;% iperf -B 10.1.0.1 -c 10.0.0.254 -t 15
&lt;br&gt;------------------------------------------------------------
&lt;br&gt;Client connecting to 10.0.0.254, TCP port 5001
&lt;br&gt;Binding to local address 10.1.0.1
&lt;br&gt;TCP window size: 16.0 KByte (default)
&lt;br&gt;------------------------------------------------------------
&lt;br&gt;[ &amp;nbsp;3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001
&lt;br&gt;[ ID] Interval &amp;nbsp; &amp;nbsp; &amp;nbsp; Transfer &amp;nbsp; &amp;nbsp; Bandwidth
&lt;br&gt;[ &amp;nbsp;3] &amp;nbsp;0.0-15.7 sec &amp;nbsp; &amp;nbsp;968 KBytes &amp;nbsp; &amp;nbsp;505 Kbits/sec
&lt;br&gt;&lt;br&gt;% iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 -u -b 10Mbit
&lt;br&gt;------------------------------------------------------------
&lt;br&gt;Client connecting to 10.0.0.254, UDP port 5001
&lt;br&gt;Binding to local address 10.1.0.1
&lt;br&gt;Sending 1470 byte datagrams
&lt;br&gt;UDP buffer size: &amp;nbsp; 110 KByte (default)
&lt;br&gt;------------------------------------------------------------
&lt;br&gt;[ &amp;nbsp;3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001
&lt;br&gt;[ ID] Interval &amp;nbsp; &amp;nbsp; &amp;nbsp; Transfer &amp;nbsp; &amp;nbsp; Bandwidth
&lt;br&gt;[ &amp;nbsp;3] &amp;nbsp;0.0-15.0 sec &amp;nbsp;18.8 MBytes &amp;nbsp;10.5 Mbits/sec
&lt;br&gt;[ &amp;nbsp;3] Sent 13382 datagrams
&lt;br&gt;[ &amp;nbsp;3] Server Report:
&lt;br&gt;[ &amp;nbsp;3] &amp;nbsp;0.0-16.3 sec &amp;nbsp; &amp;nbsp;893 KBytes &amp;nbsp; &amp;nbsp;449 Kbits/sec &amp;nbsp;1.810 ms 12757/13379 (95%)
&lt;br&gt;&lt;br&gt;&lt;br&gt;Let me know what other information you would need to help me debugging this.
&lt;br&gt;In advance, thank you for your help
&lt;br&gt;&lt;br&gt;--
&lt;br&gt;Charles-Henri de Boysson
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26500647&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26500647&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Performance-issue-with-new-pipe-profile-feature-in-FreeBSD-8.0--RELEASE-tp26500647p26500647.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26498192</id>
	<title>Re: [CFR] unified rc.firewall</title>
	<published>2009-11-24T07:40:16Z</published>
	<updated>2009-11-24T07:40:16Z</updated>
	<author>
		<name>Hajimu UMEMOTO</name>
	</author>
	<content type="html">Hi,
&lt;br&gt;&lt;br&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; On Mon, 23 Nov 2009 10:27:43 -0800
&lt;br&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; Benjamin Lee &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26498192&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;ben@...&lt;/a&gt;&amp;gt; said:
&lt;br&gt;&lt;br&gt;ben&amp;gt; There is a bug in ipfw send_pkt() that prevents ipfw_tick() from
&lt;br&gt;ben&amp;gt; functioning for IPv6. &amp;nbsp;See PR kern/117234.
&lt;br&gt;&lt;br&gt;I confirmed that the patch fixed the problem. &amp;nbsp;Thank you for letting
&lt;br&gt;me know.
&lt;br&gt;&lt;br&gt;Sincerely,
&lt;br&gt;&lt;br&gt;--
&lt;br&gt;Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26498192&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;ume@...&lt;/a&gt; &amp;nbsp;ume@{,jp.}FreeBSD.org
&lt;br&gt;&lt;a href=&quot;http://www.imasy.org/~ume/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.imasy.org/~ume/&lt;/a&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26498192&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26498192&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/-CFR--unified-rc.firewall-tp26466319p26498192.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26497974</id>
	<title>Re: kern/118238: [bce] [patch] bce driver shows &quot;no carrier&quot; on Intel SBXD132 blade (based on IBM HS21)</title>
	<published>2009-11-24T07:30:04Z</published>
	<updated>2009-11-24T07:30:04Z</updated>
	<author>
		<name>Max V. Irgiznov-2</name>
	</author>
	<content type="html">The following reply was made to PR kern/118238; it has been noted by GNATS.
&lt;br&gt;&lt;br&gt;From: &amp;quot;Max V. Irgiznov&amp;quot; &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26497974&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;m.irgiznov@...&lt;/a&gt;&amp;gt;
&lt;br&gt;To: &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26497974&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;bug-followup@...&lt;/a&gt;&amp;gt;,
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26497974&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;supportsobaka@...&lt;/a&gt;&amp;gt;
&lt;br&gt;Cc: &amp;nbsp;
&lt;br&gt;Subject: Re: kern/118238: [bce] [patch] bce driver shows &amp;quot;no carrier&amp;quot; on Intel SBXD132 blade (based on IBM HS21)
&lt;br&gt;Date: Tue, 24 Nov 2009 18:09:43 +0300
&lt;br&gt;&lt;br&gt;&amp;nbsp;This bug still exist in FreeBSD 8.0-RELEASE #0: Tue Nov 24 17:24:49 UTC 2009
&lt;br&gt;&amp;nbsp;root@:/usr/obj/usr/src/sys/GENERIC &amp;nbsp;amd64
&lt;br&gt;&amp;nbsp;
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26497974&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26497974&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-kern-118238%3A--bce---patch--bce-driver-shows-%22no-carrier%22-on-Intel-SBXD132-blade-%28based-on-IBM-HS21%29-tp26497974p26497974.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26493146</id>
	<title>Re: Hangs down/up Intel NIC during creating vlan. Bug em driver ???</title>
	<published>2009-11-24T01:51:03Z</published>
	<updated>2009-11-24T01:51:03Z</updated>
	<author>
		<name>Prokofiev S.P.-3</name>
	</author>
	<content type="html">It happen on the 82573 and the 82546 depend on vlandev. To reproduce 
&lt;br&gt;this input command
&lt;br&gt;&lt;br&gt;ifconfig vlan557 create vlandev em1 vlan 557
&lt;br&gt;&lt;br&gt;&lt;br&gt;and you may see
&lt;br&gt;&lt;br&gt;Nov 23 11:35:49 ...... kernel: em1: link state changed to DOWN
&lt;br&gt;Nov 23 11:35:49 ...... kernel: vlan557: link state changed to DOWN
&lt;br&gt;Nov 23 11:35:52 ...... kernel: em1: link state changed to UP
&lt;br&gt;Nov 23 11:35:52 ...... kernel: vlan557: link state changed to UP
&lt;br&gt;Nov 23 11:36:09 ...... kernel: em1: link state changed to DOWN
&lt;br&gt;Nov 23 11:36:13 ...... kernel: em1: link state changed to UP
&lt;br&gt;&lt;br&gt;&lt;br&gt;For example:
&lt;br&gt;em0: flags=8843&amp;lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&amp;gt; metric 0 mtu 1500
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; options=9b&amp;lt;RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM&amp;gt;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ether 00:1b:21:06:43:1a
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; media: Ethernet autoselect (1000baseT &amp;lt;full-duplex&amp;gt;)
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; status: active
&lt;br&gt;em1: flags=8843&amp;lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&amp;gt; metric 0 mtu 1500
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; options=9b&amp;lt;RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM&amp;gt;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ether 00:1b:21:06:43:1b
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; media: Ethernet autoselect
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; status: no carrier
&lt;br&gt;....
&lt;br&gt;vlan2: flags=8843&amp;lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&amp;gt; metric 0 mtu 1500
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; options=3&amp;lt;RXCSUM,TXCSUM&amp;gt;
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ether 00:1b:21:06:43:1a
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet 10.25.224.23 netmask 0xfffffff0 broadcast 10.25.224.31
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; media: Ethernet autoselect (1000baseT &amp;lt;full-duplex&amp;gt;)
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; status: active
&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; vlan: 2 parent interface: em0
&lt;br&gt;&lt;br&gt;input command
&lt;br&gt;&lt;br&gt;ifconfig vlan557 create vlandev em0 vlan 557
&lt;br&gt;&lt;br&gt;in /var/log/messages:
&lt;br&gt;Nov 24 10:59:37 ....... kernel: em0: link state changed to DOWN
&lt;br&gt;Nov 24 10:59:37 ....... kernel: vlan2: link state changed to DOWN
&lt;br&gt;Nov 24 10:59:37 ....... kernel: vlan557: link state changed to DOWN
&lt;br&gt;Nov 24 10:59:41 ....... kernel: em0: link state changed to UP
&lt;br&gt;Nov 24 10:59:41 ....... kernel: vlan2: link state changed to UP
&lt;br&gt;Nov 24 10:59:41 ....... kernel: vlan557: link state changed to UP
&lt;br&gt;&lt;br&gt;On custom kernel ssh client lost connect and reconnect failure until 
&lt;br&gt;reboot.
&lt;br&gt;This is tcpdump on fail server (10.25.224.23):
&lt;br&gt;11:13:23.559741 IP 10.25.224.21.58222 &amp;gt; 10.25.224.23.22: Flags [S], seq 
&lt;br&gt;1981788951, win 65535, options [mss 1460,nop,wscale 8,sackOK,TS val
&lt;br&gt;&amp;nbsp;3107838092 ecr 0], length 0
&lt;br&gt;11:13:23.559771 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,TS val 1953228413 ecr 3107838092], length 0
&lt;br&gt;11:13:26.559555 IP 10.25.224.21.58222 &amp;gt; 10.25.224.23.22: Flags [S], seq 
&lt;br&gt;1981788951, win 65535, options [mss 1460,nop,wscale 8,sackOK,TS val
&lt;br&gt;&amp;nbsp;3107841092 ecr 0], length 0
&lt;br&gt;11:13:26.559579 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,TS val 1953228413 ecr 3107841092], length 0
&lt;br&gt;11:13:29.560220 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,TS val 1953228413 ecr 3107841092], length 0
&lt;br&gt;11:13:29.759620 IP 10.25.224.21.58222 &amp;gt; 10.25.224.23.22: Flags [S], seq 
&lt;br&gt;1981788951, win 65535, options [mss 1460,nop,wscale 8,sackOK,TS val
&lt;br&gt;&amp;nbsp;3107844292 ecr 0], length 
&lt;br&gt;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&lt;br&gt;11:13:29.759641 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,TS val 1953228413 ecr 3107844292], length 
&lt;br&gt;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&lt;br&gt;11:13:32.760214 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,TS val 1953228413 ecr 3107844292], length 
&lt;br&gt;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&lt;br&gt;11:13:32.959809 IP 10.25.224.21.58222 &amp;gt; 10.25.224.23.22: Flags [S], seq 
&lt;br&gt;1981788951, win 65535, options [mss 1460,sackOK,eol], length 0
&lt;br&gt;11:13:32.959829 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,eol], length 0
&lt;br&gt;11:13:35.960214 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,eol], length 
&lt;br&gt;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;
&lt;br&gt;&lt;br&gt;11:13:36.159874 IP 10.25.224.21.58222 &amp;gt; 10.25.224.23.22: Flags [S], seq 
&lt;br&gt;1981788951, win 65535, options [mss 1460,sackOK,eol], length 0
&lt;br&gt;11:13:36.159892 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,eol], length 0
&lt;br&gt;11:13:39.160211 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,eol], length 0
&lt;br&gt;11:13:39.359940 IP 10.25.224.21.58222 &amp;gt; 10.25.224.23.22: Flags [S], seq 
&lt;br&gt;1981788951, win 65535, options [mss 1460,sackOK,eol], length 0
&lt;br&gt;11:13:39.359956 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,eol], length 
&lt;br&gt;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;
&lt;br&gt;&lt;br&gt;11:13:42.360212 IP 10.25.224.23.22 &amp;gt; 10.25.224.21.58222: Flags [S.], seq 
&lt;br&gt;2713869415, ack 1981788952, win 65535, options [mss 1460,nop,wscal
&lt;br&gt;e 3,sackOK,eol], length 0
&lt;br&gt;&lt;br&gt;But on client I see only requests without reply.
&lt;br&gt;On GENERIC kernel reconnect is success. But down/up interface is not 
&lt;br&gt;right behavior.
&lt;br&gt;&lt;br&gt;&lt;br&gt;Jack Vogel wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; Custom kernel, well, does it happen on the installed GENERIC kernel, and
&lt;br&gt;&amp;gt; what is needed
&lt;br&gt;&amp;gt; to reproduce this, just down/up the interface? And are you saying that it
&lt;br&gt;&amp;gt; will happen on
&lt;br&gt;&amp;gt; either the 82573 or the 82546 or just one of them??
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Would be nice if this stuff could be discovered earlier :( In any case I
&lt;br&gt;&amp;gt; will look into it, there
&lt;br&gt;&amp;gt; is another reported problems with em and vlans as well.
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; Jack
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; 2009/11/23 Prokofiev S.P. &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26493146&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;proks@...&lt;/a&gt;&amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; &amp;nbsp; 
&lt;br&gt;&amp;gt;&amp;gt; Hi ALL !
&lt;br&gt;&amp;gt;&amp;gt; I have several servers with FreeBSD 8.0-PRERELEASE on SuperMicro with
&lt;br&gt;&amp;gt;&amp;gt; different Intel NICs. When I create new vlan on em interface
&lt;br&gt;&amp;gt;&amp;gt; ( ifconfig vlan557 create vlandev em0 vlan 557),
&lt;br&gt;&amp;gt;&amp;gt; it hangs down and then up and server becomes inaccessible by ssh, but reply
&lt;br&gt;&amp;gt;&amp;gt; on icmp request.
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; on amd64, custom kernel:
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; em0@pci0:13:0:0: &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;class=0x020000 card=0x108c15d9 chip=0x108c8086
&lt;br&gt;&amp;gt;&amp;gt; rev=0x03 hdr=0x00
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; vendor &amp;nbsp; &amp;nbsp; = 'Intel Corporation'
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; device &amp;nbsp; &amp;nbsp; = 'Intel Corporation 82573E Gigabit Ethernet Controller
&lt;br&gt;&amp;gt;&amp;gt; (Copper) (82573E)'
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; class &amp;nbsp; &amp;nbsp; &amp;nbsp;= network
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; subclass &amp;nbsp; = ethernet
&lt;br&gt;&amp;gt;&amp;gt; em1@pci0:14:0:0: &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;class=0x020000 card=0x109a15d9 chip=0x109a8086
&lt;br&gt;&amp;gt;&amp;gt; rev=0x00 hdr=0x00
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; vendor &amp;nbsp; &amp;nbsp; = 'Intel Corporation'
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; device &amp;nbsp; &amp;nbsp; = 'Intel PRO/1000 PL Network Adaptor (82573L)'
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; class &amp;nbsp; &amp;nbsp; &amp;nbsp;= network
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; subclass &amp;nbsp; = ethernet
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; on i386, GENERIC kernel:
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; em0@pci0:2:1:0: class=0x020000 card=0x11798086 chip=0x10798086 rev=0x03
&lt;br&gt;&amp;gt;&amp;gt; hdr=0x00
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; vendor &amp;nbsp; &amp;nbsp; = 'Intel Corporation'
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; device &amp;nbsp; &amp;nbsp; = 'Dual Port Gigabit Ethernet Controller (82546EB)'
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; class &amp;nbsp; &amp;nbsp; &amp;nbsp;= network
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; subclass &amp;nbsp; = ethernet
&lt;br&gt;&amp;gt;&amp;gt; em1@pci0:2:1:1: class=0x020000 card=0x11798086 chip=0x10798086 rev=0x03
&lt;br&gt;&amp;gt;&amp;gt; hdr=0x00
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; vendor &amp;nbsp; &amp;nbsp; = 'Intel Corporation'
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; device &amp;nbsp; &amp;nbsp; = 'Dual Port Gigabit Ethernet Controller (82546EB)'
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; class &amp;nbsp; &amp;nbsp; &amp;nbsp;= network
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; subclass &amp;nbsp; = ethernet
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; /var/log/messages:
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; Nov 23 11:35:49 freebsd kernel: em1: link state changed to DOWN
&lt;br&gt;&amp;gt;&amp;gt; Nov 23 11:35:49 freebsd kernel: vlan557: link state changed to DOWN
&lt;br&gt;&amp;gt;&amp;gt; Nov 23 11:35:52 freebsd kernel: em1: link state changed to UP
&lt;br&gt;&amp;gt;&amp;gt; Nov 23 11:35:52 freebsd kernel: vlan557: link state changed to UP
&lt;br&gt;&amp;gt;&amp;gt; Nov 23 11:36:09 freebsd kernel: em1: link state changed to DOWN
&lt;br&gt;&amp;gt;&amp;gt; Nov 23 11:36:13 freebsd kernel: em1: link state changed to UP
&lt;br&gt;&amp;gt;&amp;gt; _______________________________________________
&lt;br&gt;&amp;gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26493146&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;gt;&amp;gt; &lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;&amp;gt;&amp;gt; To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26493146&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; &amp;nbsp; &amp;nbsp; 
&lt;br&gt;&amp;gt; _______________________________________________
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26493146&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;&amp;gt; To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26493146&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt;
&lt;br&gt;&amp;gt; &amp;nbsp; 
&lt;/div&gt;&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26493146&amp;i=5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26493146&amp;i=6&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Hangs-down-up-Intel-NIC-during-creating-vlan.-Bug-em-driver-----tp26479907p26493146.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26489614</id>
	<title>Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock</title>
	<published>2009-11-23T18:30:06Z</published>
	<updated>2009-11-23T18:30:06Z</updated>
	<author>
		<name>Benjamin Kaduk-2</name>
	</author>
	<content type="html">The following reply was made to PR kern/140036; it has been noted by GNATS.
&lt;br&gt;&lt;br&gt;From: Benjamin Kaduk &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26489614&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;kaduk@...&lt;/a&gt;&amp;gt;
&lt;br&gt;To: Bernhard Schmidt &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26489614&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;bschmidt@...&lt;/a&gt;&amp;gt;
&lt;br&gt;Cc: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26489614&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;bug-followup@...&lt;/a&gt;
&lt;br&gt;Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock
&lt;br&gt;&amp;nbsp;and iwn0 softc lock
&lt;br&gt;Date: Mon, 23 Nov 2009 21:27:15 -0500 (EST)
&lt;br&gt;&lt;br&gt;&amp;nbsp;On Mon, 23 Nov 2009, Benjamin Kaduk wrote:
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;&amp;gt; On Sun, 22 Nov 2009, Bernhard Schmidt wrote:
&lt;br&gt;&amp;nbsp;&amp;gt;&amp;gt; 
&lt;br&gt;&amp;nbsp;&amp;gt;&amp;gt; Can you verify that the LOR is gone with the latest checkout of my 
&lt;br&gt;&amp;nbsp;&amp;gt;&amp;gt; repository?
&lt;br&gt;&amp;nbsp;&amp;gt;&amp;gt; Compile instructions:
&lt;br&gt;&amp;nbsp;&amp;gt;&amp;gt; &lt;a href=&quot;http://forums.freebsd.org/showpost.php?p=47627&amp;postcount=16&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://forums.freebsd.org/showpost.php?p=47627&amp;postcount=16&lt;/a&gt;&lt;br&gt;&amp;nbsp;&amp;gt;
&lt;br&gt;&amp;nbsp;&amp;gt; I upgraded to today's current (which picked up a number of probably-unrelated 
&lt;br&gt;&amp;nbsp;&amp;gt; changes), and then installed the driver from
&lt;br&gt;&amp;nbsp;&amp;gt; your tree on top of it.
&lt;br&gt;&amp;nbsp;&amp;gt; No LOR on boot, and I'll let you know if I see any lockups.
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;I got a &amp;quot;lockup&amp;quot; (no idea what actually was happening) while in X tonight; 
&lt;br&gt;&amp;nbsp;nothing useful is in the logs.
&lt;br&gt;&amp;nbsp;I'm not even sure if I can blame iwn for it ...
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;I did get a LOR after turning on the hardware wireless switch, though:
&lt;br&gt;&amp;nbsp;iwn0: RF switch: radio enabled
&lt;br&gt;&amp;nbsp;wlan0: link state changed to UP
&lt;br&gt;&amp;nbsp;lock order reversal:
&lt;br&gt;&amp;nbsp; &amp;nbsp;1st 0xffffff800033d018 iwn0_com_lock (iwn0_com_lock) @ 
&lt;br&gt;&amp;nbsp;/usr/devel/iwn/freebsd/sys/modules/iwn/../../dev/iwn/if_iwn.c:3280
&lt;br&gt;&amp;nbsp; &amp;nbsp;2nd 0xffffff8000309010 iwn0 (network driver) @ 
&lt;br&gt;&amp;nbsp;/usr/devel/iwn/freebsd/sys/modules/iwn/../../dev/iwn/if_iwn.c:3289
&lt;br&gt;&amp;nbsp;KDB: stack backtrace:
&lt;br&gt;&amp;nbsp;db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
&lt;br&gt;&amp;nbsp;_witness_debugger() at _witness_debugger+0x2e
&lt;br&gt;&amp;nbsp;witness_checkorder() at witness_checkorder+0x81e
&lt;br&gt;&amp;nbsp;_mtx_lock_flags() at _mtx_lock_flags+0x78
&lt;br&gt;&amp;nbsp;iwn_start() at iwn_start+0x35
&lt;br&gt;&amp;nbsp;if_transmit() at if_transmit+0xd6
&lt;br&gt;&amp;nbsp;ieee80211_start() at ieee80211_start+0x3f4
&lt;br&gt;&amp;nbsp;scan_task() at scan_task+0x4c7
&lt;br&gt;&amp;nbsp;taskqueue_run() at taskqueue_run+0x91
&lt;br&gt;&amp;nbsp;taskqueue_thread_loop() at taskqueue_thread_loop+0x3f
&lt;br&gt;&amp;nbsp;fork_exit() at fork_exit+0x12a
&lt;br&gt;&amp;nbsp;fork_trampoline() at fork_trampoline+0xe
&lt;br&gt;&amp;nbsp;--- trap 0, rip = 0, rsp = 0xffffff80001ffd30, rbp = 0 ---
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;I don't think I'll have time to look at it particularly soon, though.
&lt;br&gt;&amp;nbsp;
&lt;br&gt;&amp;nbsp;-Ben Kaduk
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26489614&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26489614&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-kern-140036%3A--iwn---lor--lock-order-reversal-with-iwn0_com_lock-and-iwn0-softc-lock-tp26473675p26489614.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-26484725</id>
	<title>Re: [CFR] unified rc.firewall</title>
	<published>2009-11-23T11:52:49Z</published>
	<updated>2009-11-23T11:52:49Z</updated>
	<author>
		<name>Kevin Oberman</name>
	</author>
	<content type="html">&lt;div class='shrinkable-quote'&gt;&amp;gt; From: John Baldwin &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26484725&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;jhb@...&lt;/a&gt;&amp;gt;
&lt;br&gt;&amp;gt; Date: Mon, 23 Nov 2009 12:55:25 -0500
&lt;br&gt;&amp;gt; Sender: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26484725&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;owner-freebsd-current@...&lt;/a&gt;
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; On Monday 23 November 2009 12:27:23 pm Hajimu UMEMOTO wrote:
&lt;br&gt;&amp;gt; &amp;gt; Hi,
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; &amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; On Mon, 23 Nov 2009 10:56:14 -0500
&lt;br&gt;&amp;gt; &amp;gt; &amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; John Baldwin &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26484725&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;jhb@...&lt;/a&gt;&amp;gt; said:
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; @@ -178,6 +212,16 @@
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; # Allow any traffic to or from my own net.
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ${fwcmd} add pass all from me to ${net}
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ${fwcmd} add pass all from ${net} to me
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; if [ -n &amp;quot;$net6&amp;quot; ]; then
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ${fwcmd} add pass ip6 from me6 to ${net6}
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ${fwcmd} add pass ip6 from ${net6} to me6
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; fi
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; +
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; if [ -n &amp;quot;$net6&amp;quot; ]; then
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; # Allow any link-local multicast traffic
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ${fwcmd} add pass ip6 from fe80::/10 to ff02::/16
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ${fwcmd} add pass ip6 from ${net6} to ff02::/16
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; fi
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; Any reason to not use 'all' here rather than 'ip6' to match the earlier IPv4
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; rules?
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; Thank you for the review.
&lt;br&gt;&amp;gt; &amp;gt; The rule is only applicable for IPv6. &amp;nbsp;Rather, I prefer to use 'ip4'
&lt;br&gt;&amp;gt; &amp;gt; explicitly over 'all' or 'ip' here. &amp;nbsp;However, changing 'all' to 'ip4'
&lt;br&gt;&amp;gt; &amp;gt; makes the diff complex. &amp;nbsp;So, I keep 'all' as is.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Hmm, however, using 'all' will work, and while in this case the typing is the
&lt;br&gt;&amp;gt; same I find it easier to read 'add pass tcp &amp;lt;...&amp;gt;' vs
&lt;br&gt;&amp;gt; 'add pass ip &amp;lt;...&amp;gt; proto tcp'. &amp;nbsp;I do think they should be consistent
&lt;br&gt;&amp;gt; regardless.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; # For services permitted below.
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ${fwcmd} add pass tcp &amp;nbsp;from me to any established
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; if [ $ipv6_available -eq 0 ]; then
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ${fwcmd} add pass ip6 from any to any proto tcp established
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; + &amp;nbsp; &amp;nbsp; &amp;nbsp; fi
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; I think this extra rule here isn't needed at all as the first rule should
&lt;br&gt;&amp;gt; &amp;gt; jhb&amp;gt; already match all of those packets.
&lt;br&gt;&amp;gt; &amp;gt; 
&lt;br&gt;&amp;gt; &amp;gt; WORKSTATION type rule is fully dynamic. &amp;nbsp;However, I saw it doesn't
&lt;br&gt;&amp;gt; &amp;gt; work for IPv6 as expected. &amp;nbsp;SSH connection stalls after some period.
&lt;br&gt;&amp;gt; &amp;gt; I suspect keepalive timer doesn't work well for IPv6.
&lt;br&gt;&amp;gt; &amp;gt; So, I changed to use traditional setup/established rule for TCP/IPv6.
&lt;br&gt;&amp;gt; &amp;gt; Further, 'me' doesn't match to IPv6 address.
&lt;/div&gt;&lt;br&gt;FWIW, I have been seeing this since the last update of OpenSSH. I never
&lt;br&gt;saw it until then. It's a real pain and I'd love to see it fixed. Right
&lt;br&gt;now I'm forced to use IPv4 for the jobs that I tunnel in SSH.
&lt;br&gt;-- 
&lt;br&gt;R. Kevin Oberman, Network Engineer
&lt;br&gt;Energy Sciences Network (ESnet)
&lt;br&gt;Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
&lt;br&gt;E-mail: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26484725&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;oberman@...&lt;/a&gt;			Phone: +1 510 486-8634
&lt;br&gt;Key fingerprint:059B 2DDF 031C 9BA3 14A4 &amp;nbsp;EADA 927D EBB3 987B 3751
&lt;br&gt;_______________________________________________
&lt;br&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26484725&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net@...&lt;/a&gt; mailing list
&lt;br&gt;&lt;a href=&quot;http://lists.freebsd.org/mailman/listinfo/freebsd-net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.freebsd.org/mailman/listinfo/freebsd-net&lt;/a&gt;&lt;br&gt;To unsubscribe, send any mail to &amp;quot;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=26484725&amp;i=5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;freebsd-net-unsubscribe@...&lt;/a&gt;&amp;quot;
&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/-CFR--unified-rc.firewall-tp26466319p26484725.html" />
</entry>

</feed>
