- User Since
- Oct 12 2018, 10:21 PM (111 w, 4 d)
Oct 17 2020
Jul 4 2020
for me it looks like a name lookup error. I have read the forum entry mentioned above. And they fixed it by disabling name lookup.
Jun 8 2020
May 21 2020
Apr 23 2020
Feb 28 2020
looks for my like an frr bug. Has someone contacted upstream?
Feb 23 2020
removing the check makes it work like a charme push request incomming..
run into the same. If I add parameters default 'no-ipv4-unicast' to my config and commit I get the waring above. All runs fine, cause the sessions where already configured before.
If I do a reboot, bgp config in frr is neartly empty only "router bgp 64512" was there not more. Removing it and do an commit nothing changed. Removing it an reboot helped.
Feb 21 2020
Pull Request: https://github.com/vyos/ppp-upstream/pull/2
Feb 20 2020
I send a pull request to fix it:
Feb 12 2020
I think we should make somewhere a list of services and which level of vrf support they have.
Openssh for example has build in support for vrf
Could be away. But from my experience most people use vrf to seperate managment from production, and as second prio seperate customers and so on.
But the managment vrf must not be the "default" vrf.
Jan 2 2020
I got this on two production systems on the next two I migrated I changed my workflow to:
Nov 12 2019
In this way we could also add vpp nat64 running complete in vpp independent from all other vyos services:
Nov 10 2019
Oct 9 2019
@cpo cumulus behave differently cause they use an other implementation as in pure frr. They use PTMD see https://docs.cumulusnetworks.com/cumulus-linux/Layer-3/Bidirectional-Forwarding-Detection-BFD/ and https://github.com/CumulusNetworks/ptm
Sep 24 2019
Seems that it s merged an in 1.2.3 it looks in the moment good for me:
Sep 18 2019
Seems that upstream did not backport the fixes to the stable version's. So it is only included in frr 7.2.
I asked them for backport.
Aug 8 2019
You can add a community via route-map to your outgoing routes.
Aug 2 2019
I have setup two vyos router and one is origination default.
All runs fine with this patches since more then 40 minutes so it fixes the problems.
Jul 31 2019
Can we make a nightly with the patches from:
Jul 30 2019
https://github.com/vyos/vyatta-op-quagga/pull/3 I hope now it looks better
Jul 29 2019
https://github.com/FRRouting/frr/pull/4742 let's give it a try?
Jul 25 2019
Some Feedback from the frr people:
Jul 23 2019
Run into the same with 1.2.2
Jul 15 2019
I created a pull request to fix it. @guertinf has already test the fix
Jul 6 2019
Jul 5 2019
For my point of view this is a dependency from the bfd protocol specs.
Jun 27 2019
May 30 2019
I have added the Documentation:
As far as I can see it is included in 1.2.1 so we can close this or?
If yes I will submit a config example for ospf ip unnumbered that uses it
May 29 2019
https://github.com/vyos/vyatta-cfg-quagga/pull/27 < -- seems to look better
May 28 2019
See my pull request: https://github.com/vyos/vyatta-cfg-quagga/pull/26
can it be that the fix for T1243 is broken? I can understand that local-as can't be the same like remote-as if router-as diff from local-as but the patch forbit to set remote-as to the same like router-as that will break ibgp
May 20 2019
I want to build a setup like described in:
Mar 26 2019
@dmbaturin can you explain why we schedule it to the next release and not to 1.2.1 for example? Are there any policies?
Mar 25 2019
I want write an follow up.
Mar 21 2019
seems so but:
Mar 17 2019
Here is the current frr documentation:
Mar 3 2019
Sorry found it.
Feb 26 2019
Would it be possible to add an option to bind an specific interface to an routing table?
I have tested the scenario above and create only the routing table via protocol static.
After this I manual add:
Feb 24 2019
I added a log rule to:
why do we use fwmark in this case? As far as I can see ip rule give us all needed selectors:
Feb 18 2019
@TriJetScud please see :
Jan 24 2019
can reproduce ob EPA3:
Jan 21 2019
Can't reproduce with EPA3
Jan 18 2019
Jan 11 2019
@syncer thats not true:
Jan 10 2019
Was it not RC6 which got 4.19.0? If I read the kernel changelog right there where some other problems with igb fixed in this area ....
Also I found https://ubuntuforums.org/showthread.php?t=2404431.
Jan 8 2019
Please unbreak now. The next test date was announced!!
Jan 6 2019
Jan 5 2019
@merjin @c-po please have a look to the debian wiki page especially to the mibs-downloader.
Jan 4 2019
We should have an eye on https://community.openvpn.net/openvpn/ticket/208 cause this will change the config logic again completly.
It is not a bug in VyOS self. If you look inside the description of this oid:
Thx for the feedback indeed it runs much better with the virtio-net driver. Bit the e1000 is the default if you choose Debian as OS in Virtualbox.
VyOS is not available in Virtualbox as OS Template. I think we should try to get an own template with nice defaults into Virtualbox. Should I open a case
in Virtualbox for it? Do we have a list of settings that would be optimal for an VyOS vm?
Jan 3 2019
Dec 12 2018
Please go direct to version 1.0.3 cause:
Oct 20 2018
pdns recursor is from the same people who writes dnsdist.
There are three products wirh diffrent scopes:
There is no way to signal DOH (DNS over HTTP/S) via dhcp.
DOH and DOT is supported in latest dnsdist packages see https://dnsdist.org/ and https://mailman.powerdns.com/pipermail/dnsdist/2018-August/000466.html.
Oct 19 2018
As far as I can see it is enabled by default in recent frr:
Oct 18 2018
I will bring this up again. We have now in 1.2 all we need.