Adding a prefix does not cause said prefix to be routed to the defined node

[lucyrose39]

Adding a prefix into central config doesn't cause the route to propegate to other nodes, and it doesn't seem to do anything - attempted with static and ping based routes

routers:
  - id: sgp-1
    pubkey: o1bZGzwSLDhogblTVFBA9rMGZIvjhFgSW6Xql5FJaSc=
    endpoints:
      - "domain.here.com:57175"
    addresses:
      - 10.109.14.1 # this is the internal nylon IP
  - id: fra-1
    pubkey: qfOIh+HGDoNWe17YKfgdJJw2ng8+hI7XrTNaBGsr40o=
    endpoints:
      - "domain.here.com:57175"
    addresses:
      - 10.109.14.2
    prefixes:
      - type: static
        prefix: 192.168.200.0/26

# Define the connections between nodes
graph:
  - sgp-1, fra-1 # This means node-1 and node-2 will try to connect to each other`

this config i would expect to generate a route entry on sgp-1 to send traffic destined for 192.168.200.0/26 to fra-1, however it does nothing, and creates no route in the routing table

[lucyrose39]

updated information - it appears that despite the central config having the prefixes in the config, when the nodes fetch the central config, it removes the prefix section entirely from it
If the central config is placed manually without fetching from a url, it works fine

[encodeous]

That sounds a little bit suspicious... are you sure your distributed config is indeed the latest? There is a timestamp included when the config is sealed, did you check if that is greater than your local config?

[lucyrose39]

i checked the last time i tested with it and the timestamp was up to date from what i could tell - it had completely removed the prefix section
i'll give it another test tomorrow and see if i can dump the network requests it's making, maybe it's not actually requesting a new copy of the config?