fwip(4) carrier detection

[Roy Marples]

Hi List

fwip(4) lacks carrier detection that most other drivers offer.
How hard would it be to add?

Or another solution for me would be to rely on SIOCGIFMEDIA working down the
interface is down. This seems to work for bge(4) - should this generally be
the case?

Thanks

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Quentin Garnier]

Post by Roy Marples
Hi List
fwip(4) lacks carrier detection that most other drivers offer.
How hard would it be to add?
Or another solution for me would be to rely on SIOCGIFMEDIA working down the
interface is down. This seems to work for bge(4) - should this generally be
the case?

What does carrier detection mean in the context of fwip(4)? What in
your opinion should happen for a host that has more than one firewire
port and only one controller?

You have to keep in mind fwip(4) is not Ethernet.

[Roy Marples]

Post by Quentin Garnier

Post by Roy Marples
Hi List
fwip(4) lacks carrier detection that most other drivers offer.
How hard would it be to add?
Or another solution for me would be to rely on SIOCGIFMEDIA working down the
interface is down. This seems to work for bge(4) - should this generally be
the case?

What does carrier detection mean in the context of fwip(4)? What in
your opinion should happen for a host that has more than one firewire
port and only one controller?
You have to keep in mind fwip(4) is not Ethernet.

Well, on my systems I have fwip0 reported as an interface.
It does not advertise carrier, so dhcpcd will automatically try and get
an IP address and fail. This normally isn't an issue, but I'm looking at
getting dhcpcd to background when after getting an IP or no interface
has a carrier. NetBSD is my only system where fwip0 is visible by
default, so I'd like to get something done, either in dhcpcd or in NetBSD.

Thanks

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[David Young]

Post by Quentin Garnier

Post by Roy Marples
Hi List
fwip(4) lacks carrier detection that most other drivers offer.
How hard would it be to add?
Or another solution for me would be to rely on SIOCGIFMEDIA working down the
interface is down. This seems to work for bge(4) - should this generally be
the case?

What does carrier detection mean in the context of fwip(4)? What in
your opinion should happen for a host that has more than one firewire
port and only one controller?
You have to keep in mind fwip(4) is not Ethernet.

IIUC, ports belonging to the same controller form a "broadcast" network,
that is, devices on port A are addressable by devices on port B, and
vice versa, for any two ports A or B. In other words, the FireWire
controller acts analogously to an ethernet hub/switch for its ports.
In that case, if there is no "live" device attached to any port, the
appropriate media status is 'no carrier'. If there is a live device on
any single port, however, the media status should be 'active'.

I don't know if there is any way to detect the status of any single
port. I *do* think that you can enumerate the nodes on the FireWire
bus. If there is just one node, the local host, 'no carrier' seems
right, and if there are two or more nodes, then 'active'.

Dave

[Ignatios Souvatzis]

Post by David Young
I don't know if there is any way to detect the status of any single
port. I *do* think that you can enumerate the nodes on the FireWire
bus. If there is just one node, the local host, 'no carrier' seems
right, and if there are two or more nodes, then 'active'.

This sounds good to me. Who'll implement?

-is