Can you pls. share the patch for freebsd 7?
On 2/7/2011 3:23 AM, Mike Tancsa wrote:
So far so good. I would often get a hang on the level zero dumps to my
backup server Sunday AM, and it made it through! So a good sign, but
not a definitive sign.
I have a PCIe em card that has this chipset as
On 7/6/2011 4:29 AM, Hooman Fazaeli wrote:
> Can you pls. share the patch for freebsd 7?
Its in the tree.
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/e1000/
---Mike
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet
Hi Artem,
I have exactly the same problem as you are describing below, also with quite
a number of amd mounts.
In addition to the scenario you describe, another way this happens here
is when downloading a file via firefox to a directory currently open in
dolphin (KDE file manager). This will alm
Hi Jack,
many thanks for your work. I'm still interested in hearing back from
you. Is there anything I can do to help?
Also I would not mind losing hardware VLAN assistance should it be the only way.
BTW, what about MAC addresses? Is the card reset when a MAC address changed?
Thanks!
Igor
On
Can someone please review this and check in the patch? (And MFC it to
stable/8?)
Thank you,
Andrew
Begin forwarded message:
> From: lini...@freebsd.org
> Date: May 12, 2011 10:36:26 AM EDT
> To: lini...@freebsd.org, freebsd-b...@freebsd.org, freebsd-net@FreeBSD.org
> Subject: Re: kern/156978
Hi all,
I have two separate LANs (one 10.0.1.0/24 and the other 10.0.2.0/24). Both are
connected to FreeBSD 8.2 router (ifaces em1 and em2).
To em0 I have my ISP (10.0.0.0/24) connected.
The idea is to share the Internet connection to both networks, and block any
traffic between them.
I was tr
On Jul 6, 2011, at 11:01 AM, Marek Salwerowicz wrote:
> The idea is to share the Internet connection to both networks, and block any
> traffic between them.
>
> I was trying to set up the firewall like this:
>
> #!/bin/sh
>
> cmd="ipfw -q"
>
> $cmd flush
>
> $cmd add 50 check-state
>
> $cmd
Hi all,
I've attached a patch which fixes the "nfrags > 18, netback won't be able to
handle it" problem with xen netfront when TSO is enabled.
It's not finished, though:
+ int max_mbuf_chain_len = 16;/* XXX Set this based on interface? */
I'm not sure what the right way is to feed a va
Old Synopsis: [PATCH] [if_tap] Add VIMAGE support to if_tap
New Synopsis: [patch] [tap] Add VIMAGE support to if_tap
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Jul 6 19:19:24 UTC 2011
Responsible-Changed-Why:
Over to mainta
On Jul 5, 2011 4:49 PM, "Chuck Swiger" wrote:
>
> On Jul 4, 2011, at 6:32 PM, Charles Sprickman wrote:
> > We're running a few 8.1-R servers with Broadcom bce interfaces (Dell
R510) and I'm seeing occasional packet loss on them (enough that it trips
nagios now and then). Cabling seems fine as nei
On Jul 6, 2011, at 12:27 PM, Kevin Oberman wrote:
> 1 in 10**6? That is totally excessive.
It's high for a switched LAN, but I'd imagine you remember collision rates on
hubs, which might well exceed 1% of the packets when the network is under load.
> The Ethernet spec requires no worse than 10**
On Mon, Jul 04, 2011 at 09:32:11PM -0400, Charles Sprickman wrote:
> Hello,
>
> We're running a few 8.1-R servers with Broadcom bce interfaces (Dell R510)
> and I'm seeing occasional packet loss on them (enough that it trips nagios
> now and then). Cabling seems fine as neither the switch nor t
On Wed, Jul 06, 2011 at 02:28:19PM -0700, David Christensen wrote:
> > You had 282 RX buffer shortages and these frames were dropped. This
> > may explain why you see occasional packet loss. 'netstat -m' will
> > show which size of cluster allocation were failed.
> > However it seems you have 0 com
> You had 282 RX buffer shortages and these frames were dropped. This
> may explain why you see occasional packet loss. 'netstat -m' will
> show which size of cluster allocation were failed.
> However it seems you have 0 com_no_buffers which indicates
> controller was able to receive all packets de
> > > Data sheet says IfHCInBadOctets indicates number of octets received
> > > on the interface, including framing characters for packets that
> > > were dropped in the MAC for any reason.
> >
> > The IfHcInBadOctets counter says the controller received X bytes
> > that were bad on the wire (colli
Old Synopsis: TSO breaks BPF packet captures with em driver
New Synopsis: [em] TSO breaks BPF packet captures with em driver
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Jul 6 21:53:02 UTC 2011
Responsible-Changed-Why:
Over t
On Wed, Jul 06, 2011 at 02:47:24PM -0700, David Christensen wrote:
> > > > Data sheet says IfHCInBadOctets indicates number of octets received
> > > > on the interface, including framing characters for packets that
> > > > were dropped in the MAC for any reason.
> > >
> > > The IfHcInBadOctets coun
Have a customer reporting problems with ixgbe, but investigation has
suggested that lagg
is the real issue, or the two combined. If anyone out there is using the
ixgbe driver with
lagg I'd like to hear from you.
Thanks all,
Jack
___
freebsd-net@freebsd.
On Wed, Jul 6, 2011 at 1:04 PM, Chuck Swiger wrote:
> On Jul 6, 2011, at 12:27 PM, Kevin Oberman wrote:
>> 1 in 10**6? That is totally excessive.
>
> It's high for a switched LAN, but I'd imagine you remember collision rates on
> hubs, which might well exceed 1% of the packets when the network is
Old Synopsis: ix0 is not working within lagg(4)
New Synopsis: [ix] [lagg] ix0 is not working within lagg(4)
Responsible-Changed-From-To: freebsd-amd64->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jul 7 02:29:04 UTC 2011
Responsible-Changed-Why:
reclassify.
http://ww
More inline, including a bigger picture of what I'm seeing on some other
hosts, but I wanted to thank everyone for all the fascinating ethernet BER
info and the final explanation of what the "IfHCInBadOctets" counter
represents. Interesting stuff.
On Wed, 6 Jul 2011, YongHyeon PYUN wrote:
O
21 matches
Mail list logo
