Community discussions

MikroTik App
 
ko00000000001
just joined
Topic Author
Posts: 9
Joined: Thu Feb 29, 2024 9:12 am

CHR 7.14/7.15b4 can't find network interface in Vultr

Thu Feb 29, 2024 9:25 am

Update 2024-3-6

1.Can't find the interface in Vultr
CHR 7.14
CHR 7.15beta4 Testing

2.Only CHR 7.13.5 find the network interface in Vultr

3.Vultr Debian11 network interface details
...............................................................................................................
root@vultr:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 56:00:04:cc:27:9a brd ff:ff:ff:ff:ff:ff
inet 45.xxxxxxxxx/23 brd xxxxxxxxxxxxxxxx scope global dynamic enp1s0
valid_lft 85690sec preferred_lft 85690sec
inet6 2401:c080:xxxxxxxxxxxxxxxxxxxxxxxx/64 scope global dynamic mngtmpaddr
valid_lft 2591939sec preferred_lft 604739sec
inet6 fe80::5500:5ff:fecc:279a/64 scope link
valid_lft forever preferred_lft forever
root@vultr:~#

root@vultr:~# lspci
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller
00:01.0 VGA compatible controller: Device 1234:1111 (rev 02)
00:02.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.4 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.5 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.6 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.7 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.4 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.5 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.6 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.7 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:04.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:04.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
01:00.0 Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)
02:00.0 PCI bridge: Red Hat, Inc. Device 000e
03:01.0 System peripheral: Intel Corporation 6300ESB Watchdog Timer
04:00.0 USB controller: Red Hat, Inc. QEMU XHCI Host Controller (rev 01)
05:00.0 SCSI storage controller: Red Hat, Inc. Virtio block device (rev 01)
06:00.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon (rev 01)
07:00.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG (rev 01)
root@vultr:~#

root@vultr:~# modinfo virtio_net
filename: /lib/modules/5.10.0-27-amd64/kernel/drivers/net/virtio_net.ko
license: GPL
description: Virtio network driver
alias: virtio:d00000001v*
depends: virtio,virtio_ring,net_failover
retpoline: Y
intree: Y
name: virtio_net
vermagic: 5.10.0-27-amd64 SMP mod_unload modversions
sig_id: PKCS#7
signer: Debian Secure Boot CA
sig_key: 32:A0:28:7F:84:1A:03:6F:A3:93:C1:E0:65:C4:3A:E6:B2:42:26:43
sig_hashalgo: sha256
signature: 99:A5:03:76:D0:11:87:2E:CF:A0:39:39:89:E5:30:8B:5C:02:9B:EF:
B7:F5:7A:41:56:21:7E:65:2C:2E:71:AD:5C:67:83:6D:DC:C6:44:8A:
4B:A2:50:5E:53:E9:B8:43:41:72:82:75:B1:90:27:D3:DF:5D:F9:52:
F7:F3:CD:21:46:79:18:09:57:A0:C9:92:95:EE:9B:E9:74:D9:08:82:
F7:29:BB:E2:F7:43:B7:47:4B:FE:55:48:5C:0F:F1:C0:F5:14:3B:46:
BB:87:40:45:99:D6:6E:23:BB:DB:CA:BA:77:F0:81:BD:05:E5:5E:71:
35:9A:CA:C1:65:A6:F4:A4:B3:FE:AE:D7:6C:2A:00:BC:3C:E2:45:9B:
11:54:1A:98:2A:32:78:5F:C6:78:59:B7:45:BB:BF:CE:6C:9A:8F:D3:
99:33:5A:6D:44:8B:42:9A:C6:4E:46:8B:96:0B:5E:C8:F4:6C:B1:2F:
96:1E:D7:B2:20:C7:61:79:F2:E1:9C:4C:AB:60:45:2C:FB:7F:38:B1:
6B:8E:8E:0D:FC:AF:0D:8F:83:63:54:F2:E6:79:F6:FA:B6:88:1A:36:
7C:4B:30:05:60:B6:B2:91:4E:CD:05:F3:32:E5:40:70:E5:B7:42:1E:
AF:C8:14:FE:14:9E:9D:B6:F0:0C:09:8E:48:43:0E:C8
parm: napi_weight:int
parm: csum:bool
parm: gso:bool
parm: napi_tx:bool
root@vultr:~#





.............................................................

Hello everyone

7.14rc3 Testing
7.14rc4 Testing
In Vultr
can't find network interface in Vultr

7.13.5 Stable
In Vultr
Found the network interface. It's working.

Is 7.14 removing some NIC drivers?

Vultr instances of any system are UEFI bootable
I modified CHR partition 1 to FAT16 format to support UEFI
I was able to run CHR in VULTR

Image
Last edited by ko00000000001 on Tue Mar 05, 2024 6:38 pm, edited 3 times in total.
 
DarkNate
Forum Guru
Forum Guru
Posts: 1015
Joined: Fri Jun 26, 2020 4:37 pm

