@EwaldvanGeffen can i mark this as solved?

can you add required nodes for this maybe
@UnicronNL please assist

@dmbaturin please review and merge in

i removed serial device in OVA

@dmbaturin @UnicronNL please review and merge in

@dmbaturin can you merge it in

@c-po can you look into this please

I'll check, meanwhile, could you verify that you still see this issue in the latest build?

@aopdal try latest nightly as we pushed changes related to vrrp

package is now in the vyos repo and used in images

@syncer I am the unofficial maintainer of the Squid-Cache RPM's and DEB packages and doing it for more then 4 years now.
These days network routers are actually Route Servers and only the low cost devices doesn't contains any form of proxy functionality on them.
If you need a simple IP router you don't need it and this is most of the use cases of YVOS to my knowledge.
However we might be able to compromise on something in the middle instead of ditching it or other proxies.
Squid-Cache is good for caching but very old so for filtering there are couple other more efficient solutions and also the nature of the Internet HTTP world have changed so caching is good only for very specific purposes...
So I think that it would be a nice to have but if it's possible to allow the admin configure Squid or another proxy outside of the configuration shell it would be a better solution.
Also if you want to intercept traffic into squid you can just use DNAT rules.

I use squid as a caching proxy to very considerably speed up patching and non-encrypted static web content. I also use the blacklists which are updated every day. While VyOS with Squid and Wifi is a very good integrated router for home and SOHO, I also use it as building bloc for sample firewalls you encounter in corporate environments in several showcases.

Does anyone have any ideas how to get VRRPv3 in 1.2?
If we could conclude on the approach we could go further by describing cli commands, make out how the upgrade should be done, create documentation and so on.

support added,
only need Jenkis up to build te kernel.
https://github.com/vyos/vyos-kernel/commit/b72a65de9fd1c68c8d371152cfdcbc85d2b0dbd9

@ebob9 Thank you! It's very helpful.

Played with the VHD and attempted to make it an image that could be deployed as a template. Looks like the following is lacking currently to allow provision support:

• No support for provision credentials (that's ok for me)
• WAAGENT can't ever report provision success to azure.

Probably not the best place to ask, but can anyone guide me the steps to build VyOS 1.2 with frr. I have built the latest source but it still comes with quagga (and without IS-IS support which is enabled in 1.2 alpha image).

Anyone having any ideas to how to solve this problem?

Unfortunately this does not properly work as debian live-build can not distinguish between ISO and IMAGE because both are actually the same.

@dmbaturin do you know what is for?

Worked, thanks
https://wiki.vyos.net/wiki/User_Guide#mDNS_Repeater

After removal of telnet configuration nodes/scripts and upgrading from VyOS 1.1.8 with telnet enabled worked.

Installing VyOS 1.1.8 on RAID1 and later on upgrading to 1.2.x works. Also the RAID set is intact.

vyos@vyos:~$ cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda1[0] sdb1[1]
      4190144 blocks [2/2] [UU]

whitelisted again,
buggy system, try in 10 mins or so
hopefully will work this time

Still the same

try again please

I wanted to add the following into the WiKi

TODO: Add CI job for https://github.com/vyos/mdns-repeater when CI is back online

Using AVAHI as mDNS reflector has the big disadvantage that the reflection interface can not be specified. It will reflect the mDNS messages on ALL interfaces. Mdns-reflector does not have this problem. It needs to be configured which interface is used for repetition. Configuration is planned for vyos-1x package.

https://github.com/zevlag/pfsense-ports/tree/master/pfSense-pkg-zerotier
https://docs.opnsense.org/manual/how-tos/zerotier.html

Is this really an issue with 1.2? It looks like FRR 2.0 is what vyos-frr is based on and FRR 2.0 appears to have support for BGP AddPath.

After some discussion surrounding similar issue in IRC recently, I believe FORWARD is the correct place for this, and 'set-mss' should be configurable in a rule which can specify one or both of input *and* output interface to allow proper expression of explicit MSS for inbound and outbound connections.

trivial patch

Ah ok, maybe that not the case than

Each time a new image is added via add system image GRUB configuration is triggered.