Tomorrows rolling release will come with a first version of the fix. It requires you to use speed/duplex auto setting. The next part will also cover fixed speed/duplex settings.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Nov 10 2019
The offender is the call to vyos.ifconfig.set_flow_control() which triggers /sbin/ethtool --pause eth0 autoneg on tx on rx on. we should only change this if it is really necessary and not on every commit.
Gentlemen, PLZ! Enplane me, what's wrong with it? Why my ISOs wont work?!?!
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?
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.
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.
Nov 9 2019
PR for CLI https://github.com/vyos/vyos-1x/pull/159
pending review: https://github.com/vyos/vyos-build-kernel/pull/1
Backport to crux complete
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:
So testing done so far:
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.
Nov 6 2019
Nov 5 2019
Confirmed fixed in
vyos@mke-fw1:~$ show version Version: VyOS 1.2-rolling-201911051339 Built by: autobuild@vyos.net Built on: Tue 05 Nov 2019 13:39 UTC Build UUID: 3863567b-039d-4fdd-90cc-eda2e1b11bc6 Build Commit ID: 33c865b2ada281
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
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
Confirmed using a copy of the Hyper-V VM
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.