- User Since
- Aug 3 2017, 1:55 PM (15 w, 4 d)
@alainlamar Unfortunately I have some problems with APT building my ISO but I added the steps for you here: https://wiki.vyos.net/wiki/Rebuild_VyOS_kernel_Step#VyOS_1.2.x
@alainlamar would you be willing to test a special image with all your required changes inside (Kernel, hostapd, firmware-atheros)? Only extension of vyatta-wireless is missing, but looks you could do this "on the fly"?
I can confirm that by using this approach we can have hostapd 2.4 from debian stretch
Sat, Nov 18
Closed b/c I wanted to rewrite it using vyos-1x command package.
Wed, Nov 15
Thanks for this feature request. I'm not to happy having a cloud provider install some SSH keys onto my system. If you have to manage many VyOS machines, why not use Ansible?
Tue, Nov 14
Possibly http://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#apt-pinning will do the trick. I will start a test build...
Mon, Nov 13
@alainlamar thank you very much for providing such detailed information e.g. what is required inside the kernel configuration. This seems to be not a big deal to enable those.
Sun, Nov 12
Wed, Nov 8
Tue, Nov 7
This did the trick. Just build a fresh ISO:
@UnicronNL maybe this will fix this issue:
Fri, Nov 3
Our nightly builds ships wpasupplicant 2.3-1+deb8u4, according to https://www.debian.org/security/2017/dsa-3999 it's fixed in 2.3-1+deb8u5.
Using a self build ISO: VyOS 999.201710291829 I can confirm this.
This regression is fixed. @syncer should we resolve it?
False positive as a previous command was failing.
Isn't it the scenario for which all those people in debian have used package manager for decades? Isn't it better to just update one package in installed system?
Thu, Nov 2
This action installs the following cronjob:
sudo sh -c 'echo "#!/bin/sh" > /etc/cron.weekly/01vyos-popcon' sudo sh -c 'echo "/opt/vyatta/bin/vyos-popcon.pl 2>&1 >/var/log/popcon.log" >> /etc/cron.weekly/01vyos-popcon' sudo sh -c 'chmod +x /etc/cron.weekly/01vyos-popcon'
Mon, Oct 30
Do we know why it‘s not possible? Is it due to a missing configuration option in VyOS or is it due to non availability in the underlying Linux Components e.g. Strongswan?
Sun, Oct 29
Fri, Oct 27
On VyOS 1.1.7 we have /etc/radiusclient-ng/dictionary.merit which moved to /usr/share/freeradius/dictionary.merit on VyOS 1.2.x.
Thu, Oct 26
Wed, Oct 25
Thank you for the effort. I always liked the VMWare template installation. I also tried it for VyOS 1.2.x on ESXi 6.5. I followed the WiKi instructions which worked like a charm!
Mon, Oct 23
Vote for 1.2.x only.
Oct 13 2017
Oct 10 2017
BusyBox is a multi-call binary. A multi-call binary is an executable program that performs the same job as more than one utility program. That means there is just a single BusyBox binary, but that single binary acts like a large number of utilities. This allows BusyBox to be smaller since all the built-in utility programs (we call them applets) can share code for many common operations.
Oct 9 2017
+1 for removal
As VyOS fully re-uses Debian packages it is not possible to enable any given applet inside Busybox. To get this enabled, VyOS has to maintain a forked version of the Debian busybox packages which makes life only harder.
Sep 20 2017
cpo@AC1:~$ cat /boot/grub/grub.cfg | grep timeout set timeout=5
Sep 16 2017
Please also see T393
Sep 15 2017
@mickvav Interesting Idea, I should give it a try ...
@Asteroza this program forwards UDP packets (Layer 3) on specific ports. Unfortunately WoL is Layer 2 based.
Sep 12 2017
I can verify that it now also boots on OVH.net VPS.
@babak that would be awesome as I do not have any IPv6 BGP connectivity. I created a temporary SSH key for this, could you please create a user cpo:
Sep 10 2017
I guess that you are referring to the installation of VyOS, as a proper installed system will automatically boot up. At least last nights build does.
Maybe this is the reason why we also can't boot a VyOS instance on VPSs rentet from OVH.net
Well I think porting this to vyos-1x package would be a good lesson to learn the new system. Let me have a look...
Sep 8 2017
@dmbaturin You have some good points. Using "service" to start/stop a daemon should be the weapon of choice now. This could/should be changed to have a consitent system, but this inital commit is just a 1:1 EdgeOS copy.
Sep 7 2017
Sep 4 2017
@syncer: Thinking about it I have a different proposal:
I think as not everybody has access to an IPv6 BGP router, a ro SNMP community for testing would be good. Even better would be a virtual instance to develop a fix for this problem.
Sep 3 2017
Looks to me that you are mixing up two things. 6rd (Radpid Deployment) is used for ISPs to connect the customers to the IPv6 world (https://en.wikipedia.org/wiki/IPv6_rapid_deployment).
Tag VyOS 1.2.x should be removed as CVE is already fixed.
Verified using iOS 10.3.3 accross VLANs. mDNS services like Airplay working.
Sep 2 2017
@UnicronNL could you please mirror https://github.com/c-po/vyos-bcast-relay.git to https://github.com/vyos/vyos-bcast-relay.git and set up a CI job? After this I can submit the appropriate merge requests for vyos-world abd vyos-build.
@UnicronNL could you please mirrir https://github.com/c-po/vyos-cfg-avahi to https://github.com/vyos/vyos-cfg-avahi and set up a CI job? After this I can submit the appropriate merge requests for vyos-world abd vyos-build.
Status can be seen here: https://github.com/c-po/vyatta-cfg-avahi
Actually I like the fact to have the users SSH pub key inside the config. This makes it super handy to just copy/paste a users config entry arround VyOS instances.
Sep 1 2017
@syncer This one is fixed/merged and already working in the nightly builds.
Just to give some more information.
Aug 31 2017
strip-private is a bash-pipe function (/etc/bash_completion.d/vyatta-op).
Good objection. This should be avoided!
Aug 30 2017
VyOS 1.1.7 also has two interfaces (vti0 and ip_vti0)
Using VyOS 999.201708292137 I'm able to reproduce this.
@syncer could this change be approved or is anything else missing?
Aug 29 2017
I double checked with VyOS 1.1.7 where I can not reproduce the error. Is version 1.1.7 correct in this BUG report?
@ethomas could you please provide a full configuration for my tests? The only thing I see is: