Ticket#416 LanManFS latches onto the first announced ether, not the first active

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.

I finally got a response from the bug tracker but I thought I’d reply here as I may not get access again.

Lanman can’t configure itself properly in ROM as networking isn’t up until after lanman has initialised.

Looks to me like InetSetup just makes the primary interface the first one saved in the internet startup file and gives it the default system variables.

Easiest solution to this is to save the following in the primary interface of the internet startup file created in inetsetup

x rmreinit lanmanfs -d<primary interface unit>

alternatively you can remove lanmanfs from rom and softload lanmanfs in internet startup

x rmload ...lanmanfs -d<primary interface unit>

or you could set a new variable Inet$PrimaryInterfaceUnit in internet startup and softload LanManFS in !Omni.