I can see the fix, but now trying invert selection on tcp flags doesn't work
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jan 16 2022
Testing this feature in VyOS 1.4-rolling-202201100317 I'm getting some unexpected behavior.
Config:
For full support we need this added to FRR: https://github.com/FRRouting/frr/pull/9204
Jan 15 2022
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1172
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1170
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1170
Re-tested in VyOS 1.4-rolling-202201140317
Now it works, thank you!
Jan 14 2022
@NikolayP Could you re-test it?
Some detail here T1280
@sdev: in your original commit for this task, recent rules are somehow semi-discarded (the time/counter condition will not be written out; however, the action will be written out) because of an apparent problem with nftables in this area.
Thanks; I just tested commenting out line 5 of that file, and it successfully works around the issue, allowing me to set a link-local IPv6 address as my endpoint. The wireguard connection itself also works, and I can pass traffic.
@odhnera Try to comment or delete the validation string and restart vyos-configd service
Jan 13 2022
Getting link-local addresses to work would probably be very low-priority, but I did run into an extremely niche case where I wanted to do that. It's not the type of situation that would happen in a production environment, but I was running VyOS on a computer tethered via ethernet to an Android-based phone, and I wanted to connect to a wireguard peer running on the phone. Modern version of Android randomize the IPv4 address of their tethered interface on each reboot, but their link-local IPv6 address remains the same, making it more convenient to use it.
Link-local addresses with %ethX are not accepted in any protocols/peers/etc. A few services are allowed to set them as listen like ssh/dns at the moment.
Is there a real use case why you need it on wireguard interfaces?
It generates by openvpn, maybe something new in the new OpenVPN version
So I see only one option - add mode server-bridge
@hensur I'm glad you reimplemented this feature. Come on
See comment in T4164: is working now.
See comment in T4164: my config runs through easily now.
@sdev this (and the other fixes) look promising: after upgrading to the latest rolling release from 13.1.2022, both the example provided in the ticket as well as my config (a copy of my production setup with rules covering PBR, empty groups, references to "defines" in PBR rules) ran through easily. My production config created no errors when loading the config after the update.
Thanks for the report, working on the fix now.