Quantcast
Channel: stardot.org.uk
Viewing all articles
Browse latest Browse all 5552

8-bit acorn hardware • Re: PiBridge 2.1-dev pushed to github

$
0
0
On the plus side, authenticated TRUNK works. Yey. =D>
I've noticed what appears to be rather a shortcoming of the trunking though. And it wasn't obvious until I stumbled on the following comment in the example 'econet-hpbridge.cfg-EconetPlusFileserverAndTrunk' file:

Code:

# Support myfriend advertises network 1, and the bridge will automatically# drop that because net 1 is defined as a Wire above.
And it seems there's no way to TRUNK XLATE your way out of this problem... if you have called your local network '1' and your friend also has theirs as '1' (because that's the default and why would you do anything else?) then they cannot be TRUNK connected. Only when I changed one of the networks to be '2' would it then all spring in to life.

What's the reason for this? Why can't I have a XLATE for remotes clashing my local network numbers? (I tried, it doesn't work).

I think this could be a problem for the TNMoC LAN party, because it means anyone who happens to have used the same network number as used on the TNMoC LAN wouldn't be able to connect their home network in via TRUNK.

Sooo... what's the network number for the TNMoC LAN going to be, so we can all avoid it? Hopefully not '1', or I suspect 'everyone' is going to have to reconfigure.

Statistics: Posted by IanJeffray — Sat May 11, 2024 12:46 am



Viewing all articles
Browse latest Browse all 5552

Trending Articles