Some more issues with FRR 8.1
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Nov 28 2021
Nov 27 2021
Nov 26 2021
Require rewriting vyatta-config-mgmt to XML/Python
Tested with the latest rolling version: "1.4-rolling-202111240711"
Nov 25 2021
@NikolayP Can you play with it?
In T3976#112210, @Viacheslav wrote:Already implemented in FRR 8.x, so for first, we should migrate to FRR 8.x if it is possible T3753
Already implemented in FRR 8.x, so for first, we should migrate to FRR 8.x if it is possible T3753
We try not to use "raw options" of commands.
But I don't see another universal solution for it.
Added the PR for equuleus https://github.com/vyos/vyos-1x/pull/1085
I've tested root-partition-auto-resize on GCP, AWS and Azure. It was found that disk extension on Azure brakes GPT table, so I added the fix in this PR https://github.com/vyos/vyos-1x/pull/1084 .
Nov 24 2021
Opened https://github.com/vyos/vyos-1x/pull/1083 which fixes this issue
I have a fix that will make it send a single item list and pass the validation check
The plan is to weaken this to a warning in 'verify'; as summarized above, validators are pass/fail and warnings are not an appropriate response for a validator
Also, fixed certificate files check. PR https://github.com/vyos/vyos-1x/pull/1081
Still works perfectly fine for 1.3 nightly. (1.3-beta-202111240443)
Brilliant, thanks @c-po!
@marc_s I ensure that there is always a volatile folder used for those PIDs
@c-po I see that you've marked this as resolved, but I don't see any comments (maybe I'm doing something wrong). I'd appreciate some feedback.
Is it resolved as in: will be fixed as soon as third-party code is fixed? Or have you made changes to the code to mitigate?
Nov 23 2021
As the first step:
PR fo equuleus https://github.com/vyos/vyos-build/pull/205
PR for current https://github.com/vyos/vyos-build/pull/204
Nov 22 2021
PR ready for current https://github.com/vyos/vyos-1x/pull/1076
Nov 20 2021
Has been fixed in latest rolling version:
I think this is what it would look like in service dhcp server. I left some comments to explain my thinking a bit, and I tried to make it as flexible as possible (for example the way match options are strings, so future DHCP options can be supported as soon as ISC supports them):
failover {
name INT
remote 192.168.15.4
source-address 192.168.15.3
status primary
}
shared-network-name INT {
description "Internal connection to ir01"
class CLIENT_MAP {
rule 10 {
action permit # This is equivalent to dhcpd's allow/deny members of
match option "agent.circuit_id" value "Vlan200" # This could match any option (ex: dhcp-client-identifier)
}
}
class GUEST_MAP {
rule 10 {
action permit
match option "agent.circuit_id" value "Vlan240"
}
}
subnet 192.168.1.0/24 {
class CLIENT_MAP
default-router 192.168.1.1
domain-name int.trae32566.org
domain-search int.trae32566.org
domain-search ipa.trae32566.org
domain-search trae32566.org
enable-failover
name-server 192.168.255.1
name-server 192.168.15.10
name-server 192.168.31.3
ntp-server 192.168.255.2
ntp-server 192.168.15.11
ntp-server 192.168.31.4
range CLIENTS {
start 192.168.1.2
stop 192.168.1.240
}
server-identifier 192.168.15.2
static-mapping QUEST {
ip-address 192.168.1.17
mac-address 80:f3:ef:11:e7:e7
}
}
subnet 192.168.6.0/24 {
class GUEST_MAP
default-router 192.168.6.1
enable-failover
name-server 1.1.1.1
name-server 1.0.0.1
name-server 8.8.8.8
ntp-server 50.205.57.38
ntp-server 64.225.34.103
ntp-server 129.250.35.251
server-identifier 192.168.15.2
range GUESTS {
start 192.168.6.2
stop 192.168.6.254
}
}
subnet 192.168.15.0/29 { # This tells it indirectly to use the interface eth2, which is on this subnet (is there a better way?)
default-router 192.168.15.1
enable-failover
range DUMMY {
start 192.168.15.2
stop 192.168.15.7
}
}
}Nov 19 2021
I would not call this a bug as this is produced on intention.
Submitted this PR: https://github.com/vyos/vyos-1x/pull/1075
I wish I understood this subsystem better as I'd love to get it fixed. I'm going to take a closer look tomorrow