Bridging an IEEE1394 nic - Troubles

Hello,
brctl replies:

can't add eth1 to bridge0, invalid argument

the firewire nic works fine in standalone mode
tia for helping

l.

Luciano <(E-Mail Removed)> wrote:

> brctl replies:
> can't add eth1 to bridge0, invalid argument
>
> the firewire nic works fine in standalone mode
> tia for helping

I haven't used brctl. So I just guess here. Could it
mean that your eth1/firewire interface can't be put
into promiscious mode? Try tcpdump -i eth1. Does this
succeed?

Ciao, Horst
--
»When pings go wrong (It hurts me too)« E.Clapton/E.James/P.Tscharn

Horst Knobloch <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Luciano <(E-Mail Removed)> wrote:
>
> > brctl replies:
> > can't add eth1 to bridge0, invalid argument
> >
> > the firewire nic works fine in standalone mode
> > tia for helping
>
> I haven't used brctl. So I just guess here. Could it
> mean that your eth1/firewire interface can't be put
> into promiscious mode? Try tcpdump -i eth1. Does this
> succeed?
>

you are quite right:

# tcpdump -i eth1

eth1 entered promiscous mode
Warning: arptype 24 not supported by lincap...

fear I have to wait a bit before a firewire nic will be fully supported by
net tools and brctl.

It works fine with windose, grrr...thanks for your reply.

Luciano