21 Sep
2014
21 Sep
'14
12:28 a.m.
The 44.136/21 subnet had been entered twice in the database;
I've removed the duplicate and the file should now be ok again.
- Brian
On Sat, Sep 20, 2014 at 07:44:56PM -0700, Tom Hayward wrote:
route addprivate 44.136/21 encap 124.171.137.31
started appearing twice in the encap file. Before this, all entries in
the encap file were unique.
Did something change about how the encap file is generated?
Is this line intentionally included twice?
If so, what value does the second entry serve?