"Rogier R. Mulhuijzen" wrote:
>
> I found this while experimenting with both "legacy" bridge and ng_bridge.
> The bridging code doesn't check its activation everywhere so when I started
> using an ng_bridge node I started getting weird errors.
>
> Patch is rather simple, can someone submit this?
At 00:48 3-2-01 -0800, Julian Elischer wrote:
>"Rogier R. Mulhuijzen" wrote:
> >
> > I found this while experimenting with both "legacy" bridge and ng_bridge.
> > The bridging code doesn't check its activation everywhere so when I started
> > using an ng_bridge node I started getting weird errors.
> >I have a question about FreeBSD and I'm hoping you
> >can steer me in the right direction. We currently have a BSD box that is
> >acting as our firewall with a NT domain behind it. We want to set up VPN
> >solution where a client (running NT or Win2K) can access the internal NT
> >server thr
"Rogier R. Mulhuijzen" wrote:
>
[explanation]
ok I understand now...
I thought you were saying that the netgraph code was acting differently
to how I belive it should act.
>
>
>
>
> Exactly if there's just one interface when netgraph bridging is on. Why?
> Why just one interface? Now that m
>ok I understand now...
>I thought you were saying that the netgraph code was acting differently
>to how I belive it should act.
Nope that was the legacy bridge.
> > Exactly if there's just one interface when netgraph bridging is on. Why?
> > Why just one interface? Now that my kernel is patche
I'm running -STABLE (cvsup'ed on 26jan2001) on a machine with the
BRIDGE option, bridging between two PCI NICs (rl0 and xl0).
I'm having ARP problems. Machines on the "rl0" card are unable to
get a hardware address for the bridge. (For whatever reason, I have
no problems talking via the "xl0" i
On Sat, Feb 03, 2001 at 02:26:10PM -0800, Rich Wales wrote:
> I'm running -STABLE (cvsup'ed on 26jan2001) on a machine with the
> BRIDGE option, bridging between two PCI NICs (rl0 and xl0).
>
> I'm having ARP problems. Machines on the "rl0" card are unable to
> get a hardware address for the bri
Crist Clark wrote:
> Not all cards support bridging.
As far as I can tell, the "rl" device is (or, at least, is supposed to
be) supported by the bridge code.
"ifconfig rl0" on my bridge shows the interface is running in promis-
cuous mode, and bridging works perfectly for me in all respects
Hi,
> > I can't see how this can happen without any previous log lines saying
> > that a chap packet has been received.
> >
> > If this is repeatable, can you try doing a ``show timer'' right after
> > the SUCCESS response has been sent ? If the radius timer wasn't
> > cleared properly this
Earlier, I reported an ARP problem on a 4.2-STABLE bridge system.
A few people wrote me privately, advising me to include a firewall
rule passing UDP packets on port 2054 to/from the IP address 0.0.0.0.
I've tried this, but it doesn't help any. I should mention, though,
that I don't think this
> I think I've figured out the problem though... can you try the latest
> version of ppp - should be available via
> http://www.Awfulhak.org/ppp.html RSN (the 010204 archive) if you
> don't get -current.
>
> I think you're just missing an acct line in your radius config file.
> The bug in pp
11 matches
Mail list logo