just a follow-up, Jordan experianced the same bug and tracked it down,
I think Peter Wemm fixed it. it was something with isa+sysctl, and not
bridge related, sorry.
no problem, you don't know until you find the bug, so i think it
is better to receive a false alarm than no alarm for a real bug
On Mon, 3 May 1999, Alfred Perlstein wrote:
On Mon, 3 May 1999, Luigi Rizzo wrote:
a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in,
doing a sysctl -a will panic the box. (currproc == sysctl)
if you think the panic is bridge-related, can you try manually the
a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in,
doing a sysctl -a will panic the box. (currproc == sysctl)
i have both bridging and ipfw enabled on the bridged packets,
my de0 card has no ip and my xl0 card does.
if you aren't easily able to reproduce it, i'll try harder,
a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in,
doing a sysctl -a will panic the box. (currproc == sysctl)
if you think the panic is bridge-related, can you try manually the
net.link.ether.bridge* sysctl -- if they do not fail, then the problem
could be with the sysctl to
On Mon, 3 May 1999, Luigi Rizzo wrote:
a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in,
doing a sysctl -a will panic the box. (currproc == sysctl)
if you think the panic is bridge-related, can you try manually the
net.link.ether.bridge* sysctl -- if they do not fail,
ok, egg in my face, that's not it i guess. What about patching rc.network
to allow early setup of bridge though?
i have no objections, the thing is i dont run current or even stable
so i can't completely check changes if i do the patch myself, and
i'd rather not break things so close to a
