Gentlemen, PLZ! Enplane me, what's wrong with it? Why my ISOs wont work?!?!
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Nov 10 2019
Nov 10 2019
syncer moved T1788: Intel QAT (QuickAssist Technology ) implementation from Needs Triage to In Progress on the VyOS 1.2 Crux (VyOS 1.2.4) board.
syncer edited projects for T1788: Intel QAT (QuickAssist Technology ) implementation, added: VyOS 1.2 Crux (VyOS 1.2.4); removed VyOS 1.2 Crux.
syncer edited projects for T1720: support for more 'show ip route' commands , added: VyOS 1.3 Equuleus; removed VyOS 1.2 Crux.
syncer moved T1705: High CPU usage by bgpd when snmp is active from Needs Triage to Backlog on the VyOS 1.2 Crux (VyOS 1.2.4) board.
syncer moved T1705: High CPU usage by bgpd when snmp is active from Need Triage to Finished on the VyOS 1.3 Equuleus board.
syncer edited projects for T1705: High CPU usage by bgpd when snmp is active, added: VyOS 1.3 Equuleus, VyOS 1.2 Crux (VyOS 1.2.4); removed VyOS 1.2 Crux.
While "interface ignore wildcard" configured, we got:
ntpq -c lpeer remote refid st t when poll reach delay offset jitter ============================================================================== 10.255.0.1 .INIT. 16 u - 64 0 0.000 0.000 0.000
show system ntp
allow-clients {
address 192.168.100.0/24
}
server 10.255.0.1 {
prefer
}Hello all! Was anything made with this issue?
c-po closed T1792: Update WireGuard to Debian release 0.0.20191012-1, a subtask of T1791: Update Linux Kernel to 4.19.82, as Resolved.
Colons in interface description should be allowed. There are tools like libreNMS which use defined prefixes for internal mapping and they have a colon inside.
c-po changed Difficulty level from unknown to normal on T1793: Editing description on an interface causes BGP sessions to reset on commit.
c-po changed the status of T1793: Editing description on an interface causes BGP sessions to reset on commit from Open to Confirmed.
c-po added a comment to T1793: Editing description on an interface causes BGP sessions to reset on commit.
There should be no reason the session is reset. This is an implementation "missdesign" by me when rewriting the ethernet interface. All interfaces are placed in admin down state on commit and will be placed in admin up state once the commit has run. and interface is not disabled.
rherold awarded T1788: Intel QAT (QuickAssist Technology ) implementation a Like token.
rherold awarded T31: Add VRF support a Like token.
Nov 9 2019
Nov 9 2019
Unknown Object (User) added a comment to T1788: Intel QAT (QuickAssist Technology ) implementation.
PR for CLI https://github.com/vyos/vyos-1x/pull/159
pending review: https://github.com/vyos/vyos-build-kernel/pull/1
hagbard moved T1788: Intel QAT (QuickAssist Technology ) implementation from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po changed the status of T1792: Update WireGuard to Debian release 0.0.20191012-1, a subtask of T1791: Update Linux Kernel to 4.19.82, from Open to In progress.
c-po changed the status of T1792: Update WireGuard to Debian release 0.0.20191012-1 from Open to In progress.
c-po closed T1030: Upgrade ddclient from 3.8.2 to 3.9.0 (support Cloudflare API v4), a subtask of T1763: CloudFlare DDNS support, as Resolved.
c-po moved T1030: Upgrade ddclient from 3.8.2 to 3.9.0 (support Cloudflare API v4) from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.4) board.
Backport to crux complete
Nov 8 2019
Nov 8 2019
If someone can confirm I'm linking to the correct github repo (there are two cloud init ones under vyos), I could submit a pull request for this. @syncer, @Unicron?
cf. T1001 as a related issue:
SquirePug renamed T1790: OSPF Exchanged Routes marked as invalid when run through a GRE PTMP/PTP OSPF between peers from OSPF Exchanged Routes marked as invalid when run through a GRE Tunnel between peers to OSPF Exchanged Routes marked as invalid when run through a GRE PTMP/PTP OSPF between peers .
SquirePug added a comment to T1790: OSPF Exchanged Routes marked as invalid when run through a GRE PTMP/PTP OSPF between peers .
So testing done so far:
SquirePug added a comment to T1790: OSPF Exchanged Routes marked as invalid when run through a GRE PTMP/PTP OSPF between peers .
Config3 KBDownload
Example Config demonstrating issueNov 7 2019
Nov 7 2019
The real problem is the config parser it seems as it can not deal with special characters used in a pre-login banner.
Unknown Object (User) created T1788: Intel QAT (QuickAssist Technology ) implementation.
Nov 6 2019
Nov 6 2019
Unknown Object (User) changed the status of T1747: L2TP breaks after upgrading to VyOS 1.2-rolling-201910180117 [issue report and proposed solution] from Open to In progress.
Nov 5 2019
Nov 5 2019
Confirmed fixed in
vyos@mke-fw1:~$ show version Version: VyOS 1.2-rolling-201911051339 Built by: [email protected] Built on: Tue 05 Nov 2019 13:39 UTC Build UUID: 3863567b-039d-4fdd-90cc-eda2e1b11bc6 Build Commit ID: 33c865b2ada281
dmbaturin added a project to T1394: syslog systemd and host_name.py race condition: VyOS 1.2 Crux (VyOS 1.2.4).
dmbaturin moved T1578: completion offers "show table", but show table does not exist from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.4) board.
dmbaturin changed the status of T1578: completion offers "show table", but show table does not exist from Open to Needs testing.
dmbaturin moved T1742: NHRP unable to commit. from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.4) board.
dmbaturin moved T1780: Adding ipsec ike closeaction from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.4) board.
dmbaturin moved T1740: Broken OSPFv2 virtual-link authentication from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.4) board.
dmbaturin changed the status of T1740: Broken OSPFv2 virtual-link authentication from In progress to Needs testing.
Ah you were using bleeding edge equuleus builds. Ddclient 3.9.0 has been added to recent rolling image.
In 1.2.3 build this error does not appear and it seems to work correctly
starcraft66 added a comment to T1030: Upgrade ddclient from 3.8.2 to 3.9.0 (support Cloudflare API v4).
Upgraded to 1.3-rolling-201911041446 and the config file issue is still present.
After adding the missing command set high-availability vrrp sync-group sync member int1, we have a new error when starting conntrackd
Nov 4 2019
Nov 4 2019
Confirmed using a copy of the Hyper-V VM
c-po changed the status of T1787: Failed config migration from V1.2.3 to 1.2-rolling-201911030217 from Open to Confirmed.
ppp0 not renaming to pppoe0 on 1.8.0 https://community.ui.com/questions/ppp0-not-renaming-to-pppoe0-on-1-8-0/b4aeea88-5d52-4222-b065-e6903afdda9a
600MB
that's really strange. As I can reproduce the problem on both intances in 100% of the cases. But not the same config and not the same inital VyOS version.
Can I do some troubleshooting steps for you?
I can also give you the vhd, but on a private channel if possible (is it possible on slack?)
This is weird. I can not reproduce it either with VMWare vSpher enot using Hyper-V.
1vCPU, 512MB RAM
What is your VMs CPU/RAM configuration?
Well, then there is a bug in the interface renaming script with later ifupdown scripts which should be fixed.
No good I'm afraid. NAT is not working set to pppoe0 and is still offering ppp0.
c-po triaged T1787: Failed config migration from V1.2.3 to 1.2-rolling-201911030217 as High priority.
Line2 updated the task description for T1787: Failed config migration from V1.2.3 to 1.2-rolling-201911030217.
the interface name ppp0 is wrong. If we configure it to be pppoe0 on the CLI it should also have this name on the bare linux system. This sounds a bit like: T1242 which was fixed in commit https://github.com/vyos/vyatta-cfg-op-pppoe/commit/4330d41fcda30553ca1b3e2588d05eebdd59fc80
Interface doesn't work if changed to ppp0. The interface seems to expect pppoe0 and everything else seems to expect ppp0. pppoe0 is still showing as 'coming up', even though everything seems to be working
More info,
You have to add a sync-group.
set high-availability vrrp sync-group intgroup member int1
set service conntrack-sync failover-mechanism vrrp sync-group intgroup
After a bit of fiddling, I have found the problem. The config.boot conversion from 1.2 to 1.3 did not chnage the NAT interface entries from pppoe0 to ppp0. Once changed, all is working. As can be seen below, NAT & monitor traffic interface expect ppp0, whilst the actual interface and firewall zones expect pppoe0. I think this is a little confusing and should probably be made consistent one way or the other.. pppoe0: is also still showing as "Coming up" even though everything appears to work so there is still a reporting problem there at the very least.
Wait, Argo tunnel uses Cloudflare's WARP VPN system, which under the hood is basically wireguard...
Nov 3 2019
Nov 3 2019
Confirmed still present in VyOS 1.3-rolling-201911030242
c-po moved T1777: Bonding interface MAC address mismatch after reboot from In Progress to Finished on the VyOS 1.3 Equuleus board.
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP group default qlen 1000
link/ether 08:07:06:05:04:03 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP group default qlen 1000
link/ether 08:07:06:05:04:03 brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP group default qlen 1000
link/ether 08:07:06:05:04:03 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a07:6ff:fe05:403/64 scope link
valid_lft forever preferred_lft foreverc-po moved T1752: PPPoE does not automatically start on boot from Need Triage to Finished on the VyOS 1.3 Equuleus board.
Tested using the below configuration on VyOS 1.2-rolling-201911030217
Nov 2 2019
Nov 2 2019