- User Since
- May 25 2018, 2:31 AM (73 w, 3 d)
Sat, Oct 19
Thanks for your contribution.
Fri, Oct 18
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 ocumentation: https://vyos.readthedocs.io/en/latest/system/proxy.html
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.
Thu, Oct 17
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.
I have that issue for a while here too and just helped myself locally. I'll can take care of that.
Tue, Oct 15
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.
Version: VyOS 1.2-rolling-201910110117 Built by: firstname.lastname@example.org 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
Fri, Oct 11
@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.
Thu, Oct 10
@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.
@bertleywjh wg state and link state is all is unfortunately all you will be able to see, plus like when was the last handshake and how many bytes were transfered. AFAIK there is no other way to see states of the handshake etc.
@fvbrasileiro Yeah, we found that out too today, we are working on a solution already. Please be patient.
@bertleywjh What issue are your trying to debug?
Next rolling will have it: https://github.com/vyos/vyatta-op-quagga/commit/219265ae4c8886bb6997ffc79f34610d6e2ea2d0 or you can manually install from the source below, if it is an urgent matter.
The cli part for the routing suite is up for rewrite, json is only working because it's supported by frr and the cli doesn't filter it. I think getting show ip route tag 20 working shouldn't be a big deal, but I try to avoid to add too much to the cli, will make just the rewrite way harder.
There were multiple complains about bgpd crashes, memory issues inthe forum. They used the workaround removing the tables from snmpd successfully.
@olofl How do you set the tag? via CLI?
@fvbrasileiro Please test at your earliest convenience.
Wed, Oct 9
1.2 is not affected which runs OpenSSH_6.7p1 Debian-5+deb8u8, OpenSSL 1.0.1t 3 May 2016
Tue, Oct 8
Can we just remove the deprecated options from being generated? They only leave a few lines in syslog, but these options are deprecated already in stretch.
- systemctl disable pacemaker
- systemctl disable corosync
- systemctl disable wpa_supplicant
Thu, Oct 3
Wed, Oct 2
I'll close as won't fix, given the fact that it is an upstream issue. Anything build around it, is in my opinion just a kludge, unless we would go with a separate daemon which can check and re-establish connections if they fail. The danger is that vyos becomes then more a server than a router. As workaround, a cronjob could do that as well, either setting an option via cli (wg-heartbeat or so since keepalive is a wg option already), which drops a cronjob onto the box and checks the wg endpoint periodically, if it fails it just calls diable/enable and checks again for X times, before it sleeps for let's say 24hs or so. @kroy would something like acronjob help you? Could be also set as a @reboot job and once the traffic flows it kicks itself out. Just wanna throw out ideas here.
Tue, Oct 1
https://github.com/vyos/vyos-1x/commit/cf499f958423919264884e9f1c5c1b593fd9de0e next rolling will have it fixed.
They have been committed at the same time, while I was using the current version if ifconfig.py and new one was published.