Closed LaxSlash closed 7 years ago
hi laxslash, thats not a problem, they dont get one
This was taken in the sample world file... I'm lost on what makes some signs get addresses and others not?
hi, i just checked back to my own world, as your statement irritated me..
i have addresses on the BC8020, but only where it connects to configured rings
As i have a few BC8020 span togeter to form an hugh fastpath with teleporting in between, i dont have any address between two BC8020.
so my statement is only half true.
sorry about that
so you should have an address on the BC8020 where it connects to a BC8010, or in the garbage collector in the backbone
Yup, no addresses on any of them for me... region connected rings nor for the garbage collector.
hmm.. what version of mc do you run? as till spigot 1.10 it worked for me, so its either with 1.11 or an mistake on your side somewhere.. gota have to run an updater on my network with 1.11 now to compare
i can also offer to look at it, although im not sure if i see something ingame
On MC 1.10.2
well, it worked there for me, so it must be something with your setup.
well, bc aint easy and i still fight with it, yet still worth it ;)
if you like, i spy on your game to see if i see an issue
If you can take a look at it and see if you could figure it out, that'd be sweet.
send me the ip, and i will join in aprox. 18 hours..
Hi all,
Backbone updaters do not write on signs, they only update the routing table of backbone routers.
Region updaters, when at the frontier of the region they meet a BC8020, write the region address in the form "N.0.0" on the BC8020 sign connected to the region, but this is purely informational and is not really used in route computation.
I wonder why the sample world file has this, probably because it has a long history, and because, as I said, this information is not used.
Log:
East track is region 2, west track is region 1. North track is a closed loop, garbage is on the South track. Both Region 1 and Region 2 are configured.