he FreeBSD driver as well.
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind Riv
> Hello Bill,
>
> * Bill Paul <[EMAIL PROTECTED]> wrote:
> > > - Switching from and to promiscuous mode takes 7 seconds. All packets
> > > are dropped in the mean time.
> >
> > The SIOCSIFFLAGS handler in re_ioctl() currently just takes a short
> * Bill Paul <[EMAIL PROTECTED]> wrote:
> > > It's more likely a problem with the multicast filter programming.
> > > IPv6 is all about the multicasting (neighbord discovery depends on it
> > > to work correctly). I can't explain why it's not
> > On Tue, Nov 28, 2006 at 08:46:00PM +0100, Ed Schouten wrote:
> > > Hello,
> > >
> > > I'm running FreeBSD 6.2-PRERELEASE on my new desktop. It has the
> > > following hardware:
> > >
> > > - Intel Core 2 Duo 6400
> > > - Asus P5B motherboard
> > > - On-board Realtek NIC (8168B/8111B)
> On Tue, Nov 28, 2006 at 08:46:00PM +0100, Ed Schouten wrote:
> > Hello,
> >
> > I'm running FreeBSD 6.2-PRERELEASE on my new desktop. It has the
> > following hardware:
> >
> > - Intel Core 2 Duo 6400
> > - Asus P5B motherboard
> > - On-board Realtek NIC (8168B/8111B)
> >
> > For som
;ifconfig steX ether xx:xx:xx:xx:xx:xx' without even using the
fast etherchannel driver?
If you have not tried this, then try it now:
# ifconfig ste2 ether 0:0:e8:1:2:3
# ifconfig ste2 1.1.1.4 netmask 0xff00 up
# ping 1.1.1
packets to your heart's content. Don't let the big bad
tcpdump warning message scare you.
-Bill
--
=
-Bill Paul
name, strip out all the device-dependent
stuff specific to the old device and replace it with stuff for the
new device.
And then the stork comes, and it's a driver.
-Bill
--
=
you need to do to enable/power up the
on-board NIC that we're not doing
This is something you should be asking the PCI gurus about,
not the networking gurus.
-Bill
--
=
-Bill Paul(510) 749-2329 | Senio
e for the 5704 ASIC.
-Bill
--
=
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Systems
=
&q
> Copied to -net rather than the cvs lists...
>
> On Thu, 7 Aug 2003, Bill Paul wrote:
>
> > Tested with the Xterasys XN-152 NIC (hard to beat $29 for a gigE
> > NIC).
>
> That's definately not a bad price. Do the remarks about the earlier
> rl cards sti
> On Thu, 7 Aug 2003, Bill Paul wrote:
>
> > Pros:
> >
> > - The 8169 is very easy to program. RealTek has been very peculiar
> > in how it's releasing documentation for it though. They had the
> > manual on their site for a while, then t
duplex as well.
If your switch is not managed and doesn't allow you to manually
configure the port settings, then you're out of luck. You'll just
have to live with half duplex mode.
-Bill
--
==
I've been told they will not prevent me from releasing driver source.
I hope to get this resolved soon. Stay tuned.
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Uni
MAIL PROTECTED] And don't be
afraid to spread the word. Ask other people on other mailing lists.
Ask your friends. Ask your enemies. Ask not what your OS can do for
you: ask what you can do for your OS.
-Bill
--
=
-B
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
by
each device.
What I did see was a lot of people holding forth about duplex mismatches
which, while they can be annoying, are not the only source of RX errors.
A duplex mismatch typically yeilds very low overall throughput and very
bursty traffic patterns.
-Bill
--
=
/sys/dev/mii
- Rebuild your kernel and/or if_bge.ko and miibus.ko modules
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Sy
and miidevs into /sys/dev/mii
- Recompile your kernel and/or if_bge.ko and miibus.ko modules.
-Bill
--
=
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind
y help anyone is able to provide.
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Systems
=
"If stupidity were
me know how this works.
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Systems
=
ot works.
I don't know if this is still a problem or not. At the moment, I have
no easy way to test it.
> There are more verbose details on these lists too.
> Are there any chances to get these fixed?
Like I said, it depends on time and availability of resources.
-Bill
--
===
0x9 is
an 82557/8/9, which won't gain anything from these mods, I'm sorry to
say.
-Bill
--
=
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Systems
ike to commit this soon. I'm
fairly confident that (at the very least) it doesn't break any existing
functionality. Unfortunately, I'm not in a position to do in-depth
performance tests right now.
-Bill
--
=
-Bill
> Hi guys,
>
> I'm moving from the wx driver to either the gx or em driver. I haven't seen
> a lot of traffic about either and I was wondering what people's experiences
> have been like. Has any one done performance tests? How do the three drivers
> stack up? Any negative points on either driver?
transfers, I'd be
interested to see the results.
Share and enjoy!
-Bill
--
=====
-Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu
[EMAIL PROTECTED] | Wind River Sy
://www.freebsd.org/~wpaul/Sundance/ste.diff
# cd /sys/pci
# patch < /tmp/ste.diff
Then compile a new kernel and/or new if_ste.ko kernel module.
Please let me know if this helps.
-Bill
--
=
-Bill Paul(510) 749-2329 | Sen
advertisement without
> running tcpdump ?
You can also run tcpdump -n -e -p -i ste0. The -p flag means "don't
put the interface into promisc mode."
-Bill
--
=
> Hi,
> I would like to have information regarding the implementation of the
> xl_start_90xB function in the xl driver. After reading the code and the
> technical reference from 3com I still cannot understand how the driver
> signals the NIC for packet downloading.
It doesn't. Instead, the xl_ini
>
> Okay, tried this, same results. Still getting a 6 in the capabilities.
G
> I'm not familiar with the VIA Rhine. How can I check this?
It's a moot point. I realized that in your earlier mail, you claimed
that the card included a Linux driver called rtl8139.c, so it can't be
a VIA
>
> Alas, that patch is exactly what I have already done. I was hoping you'd
> found somewhere that I missed an update, but I already had those three spots
> covered.
Fine. I'm including another patch with a slight change. I don't know if
this will make a difference or not since I've never kn
Guh. Support for this card was added to -current, but the changes never
made it back to -stable. The problem (I think) is that while you updated
the device list, you overlooked a piece of code in rl_attach() that selects
the driver behavior depending on the PCI device ID. Get back your original
ve
> >> >Each link is checked once every second to see if the link is still up.
> >> >An attempt to send a packet over a dead link will cause the packet to
> >> >be shifted over to the next link in the bundle.
> >>
> >> Any chance this can be done through an async event rather
> >> than by polling?
> >Each link is checked once every second to see if the link is still up.
> >An attempt to send a packet over a dead link will cause the packet to
> >be shifted over to the next link in the bundle.
>
> Any chance this can be done through an async event rather
> than by polling?
If there was, I w
> Date: Sat, 10 Feb 2001 15:29:17 +0100
> From: Rainer Clasen <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: call for testers: port aggregation netgraph module
>
> On Thu, Feb 08, 2001 at 01:25:09PM -0800, Bill Paul wrote:
> >
> Bill Paul writes:
> > http://www.freebsd.org/~wpaul/FEC/4.x/fec.tar.gz
> > http://www.freebsd.org/~wpaul/FEC/5.x/fec.tar.gz
> >
> > This is a call for testers for a netgraph module that can be used to
> > aggregate 2 or 4 ethernet interfaces into a single inte
> On Fri, 9 Feb 2001, Chris Dillon wrote:
>
> > On Fri, 9 Feb 2001, Dan Nelson wrote:
>
> > Cool, if thats all it will take, I'll give it a try. But, whatever
> > method Compaq/Intel is using doesn't require me to set up the ports on
> > the switch as being part of a trunk. It "just works". A
http://www.freebsd.org/~wpaul/FEC/4.x/fec.tar.gz
http://www.freebsd.org/~wpaul/FEC/5.x/fec.tar.gz
This is a call for testers for a netgraph module that can be used to
aggregate 2 or 4 ethernet interfaces into a single interface. Basically,
it lets you do things like the following:
# kldload ./ng
38 matches
Mail list logo
