Comment 2 for bug 1365368

I've confirmed that uploading network yaml will NOT update the range in the database

# fuel --env 1 network --download

edit range start for any network but public

# fuel --env 1 network --upload

you can then download the network yaml or check the database ip_address_ranges table which have the same value (.1 or .2 it may move from .1 to .2 because some validator updates it to remove .1 from allocation after the networks are updated.

Real networks don't start at .1 or .2. This is a high issue and needs to be addressed in 7.0