Re: CHR 7.14RC3/RC4 can't find network interface in Vultr

Fri Mar 01, 2024 12:40 pm

I'd recommend just using Debian/Ubuntu + FRR or BIRD instead.
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1053
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: CHR 7.14RC3/RC4 can't find network interface in Vultr

Fri Mar 01, 2024 4:50 pm

Is 7.14 removing some NIC drivers?

Similar issues have been reported regarding other virtual environments. Check forum.mikrotik.com/viewtopic.php?t=205097 for possible workarounds
 
zlook
just joined
Posts: 2
Joined: Mon Mar 04, 2024 4:55 pm

Re: CHR 7.14RC3/RC4 can't find network interface in Vultr

Mon Mar 04, 2024 6:34 pm

I modified CHR partition 1 to FAT16 format to support UEFI
How did you do it?
 
ko00000000001
just joined
Topic Author
Posts: 9
Joined: Thu Feb 29, 2024 9:12 am

Re: CHR 7.14RC3/RC4 can't find network interface in Vultr

Tue Mar 05, 2024 6:33 pm

I modified CHR partition 1 to FAT16 format to support UEFI
How did you do it?
kpartx -av chr-7.15beta4.img
mount /dev/mapper/loop0p1 /mnt
mkfs.vfat -F 16 -n "BOOT" /dev/mapper/loop0p1
....

The process is cumbersome
finished products
https://github.com/alecthw/mikrotik-rou ... i/releases
 
ko00000000001
just joined
Topic Author
Posts: 9
Joined: Thu Feb 29, 2024 9:12 am

Re: CHR 7.14/7.15b4 can't find network interface in Vultr

Wed Mar 06, 2024 9:07 am

Hello,

RouterOS 7.15alpha131 with a possible fix.
https://box.mikrotik.com/f/589c29156d524118a401/?dl=1

RouterOS 7.15alpha131 on Vultr,
Network interface found,
Network interface is working properly,
This is great,
I hope that later versions will add this driver.

I think RouterOS CHR should add commonly used drivers,
Because the hard disk space is large.

Thank you!
 
ko00000000001
just joined
Topic Author
Posts: 9
Joined: Thu Feb 29, 2024 9:12 am

Re: CHR 7.14/7.15b4 can't find network interface in Vultr

Wed Mar 06, 2024 9:55 am

Technical Support Response

This issue was due to this: https://cgit.freebsd.org/src/commit/?id ... a991fa2901
And it wasn't the drivers fault.
 
grutmic
just joined
Posts: 19
Joined: Mon Dec 18, 2023 7:42 pm

Re: CHR 7.14/7.15b4 can't find network interface in Vultr

Thu Mar 07, 2024 1:36 am

I have the same problem with chr and ethernet ports, could you bring these patches into the new release 7.14 and further ?
 
ko00000000001
just joined
Topic Author
Posts: 9
Joined: Thu Feb 29, 2024 9:12 am

Re: CHR 7.14/7.15b4 can't find network interface in Vultr

Thu Mar 07, 2024 6:33 am

I have the same problem with chr and ethernet ports, could you bring these patches into the new release 7.14 and further ?
I sent a support email, and

It was handled by MikroTik staff.

And gave me the order number: SUP-145324.
 
ko00000000001
just joined
Topic Author
Posts: 9
Joined: Thu Feb 29, 2024 9:12 am

Re: CHR 7.14/7.15b4 can't find network interface in Vultr

Fri Mar 08, 2024 4:49 pm

*) chr - fixed Xen and Vultr missing ethernet (introduced in v7.14)

Release 7.15beta62024-03-08
What's new in 7.15beta6 (2024-Mar-08 08:23):

*) certificate - added support for importing pbes2 encrypted private keys with aes128;
*) chr - fixed bogus messages printed out while booting up the system (introduced in v7.14);
*) chr - fixed Xen and Vultr missing ethernet (introduced in v7.14);
*) ethernet - fixed default names for CRS310-8G+2S+ device (introduced in v7.14);
*) lte - make interface persistent (unused interface configs can be removed, allow to export and examine current configuration without the device present);
*) package - reduced package size for SMIPS;
*) poe-out - improved firmware upgrade stability for AF/AT controlled boards;
*) qos-hw - added congestion avoidance support for 98DX8xxx, 98DX4xxx, 98DX325x switch chips (CLI only);
*) qos-hw - added WRED support for compatible switches;
*) route - rework of route attributes;
*) sfp - improved system stability for CR2004-1G-2XS-PCIe (introduced in v7.14);
*) ssh - added passphrase option for host key import;
*) vrf - fixed VRF interfaces being moved to main table after reboot (introduced in v7.14);
*) wifi-qcom - improved regulatory compliance for L11, L22 devices;
*) wireguard - added peer "name" field and display it in logs;
*) wireguard - do not attempt to connect to peer without specified endpoint-address;

Who is online

Users browsing this forum: Luffy and 2 guests