Hi @mbailey
thanks for reporting
you can use Paste app (on the left side of the menu)
set visibility to subscribers and set yourself and maintainers as subscribers
Also, do you know what runs neighbor?
If you can reproduce it, will be great to have tcpdump capture

I did a bit of digging on my R1 after reboot and I am seeing the following logs in Zebra, so it looks like it's completely unrelated to the neighbor deletion:

I have take a look and the todo would be:

You don't need this FEAT for others enforcing your ROAs. You need this FEAT to enforce received-routes on VyOS.

In T865#20843, @rherold wrote:

It would be nice to have it in 1.2 .x cause in the moment most poviders start enforcing it.

This is still a problem with vyos 1.2.0-rc2.

this is now fixed in 201810180337. Please test!
On my system ist runs without problems

There is a package in stretch https://packages.debian.org/stretch/bgpq3

Pull request: https://github.com/vyos/vyos-build/pull/28

verified via latest rolling iso.

Any further action on this?
I can't find any public images and this thread is a bit lacking in information.

Ahh, my mistake! Will remember that :)

My attempt to use github's editing GUI didn't go well, sorry for the poor commit description.

Oh, sorry, I misunderstood the issue. It's the "run show bridge brN" command that is not working, while the "run show bridge" command does.

It works for me, so we need exact reproducing steps.

I have the same problem here with 201810170747.
My router is without this firmware complete unuseable.

@dsummers no problem at all I found a few issues in the existing code, plus I had to read up on the virtio code as well :).

I just wanted to mention that the two problems I mentioned earlier had nothing to do with this issue.

I've redone the patch, it uses a simpler regex because we do not need mixed-mode. The main issue was it didn't validate lowercase. I had to split the host/mask parsing to do the cidr variant properly. I've added tests and it ran succesfully. PR#2

https://github.com/vyos/vyatta-cfg-system/commit/bf7fe3da15446eef6d5974d26106c130179c32fc
The function set_speed_duplex checks the setting via ethtool again and compares it with the requested ones, since virtio_net returns 'unknown', the setting have been applied only every 2nd commit.

Found another weird bug in the vyatta script, it applies duplex and speed only after 2 commits.

verified availability.
VyOS 1.2.0-rolling+201810160337

@JulesT want to look into that?

I'm seeing the same thing using a newer rolling version. My tunnels are up and can pass traffic.

vyos@cni-lima-iptv-vpn-1:~$ show vpn ipsec sa
Peer ID / IP                            Local ID / IP
------------                            -------------
remote                                  local

That needs to be handled with care, since the old perl script have some easter eggs in it.

https://github.com/vyos/vyos-build/pull/26