Re: kern/141843: [em] [vlan] Intel txcsum and assigned vlan invoke wrong dst MAC in TCP packets
The following reply was made to PR kern/141843; it has been noted by GNATS. From: Dennis Yusupoff To: pyu...@gmail.com, bug-follo...@freebsd.org Cc: Subject: Re: kern/141843: [em] [vlan] Intel txcsum and assigned vlan invoke wrong dst MAC in TCP packets Date: Mon, 11 Jan 2010 12:20:46 +0300 30.12.2009 23:20, Pyun YongHyeon пиÑеÑ: > > Sorry, that wasn't expected one. From your explanation above I > think I found a possible cause of checksum offload issue of em(4). > The issue was not I initially thought though. It seems the checksum > offload context configured in em(4) was incorrectly reused even if > a frame requires a new context as IP/TCP header length, checksum > offload offset was changed. Setting up new context put more burden > to hardware such that em(4) used to avoid new context setup as > possible as it can. However it seems em(4) failed to compare all > required field in the checksum offload context. Would you try the > following patch again? > > http://people.freebsd.org/~yongari/em.csum_tso.20091230.patch Gotcha! It works! --- With best regards, Dennis Yusupoff, network engineer of Smart-Telecom ISP Russia, Saint-Petersburg ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/142518: [em] [lagg] Problem on 8.0-STABLE with em and lagg
Old Synopsis: Problem on 8.0-STABLE with em and lagg New Synopsis: [em] [lagg] Problem on 8.0-STABLE with em and lagg Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 11 09:44:54 UTC 2010 Responsible-Changed-Why: This does not sound i386-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=142518 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Current problem reports assigned to freebsd-net@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o bin/142547 netwpa_supplicant(8) drops connection on key renegotiatio o kern/142518 net[em] [lagg] Problem on 8.0-STABLE with em and lagg o kern/142392 net[panic] rtadvd(8) triggers kernel panic when started f o kern/142391 net[panic] bsnmpd(8) triggers kernel panic when a second o kern/142019 net[em] em needs "ifconfig em0 down up" when link was gon o kern/142018 net[iwi] [patch] Possibly wrong interpretation of beacon- o kern/141861 net[wi] data garbled with WEP and wi(4) with Prism 2.5 o kern/141843 net[em] [vlan] Intel txcsum and assigned vlan invoke wron o kern/141777 net[rum] [patch] Support usbdevs / rum(4) for Buffalo WLI f kern/141741 netEtherlink III NIC won't work after upgrade to FBSD 8, o kern/141720 net[sctp] [lor] [hang] sctp-create vs. sctp-it causes sys o kern/141698 net[sctp] [panic] Own lock on stcb at return from input o kern/141697 net[sctp] [panic] lock (sleep mutex) sctp-tcb not locked o kern/141696 net[rum] [panic] rum(4)+ vimage = kernel panic o kern/141695 net[sctp] [panic] kernel page fault with non-sleepable lo o kern/141646 net[em] em(4) + lagg(4) + vlan(4) generates ISL-tagged fr o kern/141314 netNetwork Performance has decreased by 30% [regression] o kern/141285 net[em] hangs down/up intel nic during creating vlan o kern/141023 net[carp] CARP arp replays with wrong src mac o kern/140970 net[bce] The two NetXtreme II BCM5709S NICs on our HP Bl4 o kern/140796 net[ath] [panic] privileged instruction fault o kern/140778 net[em] randomly panic in vlan/em o kern/140742 netrum(4) Two asus-WL167G adapters cannot talk to each ot o kern/140728 net[em] [patch] Fast irq registration in em driver o kern/140684 net[bce] Broadcom NetXtreme II BCM5709 1000Base-T - fail o kern/140647 net[em] [patch] e1000 driver does not correctly handle mu o kern/140634 net[vlan] destroying if_lagg interface with if_vlan membe o kern/140619 net[ifnet] [patch] refine obsolete if_var.h comments desc s kern/140597 net[request] implement Lost Retransmission Detection o kern/140567 net[ath] [patch] ath is not worked on my notebook PC o kern/140564 net[wpi] Problem with Intel(R) PRO/Wireless 3945ABG o kern/140346 net[wlan] High bandwidth use causes loss of wlan connecti o kern/140326 net[em] em0: watchdog timeout when communicating to windo o kern/140245 net[ath] [panic] Kernel panic during network activity on o kern/140142 net[ip6] [panic] FreeBSD 7.2-amd64 panic w/IPv6 o kern/140066 net[bwi] install report for 8.0 RC 2 (multiple problems) o kern/140051 net[bce] [arp] ARP not sent through Bridge Firewall with o kern/140036 net[iwn] [lor] lock order reversal with iwn0_com_lock and o kern/139761 net[bce] bce driver on IBM HS22 [No PHY found on Child MI o kern/139565 net[ipfilter] ipfilter ioctl SIOCDELST broken o kern/139387 net[ipsec] Wrong lenth of PF_KEY messages in promiscuous o bin/139346 net[patch] arp(8) add option to remove static entries lis o kern/139268 net[if_bridge] [patch] allow if_bridge to forward just VL o kern/139204 net[arp] DHCP server replies rejected, ARP entry lost bef o kern/139162 net[fwip] [panic] 8.0-RC1 panics if using IP over firewir o kern/139117 net[lagg] + wlan boot timing (EBUSY) o kern/139079 net[wpi] Failure to attach wpi(4) o kern/139058 net[ipfilter] mbuf cluster leak on FreeBSD 7.2 o kern/138999 net[libc] lighttpd/php-cgi with freebsd sendfile(2) enabl o kern/138850 net[dummynet] dummynet doesn't work correctly on a bridge o kern/138782 net[panic] sbflush_internal: cc 0 || mb 0xff004127b00 o kern/138739 net[wpi] wpi(4) does not work very well under 8.0-BETA4 o kern/138694 net[bge] FreeBSD 6.3 release does not recognize Broadcom o amd64/138688 net[rum] possibly broken on 8 Beta 4 amd64: able to wpa a o kern/138678 net[lo] FreeBSD does not assign linklocal address to loop f kern/138666 net[multicast] [panic] not working multicast through igmp o kern/138660 net[igb] igb driver troubles in 8.0-BETA4 o kern/138652 net[tcp] TCP window scaling value calculated incorrectly? o kern/138620 net[lagg] [patch] lagg port bpf-writes blocked o kern/138427 net
Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock
To follow-up after a fairly long hiatus: I had been running Bernhard's driver from his svn repository for a while with no LORs. Over the weekend, I updated past FreeBSD r201882 to pick up Rui's big update from r201209 as well as the firmware error fix in r201882. I do not see the LOR anymore (and I had a rather repeatable test case), so I think that this PR should be closed. I didn't have a reliable way to reproduce the firmware error, though, so no data if that is fixed for me, too. -Ben Kaduk ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock
The following reply was made to PR kern/140036; it has been noted by GNATS. From: Benjamin Kaduk To: bug-follo...@freebsd.org Cc: Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock Date: Mon, 11 Jan 2010 17:51:17 -0500 (EST) Helps if I complete the domain name ... -- Forwarded message -- Date: Mon, 11 Jan 2010 16:53:22 -0500 (EST) From: Benjamin Kaduk To: bug-follo...@mit.edu Cc: freebsd-net@freebsd.org Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock To follow-up after a fairly long hiatus: I had been running Bernhard's driver from his svn repository for a while with no LORs. Over the weekend, I updated past FreeBSD r201882 to pick up Rui's big update from r201209 as well as the firmware error fix in r201882. I do not see the LOR anymore (and I had a rather repeatable test case), so I think that this PR should be closed. I didn't have a reliable way to reproduce the firmware error, though, so no data if that is fixed for me, too. -Ben Kaduk ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: freebsd for Sun Fire X4250
On Mon, 11 Jan 2010, Sam Wun wrote: > This server is built with Xeon cpu processor, Intel based. > Can FreeBSD 8+ fully compatible with this server like those ordinary > Intel i386 machine? Although it's hard to say (the Sun website doesn't realy give enough spec details), I'd be surprised if it doesn't work. FreeBSD runs very nicely on every Intel- and amd64-based Sun machine I've tried it on. You'll almost certainly want to use the FreeBSD amd64 release rather than i386, and I'd probably recommend 8.0-RELEASE, although 7.2 should work fine. By the way, this is the wrong list for questions like this: if you have any others, you're probably best off directing them to freebsd-questi...@freebsd.org Gavin ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
ng_patch node
Hi,
I've written netgraph node able to modify arbitrary (8|16|32)-bit
unsigned integer in passing packets. Node applies one of =,+,-,&,| and
^ operations to number at given offset.
Modification applied to each packet received on "in" hook. If "out"
hook is connected - resulting packets passed on it, otherwise -
returned back on "in" (for more easy use with ng_ipfw). Packets
received on "out" hook passed on "in" unmodified.
Node supports two control messages: "getconfig" and "setconfig".
Configuration represented in next structure:
struct ng_patch_config {
uint32_tvalue; /* argument passed to requested operation */
uint32_toffset; /* offset in bytes */
uint32_tlength; /* 1,2 or 4 bytes */
uint32_tmode; /* operation code: 1 - "=", 2 - "+", 3 -
"-", 4 - "&", 5 - "|", 6 - "^" */
};
Same names used in ASCII representation.
I wanted to make ipfw able to modify TTL and ToS fields in IP packets,
but after some generalization idea looked like described above.
Next patch made against 8-STABLE r200201
Index: modules/netgraph/patch/Makefile
===
--- modules/netgraph/patch/Makefile (revision 0)
+++ modules/netgraph/patch/Makefile (revision 0)
@@ -0,0 +1,6 @@
+# $FreeBSD$
+
+KMOD= ng_patch
+SRCS= ng_patch.c
+
+.include
Index: netgraph/ng_patch.c
===
--- netgraph/ng_patch.c (revision 0)
+++ netgraph/ng_patch.c (revision 0)
@@ -0,0 +1,393 @@
+/*
+ * ng_patch.c
+ */
+
+/*-
+ * Copyright (C) 2010 by Maxim Ignatenko
+ * All rights reserved. *
+ * *
+ * Redistribution and use in source and binary forms, with or without*
+ *modification, are permitted provided that the following conditions *
+ *are met: *
+ * * Redistributions of source code must retain the above copyright*
+ * notice, this list of conditions and the following disclaimer. *
+ * * Redistributions in binary form must reproduce the above copyright *
+ * notice, this list of conditions and the following disclaimer in *
+ * the documentation and/or other materials provided with the*
+ * distribution. *
+ * *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS *
+ * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT *
+ * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR *
+ * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT *
+ * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, *
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT *
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, *
+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY *
+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT *
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE *
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. *
+ *
+ * Author: Maxim Ignatenko
+ *
+ * $FreeBSD$
+ */
+
+#include
+#include
+#include
+#include
+#include
+#include
+
+#include
+#include
+#include
+#include
+
+static ng_constructor_tng_patch_constructor;
+static ng_rcvmsg_t ng_patch_rcvmsg;
+static ng_shutdown_t ng_patch_shutdown;
+static ng_newhook_tng_patch_newhook;
+static ng_rcvdata_tng_patch_rcvdata;
+static ng_disconnect_t ng_patch_disconnect;
+
+/* Parse type for struct ngpatchstat */
+static const struct ng_parse_struct_field ng_patch_config_type_fields[]
+ = NG_PATCH_CONFIG_TYPE_INFO;
+static const struct ng_parse_type ng_patch_config_type = {
+ &ng_parse_struct_type,
+ &ng_patch_config_type_fields
+};
+
+/* List of commands and how to convert arguments to/from ASCII */
+static const struct ng_cmdlist ng_patch_cmdlist[] = {
+ {
+ NGM_PATCH_COOKIE,
+ NGM_PATCH_GETCONFIG,
+ "getconfig",
+ NULL,
+ &ng_patch_config_type,
+ },
+ {
+ NGM_PATCH_COOKIE,
+ NGM_PATCH_SETCONFIG,
+ "setconfig",
+ &ng_patch_config_type,
+ NULL
+ },
+ { 0 }
+};
+
+/* Netgraph node type descriptor */
+static struct ng_type typestruct = {
+ .version = NG_ABI_VERSION,
+ .name = NG_PATCH_NODE_TYPE,
+ .constructor = ng_patch_constructor,
+ .rcvmsg = ng_patch_rcvmsg,
+ .shutdown = ng_patch_shutdown,
+ .newhook = ng_patch_newhook,
+ .rcvdata = ng_patch_rcvdata,
+ .disconnect = ng_patch_disc
Re: ng_patch node
Maxim Ignatenko wrote:
Hi,
I've written netgraph node able to modify arbitrary (8|16|32)-bit
unsigned integer in passing packets. Node applies one of =,+,-,&,| and
^ operations to number at given offset.
Modification applied to each packet received on "in" hook. If "out"
hook is connected - resulting packets passed on it, otherwise -
returned back on "in" (for more easy use with ng_ipfw). Packets
received on "out" hook passed on "in" unmodified.
Node supports two control messages: "getconfig" and "setconfig".
Configuration represented in next structure:
struct ng_patch_config {
uint32_tvalue; /* argument passed to requested operation */
uint32_toffset; /* offset in bytes */
uint32_tlength; /* 1,2 or 4 bytes */
uint32_tmode; /* operation code: 1 - "=", 2 - "+", 3 -
"-", 4 - "&", 5 - "|", 6 - "^" */
};
Same names used in ASCII representation.
I wanted to make ipfw able to modify TTL and ToS fields in IP packets,
but after some generalization idea looked like described above.
I like it :-)
if you can provide a short man page, I can commit it for you.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ng_patch node
2010/1/12 Julian Elischer :
> Maxim Ignatenko wrote:
>>
>> Hi,
>> I've written netgraph node able to modify arbitrary (8|16|32)-bit
>> unsigned integer in passing packets. Node applies one of =,+,-,&,| and
>> ^ operations to number at given offset.
>> Modification applied to each packet received on "in" hook. If "out"
>> hook is connected - resulting packets passed on it, otherwise -
>> returned back on "in" (for more easy use with ng_ipfw). Packets
>> received on "out" hook passed on "in" unmodified.
>> Node supports two control messages: "getconfig" and "setconfig".
>> Configuration represented in next structure:
>> struct ng_patch_config {
>> uint32_t value; /* argument passed to requested operation */
>> uint32_t offset; /* offset in bytes */
>> uint32_t length; /* 1,2 or 4 bytes */
>> uint32_t mode; /* operation code: 1 - "=", 2 - "+", 3 -
>> "-", 4 - "&", 5 - "|", 6 - "^" */
>> };
>> Same names used in ASCII representation.
>>
>> I wanted to make ipfw able to modify TTL and ToS fields in IP packets,
>> but after some generalization idea looked like described above.
>
>
> I like it :-)
> if you can provide a short man page, I can commit it for you.
>
I'll try to do this in few days, thanks :)
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: freebsd for Sun Fire X4250
Hi Gavin, The reason I want to stick with i386 is because about few years ago when I tried AMD release of FreeBSD, it didn't have the same level of proficiency as i386 release of FreeBSD - packagThat was my impression at that time. I hope it has changed in this years. Is there any major installation difference between AMD (64) and i386 release of FreeBSD (8.0)? Thank you for your answers. Sam On Tue, Jan 12, 2010 at 10:05 AM, Gavin Atkinson wrote: > On Mon, 11 Jan 2010, Sam Wun wrote: >> This server is built with Xeon cpu processor, Intel based. >> Can FreeBSD 8+ fully compatible with this server like those ordinary >> Intel i386 machine? > > Although it's hard to say (the Sun website doesn't realy give enough spec > details), I'd be surprised if it doesn't work. FreeBSD runs very nicely > on every Intel- and amd64-based Sun machine I've tried it on. > > You'll almost certainly want to use the FreeBSD amd64 release rather than > i386, and I'd probably recommend 8.0-RELEASE, although 7.2 should work > fine. > > By the way, this is the wrong list for questions like this: if you have > any others, you're probably best off directing them to > freebsd-questi...@freebsd.org > > Gavin > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/134079: [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8.0)
The following reply was made to PR kern/134079; it has been noted by GNATS. From: Jaz To: bug-follo...@freebsd.org, g.zhengm...@gmail.com Cc: Subject: Re: kern/134079: [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8.0) Date: Tue, 12 Jan 2010 11:32:22 +1100 I have the same problem since upgrading from 7.2 to 8.0. I have a PCI Intel 1000 card. Perhaps someone could make a patch that does what Korba has done? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/134079: [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8.0)
On Mon, Jan 11, 2010 at 7:10 PM, Jaz wrote: > The following reply was made to PR kern/134079; it has been noted by GNATS. > > From: Jaz > To: bug-follo...@freebsd.org, g.zhengm...@gmail.com > Cc: > Subject: Re: kern/134079: [em] "em0: Invalid MAC address" in FreeBSD-Current ( > 8.0) > Date: Tue, 12 Jan 2010 11:32:22 +1100 > > I have the same problem since upgrading from 7.2 to 8.0. I have a PCI > Intel 1000 card. > > Perhaps someone could make a patch that does what Korba has done? Try 9 Current, I had the same problem with a Fibre em(4) card and I build a -CURRENT kernel last week and it worked Sam Fourman Jr. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: freebsd for Sun Fire X4250
We have a SunFire 420 running amd64 FreeBSD release 7.2. I doubt you will have a problem. --On January 11, 2010 5:05:04 PM -0600 Gavin Atkinson wrote: On Mon, 11 Jan 2010, Sam Wun wrote: This server is built with Xeon cpu processor, Intel based. Can FreeBSD 8+ fully compatible with this server like those ordinary Intel i386 machine? Although it's hard to say (the Sun website doesn't really give enough spec details), I'd be surprised if it doesn't work. FreeBSD runs very nicely on every Intel- and amd64-based Sun machine I've tried it on. You'll almost certainly want to use the FreeBSD amd64 release rather than i386, and I'd probably recommend 8.0-RELEASE, although 7.2 should work fine. By the way, this is the wrong list for questions like this: if you have any others, you're probably best off directing them to freebsd-questi...@freebsd.org Gavin ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ng_patch node
Hi, I've written netgraph node able to modify arbitrary (8|16|32)-bit unsigned integer in passing packets. Node applies one of =,+,-,&,| and ^ operations to number at given offset. Thank you. I think about more functionality... ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
lagg doesn't fail back to master
Hi all, I've sucessfully setup a lagg0 interface on my laptop to fail the wired connection over to wireless when it's unplugged. I have the following in my rc.conf: wlans_bwi0="wlan0" ifconfig_bwi0="ether XXX" ifconfig_wlan0="WPA mode 11g" cloned_interfaces="lagg0" ifconfig_lagg0="SYNCDHCP laggproto failover laggport bge0 laggport wlan0" This seems to work fine at boot. However, once I plug wired back in, lagg doesn't switch back to the master. Here is what ifconfig is showing: bge0: flags=8802 metric 0 mtu 1500 options=9b ether XXX media: Ethernet autoselect (100baseTX ) status: active bwi0: flags=8843 metric 0 mtu 2290 ether XXX media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether XXX media: IEEE 802.11 Wireless Ethernet OFDM/24Mbps mode 11g status: associated ssid 47FifthSt channel 6 (2437 Mhz 11g) bssid 00:0f:66:4f:1c:b8 country US authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit TKIP 3:128-bit txpower 0 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS roaming MANUAL lagg0: flags=8843 metric 0 mtu 1500 ether XXX inet 192.168.1.4 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect status: active laggproto failover laggport: wlan0 flags=4 laggport: bge0 flags=1 The handbook says lagg should switch back to master when it becomes active again. I tried a few other things like taking wlan0 down manually and even stopping the interface and restarting lagg without wlan active, but this just hung my network connection. Even destroying lagg and recreating by hand had no effect and lagg0 came back with the children already attached (as seen above) so the system is caching that information somewhere and lagg just won't let go of wlan... I'm on 8.0-STABLE from about 4 Dec 2009. Any ideas? regards, Callum -- Callum Gibson @ home http://members.optusnet.com.au/callumgibson/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ng_patch node
Dmitriy Zamuraev wrote: Hi, I've written netgraph node able to modify arbitrary (8|16|32)-bit unsigned integer in passing packets. Node applies one of =,+,-,&,| and ^ operations to number at given offset. have an IP version that corrects the checksums as you fiddle bytes. juat an idea Thank you. I think about more functionality... ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Hi. Regarding "automatic vlan creation"
On Thu, Oct 29, 2009 at 11:17:27AM +0200, Artis Caune wrote: > 2009/10/29 Brooks Davis : > >> btw, wouldn't it be nice not to bother with loader.conf when using > >> . syntax? > >> This patch will load if_vlan automatically in this case: > > > > Sorry but my reation is: eww. ??There's no way I'd commit that. ??You'd be > > randomly loading the vlan code for any interface that had a dot in it. > > You are right, forgot about 'ifconfig rename'. > > > The real change we should make it to add device vlan to GENERIC. ??It's > > long past time for it to be in by default. > > It's even better, what's need to be done to move it to GENERIC? It took me longer than I'd hoped, but I've added vlan to GENERIC in HEAD, RELENG_8, and RELENG_7 so it will be there 7.3 and 8.1. -- Brooks pgpy6O6T5ZxNS.pgp Description: PGP signature
Re: bin/142547: wpa_supplicant(8) drops connection on key renegotiation
The following reply was made to PR bin/142547; it has been noted by GNATS. From: Kevin Dorne To: bug-follo...@freebsd.org Cc: Subject: Re: bin/142547: wpa_supplicant(8) drops connection on key renegotiation Date: Mon, 11 Jan 2010 22:16:46 -0800 The same behavior occurs with the SVN driver. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: vimage vs. ipfilter
jul...@elischer.org (Julian Elischer) writes: >[vimage compatibility in 8.0] >ipfw is, (experimentally) and pf has patches to make it so. Thanks for your reply (and for your vimage efforts). I'd like to try vimage + pf and searched for the patch (including freebsd-pf and freebsd-virtualization list archives) but couldn't find it. Do you have a pointer? thanks, ~!paul -- G. Paul Ziemba FreeBSD unix: 11:06PM up 29 days, 47 mins, 26 users, load averages: 0.21, 0.20, 0.21 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: vimage vs. ipfilter
On Tue, 12 Jan 2010, G. Paul Ziemba wrote: jul...@elischer.org (Julian Elischer) writes: [vimage compatibility in 8.0] ipfw is, (experimentally) and pf has patches to make it so. Thanks for your reply (and for your vimage efforts). I'd like to try vimage + pf and searched for the patch (including freebsd-pf and freebsd-virtualization list archives) but couldn't find it. Do you have a pointer? I am not sure if a patch was published but you should be able to find the code to update pf and add V_support at: http://svn.freebsd.org/viewvc/base/user/eri/ /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ng_patch node
Maxim Ignatenko wrote:
> I've written netgraph node able to modify arbitrary (8|16|32)-bit
> unsigned integer in passing packets. Node applies one of =,+,-,&,| and
> ^ operations to number at given offset.
> Modification applied to each packet received on "in" hook. If "out"
> hook is connected - resulting packets passed on it, otherwise -
> returned back on "in" (for more easy use with ng_ipfw). Packets
> received on "out" hook passed on "in" unmodified.
> Node supports two control messages: "getconfig" and "setconfig".
> Configuration represented in next structure:
> struct ng_patch_config {
>uint32_tvalue; /* argument passed to requested operation */
>uint32_toffset; /* offset in bytes */
>uint32_tlength; /* 1,2 or 4 bytes */
>uint32_tmode; /* operation code: 1 - "=", 2 - "+", 3 -
> "-", 4 - "&", 5 - "|", 6 - "^" */
> };
> Same names used in ASCII representation.
>
> I wanted to make ipfw able to modify TTL and ToS fields in IP packets,
> but after some generalization idea looked like described above.
>
> Next patch made against 8-STABLE r200201
Just few stones into your garden:
> + if (((struct ng_patch_config *)msg->data)->offset < 0)
> + error = EINVAL;
As I see, offset field is unsigned there.
> + case 4:
> + *((uint32_t *)dst) +=
> priv->value4;
I think such dereference may crash archs with strong alignment
requirements. m_copydata/m_copyback could do it possibly slower, but
safer and wouldn't require m_pullup.
Also result of such multi-byte operations is endian-dependent. I would
be nice to do hton/ntoh somewhere.
Also, what's about checksums?
--
Alexander Motin
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
