thanks Kim

@Line2 I will look at it!

@UnicronNL Yes, exactly that is what is discussed in T440.

@Line2 What do you mean?
This is only for dhcp ip renewals or disconnected interfaces.

is this change only VyOS local interface with dhcp address? Not related to T440 (FQDN peer)?

I made it.

Do you have an iso to test? I tried latest rolling and also my own iso built from current and i continue to see this issue.
It makes transitioning to 1.2.0 impossible at this moment. Still at 1.1.8 on the routers.

FRR 7.0 was released three days ago.

I tested the current release and the issue still exists.
After adding staticd=yes on a reboot everything seemed to work.
More specific routes work even when a larger blackhole route is present.
However adding a new blackhole route while more specific routes exist (and work fine) stops them from working. The new blackhole routes get loaded and supress the more specific routes.
Removed a blackhole route allow other routes to work even when they are not part of the blackhole route.

No further complaints - seems to be resolved.

okay - then I kindly close this one.

Awesome, thx.

We've not had this issue since i applied the patch.

@hagbard last rolling has no issue.
everything works as expected

@thinkl33t any updates?

@oleksandr.ovsiannikov any updates?

In T1247#32887, @oleksandr.ovsiannikov wrote:

@hagbardIt fixes the issue with WANLOADBALANCE_PRE chain, but we still observe unexpected behavior.
I will write a little bit more letter.

this solve the issue

Thanks for testing. New rolling has been built as well.
https://downloads.vyos.io/rolling/current/amd64/vyos-1.2.0-rolling%2B201902142225-amd64.iso

With new package all works fine.

Please test http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-wanloadbalance/vyatta-wanloadbalance_0.13.69+vyos2+current1_amd64.deb or latest rolling release.

@kroy by using chroot and trying to install the vyatta-cfg-quagga package i found out what is causing my build iso error:

@Maltahl just re-tested this, with the staticd=yes added, and a reboot done.
When i add two static routes i would expect the /24 route to work because it is more specific. But is does not and show ip route shows only the /23 blackhole.

@Maltahl for me it was not fixed with that addition, and i read above that others had this as well.

i tried doing complete reinstalls and i can now confirm this bug as well.

Strange. I’ve seen that error a lot. Every time it’s been when I’ve forgotten to checkout current after cloning the repo.

@kroy everything is at current, except 'frr' because then i get 7.1dev and i would like 6.0.2 to test if this solved it.
I used debian/master branch from FRR.

@Merijn make sure you git checkout currenton everything.

I am experiencing the same issues with a router i tested with 1.2.0 current.
Can we create a test release going back to FRR 6.0.2?

Implemented in latest rolling and backported to Crux branch for 1.2.1

An easier solution is to wrap the test in ' like use-web='this is your IP'

After some digging this is what I found out with VyOS 1.2.0-epa3:

Yes

@c-po you can proceed with the removal

@c-po want to handle this yourself or need @dmbaturin participation?

need to build kb article for process

Hello, @adestis!
You can use values from 5 to 100. 600 is unsupported in current FRRouting.

In T1218#32229, @kroy wrote:

@lbv2rus

Yeah, it wasn't really a workable solution for me either and I too had to roll back. But it would be good to confirm that is the problem.

Yeah, it wasn't really a workable solution for me either and I too had to roll back. But it would be good to confirm that is the problem.

In T1218#32227, @kroy wrote:

@lbv2rus There might actually be a few problems here. We might have hacked out that it's the interface-route with the custom routing table that's causing the problem.

Removing that should bring back static routes.

@lbv2rus There might actually be a few problems here. We might have hacked out that it's the interface-route with the custom routing table that's causing the problem.

I can confirm, that fresh installed instance of 1.2 do not add static routes, include default route.
After deleting all "protocols static" section and recreating it manualy, only default route is added.
But, after reboot no default route is set.

Ah, there was a similar issue with dhcp last couple of weeks where quotes broke the config (T1129). Can you try using &nbsp instead of your whitespace?

if we use a more simply string without blank as e.g.

skip "yourIP"

all seems OK. So I think there is some problem in parsing a whole quoted string.

just what I've post
dynamic {

interface eth1 {
    service dyndns {
        host-name xxxxx.mine.nu
        host-name yyyyy.dnsalias.com
        login someuser
        password somepsw
    }
    use-web {
        skip "this is your IP"
        url http://www.web.net/GetRemoteIP.asp
    }
}

}