[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Bridging on U60 with qfe


Thank you for the pointer.  I managed to get the bridge-utils64.  It wants a
newer version of libc6-sparc64.  I noticed this is only in the unstable
branch, so I changed my system to update everything to unstable.  This seems
to have resulted in some stability issues (surprise, right???  ;-).  Anyway,
my question is, if I just want to get bridging working, what is the minimum
I have to do?  Should I just upgrade libc6-sparc64 and dependencies?  Should
I be running a specific version of the kernel other than 2.4.18?  Does it
matter if the bridging is compiled into the kernel or a module?

Currently, when I use brctl, I don't get errors, but doing an addbr br0
doesn't work.  Nothing is added.

At this point, I'm thinking I should start over from scratch and I'm hoping
you can point me in the right direction as far as what I need to get
bridging working.  I also wanted to mention that I use bridging on the x86
architecture without issue.  I'm just hoping I can get it working on my U60.

   <> Jim

-----Original Message-----
From: Ben Collins [mailto:bcollins@phunnypharm.org] On Behalf Of Ben Collins
Sent: Thursday, February 26, 2004 1:53 PM
To: Small, Jim
Cc: debian-sparc@lists.debian.org
Subject: Re: Bridging on U60 with qfe

On Thu, Feb 26, 2004 at 01:46:18PM -0500, Small, Jim wrote:
> I would like to enabled bridging on my Ultra 60.  I have a Sun qfe card in
> addition to the built-in hme port.  I enable bridging in the kernel, but
> when I try to use it, I get the following errors:
> # brctl addbr br0
> NET4: Ethernet Bridge 008 for NET4.0
> # brctl show
> sys32_ioctl(brctl:468): Unknown cmd fd(3) cmd(000089f3) arg(effff9b0)
> bridge name    bridge id                   STP enabled          interfaces

You need the 64-bit compiled bridge-utils available here:


Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/

Reply to: