@Viacheslav we need to port this to 1.2 too
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 17 2021
Oct 16 2021
The router does not automatically configure the prefix route that the client received. If you use the client's link-local address for the prefix route then everything works. The client also uses the dhcpv6-server link-local address for the default route.
https://github.com/vyos/vyos-1x/pull/1028 — though probably needs some tests developed?
Oct 15 2021
@artooro Will be available in the next rolling release
Let us know, if you want some other capabilities
Sorry for the late reply, I've been waiting for a maintenance window to test this in. Again as this is a production device I only have limited debug info before having to roll back to the working version. I installed 1.4-rolling-202110150613 and on booting show interfaces does indeed show all the interfaces. The igb driver interfaces were showing as up (u/u). The i40e interfaces were showing as down (u/D).
Maybe be added to gether with T1229
@maznu Can you create a PR?
Initial bug was Fixed, VyOS 1.4-rolling-202110130217
vyos@r1-roll# compare
[edit container]
+name dns02 {
+ image ubuntu:focal
+ network dnsnet {
+ address 10.0.72.253
+ }
+}
+network dnsnet {
+ prefix 10.0.72.0/24
+}
-network net01 {
- prefix 10.0.72.0/24
-}Why not always move to decimal output and detect on demand if colons are present or not and adjust the string? Ne need for the user to take any action at all?
Oct 14 2021
Yes, closing this ...
@c-po Is it already implemented with commit https://github.com/vyos/vyos-1x/commit/ae2dc55aa68679e828d4bb133fc515172c081d0f ?
Fixed, VyOS 1.4-rolling-202110130217
vyos@r1-roll:~$ show nat source rules Rule Source Translation Outbound Interface ---- ------ ----------- ------------------ 3 192.168.0.0/24 masquerade eth0
Is a double task, it looks like the package is not update upstream.
Maybe, but if the effort is made in order to be able to configure log level, it would be good that it can be set in different levels.
I'm thinking in a mix scenario, where majority of rules may log with info/debug level (for example default accept rules), while other rules may need a warning/error level (some drop rules).
As for me, it should be configured in the global firewall log level, not per rule.
set firewall log-level x
For this we create text files as the group-config includes (they contain route and other per group config directives, generally around security).
Oct 13 2021
If I change the double-quotes to single-quotes for all the rules in that firewall, I get this (no changes detected):