Date: Sat, 23 Sep 2000 10:06:14 -0400 (EDT) From: "Vladimir N. Silyaev" <vsilyaev@mindspring.com> To: nsayer@quack.kfu.com Cc: emulation@freebsd.org, net@freebsd.org Subject: Re: Bridging fix Message-ID: <200009231406.KAA00417@jupiter.delta.ny.us> In-Reply-To: <39CCAC0A.ABCB738D@quack.kfu.com> References: <39CCAC0A.ABCB738D@quack.kfu.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Oh, great. Do you know, does that fixed problem with bridging code in the case when active more than two network interfaces? And probably that fix should significantly reduce perfomance for the case when bridging are used not for VMware needs ;-(. Vladimir In muc.lists.freebsd.emulation, you wrote: >This doesn't really have anything to do with emulation, except that lots >of vmware users hang out here. :-) > >I have figured out that the upper protocol layers are not yet completely >read-only with regards to mbufs coming in from downstream. What this >means is that the bridge code must use m_dup rather than m_copypacket >(the latter only bumps up refcounts to make it LOOK like you copied the >packet). > >So if you are having trouble getting a vmware guest to be a DHCP client >or otherwise participate correctly with broad- or multi-cast services, >change all instances of m_copypacket in /sys/net/bridge.c and >/sys/netgraph/ng_bridge.c to m_dup. That should fix it. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-emulation" in the body of the message > -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009231406.KAA00417>