Jessie based VyOS - Crux
Sat, Oct 19
Agree with you, thank you. We need fixed these moments.
Unfortunately it doesn't work without gw-ip-address also in [chap-secrets]. In my early trials I've tried that, and the clients received IP's from the pool instead the static values.
I think better calculate gw-ip-address automatically. outside-nexthop excluded from required for migration reasons.
Not necessary define gw-ip-address in [chap-secrets] section, it works without any issue if defined it in [ip-pool] only.
@Dmitry Thanks for pointing that out, I've looked on the wiki (https://wiki.vyos.net/) and searched for a description for outside-nexthop, and failed to find it, and the in-line help while configuring doesn't help much.
You can set outside-nexthop which fixed this. Also I think we can calculate first ip for gw-ip-address if outside-nexthop is not defined by cli.
This is present in branches crux and current too, so adding tag for crux.
Via the process of elimination I found the culprit - comments with special characters in them, that at some point in the upgrade cycle got converted into backslash-escped octal:
description "\197\160" # this was once Š description "\196\140 \196\141" # Č č
So old versions allowed these characters in comments and worked fine with them, then at one opint a upgrade converted them to backslash octal numbers, which still worked until at some point they started causing the error.
Fri, Oct 18
Wed, Oct 16
Tue, Oct 15
Version: VyOS 1.2-rolling-201910110117 Built by: email@example.com 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
Okay, after working with this for a while, I believe the whole 'vyatta-webproxy` should be a candidate for deletion in equuleus (see T1732).
Mon, Oct 14
To be fair, that’s what prompted this. The logs go to a different file already.
Because the amount of logs from this system could be enormous, Is it possible to move these logs to another syslog file to not overcroud the main syslog file?
This PR should address those concerns
I would rather prefer it to send messages to local syslog and then distribute it to remote hosts. Otherwise we have an async syslog interface.
Sun, Oct 13
Okay - just installed the latest rolling and it does not even boot up anymore. Its trapped in a snmp restart loop somehow. Going to revert this commit.
The change now leads to not starting SNMP when I do not use BGP
Sat, Oct 12
Fri, Oct 11
Yes I was running from a live image exactly as hagbard mentioned.
running from the live-cd I think.
@brian.ward no problem. Could you please tell us what was your problem so we could probably reference this in the future for other people?
Sure enough, /config is not mounted.
Not sure how the configuration was being saved.
@brian.ward Please show the output of df-h at your earliest convenience.
@hagbard yea if there's no way to do it, there's no way to do it. Thanks though.
@bertleywjh any other input, or can I close the ticket?
@brian.ward I just tried to reproduce this with a clean VyOS installation and it works as expected.