Implemented in
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 10 2021
The DUID is presented in binary inside /var/lib/dhcpv6/dhcp6c_duid to read it back into ASCII use: hexdump -e '"%07.7_ax " 1/2 "%04x" " " 14/1 "%02x:" "\n"' /var/lib/dhcpv6/dhcp6c_duid
Oct 9 2021
You are right @NikolayP but opening an entire subtree might be a bit of overkill.
Oct 8 2021
Perhaps the command should be changed a bit
MSS is a property of the TCP protocol, not IP:
@dmbaturin Did you get my email? If not, please let me know and I will send it again
@RyVolodya can you check a new image and close this task if it was fixed?
Oct 7 2021
We usually communicate via https://vyos.slack.com
or matrix
sure I will just create a separate VM with a clean VyOS and the card - you got some sort of irc or discord to communicate?
Any chance to get remote access to the system to debug this?
Problem solved and it was my mistake.
Oct 6 2021
Suricata IPS with ipset
Oct 5 2021
Yeah, that seems reasonable to me. I would prefer not add clutter to the system node if it can be avoided.
Should we expose a system-level DUID at all? If a user wants to customize it, they could always set it on a per-interface basis using the existing configuration node.
That seems fair, basically make the DUID generation deterministic. There is some defined structure to the DUID format, I think this would be a "type 3 DUID" per this document: https://www.juniper.net/documentation/en_US/junose15.1/topics/concept/dhcp-unique-id-servers-clients-overview.html.
Oct 4 2021
Can we close it @Viacheslav?
what about the following:
- Add a new system ipv6 duid CLI node which acts as the general DUID used on the system and renders /var/lib/dhcpv6/dhcp6c_duid, if not overwritten at the "interface" level set interfaces ethernet eth0 dhcpv6-options duid
- If system ipv6 duid is not configured, we "generate" the DUID using the eth0 MAC address automatically and store it in /var/lib/dhcpv6/dhcp6c_duid - thus no issue on image upgrades anymore
Hi c-po,
Submitted this PR: https://github.com/vyos/vyatta-cfg/pull/42
Oct 3 2021
Can you check the MAC address of the card not that the interface got mixed up in their naming?
Oct 2 2021
Package was upgraded to PDNS 4.5 should be fixed - can you please retest with ANY release AFTER
- vyos-1.4-rolling-202110020217-amd64.iso
- vyos-1.3-beta-202110020342-amd64.iso