I can not reproduce this issue in 1.3-beta-202109050342 and 1.4-rolling-202109050613
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Sep 5 2021
Sep 5 2021
c-po moved T2434: Duplicate Address Detection Breaks Interfaces from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T2776: QAT acceleration not working for IPSec AES-128 (CBC) / SHA256 tunnel from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T2127: restart dhcp server reports a failure from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3196: No NAT translations showing up from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3275: Disable conntrack helpers by default from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3788: Keys are not allowed with ipip and sit tunnels from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3738: openvpn fails if server and authentication are configured from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3756: VyOS generates invalid QR code for wireguard clients from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3794: MACsec interfaces in down state after create from Need Triage to In Progress on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3708: isisd and gre-bridge commit error from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3730: op-mode conntrack-sync miss some functions from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3736: openvpn-option keeps and adds double dashes ''--" from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3768: Remove early syntaxVersion implementation from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3731: verify_accel_ppp_base_service return wrong config error for SSP from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3740: HTTPs API breaks when the address is IPv6 from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3776: Rename FRR daemon restart op-mode commands from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3772: VRRP virtual interfaces are not shown in show interfaces from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3781: Revert the NAT implementation in 1.3 back to iptables from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3777: adding IPv6 EUI64 address fails commit in 1.3.0-rc6 from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3782: Ingress Shaping with IFB No Longer Functional with 1.3 from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3790: Does not possible to configure PPTP static ip-address to users from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3789: Add custom validator for base64 encoded CLI data from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3783: "set protocols isis spf-delay-ietf" is not working from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
c-po moved T3797: show interface errors with vrrp configuration from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0-epa1) board.
GitHub <noreply@github.com> committed rVYOSONEXf695a70f8557: Merge pull request #996 from dmbaturin/ping-source-address (authored by c-po).
c-po edited a custom field on T3804: cli: Migrate and merge "system name-servers-dhcp" into "system name-server".
Here is the screenshot of vulnerability reproduction.
I tried to reproduce the vulnerability we found on v1.2.7 version of VyOS and debug the vulnerability, hoping to provide you with a detailed vulnerability report.
Sep 4 2021
Sep 4 2021
The patch worked up through vyos-1.3-beta-202108311126. It stopped
Restricted Repository Identity closed T3697: Impossible to delete IPsec completely as Resolved by committing rVYOSONEX38eaf24821da: Merge pull request #992 from dmbaturin/ipsec-settings-fix.
GitHub <noreply@github.com> committed rVYOSONEX38eaf24821da: Merge pull request #992 from dmbaturin/ipsec-settings-fix (authored by jestabro).
Client should also enable "SLAAC"
Works as expected it seems https://serverfault.com/a/918480 and https://teamarin.net/2018/06/25/common-mistake-dhcpv6/
Duplicate of T3772
- The problem about DHCPv6 has been solved
- The communication problem has been solved
jack9603301 moved T3778: Abnormal network communication and settings from Open to Finished on the VyOS 1.4 Sagitta board.
It seems that the problem is related to IPv6 MSS. When I set IPv6 MSS to 1280 and IPv4 MSS to 1452, the problem seems to disappear
Updated default response to "No"
I don't see any issue yet with multiple static addresses
vyos@r4-1.3:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
eth0 192.168.122.14/24 u/u FOO-BAR
eth1 192.0.2.14/24 u/u FOO
100.64.5.1/24
100.64.6.1/24
2001:db8::199/128adminuser@vyos:~$ show interfaces ethernet eth2
eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:bf:64:0b brd ff:ff:ff:ff:ff:ff inet XX.XXX.XXX.210/28 brd 98.187.179.223 scope global eth2 valid_lft forever preferred_lft forever inet XX.XXX.XXX.212/28 brd 98.187.179.223 scope global secondary eth2 valid_lft forever preferred_lft forever inet XX.XXX.XXX.213/28 brd 98.187.179.223 scope global secondary eth2 valid_lft forever preferred_lft forever inet XX.XXX.XXX.217/28 brd 98.187.179.223 scope global secondary eth2 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febf:640b/64 scope link valid_lft forever preferred_lft forever Description: WAN Network Interface
I was hoping to get that as well (and have in the past). What could be causing the problem?
c-po updated the task description for T3801: containers: do not use podman CLI to create container networks.