Fix: https://github.com/vyos/vyos-1x/commit/2f70340179a64d5936c32cc3c0d6d7f6f04054d0 applied, pkg build currently running.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 1 2019
Jan 31 2019
Jan 30 2019
Too add, routes are present in FRR
Bug confirmed.
fma@glos1ce1dk:~$ sh ver Version: VyOS 1.2.0 Built by: Sentrium S.L. Built on: Sun 27 Jan 2019 19:08 UTC Build ID: 795d6338-c1ce-4ebb-992f-d064f5af9309
I can't replicate it, but I'm using also the rolling release.
Can you please provide the output of:
Jan 29 2019
Jan 28 2019
Jan 27 2019
@UnicronNL Thank you very much, that is really useful to know.
If you manually partition you need to keep in mind 2 things.
the filesystem label needs to be "persistence" (mkfs.ext4 < device > -L persistence)
and in the root of the filesystem you must create a persistence.conf file containing "/ union"
(echo "/ union" > /persistence.conf) on your partition meat for vyos.
Jan 26 2019
Jan 25 2019
Jan 24 2019
can reproduce ob EPA3:
Jan 22 2019
Hold back on this for a moment. Might be a hardware error since behaviour under rc11 is strange as well.
Same issue with 1.2.0-rolling+201901070337 as well
look at T1181
There are no disadvantages in doing so. Any contribution is welcome.
Jan 21 2019
Jan 19 2019
Absolutely -- I'll test it next week!
Jan 18 2019
wireguard identifies peers on their key, improve the command for sh int wireguard wg01 peers etc. so that the peer name from the config is visible as well.
@ekim https://downloads.vyos.io/rolling/current/amd64/vyos-1.2.0-rolling%2B201901181924-amd64.iso should address the dhcp issue, can you please test? I only tested on VMs yet.
Jan 17 2019
I just tested this on 1.2.0-EPA3 and it works here. Please re-test with EPA3.
Jan 16 2019
All right @ekim I have that feature working in an experimental package. If you want to test it you can build it from here:
https://github.com/hagbard-01/vyos-netplug via dpkg-buildpackage -b -tc -uc -us and install it on any rolling iso. I used the latest for my tests, but it should work on older ones too. It will still take a little time to have that pushed into the normal build process, since it requires some integration work.
@ekim Yeah, that is a known issue I was looking into a while ago already. disable/enable in eth interfaces should now work in the latest rolling, the plug-in and unplug will still need a little. I'll keep this task here open for it.
That’s correct, when deleting disable from the interface config. Additionally, It doesn’t seem like dhclient gets triggered when a physical interface is unplugged then plugged back into that same port, but should receive a new address as a different dhcp serving a different dinner is available
Jan 15 2019
@ekim I think I found it. When I put the interface into disabled mode and then delete disabled, the dhcp client isn't started anymore if the address is supposed to be received via dhcp, correct?
Yes, no issues on either DHCP server. All other clients on the network perform as expected.
Have you checked on the server DHCP server side for issues?
Jan 14 2019
Superseded by T1178
Seems to be a problem with just that build. I'll install a newer rolling when I get a chance and see if that corrects it.
Edit... actually I can't update anything:
Jan 11 2019
Jan 10 2019
Jan 9 2019
Jan 7 2019
With VyOS as the edge:
Next rolling will have the fix applied:
https://github.com/vyos/vyos-1x/commit/76fe726e3530158ee175d34b9cb74209ccca2345
Jan 6 2019
From the 1.2.0 instance (10.240.4.31) I'm able to ping the 1.1.8 (10.240.4.32) instance immediately after adding the address, but cannot ping out to the internet until after a reboot.