Ticket #416 (Open)Mon Nov 23 16:42:19 UTC 2015
LanManFS latches onto the first announced ether, not the first active
| Reported by: | Sprow (202) | Severity: | Normal |
| Part: | RISC OS: Module | Release: | |
| Milestone: | Status | Open |
Details by Sprow (202):
LanManFS (correctly) listens out for the 2 DCI service calls and tracks when protocol modules (Internet) come and go and drivers come and go. However, it uses a cached copy of Inet$EtherType to choose which to attach to.
In the DCI4 spec Inet$EtherType is noted as for backwards compatibility only and should be set only if unset, so in the situation of having more than one ethernet interface (eg. an EtherY podule and an EtherI NIC) LanManFS doesn’t choose the right one.
I think the “Primary Interface” checkbox in InetSetup is supposed to resolve this, but haven’t spotted what ticking that actually does – all the Inet variables seem to be the same.
Likely might need a 2 part fix then: for LanManFS to not look at Inet$EtherType and to do some digging in the archives to find out what “Primary Interface” does and how to select from it, being careful not to break LanMan’s listening to the DCI calls to handle drivers coming and going.
