- User Since
- Feb 6 2019, 6:22 PM (107 w, 3 d)
Sun, Feb 21
Hmmm I retract that, apparently not in my configs. But that review indicates that a common pattern is to define the VRF at a global level, then specify an instance at the BGP level...
@c-po not in constrat to other verndors - I know that Juniper ERX allowed for different ASNs if in a VRF. I'll see if I still have some old configs.
Mon, Feb 1
There's an easy workaround to hack this into your "configure" scripts:
Jun 18 2020
No, seems to be fixed! I was pretty sure it was upstream, must be resolved now.
Aug 31 2019
Thanks!!!! I'll test it once it's pulled...
Aug 22 2019
Does this mean it'll make it into Crux soon?
Jun 21 2019
Oh, er, forgot to mention that the exact same configuration worked perfectly when run on the version of Crux compiled on 2019-06-16.
Apr 24 2019
Hmmm, yeah, this one isn't doing anything yet either - just a test.
Ah, Thanks Merijn!
My next step is to replace the VMWare image with the standard ISO I build at the same time, to eliminate vmtools. I tried reducing the open-vm-tools config statement:
I am also seeing a memory leak on a BGP full tables router. It is NOT using flow accounting, but IS a Crux 1.2.1 compiled VMWare image.
Feb 6 2019
Even in a shut down peer, even with no route-map set, I still get that message.
This is not a Vyos issue - adding the same thing in vtysh does the same thing.
I encountered this same problem: I saw the output: