@c-po While I was wrong about the MSS clamp not being applied, the missing clamp-mss-to-pmtu feature and the incorrect MSS limits are both still problems that PR 1557 addresses. I believe we can close this after those issues are addressed.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Dec 14 2022
Dec 13 2022
Dec 12 2022
As I understand it is impossible directly with config option but possible with module omudpspoof
It works. The user connections persist over a reload and configuration changes causes a reload instead of a restart!
Thank you.
Dec 11 2022
@initramfs can we close this?
vyos@vyos# show interfaces sstpc
sstpc sstpc10 {
authentication {
password vyos
user vyos
}
server sstp.vyos.net
ssl {
ca-certificate VyOS-CA
}
}Hi,
same issue on VyOS 1.4-rolling-202212090319
Dec 10 2022
Dec 9 2022
Started a PR for this: https://github.com/vyos/vyos-1x/pull/1702
PR with fix is here: https://github.com/vyos/vyatta-cfg-firewall/pull/35
@klase It is already in the latest rolling release. Could you re-check?
This works,
but if this is the new syntax the cli needs some cleanup.
According to this https://forum.vyos.io/t/vagrant-auth-failure-on-new-vagrant-images/9871/2
This issue is due to T874.
My understanding is that is not changeable, so my proposal is to add the "vagrant insecure key" for the vyos user during the vagrant box creation.
use the next syntax
show bgp ipv4 neighbors x.x.x.x advertised-routes
Dec 8 2022
PR for show/reset functions:
https://github.com/vyos/vyos-1x/pull/1699
fix for 1.4 PR https://github.com/vyos/vyos-1x/pull/1698
vyos@r14# cat /run/accel-pppd/l2tp.conf | grep dae-s dae-server=127.0.0.1:1700,testing123 [edit] vyos@r14#