Re: bridging broken in -current AND -stable
> > let me doubt it. i have had a fair amount of trouble with these nics, > > maybe it's driver's fault, but still... anyways, the driver is > > not as easy to work on as others. > > For future investments: which nics do you recommend? > (stable driver, speed...) fxp? probably, yes, though the whole bunch of drivers contributed by Bill Paul look interesting as well (i have no idea on how good is the hardware, e.g. the rl 8139 is not such a good card). > Which nics are capable for bridging now in -current? ed, fxp, ...? and 'rl' i think. > To prevent the page faults in the upcomping release the bridging support > should be disabled in if_de. > Maybe the manpage should note the real supported nics. wish i had more time. cheers luigi > > Boris > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bridging broken in -current AND -stable
On Thu, Mar 09, 2000 at 07:26:52AM +0100, Luigi Rizzo wrote: > let me doubt it. i have had a fair amount of trouble with these nics, > maybe it's driver's fault, but still... anyways, the driver is > not as easy to work on as others. For future investments: which nics do you recommend? (stable driver, speed...) fxp? > at 10Mbit the ed does a reasonable job considering todays machines. > will try and have a look at the de driver some time in the future. ok. Which nics are capable for bridging now in -current? ed, fxp, ...? To prevent the page faults in the upcomping release the bridging support should be disabled in if_de. Maybe the manpage should note the real supported nics. Boris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bridging broken in -current AND -stable
> > > Is it possible that bridging is broken in -current and -stable?
> >
> > no, but the "de" driver on bridging is now unsupported and i could not
> > find the time to make it work after recent fixes to the bridging code.
>
> Ooo n! :-((
> The best nic_s all around are unsupported? ;)
let me doubt it. i have had a fair amount of trouble with these nics,
maybe it's driver's fault, but still... anyways, the driver is
not as easy to work on as others.
> > can you switch to some supported card ("ed" or "fxp") ?
>
> Hmm, "ed" is lousy and "fxp" is too expensive for me now...
at 10Mbit the ed does a reasonable job considering todays machines.
will try and have a look at the de driver some time in the future.
cannot tell how far asway, sorry.
cheers
luigi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: bridging broken in -current AND -stable
On Thu, 9 Mar 2000, Boris Staeblow wrote:
> On Wed, Mar 08, 2000 at 11:15:23PM +0100, Luigi Rizzo wrote:
>
> > >
> > > Is it possible that bridging is broken in -current and -stable?
> >
> > no, but the "de" driver on bridging is now unsupported and i could not
> > find the time to make it work after recent fixes to the bridging code.
>
> Ooo n! :-((
> The best nic´s all around are unsupported? ;)
>
> > can you switch to some supported card ("ed" or "fxp") ?
>
> Hmm, "ed" is lousy and "fxp" is too expensive for me now...
>
> How great is the chance that good old dec is coming back?
> I could help you testing your code... :)
>
> I would like to prevent to buy new hardware again.
I have what appear to be functional patches to provide support for if_dc,
used in the common and cheap PCI Linksys ethernet cards (LNE100TX?). If
jkh approves the commit, I can stick it in before the release. I don't
have access to an if_de card where I am currently, so won't be able to
look at that for at least a week or two.
The patch for if_dc is below.
Robert N M Watson
[EMAIL PROTECTED] http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services
Index: if_dc.c
===
RCS file: /home/ncvs/src/sys/pci/if_dc.c,v
retrieving revision 1.7
diff -u -r1.7 if_dc.c
--- if_dc.c 2000/01/24 17:19:37 1.7
+++ if_dc.c 2000/03/08 18:15:55
@@ -122,6 +122,11 @@
#include
+#include "opt_bdg.h"
+#ifdef BRIDGE
+#include
+#endif
+
#include /* for vtophys */
#include /* for vtophys */
#include /* for DELAY */
@@ -2099,14 +2104,30 @@
ifp->if_ipackets++;
eh = mtod(m, struct ether_header *);
- /*
-* Handle BPF listeners. Let the BPF user see the packet, but
-* don't pass it up to the ether_input() layer unless it's
+ /* Handle BPF listeners. Let the BPF user see the packet */
+ if (ifp->if_bpf)
+ bpf_mtap(ifp, m);
+
+#ifdef BRIDGE
+ if (do_bridge) {
+ struct ifnet *bdg_ifp ;
+ bdg_ifp = bridge_in(m);
+ if (bdg_ifp != BDG_LOCAL && bdg_ifp != BDG_DROP)
+ bdg_forward(&m, bdg_ifp);
+ if (((bdg_ifp != BDG_LOCAL) && (bdg_ifp != BDG_BCAST) &&
+ (bdg_ifp != BDG_MCAST)) || bdg_ifp == BDG_DROP) {
+ m_freem(m);
+ continue;
+ }
+ }
+
+ eh = mtod(m, struct ether_header *);
+#endif
+
+ /* Don't pass it up to the ether_input() layer unless it's
* a broadcast packet, multicast packet, matches our ethernet
* address or the interface is in promiscuous mode.
*/
if (ifp->if_bpf) {
- bpf_mtap(ifp, m);
if (ifp->if_flags & IFF_PROMISC &&
(bcmp(eh->ether_dhost, sc->arpcom.ac_enaddr,
ETHER_ADDR_LEN) &&
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: bridging broken in -current AND -stable
On Wed, Mar 08, 2000 at 11:15:23PM +0100, Luigi Rizzo wrote:
> >
> > Is it possible that bridging is broken in -current and -stable?
>
> no, but the "de" driver on bridging is now unsupported and i could not
> find the time to make it work after recent fixes to the bridging code.
Ooo n! :-((
The best nic´s all around are unsupported? ;)
> can you switch to some supported card ("ed" or "fxp") ?
Hmm, "ed" is lousy and "fxp" is too expensive for me now...
How great is the chance that good old dec is coming back?
I could help you testing your code... :)
I would like to prevent to buy new hardware again.
Boris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: bridging broken in -current AND -stable
[Charset iso-8859-1 unsupported, filtering to ASCII...]
>
> Is it possible that bridging is broken in -current and -stable?
no, but the "de" driver on bridging is now unsupported and i could not
find the time to make it work after recent fixes to the bridging code.
can you switch to some supported card ("ed" or "fxp") ?
cheers
luigi
---+-
Luigi RIZZO, [EMAIL PROTECTED] . Dip. di Ing. dell'Informazione
http://www.iet.unipi.it/~luigi/ . Universita` di Pisa
TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
Mobile +39-347-0373137
---+-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
bridging broken in -current AND -stable
Is it possible that bridging is broken in -current and -stable? Some minutes (02 - 30 min.) after bootup I get: Fatal trap 12: Page fault while in kernel mode fault code: Supervisor read, page not present Sorry, i´ve no further crashlogs/dumps. This panic occur only with bridging enabled - in -current AND -stable. My last working (stable) kernel with bridging is from 17 Jan 2000. Extract from -current dmesg: de0: port 0xe000-0xe07f \ mem 0xe500-0xe50003ff irq 7 at device 9.0 on pci0 de0: 21143 [10-100Mb/s] pass 4.1 de0: address 00:80:ad:78:11:4b de0: driver is using old-style compatability shims de1: port 0xd400-0xd47f \ mem 0xe400-0xe47f irq 11 at device 12.0 on pci0 de1: 21041 [10Mb/s] pass 1.1 de1: address 00:80:ad:1c:af:a8 de1: driver is using old-style compatability shims BRIDGE 990810, have 13 interfaces -- index 1 type 6 phy 0 addrl 6 addr 00.80.ad.78.11.4b -- index 2 type 6 phy 0 addrl 6 addr 00.80.ad.1c.af.a8 Boris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
