Any idea how you would like the CLI to look like for option 82 support?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Nov 3 2021
I use Microsoft NPS and it feels correct for me:
I also have some of those APU4 devices and they work actually pretty good. The reasons for those "low" defaults are actually not from VyOS but from the Linux Kernel itself.
Nov 2 2021
After the investigation, we figured out that it is possible to get the prefix and link-local address during the DHCP commit procedure.
The statement
log(info, binary-to-ascii(16, 8, ":", substring(option dhcp6.ia-pd, 24, 17)));
will give us the next info:
dhcpd[1568]: 40:20:1:ca:fe:11:11:ff:ff:0:0:0:0:0:0:0:0
So, a prefix can be extracted. Also, a link-local address may be generated from the MAC address extracted from the DHCP packet structure.
Possibly unrelated, but I'll leave it here
frr-reload output: 0 /usr/lib/frr/frr-reload.py:851: SyntaxWarning: "is not" with a literal. Did you mean "!="? frr-reload output: 1 if line is not "exit-vrf": frr-reload output: 2 2021-11-02 18:33:34,225 INF
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1060
set vpn sstp authentication local-users username foo password 'bar' set vpn sstp authentication local-users username foo2 password 'bar2' set vpn sstp authentication mode 'local' set vpn sstp client-ipv6-pool prefix 2001:db8::/48 set vpn sstp gateway-address '192.168.122.14' set vpn sstp ppp-options ipv4 'deny' set vpn sstp ppp-options ipv6 'allow' set vpn sstp ssl ca-cert-file '/config/user-data/sstp/ca.crt' set vpn sstp ssl cert-file '/config/user-data/sstp/server.crt' set vpn sstp ssl key-file '/config/user-data/sstp/server.key'
Check sessions:
vyos@r4-epa2:~$ show sstp-server s sessions statistics vyos@r4-epa2:~$ show sstp-server sessions ifname | username | ip | ip6 | ip6-dp | calling-sid | rate-limit | state | uptime | rx-bytes | tx-bytes --------+----------+-----------------------+-----------------------+--------+-----------------+------------+--------+----------+----------+---------- sstp0 | foo2 | 2001:db8:0:0:200::/64 | 2001:db8:0:0:200::/64 | | 192.168.122.222 | | active | 00:00:09 | 735 B | 506 B vyos@r4-epa2:~$
Additional note: this, of course, breaks the 'red' vrf connectivity.
If I manually add, using vtysh, the
vrf red vni 3000
everything on the 'red' vrf works fine.
Yes, It seems that rfc doesn't work , also I found this issues :
https://github.com/FRRouting/frr/issues/5824
@zoenan7 Sorry for the late reply! Yes, I got your email and could reproduce the crash using your PoC.
Mentioned here (FRRouting):
BGP vpnv6 next hop address maybe error?
Nov 1 2021
To enable IPv6 only it is required some new options in CLI, which are not presented in 1.3 yet
We keep this in 1.3 as the CLI is fixed - it was removed in the 1.4 development cycle with T3090
PR for 1.4 https://github.com/vyos/vyos-1x/pull/1058
For 1.4 it is impossible to set both dhcp + static in one commit.
set interfaces ethernet eth2 address dhcp set interfaces ethernet eth2 address 192.0.2.4/24
Oct 31 2021
Included this feature in the firewall/zone-policy rewrite: https://github.com/vyos/vyos-1x/pull/1033
In T3916#109326, @Viacheslav wrote:WIll be added in the next rolling release, @johannrichard could you test it?
This entries:
Same request: T292
Definitely miss behavior is generated by the new interface MGT that was created when assigning MGT vrf to eth0.