It is certainly not correct... fortunately ampr-ripd ignores such routes after it was found that other people (like SA0BXI) had created them and they caused encapsulation loops. But of course you are right, the portal should simply refuse to store such incorrect information in the first place. It should issue an error message that makes the user think again about what they have requested. I am a bit disappointed about the progress in the portal development. Sure it can happen that people are temporarily busy and have to postpone things a bit until more time is available, but the portal as it is now has halted the development of amprnet and left everything in a stalemate situation. The DNS part needs to be finished, the allocation of subnets has to be much more flexible, overrides have to be made available to coordinators, and some address management tools have to be added. When it is decided that this cannot be done in the time available to the developer, it may be better to switch to another management system like the hamnet-db. 73, Rob