Thanks! This is definitely a non-issue then, closing.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 6 2021
Since we cannot update the kernel in 1.3 due to the QAT issues, we likely need to backport netmap support. It seems to have been introduced by this commit: https://github.com/torvalds/linux/commit/3ff7ddb1353da
@maznu
Add these lines:
Thank you for pointing that out - updated defaults.json and it seems to have made that issue go away.
For some reason its now breaking on using our internal repo (no TLS there, inside the datacenter), but i suspect its got something to do with the repo itself or some change in Debian since we started using it.
I've tested it on 1.3 with kernel 5.4.138, and for me the persistent option works as expected. I think it's a non-issue for equuleus already and the task can be closed, though I'd like other people to test that first.
Not having much luck with the build environment — and it doesn't seem to be something I've caused, because I get the same error building vyos-1x from mainline:
@stepler interesting - this bahavior changes when running from frr-reload vs. vtysh.
I think all that is required is in: https://github.com/maznu/vyos-1x/commit/68d7897622ddaa4b2e5a98d79154500b33959567
Hello, @Dmitry, I agree. I'll prepare patches for 1.3 and 1.4.
Unhelpfully it looks like Salt has changed repo: https://repo.saltproject.io/#debian
Hello @maznu , I also prefer the first variant set vpn l2tp remote-access lns host-name example.com I'm sure that we no need to overload l2tp remote-access root noded
Aug 5 2021
Made the change to "do" and I noticed that.....DF is used even if there is no DF bit explicitly set...:
It seems the man page that I looked at I either didn't read carefully enough, or I completely messed it up. You're right @Viacheslav.
Did a quick test...
Already rewritten in 1.4 and 1.3 T3535
https://phabricator.vyos.net/rVYOSONEX21527ef4551613fe9b7eed9e4b2ce33ad46fe540
Hmmmm....it worked last time. I'll give it another run.
Reopen
It doesn't work properly
ipsec start error ..
It is not critical, please test without this package "libstrongswan-standard-plugins"
All necessary data is already installed.
Setting up libstrongswan (5.7.2-1) ... Setting up libstrongswan-extra-plugins (5.7.2-1) ... dpkg: dependency problems prevent configuration of libstrongswan-standard-plugins: libstrongswan-standard-plugins depends on libssl1.0.0 (>= 1.0.2~beta3); however: Version of libssl1.0.0:amd64 on system is 1.0.1t-1+deb8u14.
I have patched packages for 1.2.8. It works on my routers in the virtual environment.
Instruction:
- Upload package to the router
- Unarchiv it
sudo tar -xvf strongswan.tar
- Install packages
sudo dpkg -i *.deb
- Reboot router or reconfigure IPSec
As I understand there are 2 bugs:
- It expected --iroute-ipv6, i.e
iroute-ipv6 2001:470:1f14:af1:: ffff:ffff:ffff:ffff::
- Something wrong with such format (ipv6 address/ ipv4 mask)
ifconfig-push 2001:470:1f14:af1::2 255.255.240.0
Aug 4 2021
@SrividyaA does this configuration work or not?
set interfaces openvpn vtun10 encryption cipher 'aes256' set interfaces openvpn vtun10 hash 'sha512' set interfaces openvpn vtun10 local-host '10.2.0.15' set interfaces openvpn vtun10 local-port '1194' set interfaces openvpn vtun10 mode 'server' set interfaces openvpn vtun10 persistent-tunnel set interfaces openvpn vtun10 protocol 'udp' set interfaces openvpn vtun10 server client client1 ip '2001:470:1f14:af1::2' set interfaces openvpn vtun10 server client client1 subnet '2001:470:1f14:af1::/64' set interfaces openvpn vtun10 server push-route '2001:db8:0:abc::/64' set interfaces openvpn vtun10 server subnet '10.140.0.0/20' set interfaces openvpn vtun10 server topology 'subnet' set interfaces openvpn vtun10 tls ca-cert-file '/config/auth/ea1/ca.crt' set interfaces openvpn vtun10 tls cert-file '/config/auth/ea1/central.crt' set interfaces openvpn vtun10 tls dh-file '/config/auth/ea1/dh.pem' set interfaces openvpn vtun10 tls key-file '/config/auth/ea1/central.key'
I don't see this bug in 1.3.0-rc5,
Aug 3 2021
@stepler I created https://github.com/FRRouting/frr/pull/9281 for "easier" debugging
OK , Thank you!
I tried this locally and you can do no router bgp 100 vrf blue before no vni 2000, my vtysh instance does not scream for an error - it more feels like a programming issue on our side.
In T2851#99364, @lawrencepan wrote:
sudo ip rule add prio 219 from 192.0.2.48/30 to 192.0.2.48/30 lookup main }
As a workaround it can help in such cases:
I get the same issue in 1.2.8.