Next rolling will have it included.

https://github.com/vyos/vyos-1x/commit/dad110ce666edae42ac18c59a800bda503589f27

Gotcha, I start implement it for the rolling release for now. Since it affects multiple other nodes as well, I'll do it for all of them equally. aka facility has no constraint and completion help too. There are a few more I've found, so I crawl through all of them and enhance it a bit.

@c-po I used the 1.2.3 iso from the download portal and can't reproduce the issue. The help message was also already there since it was (re)implemented, could it be an issue with your installation?

Looks like no one really wants it except for 2 people, going to cancel it.

@kroy AFAIK, intel drivers, KVM (VM performance and I/O), Kernel memory I/O etc.
Performace data can be recorded and replyed asewll. Looks like candidate for debug images as @c-po pointed out.

perf is a tool to gather performance and debug data on a running system with a deep insight into program functions etc. Since it will need a bunch of new libs within the system, I'd like to find out if there is the need for it or not.

https://downloads.vyos.io/rolling/current/amd64/vyos-1.2-rolling-201911102307-amd64.iso or later has it included.

packages are being built via CI:
http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-qat/

pending review: https://github.com/vyos/vyos-build-kernel/pull/1

As you pass auth and get the config sent, can you please check that you have a default route set up? Ideally that should happen automatically. It looks like your ISP offers you IPv6 which seems rejected as unknown by the pppoe client, but that't not the primary issue. Check if your default route is being set up.

looks neat. I merged in in already. Can you add some explanation to https://github.com/vyos/vyos-documentation please.

https://github.com/vyos/vyos-1x/pull/149 merged. While I think the UP/DOWN status is a little brave. It leads users maybe to believe that the wg interface has really a up/down state.

For now, it has been decided not to support arm officially, due to lack of resources.

For now, it has been decided not to support arm officially, due to lack of resources.

Thanks for your contribution.

Perfect. Thanks a lot guys.

@Harliff Does curl work for you?

Is that still and issue, sorry I lost track a little while I was busy with other stuff.

already added to the documentation: https://vyos.readthedocs.io/en/latest/system/proxy.html

https://github.com/vyos/vyos-1x/commit/df9544233fb661e830285c1a0d7755cff4b27408
https://github.com/vyos/vyatta-cfg-system/commit/3a99ea6e9b8ef9ef417d38d1d0bab8d2d2401aa8 (add system image)

I have an idea, I can either write it to profile.d, that is exporting http_proxy, https_proxy and ftp_proxy into the shell env, and in the install-image script if the profile files exists, I load it which exposes these variables as well and curl is working with no issue. If removed, that file won't exists and curl works like it did before. If the proxy variables shouldn't be in the user environment, I can write it to a particular file only used by scripts which which would need that information.

curl only accepts ~/.curlrc, so that can become a hassle with multiple home directories on a box.

That would work but it's only for a single programm you define it. I think it could be enough for the beginning. I still have to check if curlrc is being read when invoked from the perl script, it usually should.

The removal makes a little headache. Setting it system wide is not an issue at all, writing and execute in profile.d. Removing it would require to logout and login again to re-read the bash.profile. I may have to rethink that. Also the image download is invoked via a perl script, so http_proxy will be lost anyway.

I have that issue for a while here too and just helped myself locally. I'll can take care of that.

Most enterprises use it still as a cheap authentication method, I'm totally in favor to drop it, not only in vyos. Breaking it off (they generate fitting ssl certs on the fly signed with a private PKI), is questionable as well, since I think https should be end to end encryption, everyone who messes with that idea, well I wouldn't trust them on other items as well.

works with:

Version:          VyOS 1.2-rolling-201910110117
Built by:         [email protected]
Built on:         Fri 11 Oct 2019 01:17 UTC
Build UUID:       48a11fa6-8c59-4dbb-94a3-215376c09a02
Build Commit ID:  46f9b2ab60e4fa

Can't create an iso right now to test it.

typo fixed: https://github.com/vyos/vyos-1x/commit/50acd442ade9a4e447269eaf94ce14d354af8d0c
http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb should work now

@jjakob Is that still an issue? I have the lastest 1.3 rolling form today and can't reproduce the issue.

running from the live-cd I think.

@brian.ward Please show the output of df-h at your earliest convenience.

@bertleywjh any other input, or can I close the ticket?

@brian.ward Can you please check that /config is mounted?

Can't reproduce it, it does work without any issues. I copied and executed your config and did a commit.

Looks like it has changed already in ifconfig.py. Tested it successfully as well.
https://github.com/vyos/vyos-1x/commit/f5c04661e6c031baedb6092ecafee501cca7bc28#diff-def38e05f2ac1eb35139b37ec8d47338R1375

@cpo operstate will be unknown for wg interfaces, I think it's the only interface type having unknown. Anything else should be up or down, I think. I can re-implement with the wg class if that's better.
Let me know what you think, wg is working with no issues, so functionality isn't an issue here.