- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 27 2018
This will be a killer feature. I wanted to spin a Atom C3000 board with VyOS 1.2 but that board comes with UEFI only so right now, no VyOS on this one. Debian Jessie CD on the other hand boots fine (build with UEFI support)
Sep 25 2018
VyOS 1.3 is fine for me
Sep 23 2018
What happens on Hypervisors not supporting UEFI or older Hardware Platforms without UEFI?
I think we should take care about this in the VRRP scripts and leave the base system untouched. Meaning, take your proposal and remove
update_sysctl_conf net.ipv4.conf.default.arp_filter 1 \ "reset promiscous arp response"
@rps seems to be the case. sorry for the noise
arp_proxy setting was introduced in an ancient commit https://github.com/vyos/vyatta-cfg-system/commit/496526b572ca83308a858b2ec4771d2f05f4970c
Sep 21 2018
@dmbaturin I actually comitted the fix yesterday morning. Somehow Phabricator only shows the corresponding commits when logged in.
Sep 20 2018
Sep 19 2018
Please find some older rolling releases here:
Sep 18 2018
As requested by @runar:
Sep 16 2018
Invalid SNMP addresses must be filtered, else the service won't start with this error message:
Sep 16 20:32:58 LR1 snmpd[4848]: Error opening specified endpoint "udp:192.168.1.1:161" Sep 16 20:32:58 LR1 snmpd[4848]: Server Exiting with code 1 Sep 16 20:32:58 LR1 snmpd[4845]: Starting SNMP services:: Sep 16 20:32:58 LR1 systemd[1]: snmpd.service: control process exited, code=exited status=1 Sep 16 20:32:58 LR1 systemd[1]: Failed to start LSB: SNMP agents. Sep 16 20:32:58 LR1 systemd[1]: Unit snmpd.service entered failed state.
Sep 15 2018
$ show version Version: VyOS 1.2.0-rolling+201809150337 $ sudo modprobe wireguard $ dmesg | tail -n 4 [ 77.915285] systemd-sysv-generator[2934]: Overwriting existing symlink /run/systemd/generator.late/isc-dhcp-server.service with real service [ 174.154861] wireguard: loading out-of-tree module taints kernel. [ 174.158164] wireguard: WireGuard 0.0.20180708-1 loaded. See www.wireguard.com for information. [ 174.158166] wireguard: Copyright (C) 2015-2018 Jason A. Donenfeld <[email protected]>. All Rights Reserved.
I can confirm L2TP/IPSec working with Windows 10 (1803) and Apple iOS 11.4.1 together with RADIUS auth backend.
Sep 14 2018
Sep 12 2018
VyOS Kernel was rebuild with retpoline enabled https://phabricator.vyos.net/T819. As Kernel modules sometimes depend heavily on the unterlaying ABI (Application Binary Interface) this will break if the module is not rebuild.
Sep 11 2018
In addition the old patches from https://phabricator.vyos.net/T17 have been re-applied to the net-snmp repository b/c they were lost in translation on the move to Debian Jessie.
This is whats happening when we add L2TP/vpn configurtion and do a commit:
Fixed by installing dependency.
Sep 10 2018
Sep 7 2018
After a successfull connection I see the spawned process:
root 2595 0.0 0.0 4332 124 pts/1 Ss+ 22:58 0:00 /usr/sbin/xl2tpd root 2868 0.5 0.2 26108 2484 pts/1 S+ 22:59 0:00 \_ /usr/sbin/pppd passive nodetach 10.255.255.0:172.16.222.1 refuse-pap auth name VyattaL2TPServer debug file /etc/ppp/options.xl2tpd /dev/pts/1
Okay, I narrowed it down even further:
Thanks! Sounds like a proper fix to me.
Sep 6 2018
I‘m using VyOS 1.2.x wirh a 4GB HDD on ESXi
Issue was introduced between those two images:
Sep 5 2018
I guess then it was "broken" all the time
Does downstreaming work when you configure set system ntp allow-clients address?
Sep 4 2018
Sep 3 2018
@dmbaturin the "workaround" and implementation is IMHO super bad (https://github.com/vyos/vyos-1x/blob/current/src/conf_mode/snmp.py#L808-L813) as it uses /opt/vyatta/sbin/my_set or /opt/vyatta/sbin/my_delete.
Yes, just pass the variable on calls to os.system()
Sep 2 2018
Sep 1 2018
cpo@LR1:~$ cat /sys/devices/system/cpu/vulnerabilities/spectre_v2 Mitigation: Full generic retpoline, IBPB, IBRS_FW
Even happens without any argument:
cpo@LR1# sudo /usr/sbin/lldpd -d 2018-09-01T20:12:53 [WARN/lldpctl] unknown command from argument 1: `#` 2018-09-01T20:12:53 [WARN/lldpctl] unknown command from argument 1: `#`
Happens too when started by hand, where 172.16.254.35 is the management address
The user/password thing is closed. The Port issue seems to not be easy. Will be easier with a vyos-1x rewrite
IPv6 DHCP
Just tried your configuration and adopted it to my LAB. I can't reproduce your issue.
Done!
I had the exact same problem for the service broadcast-relay code. I did a cleanup on the youthful folly. Resulting in this issue going away (https://github.com/vyos/vyos-1x/commit/fd1eabe72862ec364643a61cb94b21c330a385f5#diff-e27a1d5bf8f371aae9da8bbd36e674d0).