- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 14 2021
Apr 13 2021
- A̶d̶d̶ ̶c̶h̶e̶c̶k̶s̶ ̶t̶o̶ ̶p̶r̶e̶v̶e̶n̶t̶ ̶s̶e̶t̶ ̶i̶p̶ ̶a̶d̶d̶r̶e̶s̶s̶ ̶f̶o̶r̶ ̶c̶o̶n̶t̶a̶i̶n̶e̶r̶ ̶o̶u̶t̶ ̶o̶f̶ ̶r̶a̶n̶g̶e̶ ̶"̶p̶r̶e̶f̶i̶x̶" done
set container name alp02 image 'alpine' set container name alp02 network NET01 address '192.0.2.1' set container network NET01 ipv4-prefix '10.0.0.0/24
error
time="2021-04-14T00:52:03+03:00" level=error msg="Error adding network: failed to allocate all requested IPs: 192.0.2.1" time="2021-04-14T00:52:03+03:00" level=error msg="Error while adding pod to CNI network \"NET01\": failed to allocate all requested IPs: 192.0.2.1" Error: unable to start container "60f20a2b517b4f828bef5683cd8a20504aa984648a0911f7f8df5c1a064d2625": error configuring network namespace for container 60f20a2b517b4f828bef5683cd8a20504aa984648a0911f7f8df5c1a064d2625: failed to allocate all requested IPs: 192.0.2.1
The issue exists because the ifupdown package that is required for the eni renderer was removed by the https://github.com/vyos/vyatta-cfg-system/commit/3dd837f2d3518b7ddcf8e1ab68d8ab9f3eff0968
To not take back it again for all the platforms, the problem was resolved by the https://github.com/vyos/vyos-vm-images/commit/090e5367dc6df9b49c037e0b60f7adfafdf54a53 , so all the images created with the vyos-vm-images should not contain the problem with the renderer.
This task must be obsoleted by the https://phabricator.vyos.net/T2116
Just a small update on this.
PXE boot service for all 1.2 / 1.3 / 1.4 versions is up and running in private testing.
looks like this was missing in the bgp template
manually adding to /usr/share/vyos/templates/frr/bgp.frr.tmpl:
{% if afi_config.as_override is defined %} neighbor {{ neighbor }} as-override {% endif %}
Apr 12 2021
UPnP is something I require (as a home user with multiple gaming systems), so I'm very happy to see this making progress in VyOS. I've been getting tired of the mess over in pfSense/OPNsense-land, wanting to try a Linux-based router, and I'm familiar with VyOS from past experience with "EdgeOS" on Ubiquiti hardware so it was on the top of my list, but held back by lack of UPnP in the past.
Thanks!
@danhusan that PR was only done to current and not backported. I just packported it to the crux branch.
Sorry for the late reply, I've dismantled the setup as I needed to put the PPP link back in use, I will look into it again tonight. In essence, it would be good to see something like this on terse view:
sudo journalctl -b
lspci -knn
The reason these validations https://github.com/vyos/vyos-1x/blob/aca3254d96d01cc37c9e15e02e500a36f3708959/interface-definitions/vrrp.xml#L220-L224
There is no such problem in version 1.4.
@Viacheslav 1.2.7.
@c-po I expected this to go into 1.2.7 but it did not. How would I tag this properly so it hopefully makes it into 1.2.8?
Apr 11 2021
This can be close. The commit is working again after upgrading to the latest rolling
Submitted following PR:
Apr 10 2021
@dtoux could you provide us with a mocked up output what you would like to see?
frr-reload output: 184 % Cannot have local-as same as BGP AS number
Apr 9 2021
@olofl which version?
This issue seems to have gone away or I haven't noticed it recently.
I cannot reproduce this on VyOS 1.4-rolling-202104062128. Instead, on that version, ipv6 address autoconf commits, but the interface never picks up a v6 address.
Works! Thanks!
Add PR with improvements to documentation https://github.com/vyos/vyos-documentation/pull/503
Thanks. I think the main issue is missing required modules in the generated pppoe server config file
sudo cat /run/accel-pppd/pppoe.conf ### generated by accel_pppoe.py ### [modules] log_syslog pppoe shaper chap-secrets ippool auth_pap auth_chap_md5 auth_mschap_v1 auth_mschap_v2
Required
ipv6pool ipv6_nd ipv6_dhcp
These option enables by the foloowing CLI command::
set service pppoe-server ppp-options ipv6 allow
Even when setting above command I have no IPv6 address assigned.
Apr 8 2021
It looks like the same nature of this issue https://phabricator.vyos.net/T3393
@c-po , could you try to test fast solution
configure set system sysctl custom net.ipv6.conf.default.addr_gen_mode value 0 commit
Looks like that is actually working.
Oops, I did not see that. Thanks.
I modified bgp.frr.tmpl, but systemctl restart vyos-configd did not seem to do anything. Rebooting the router produces the correct config:
@linuxludo thanks for the heads-up - should be fixed in the next bugfix version of 5.10 then which I regularely update VyOS to. See T3318
We probably should move the following statement https://github.com/vyos/vyos-1x/blob/current/data/templates/frr/bgp.frr.tmpl#L362-L364
Just for your information.
The patch was added to kernel 5.4, 5.10 and 5.11.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/