Package needs to be build from source. There are already some packages which we build that way like libyang or librtr so not a big deal.

Sounds more reasonable (enable than disable). Will this affect backwards compatibility or will there be a migrator?

@danhusan is this your expected behavior?

can you share your DHCP configuration with us for reproducibility?

IMHO this is a general CLI design issue.

Nope, I used:

@hagbard I replaced vyos user with another one. Also image corporate setups where RADIUS is used for authing and there are no local users.

There are no disadvantages in doing so. Any contribution is welcome.

Depending on the task which needs to be executed a script might need to be run as root.

lsmod output from 4.18.6-1 (all 4 NICs working) please. We already have a lsmod output of the other versions.

Please place your code snippets inside a Code section as mentioned above, this makes it easier to read.

No reply from the vendor so far

Latest is fine

No issue known but it eases reproducibility

@alexandrestein can you share your complete dns forwarding config node please?

The provides Dockerfile lists all packages which are needed to compile VyOS on a Debian jessie host. If you do not want ro install all this on your host simply use the provided Docker image and you are ready to go.

Thanks. An lsmod from rc5 would be nice, too.

Can you share the dmesg output from RC5 please?

It also reports:

ISO is still building. You are right, a NIC is a NIC, but a NIC consists of a MAC and a PHY which does the PHYsical interface. you can have the same MAC part multiple times but with different PHY ICs. Lets wait for the ISO to compile.

According to the datasheet https://f.ipc2u.de/files/add/doc/445/3I380D-D90-Datasheet.pdf I see no PHY that is used on this board - nevertheless I saw that we do not ship every avialable PHY driver, also drivers present in 1.2.0-rc6 are no longer present like CONFIG_BCM7XXX_PHY. I will provide you with an updated ISO for testing.

Looks like a general issue here. Do you still have the old Buster ISO with Kernel 4.18 that you can install on the target HW?

• (K)ASLR is enabled with https://github.com/vyos/vyos-kernel/blob/35c51d3b30f29110aab12ade5f11f928c68951ec/arch/x86/configs/x86_64_vyos_defconfig#L405
• DEP

vyos@vyos:~$ show system kernel-messages | grep "Execute Disable" 
NX (Execute Disable) protection: active

• RELRO there's some info in the Debian Wiki but it reports permission denied: https://wiki.debian.org/Hardening

@rps what about changing the minimum supported MTU from "68" to "1450" which is the default that is used in VyOS.

Thanks for your contribution. It will be included in the next EPA and rolling images.

I will approach the vendor first.

@SteveP as it works with Debian Buster it should work with our newer Kernel, too.

Anyone can provide me with a hardware?

@dongjunbo same hardware?

Where to get those MIBs? should be simply to test before adding it to the iso

@fromport there is an option in the ./configure script tomspecify the Debian mirror you use. You should be able to simply point it to your mirror.

I assume you lack some build dependencies. Please check the Dockerfile which has all required dependencies in it and install them on your native build host.

@SteveP can you please try: https://helix.mybll.net/vyos-uefi-4eb663191c09.iso ?

I am also getting an error with sh system kernel-messages which also was not there with RC5.

Thanks for the update. May I ask which distro?

Can you provide us with e shell output of lsmod command?

Weird, as we use the exact same network adapter configuraion as Debian Buster :/

@Line2 it will be in tomorrows rolling release. I just tested it on my Windows 10 Hyper-V with a generation 2 VM (UEFI)

THX for the update. done also on current and crux

Also cherry-picked into crux

@MrFunken IPv6 is handled via T366.

CONFIG_FB_VGA16 has been removed from the kernel co fig and thus this should be resolved. Can you please retest with latest rolling?

@SteveP can you please test with latest rolling ISO?

Just hit this at my site, too.

I propose to proceed with a global change. Special case handling is always harder to test and the impact is only 5 seconds max in startup time - who cares on a 24/7 active device which is rarely rebootet?

instead of differentiating between raid and non raid installations - why not always wait 5 seconds for the discs to settle? As this is only done once on startup this is IMHO better then a special case.

I'd like to point out that the "personal appeal from the VyOS Wiki founder Daniil Baturin" at the top of the Wiki pages is fantastically defeated when we make it this difficult to contribute to the documentation. 😞

Can you share your configuration please? I use rc11, too as l2tp/ipsec access concentrator and everything is fine here.

Commit also cherry-picked to crux branch

Changes verified in commit https://github.com/vyos/vyos-kernel/commit/729bd5fafec7d2ad345ab371b04d15d2cf627229 so IMHO this one is resolved

The shared-network-parameters is a real pain and should be used "without warranty" we should rather deprecate it and add proper CLI interface.

Does the problem occur on a virtual environment e.g. ESXi, too?

As the DHCP client sometimes stores its lst IP address and sends a request for it you probably should delete the lease from the DHCP server: