Turris Build issueshttps://gitlab.nic.cz/turris/os/build/-/issues2024-03-11T22:25:48+01:00https://gitlab.nic.cz/turris/os/build/-/issues/355VLAN filtering broken in kernel 5.15.x (hbl)2024-03-11T22:25:48+01:00Ondřej CaletkaVLAN filtering broken in kernel 5.15.x (hbl)In my setup, Mox acts both as a router for some vlans as well as a switch for others. I put all ports including eth0 into one bridge and use vlan filtering.
```
config device
option name 'br-lan'
option type 'bridge'
...In my setup, Mox acts both as a router for some vlans as well as a switch for others. I put all ports including eth0 into one bridge and use vlan filtering.
```
config device
option name 'br-lan'
option type 'bridge'
option bridge_empty '1'
option force_link '1'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'eth0'
config bridge-vlan
option device 'br-lan'
option vlan '22'
list ports 'lan3'
list ports 'lan4'
config bridge-vlan
option device 'br-lan'
option vlan '60'
list ports 'eth0:t'
list ports 'lan1'
config bridge-vlan
option device 'br-lan'
option vlan '62'
list ports 'lan2'
config bridge-vlan
option device 'br-lan'
option vlan '20'
list ports 'eth0'
config bridge-vlan
option device 'br-lan'
option vlan '21'
list ports 'eth0:t'
config interface 'wan'
option device 'br-lan.20'
…
config interface 'lan'
option device 'br-lan.22'
…
```
```
# bridge vlan show
port vlan-id
eth0 20 PVID Egress Untagged
21
60
lan1 60 PVID Egress Untagged
lan2 62 PVID Egress Untagged
lan3 22 PVID Egress Untagged
lan4 22 PVID Egress Untagged
br-lan 20
21
22
60
62
wlan0 22 PVID Egress Untagged
wlan0-1 62 PVID Egress Untagged
# uname -r
5.4.203
```
After upgrade to kernel 5.15.50 in HBL, I am having troubles with VLAN 60, that just traverses tagged on `eth0` and untagged on `lan1` port. The ingress traffic on `lan1` gets tagged and delivered to `eth0` but in egress direction, the tag is not stripped when leaving `lan1` interface despite `bridge vlan show` showing `Egress Untagged`. There are no problems with other VLANs which don't traverse between ethernet ports. Alo if I use different LAN port in place of eth0 for uplink, problem is gone.https://gitlab.nic.cz/turris/os/build/-/issues/315OpenVPN 2.4 and OpenVPN 2.5 incompatibility2024-03-11T10:15:41+01:00Josef SchlehoferOpenVPN 2.4 and OpenVPN 2.5 incompatibilityI generated user client configuration on OpenVPN 2.4 (HBK) in reForis and now, I tried to use it on OpenVPN 2.5 server using OpenWrt daily snapshots and it seems that it does not work.
Output:
```
Dec 27 11:26:49 turris openvpn(xxx)[135...I generated user client configuration on OpenVPN 2.4 (HBK) in reForis and now, I tried to use it on OpenVPN 2.5 server using OpenWrt daily snapshots and it seems that it does not work.
Output:
```
Dec 27 11:26:49 turris openvpn(xxx)[13564]: --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--da.
Dec 27 11:26:49 turris openvpn(xxx)[13564]: OpenVPN 2.5.5 aarch64-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
Dec 27 11:26:49 turris openvpn(xxx)[13564]: library versions: OpenSSL 1.1.1l 24 Aug 2021, LZO 2.10
Dec 27 11:26:49 turris openvpn(xxx)[13564]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 27 11:26:49 turris openvpn(xxx)[13564]: OpenSSL: error:0909006C:PEM routines:get_name:no start line
Dec 27 11:26:49 turris openvpn(xxx)[13564]: OpenSSL: error:140AD009:SSL routines:SSL_CTX_use_certificate_file:PEM lib
Dec 27 11:26:49 turris openvpn(xxx)[13564]: Cannot load inline certificate file
Dec 27 11:26:49 turris openvpn(xxx)[13564]: Exiting due to fatal error
```Turris OS 7.0https://gitlab.nic.cz/turris/os/build/-/issues/427PPtP VPN seems broken2024-03-04T14:05:24+01:00Michal HruseckyPPtP VPN seems brokenhttps://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/20https://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/20Turris OS 7.0https://gitlab.nic.cz/turris/os/build/-/issues/429Firewall status in LuCI is empty2024-03-04T10:12:20+01:00Michal HruseckyFirewall status in LuCI is emptyAs reported on our forum, firewall statu in LuCI might be empty. This might be some mixup between iptables and nftables firewall, we need to check, but we need to reproduce first.
https://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/27As reported on our forum, firewall statu in LuCI might be empty. This might be some mixup between iptables and nftables firewall, we need to check, but we need to reproduce first.
https://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/27Turris OS 7.0Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/build/-/issues/3992.5 GBps mode not being advertised/recognized2024-01-23T21:00:44+01:00Elias Policena2.5 GBps mode not being advertised/recognizedHi there!
I bought ODI DFP-34X-2C2 module and managed it to work in my Turris Omnia (RTROM01-CE, SN 60129549590, running TurrisOS 6.0.4), replacing ISP ONU.
As others have reported ([in this forum](https://github.com/Anime4000/RTL960x#s...Hi there!
I bought ODI DFP-34X-2C2 module and managed it to work in my Turris Omnia (RTROM01-CE, SN 60129549590, running TurrisOS 6.0.4), replacing ISP ONU.
As others have reported ([in this forum](https://github.com/Anime4000/RTL960x#sucess-story)), I believe that 2500baseX mode should work transparently.
Perhaps, I can see in the logs that, after setting this mode in ODI side, it gets downgraded to 1000baseX mode.
SFP module log:
```
net_device_ops yet
<6>eth0: RTL-8686 at 0xb8012000, 00:00:00:01:00:02, IRQ 26
<6>eth0.2 (): not using net_device_ops yet
<6>eth0.2: RTL-8686 at 0xb8012000, 00:00:00:01:00:02, IRQ 26
<6>eth0.3 (): not using net_device_ops yet
<6>eth0.3: RTL-8686 at 0xb8012000, 00:00:00:01:00:02, IRQ 26
<6>nas0 (): not using net_device_ops yet
<6>nas0: RTL-8686 at 0xb8012000, 00:00:00:01:00:02, IRQ 26
<4>>>>> Set nas0 carrier off !!!
<6>pon0 (): not using net_device_ops yet
<6>pon0: RTL-8686 at 0xb8012000, 00:00:00:01:00:02, IRQ 26
<4>RTL8686 GMAC Probing..
<4>first entry: 0, portmask 127, rx: 802334ec
<4>nas0 -> 0x4
<4>Init RTK Driver Module....*** [RT_DBG] drivers/net/rtl86900/sdk/src//dal/rtl9602c/dal_rtl9602c_classify.c:3567: In function 'dal_rtl9602c_classify_unmatchAction_set' action 2
<4>
<4>OK
<4>Init RTK Core Dev Module....OK
<4>
<4> rtdrv_init !!! for netfilter
<4>pkt_redirect_init complete
<5>interrupt broadcaster init ok!
<4>u32 classifier
<4>nf_conntrack version 0.5.0 (479 buckets, 1916 max)
<6>ip_tables: (C) 2000-2006 Netfilter Core Team
<6>TCP cubic registered
<6>NET: Registered protocol family 17
<5>Bridge firewalling registered
<6>Ebtables v2.0 registered
<6>802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
<6>All bugs added by David S. Miller <davem@redhat.com>
<4>Realtek GPIO Driver for Flash Reload Default
<5>physmap platform flash device: 0b000000 at 14000000
<4>Luna SPI NOR FLASH G3 driver-C22017/MMIO16-1 <5>master->name physmap-flash
<5>cmd: cmdlinepart
<5>14 cmdlinepart partitions found on MTD device physmap-flash
<5>Creating 14 MTD partitions on "physmap-flash":
<5>0x000000000000-0x000000040000 : "boot"
<5>0x000000040000-0x000000042000 : "env"
<5>0x000000042000-0x000000044000 : "env2"
<5>0x000000044000-0x000000080000 : "config"
<5>0x000000080000-0x0000001cc000 : "k0"
<5>0x0000001cc000-0x000000440000 : "r0"
<5>0x000000440000-0x00000058c000 : "k1"
<5>0x00000058c000-0x000000800000 : "r1"
<5>0x000000000000-0x000000001000 : "Partition_008"
<5>0x000000000000-0x000000001000 : "Partition_009"
<5>0x000000000000-0x000000001000 : "Partition_010"
<5>0x000000000000-0x000000001000 : "Partition_011"
<5>0x000000080000-0x0000001cc000 : "linux"
<5>0x0000001cc000-0x000000440000 : "rootfs"
<4>VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
<6>Freeing unused kernel memory: 100k freed
<4>re8670_open 3341
<4>omci platform attached!
<4>*** [RT_ERR] drivers/net/rtl86900/sdk/src//dal/rtl9602c/dal_rtl9602c_ponmac.c:1039: In function '_rtl9602c_ponMacGponModeV2_set'
<4> Error Code: 0x8848
<4>
<4>*** [RT_DBG] drivers/net/rtl86900/sdk/src//dal/rtl9602c/dal_rtl9602c_classify.c:3567: In function 'dal_rtl9602c_classify_unmatchAction_set' action 1
<4>
<4>*** [RT_DBG] drivers/net/rtl86900/sdk/src//dal/rtl9602c/dal_rtl9602c_classify.c:3567: In function 'dal_rtl9602c_classify_unmatchAction_set' action 1
<4>
<3>register_gpon_evt_state: register gpon event state Successfully !
<4>priority: 0, portmask 127, rx: 802334ec
<4>insert here, priority: 7, portmask 255, rx: c026b34c
<4>change mode to 4(HiSGMII PHY)
<4>send to user app (5) fail (-1)
<4>write watchdog_flag to 0x00000001
<4>[Kthread : watchdog ] init complete!
<4>************ Watchdog Setting ****************
<4>WDT_E=1, (1-enable, 0-disable)
<4>LX(MHz)=200
<4>WDT_CLK_SC=3
<4>PH1_TO=31
<4>PH2_TO=0
<4>WDT_RESET_MODE=0
<4>**********************************************
<4>port 2 assign to pon0
<4>pon0 -> 0x4
<6>device eth0 entered promiscuous mode
<4>priority: 7, portmask 255, rx: c026b34c
<4>priority: 0, portmask 127, rx: 802334ec
<4>insert here, priority: 4, portmask 4, rx: 80172968
<6>br0: port 1(eth0) entering learning state
<4>drivers/net/rtl86900/sdk/src/rtk/pon_led.c:1152 led sw blink init complete!
<6>br0: port 1(eth0) entering forwarding state
<4>drivers/net/rtl86900/sdk/src/module/lan_sds/lan_sds_main.c:679 SFP_TASK_MASK_EEPROM_128TO247
<4>change mode to 1(Fiber 1G)
<4>eth0: received packet with own address as source address 38-3a-21-27-eb-86 loop intf=0 0
<4>eth0: received packet with own address as source address 38-3a-21-27-eb-86 loop intf=0 0
```
Turris kernel log:
```
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.15.82 (packaging@turris.cz) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 8.4.0 r16803+125-784565b6a0) 8.4.0, GNU ld (GNU Binutils) 2.34) #0 SMP Sun Dec 11 23:19:41 2022
[ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Turris Omnia
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x000000002fffffff]
[ 0.000000] HighMem [mem 0x0000000030000000-0x000000007fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000] percpu: Embedded 11 pages/cpu s14732 r8192 d22132 u45056
[ 0.000000] pcpu-alloc: s14732 r8192 d22132 u45056 alloc=11*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 522560
[ 0.000000] Kernel command line: earlyprintk rootwait console=ttyS0,115200 rootfstype=btrfs root=PARTUUID=00000000-01 rootflags=commit=5,subvol=@ rw cfg80211.freg=**
[ 0.000000] Bootloader command line not present
[ 0.000000] Unknown kernel command line parameters "earlyprintk mangled_fs=btrfs", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 2063496K/2097152K available (9216K kernel code, 669K rwdata, 2180K rodata, 1024K init, 258K bss, 33656K reserved, 0K cma-reserved, 1310720K highmem)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] Registering MPIC SoC Error Interrupt Controller
[ 0.000000] L2C: DT/platform modifies aux control register: 0x06070000 -> 0x16070000
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 D prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[ 0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[ 0.000001] sched_clock: 64 bits at 800MHz, resolution 1ns, wraps every 4398046511103ns
[ 0.000018] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0xb881274fa3, max_idle_ns: 440795210636 ns
[ 0.000036] Switching to timer-based delay loop, resolution 1ns
[ 0.000180] Ignoring duplicate/late registration of read_current_timer delay
[ 0.000187] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[ 0.000374] Console: colour dummy device 80x30
[ 0.000404] Calibrating delay loop (skipped), value calculated using timer frequency.. 1600.00 BogoMIPS (lpj=8000000)
[ 0.000414] pid_max: default: 32768 minimum: 301
[ 0.000509] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.000519] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.000917] CPU: Testing write buffer coherency: ok
[ 0.000939] CPU0: Spectre v2: using BPIALL workaround
[ 0.001041] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.001341] Setting up static identity map for 0x100000 - 0x100060
[ 0.001423] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[ 0.001511] mvebu-pmsu: Initializing Power Management Service Unit
[ 0.001571] rcu: Hierarchical SRCU implementation.
[ 0.001646] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build
[ 0.001708] smp: Bringing up secondary CPUs ...
[ 0.001872] Booting CPU 1
[ 0.002015] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.002022] CPU1: Spectre v2: using BPIALL workaround
[ 0.002081] smp: Brought up 1 node, 2 CPUs
[ 0.002088] SMP: Total of 2 processors activated (3200.00 BogoMIPS).
[ 0.002093] CPU: All CPU(s) started in SVC mode.
[ 0.002453] devtmpfs: initialized
[ 0.004314] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.004366] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.004376] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.004451] pinctrl core: initialized pinctrl subsystem
[ 0.005001] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.005604] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.006058] thermal_sys: Registered thermal governor 'step_wise'
[ 0.006200] cpuidle: using governor ladder
[ 0.006290] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.006297] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.006421] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[ 0.006429] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
[ 0.014955] cryptd: max_cpu_qlen set to 1000
[ 0.015753] raid6: skip pq benchmark and using algorithm neonx8
[ 0.015761] raid6: using neon recovery algorithm
[ 0.016028] SCSI subsystem initialized
[ 0.016108] libata version 3.00 loaded.
[ 0.016197] usbcore: registered new interface driver usbfs
[ 0.016218] usbcore: registered new interface driver hub
[ 0.016236] usbcore: registered new device driver usb
[ 0.016860] clocksource: Switched to clocksource arm_global_timer
[ 0.019111] NET: Registered PF_INET protocol family
[ 0.019224] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.019763] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 0.019783] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.019793] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.019833] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.019897] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.019946] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.019977] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.020118] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.020138] PCI: CLS 0 bytes, default 64
[ 0.020610] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.022525] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[ 0.024510] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.024517] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.024966] xor: measuring software checksum speed
[ 0.028802] arm4regs : 2598 MB/sec
[ 0.033729] 8regs : 1998 MB/sec
[ 0.038288] 32regs : 2160 MB/sec
[ 0.043502] neon : 1887 MB/sec
[ 0.043506] xor: using function: arm4regs (2598 MB/sec)
[ 0.043548] bounce: pool size: 64 pages
[ 0.043578] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 0.044713] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
[ 0.045254] debugfs: Directory 'f1018100.gpio' with parent 'regmap' already present!
[ 0.045567] debugfs: Directory 'f1018140.gpio' with parent 'regmap' already present!
[ 0.045892] mvebu-pcie soc:pcie: host bridge /soc/pcie ranges:
[ 0.045920] mvebu-pcie soc:pcie: MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[ 0.045935] mvebu-pcie soc:pcie: MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[ 0.045949] mvebu-pcie soc:pcie: MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[ 0.045963] mvebu-pcie soc:pcie: MEM 0x00f1048000..0x00f1049fff -> 0x0000048000
[ 0.045987] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 0.046000] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 0.046012] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[ 0.046024] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[ 0.046036] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[ 0.046048] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[ 0.046060] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[ 0.046069] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[ 0.046167] mvebu-pcie soc:pcie: pcie0.0: Slot power limit 10.0W
[ 0.046223] mvebu-pcie soc:pcie: pcie1.0: Slot power limit 10.0W
[ 0.046274] mvebu-pcie soc:pcie: pcie2.0: Slot power limit 10.0W
[ 0.046823] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[ 0.046835] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.046845] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[ 0.046880] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[ 0.046894] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[ 0.046902] pci_bus 0000:00: root bus resource [mem 0xf1048000-0xf1049fff] (bus address [0x00048000-0x00049fff])
[ 0.046908] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[ 0.046913] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 0.046988] pci 0000:00:01.0: [11ab:6820] type 01 class 0x060400
[ 0.047167] pci 0000:00:02.0: [11ab:6820] type 01 class 0x060400
[ 0.047309] pci 0000:00:03.0: [11ab:6820] type 01 class 0x060400
[ 0.048158] PCI: bus0: Fast back to back transfers disabled
[ 0.048166] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.048177] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.048186] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.049032] PCI: bus1: Fast back to back transfers enabled
[ 0.049039] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 0.049113] pci 0000:02:00.0: [14c3:7915] type 00 class 0x000280
[ 0.049135] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
[ 0.049150] pci 0000:02:00.0: reg 0x18: [mem 0x00000000-0x00003fff 64bit pref]
[ 0.049163] pci 0000:02:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit pref]
[ 0.049235] pci 0000:02:00.0: supports D1 D2
[ 0.049241] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.050137] PCI: bus2: Fast back to back transfers disabled
[ 0.050145] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 0.050218] pci 0000:03:00.0: [168c:003c] type 00 class 0x028000
[ 0.050240] pci 0000:03:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[ 0.050267] pci 0000:03:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[ 0.050338] pci 0000:03:00.0: supports D1 D2
[ 0.051233] PCI: bus3: Fast back to back transfers disabled
[ 0.051240] pci_bus 0000:03: busn_res: [bus 03-ff] end is updated to 03
[ 0.051264] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe03fffff]
[ 0.051273] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0400000-0xe07fffff]
[ 0.051281] pci 0000:00:03.0: BAR 8: assigned [mem 0xe0800000-0xe0bfffff]
[ 0.051288] pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff]
[ 0.051295] pci 0000:00:02.0: BAR 7: assigned [io 0x20000-0x20fff]
[ 0.051301] pci 0000:00:03.0: BAR 7: assigned [io 0x30000-0x30fff]
[ 0.051307] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.051313] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 0.051325] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe03fffff]
[ 0.051338] pci 0000:02:00.0: BAR 0: assigned [mem 0xe0400000-0xe04fffff 64bit pref]
[ 0.051351] pci 0000:02:00.0: BAR 2: assigned [mem 0xe0500000-0xe0503fff 64bit pref]
[ 0.051363] pci 0000:02:00.0: BAR 4: assigned [mem 0xe0504000-0xe0504fff 64bit pref]
[ 0.051374] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 0.051380] pci 0000:00:02.0: bridge window [io 0x20000-0x20fff]
[ 0.051389] pci 0000:00:02.0: bridge window [mem 0xe0400000-0xe07fffff]
[ 0.051401] pci 0000:03:00.0: BAR 0: assigned [mem 0xe0800000-0xe09fffff 64bit]
[ 0.051412] pci 0000:03:00.0: BAR 6: assigned [mem 0xe0a00000-0xe0a0ffff pref]
[ 0.051419] pci 0000:00:03.0: PCI bridge to [bus 03]
[ 0.051424] pci 0000:00:03.0: bridge window [io 0x30000-0x30fff]
[ 0.051433] pci 0000:00:03.0: bridge window [mem 0xe0800000-0xe0bfffff]
[ 0.051499] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[ 0.051569] pcieport 0000:00:01.0: pciehp: Slot #1 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[ 0.051818] pcieport 0000:00:01.0: pciehp: Slot(1): Card present
[ 0.051875] pcieport 0000:00:02.0: enabling device (0140 -> 0143)
[ 0.051937] pcieport 0000:00:02.0: pciehp: Slot #2 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[ 0.052349] pcieport 0000:00:03.0: enabling device (0140 -> 0143)
[ 0.052406] pcieport 0000:00:03.0: pciehp: Slot #3 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[ 0.052978] mv_xor f1060800.xor: Marvell shared XOR driver
[ 0.066859] mvebu-pcie soc:pcie: pcie2.0: link up
[ 0.066881] mvebu-pcie soc:pcie: pcie1.0: link up
[ 0.107286] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[ 0.107425] mv_xor f1060900.xor: Marvell shared XOR driver
[ 0.167255] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[ 0.167535] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.168854] printk: console [ttyS0] disabled
[ 0.188949] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 30, base_baud = 15625000) is a 16550A
[ 1.472877] printk: console [ttyS0] enabled
[ 1.497557] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 31, base_baud = 15625000) is a 16550A
[ 1.508949] loop: module loaded
[ 1.512110] Loading iSCSI transport class v2.0-870.
[ 1.518135] ahci-mvebu f10a8000.sata: supply ahci not found, using dummy regulator
[ 1.525803] ahci-mvebu f10a8000.sata: supply phy not found, using dummy regulator
[ 1.533349] ahci-mvebu f10a8000.sata: supply target not found, using dummy regulator
[ 1.541192] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[ 1.550276] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[ 1.559610] scsi host0: ahci-mvebu
[ 1.563306] scsi host1: ahci-mvebu
[ 1.566793] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 53
[ 1.574749] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 53
[ 1.583720] spi-nor spi0.0: found mx25l6405d, expected s25fl164k
[ 1.589777] spi-nor spi0.0: mx25l6405d (8192 Kbytes)
[ 1.594874] 2 fixed-partitions partitions found on MTD device spi0.0
[ 1.601268] Creating 2 MTD partitions on "spi0.0":
[ 1.606073] 0x000000000000-0x000000100000 : "U-Boot"
[ 1.611345] 0x000000100000-0x000000800000 : "Rescue system"
[ 1.618942] hwmon hwmon0: temp1_input not attached to any thermal zone
[ 1.625948] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled
[ 1.635007] mvneta f1070000.ethernet eth0: Using hardware mac address d8:58:d7:01:09:30
[ 1.644333] mvneta f1030000.ethernet eth1: Using hardware mac address d8:58:d7:01:09:2e
[ 1.653631] mvneta f1034000.ethernet eth2: Using hardware mac address d8:58:d7:01:09:2f
[ 1.661811] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.668371] ehci-pci: EHCI PCI platform driver
[ 1.672857] ehci-platform: EHCI generic platform driver
[ 1.678186] ehci-orion: EHCI orion driver
[ 1.682298] orion-ehci f1058000.usb: EHCI Host Controller
[ 1.687728] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1
[ 1.695363] orion-ehci f1058000.usb: irq 49, io mem 0xf1058000
[ 1.726864] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[ 1.733105] hub 1-0:1.0: USB hub found
[ 1.736904] hub 1-0:1.0: 1 port detected
[ 1.741260] xhci-hcd f10f0000.usb3: xHCI Host Controller
[ 1.746598] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2
[ 1.754174] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010
[ 1.763451] xhci-hcd f10f0000.usb3: irq 55, io mem 0xf10f0000
[ 1.769297] xhci-hcd f10f0000.usb3: xHCI Host Controller
[ 1.774627] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 3
[ 1.782174] xhci-hcd f10f0000.usb3: Host supports USB 3.0 SuperSpeed
[ 1.788815] hub 2-0:1.0: USB hub found
[ 1.792590] hub 2-0:1.0: 1 port detected
[ 1.796659] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1.804996] hub 3-0:1.0: USB hub found
[ 1.808780] hub 3-0:1.0: 1 port detected
[ 1.812907] xhci-hcd f10f8000.usb3: xHCI Host Controller
[ 1.818255] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4
[ 1.825831] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010
[ 1.835106] xhci-hcd f10f8000.usb3: irq 56, io mem 0xf10f8000
[ 1.840937] xhci-hcd f10f8000.usb3: xHCI Host Controller
[ 1.846266] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5
[ 1.853784] xhci-hcd f10f8000.usb3: Host supports USB 3.0 SuperSpeed
[ 1.860397] hub 4-0:1.0: USB hub found
[ 1.864169] hub 4-0:1.0: 1 port detected
[ 1.868240] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1.876550] hub 5-0:1.0: USB hub found
[ 1.880330] hub 5-0:1.0: 1 port detected
[ 1.884485] usbcore: registered new interface driver usb-storage
[ 1.891023] armada38x-rtc f10a3800.rtc: registered as rtc0
[ 1.896593] armada38x-rtc f10a3800.rtc: setting system clock to 2022-12-12T03:00:48 UTC (1670814048)
[ 1.905914] i2c_dev: i2c /dev entries driver
[ 1.912471] orion_wdt: Initial timeout 171 sec
[ 1.913058] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.917183] sdhci: Secure Digital Host Controller Interface driver
[ 1.928562] sdhci: Copyright(c) Pierre Ossman
[ 1.933038] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.939686] marvell-cesa f1090000.crypto: CESA device successfully registered
[ 1.947366] NET: Registered PF_INET6 protocol family
[ 1.952968] Segment Routing with IPv6
[ 1.956661] In-situ OAM (IOAM) with IPv6
[ 1.960659] NET: Registered PF_PACKET protocol family
[ 1.965010] mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci] using ADMA
[ 1.965758] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 1.986243] 8021q: 802.1Q VLAN Support v1.8
[ 1.990556] Registering SWP/SWPB emulation handler
[ 1.997608] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no
[ 2.101993] mmc0: new high speed MMC card at address 0001
[ 2.107763] mmcblk0: mmc0:0001 008G30 7.28 GiB
[ 2.113634] mmcblk0: p1
[ 2.116471] mmcblk0boot0: mmc0:0001 008G30 4.00 MiB
[ 2.121893] mmcblk0boot1: mmc0:0001 008G30 4.00 MiB
[ 2.127146] mmcblk0rpmb: mmc0:0001 008G30 4.00 MiB, chardev (247:0)
[ 2.966863] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.973130] ata1.00: ATA-9: GTA 256GB SSD, HCS1A25C, max UDMA/133
[ 2.979250] ata1.00: 500118192 sectors, multi 1: LBA48 NCQ (depth 32)
[ 2.986773] ata1.00: configured for UDMA/133
[ 2.991244] scsi 0:0:0:0: Direct-Access ATA GTA 256GB SSD A25C PQ: 0 ANSI: 5
[ 2.999803] sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
[ 3.007350] sd 0:0:0:0: [sda] Write Protect is off
[ 3.012155] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.012190] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.022240] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 3.029345] squashfs: Unknown parameter 'commit'
[ 3.035028] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 3.042285] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 1th superblock
[ 3.050968] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 3.058220] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 2th superblock
[ 3.066898] BTRFS: device fsid ec715b08-b0a6-4fb2-aca1-07df948ffd7a devid 1 transid 2787793 /dev/root scanned by swapper/0 (1)
[ 3.079709] BTRFS info (device mmcblk0p1): disk space caching is enabled
[ 3.086432] BTRFS info (device mmcblk0p1): has skinny extents
[ 3.112892] BTRFS info (device mmcblk0p1): enabling ssd optimizations
[ 3.126232] VFS: Mounted root (btrfs filesystem) on device 0:14.
[ 3.133909] devtmpfs: mounted
[ 3.137325] Freeing unused kernel image (initmem) memory: 1024K
[ 3.177017] Run /sbin/init as init process
[ 3.181124] with arguments:
[ 3.181126] /sbin/init
[ 3.181128] earlyprintk
[ 3.181130] with environment:
[ 3.181132] HOME=/
[ 3.181134] TERM=linux
[ 3.181136] mangled_fs=btrfs
[ 3.219493] init: Console is alive
[ 3.222994] init: - watchdog -
[ 3.296885] pcieport 0000:00:01.0: pciehp: Slot(1): No link
[ 3.519262] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 3.534425] Key type encrypted registered
[ 3.541185] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.com
[ 3.552150] ehci-fsl: Freescale EHCI Host controller driver
[ 3.559258] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.565862] ohci-platform: OHCI generic platform driver
[ 3.575434] uhci_hcd: USB Universal Host Controller Interface driver
[ 3.582303] ohci-pci: OHCI PCI platform driver
[ 3.588666] usbcore: registered new interface driver uas
[ 3.594123] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 3.604194] init: - preinit -
[ 5.713755] mount_root: mounting /dev/root
[ 5.720128] mount_root: loading kmods from internal overlay
[ 5.738236] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[ 5.746152] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[ 6.414082] block: attempting to load /etc/config/fstab
[ 6.421879] block: extroot: not configured
[ 6.445681] urandom-seed: Seeding with /etc/urandom.seed
[ 6.808721] BTRFS: device label srv devid 1 transid 50797 /dev/sda scanned by btrfs (625)
[ 6.817026] BTRFS info: devid 1 device path /dev/root changed to /dev/mmcblk0p1 scanned by btrfs (625)
[ 6.828992] procd: - early -
[ 6.831911] procd: - watchdog -
[ 7.361619] procd: - watchdog -
[ 7.364984] procd: - ubus -
[ 7.374276] random: ubusd: uninitialized urandom read (4 bytes read)
[ 7.417240] random: ubusd: uninitialized urandom read (4 bytes read)
[ 7.423738] random: ubusd: uninitialized urandom read (4 bytes read)
[ 7.430898] procd: - init -
[ 7.795316] kmodloader: loading kernel modules from /etc/modules.d/*
[ 7.862901] Key type dns_resolver registered
[ 7.872624] RPC: Registered named UNIX socket transport module.
[ 7.878600] RPC: Registered udp transport module.
[ 7.883318] RPC: Registered tcp transport module.
[ 7.888036] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 7.901273] tun: Universal TUN/TAP device driver, 1.6
[ 7.912572] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 7.926561] mv88e6085 f1072004.mdio-mii:10: switch 0x1760 detected: Marvell 88E6176, revision 1
[ 8.079971] random: crng init done
[ 8.083395] random: 23 urandom warning(s) missed due to ratelimiting
[ 8.997155] mv88e6085 f1072004.mdio-mii:10: configuring for fixed/rgmii-id link mode
[ 9.007059] mv88e6085 f1072004.mdio-mii:10: configuring for fixed/rgmii-id link mode
[ 9.016454] mv88e6085 f1072004.mdio-mii:10: Link is Up - 1Gbps/Full - flow control off
[ 9.025365] mv88e6085 f1072004.mdio-mii:10: Link is Up - 1Gbps/Full - flow control off
[ 9.129145] mv88e6085 f1072004.mdio-mii:10 lan0 (uninitialized): PHY [mv88e6xxx-0:00] driver [Marvell 88E1540] (irq=79)
[ 9.240740] mv88e6085 f1072004.mdio-mii:10 lan1 (uninitialized): PHY [mv88e6xxx-0:01] driver [Marvell 88E1540] (irq=80)
[ 9.357204] mv88e6085 f1072004.mdio-mii:10 lan2 (uninitialized): PHY [mv88e6xxx-0:02] driver [Marvell 88E1540] (irq=81)
[ 9.476993] mv88e6085 f1072004.mdio-mii:10 lan3 (uninitialized): PHY [mv88e6xxx-0:03] driver [Marvell 88E1540] (irq=82)
[ 9.592029] mv88e6085 f1072004.mdio-mii:10 lan4 (uninitialized): PHY [mv88e6xxx-0:04] driver [Marvell 88E1540] (irq=83)
[ 9.608181] DSA: tree 0 setup
[ 9.623331] NFS: Registering the id_resolver key type
[ 9.628475] Key type id_resolver registered
[ 9.632676] Key type id_legacy registered
[ 9.686422] i2c i2c-0: Added multiplexed i2c bus 1
[ 9.691420] i2c i2c-0: Added multiplexed i2c bus 2
[ 9.696383] i2c i2c-0: Added multiplexed i2c bus 3
[ 9.701518] i2c i2c-0: Added multiplexed i2c bus 4
[ 9.706626] i2c i2c-0: Added multiplexed i2c bus 5
[ 9.715721] i2c i2c-0: Added multiplexed i2c bus 6
[ 9.720808] i2c i2c-0: Added multiplexed i2c bus 7
[ 9.726282] pca953x 8-0071: supply vcc not found, using dummy regulator
[ 9.733125] pca953x 8-0071: using no AI
[ 9.740823] i2c i2c-0: Added multiplexed i2c bus 8
[ 9.745658] pca954x 0-0070: registered 8 multiplexed busses for I2C mux pca9547
[ 9.754270] sfp sfp: Host maximum power 3.0W
[ 9.754886] GACT probability on
[ 9.762343] Mirror/redirect action on
[ 9.769931] u32 classifier
[ 9.772662] input device check on
[ 9.776341] Actions configured
[ 9.785039] fuse: init (API version 7.34)
[ 9.793212] at24 1-0054: supply vcc not found, using dummy regulator
[ 9.804318] at24 1-0054: 8192 byte 24c64 EEPROM, writable, 1 bytes/write
[ 9.811902] Bridge firewalling registered
[ 9.821868] Loading modules backported from Linux version v5.15.58-0-g7d8048d4e064
[ 9.829497] Backport generated by backports.git v5.15.58-1-0-g42a95ce7
[ 9.855383] usbcore: registered new interface driver ums-alauda
[ 9.861840] usbcore: registered new interface driver ums-cypress
[ 9.868565] usbcore: registered new interface driver ums-datafab
[ 9.875109] usbcore: registered new interface driver ums-freecom
[ 9.881705] usbcore: registered new interface driver ums-isd200
[ 9.892342] usbcore: registered new interface driver ums-jumpshot
[ 9.899177] usbcore: registered new interface driver ums-karma
[ 9.905774] usbcore: registered new interface driver ums-sddr09
[ 9.912374] usbcore: registered new interface driver ums-sddr55
[ 9.919025] usbcore: registered new interface driver ums-usbat
[ 9.926107] usbcore: registered new interface driver usbserial_generic
[ 9.932719] usbserial: USB Serial support registered for generic
[ 9.954187] xt_time: kernel timezone is -0000
[ 9.989459] mt7915e 0000:02:00.0: enabling device (0140 -> 0142)
[ 10.098172] sfp sfp: module ODI DFP-34X-2C2 rev sn XPON22100614 dc 221009
[ 10.107541] mvneta f1034000.ethernet eth2: switched to inband/1000base-x link mode
[ 10.132855] mt7915e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222184017a
[ 10.132855]
[ 10.168508] mt7915e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20211222184052
[ 10.196071] mt7915e 0000:02:00.0: WA Firmware Version: DEV_000000, Build Time: 20211222184111
[ 10.354933] PPP generic driver version 2.4.2
[ 10.360192] NET: Registered PF_PPPOX protocol family
[ 10.367669] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 10.375530] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[ 10.399272] ath10k_pci 0000:03:00.0: enabling device (0140 -> 0142)
[ 10.405758] ath10k_pci 0000:03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 10.660499] ath10k_pci 0000:03:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[ 10.669776] ath10k_pci 0000:03:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[ 10.679409] ath10k_pci 0000:03:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
[ 10.736708] ath10k_pci 0000:03:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 11.876556] ath10k_pci 0000:03:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
[ 11.998290] ath: EEPROM regdomain: 0x0
[ 11.998299] ath: EEPROM indicates default country code should be used
[ 11.998301] ath: doing EEPROM country->regdmn map search
[ 11.998305] ath: country maps to regdmn code: 0x3a
[ 11.998308] ath: Country alpha2 being used: US
[ 11.998311] ath: Regpair used: 0x3a
[ 15.657664] usbcore: registered new interface driver qcserial
[ 15.663462] usbserial: USB Serial support registered for Qualcomm USB modem
[ 15.676783] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 18.465949] mvneta f1030000.ethernet eth1: configuring for fixed/rgmii link mode
[ 18.474095] mvneta f1030000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[ 18.482206] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 18.489378] mv88e6085 f1072004.mdio-mii:10 lan0: configuring for phy/gmii link mode
[ 18.502497] br-lan: port 1(lan0) entered blocking state
[ 18.507784] br-lan: port 1(lan0) entered disabled state
[ 18.564099] device lan0 entered promiscuous mode
[ 18.568772] device eth1 entered promiscuous mode
[ 18.741017] mv88e6085 f1072004.mdio-mii:10 lan1: configuring for phy/gmii link mode
[ 18.796955] mv88e6085 f1072004.mdio-mii:10 lan0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 18.865008] br-lan: port 2(lan1) entered blocking state
[ 18.865927] mv88e6085 f1072004.mdio-mii:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[ 18.870263] br-lan: port 2(lan1) entered disabled state
[ 18.932264] device lan1 entered promiscuous mode
[ 19.150136] mv88e6085 f1072004.mdio-mii:10 lan2: configuring for phy/gmii link mode
[ 19.190118] br-lan: port 1(lan0) entered blocking state
[ 19.195376] br-lan: port 1(lan0) entered forwarding state
[ 19.217202] br-lan: port 2(lan1) entered blocking state
[ 19.222458] br-lan: port 2(lan1) entered forwarding state
[ 19.241487] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 19.266844] BTRFS info (device sda): disk space caching is enabled
[ 19.273071] BTRFS info (device sda): has skinny extents
[ 19.303442] BTRFS info (device sda): enabling ssd optimizations
[ 19.371538] br-lan: port 3(lan2) entered blocking state
[ 19.376790] br-lan: port 3(lan2) entered disabled state
[ 19.402155] mv88e6085 f1072004.mdio-mii:10 lan2: Link is Up - 1Gbps/Full - flow control rx/tx
[ 19.983748] device lan2 entered promiscuous mode
[ 20.012570] br-lan: port 3(lan2) entered blocking state
[ 20.017843] br-lan: port 3(lan2) entered forwarding state
[ 20.026829] mv88e6085 f1072004.mdio-mii:10 lan3: configuring for phy/gmii link mode
[ 20.098417] br-lan: port 4(lan3) entered blocking state
[ 20.103680] br-lan: port 4(lan3) entered disabled state
[ 20.170789] device lan3 entered promiscuous mode
[ 20.202401] mv88e6085 f1072004.mdio-mii:10 lan4: configuring for phy/gmii link mode
[ 20.277152] br-lan: port 5(lan4) entered blocking state
[ 20.282411] br-lan: port 5(lan4) entered disabled state
[ 20.344113] device lan4 entered promiscuous mode
[ 20.383151] mvneta f1034000.ethernet eth2: configuring for inband/1000base-x link mode
[ 20.446951] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx
[ 20.455012] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[ 20.461525] IPv6: ADDRCONF(NETDEV_CHANGE): eth2.2000: link becomes ready
[ 27.350234] process '@/usr/bin/zerotier-one' started with executable stack
[ 29.470689] br-lan: port 6(vethIsxPBP) entered blocking state
[ 29.476468] br-lan: port 6(vethIsxPBP) entered disabled state
[ 29.482472] device vethIsxPBP entered promiscuous mode
[ 29.520713] eth0: renamed from veth1g5b7M
[ 29.558102] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 29.564552] IPv6: ADDRCONF(NETDEV_CHANGE): vethIsxPBP: link becomes ready
[ 29.571568] br-lan: port 6(vethIsxPBP) entered blocking state
[ 29.577361] br-lan: port 6(vethIsxPBP) entered forwarding state
[ 29.878858] br-lan: port 7(vethzdk0fh) entered blocking state
[ 29.884639] br-lan: port 7(vethzdk0fh) entered disabled state
[ 29.890634] device vethzdk0fh entered promiscuous mode
[ 29.937707] br-lan: port 7(vethzdk0fh) entered blocking state
[ 29.943490] br-lan: port 7(vethzdk0fh) entered forwarding state
[ 29.978309] eth0: renamed from veth7OaZlz
[ 30.050915] IPv6: ADDRCONF(NETDEV_CHANGE): vethzdk0fh: link becomes ready
[ 30.851636] pppoe-wan: renamed from ppp0
[ 43.826279] docker0: port 1(veth6250cc1) entered blocking state
[ 43.832290] docker0: port 1(veth6250cc1) entered disabled state
[ 43.838449] device veth6250cc1 entered promiscuous mode
[ 46.423556] eth0: renamed from veth4330730
[ 46.481672] IPv6: ADDRCONF(NETDEV_CHANGE): veth6250cc1: link becomes ready
[ 46.489874] docker0: port 1(veth6250cc1) entered blocking state
[ 46.495821] docker0: port 1(veth6250cc1) entered forwarding state
[ 46.529298] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
[ 66.794991] TCP: request_sock_TCP: Possible SYN flooding on port 5000. Sending cookies. Check SNMP counters.
[ 94.469869] docker0: port 1(veth6250cc1) entered disabled state
[ 94.476427] veth4330730: renamed from eth0
[ 94.591912] docker0: port 1(veth6250cc1) entered disabled state
[ 94.600511] device veth6250cc1 left promiscuous mode
[ 94.605518] docker0: port 1(veth6250cc1) entered disabled state
[ 94.800585] docker0: port 1(veth23868d8) entered blocking state
[ 94.806562] docker0: port 1(veth23868d8) entered disabled state
[ 94.812777] device veth23868d8 entered promiscuous mode
[ 94.820955] docker0: port 1(veth23868d8) entered blocking state
[ 94.826942] docker0: port 1(veth23868d8) entered forwarding state
[ 95.553352] docker0: port 1(veth23868d8) entered disabled state
[ 95.703530] eth0: renamed from veth87afa25
[ 95.743873] IPv6: ADDRCONF(NETDEV_CHANGE): veth23868d8: link becomes ready
[ 95.750941] docker0: port 1(veth23868d8) entered blocking state
[ 95.756906] docker0: port 1(veth23868d8) entered forwarding state
[ 106.072583] TCP: request_sock_TCPv6: Possible SYN flooding on port 5000. Sending cookies. Check SNMP counters.
[ 3588.663946] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead.
[44408.831180] br-lan: port 1(lan0) entered disabled state
[44408.837260] mv88e6085 f1072004.mdio-mii:10 lan0: Link is Down
[44434.230309] mv88e6085 f1072004.mdio-mii:10 lan0: Link is Up - 1Gbps/Full - flow control rx/tx
[44434.238937] br-lan: port 1(lan0) entered blocking state
[44434.244183] br-lan: port 1(lan0) entered forwarding state
[47703.771367] pppoe-wan: renamed from ppp0
[47738.040041] docker0: port 1(veth23868d8) entered disabled state
[47738.048085] veth87afa25: renamed from eth0
[47738.166507] docker0: port 1(veth23868d8) entered disabled state
[47738.175657] device veth23868d8 left promiscuous mode
[47738.180720] docker0: port 1(veth23868d8) entered disabled state
[47738.364785] docker0: port 1(vethfb1e356) entered blocking state
[47738.370793] docker0: port 1(vethfb1e356) entered disabled state
[47738.376993] device vethfb1e356 entered promiscuous mode
[47738.384386] docker0: port 1(vethfb1e356) entered blocking state
[47738.390374] docker0: port 1(vethfb1e356) entered forwarding state
[47739.065556] docker0: port 1(vethfb1e356) entered disabled state
[47739.326272] eth0: renamed from veth0a77a23
[47739.366345] IPv6: ADDRCONF(NETDEV_CHANGE): vethfb1e356: link becomes ready
[47739.373379] docker0: port 1(vethfb1e356) entered blocking state
[47739.379340] docker0: port 1(vethfb1e356) entered forwarding state
[86348.391702] mv88e6085 f1072004.mdio-mii:10 lan0: Link is Down
[86348.422739] br-lan: port 1(lan0) entered disabled state
[86365.861397] mv88e6085 f1072004.mdio-mii:10 lan0: Link is Up - 1Gbps/Full - flow control rx/tx
[86365.870014] br-lan: port 1(lan0) entered blocking state
[86365.875277] br-lan: port 1(lan0) entered forwarding state
```
I have done some tests, trying to figure out whats is happening, like:
- Flash modes 4, 5 and 6 in ONU side
- Force (via ethtool) 2500baseX mode
The commands and output I ran:
```
root@turris:~# ethtool -s eth2 autoneg off speed 2500 duplex full
Cannot set new settings: Invalid argument
not setting speed
not setting duplex
not setting autoneg
root@turris:~# ethtool -s eth2 autoneg off
Cannot set new settings: Invalid argument
not setting autoneg
root@turris:~# ethtool -s eth2 speed 2500 duplex half
Cannot advertise speed 2500 duplex full
root@turris:~# ethtool -s eth2 speed 2500
Cannot advertise speed 2500
```
Is there anything I can try doing for Turris to work in 2.5Gbps mode?https://gitlab.nic.cz/turris/os/build/-/issues/381IPv6 neighbor discovery breaks when igmp_snooping is enabled on the br-lan de...2023-06-19T08:35:35+02:00Mark BryarsIPv6 neighbor discovery breaks when igmp_snooping is enabled on the br-lan device.After the 6.0[.1] Upgrade, my IPv6 was partially broken, one host on my network worked, and hosts could talk to each other,
pings could reach the internet, but the replies didnt make it back.
I discovered ip -6 neigh showed lots of fail...After the 6.0[.1] Upgrade, my IPv6 was partially broken, one host on my network worked, and hosts could talk to each other,
pings could reach the internet, but the replies didnt make it back.
I discovered ip -6 neigh showed lots of failures resolving the hosts,
* tcpdump -eni br-lan icmp6 # showed it was sending neighbour solicitation but the device wasn't receiving them with a tcpdump there
* tcpdump -eni lan2 icmp6 # showed the icmp packets from the host that was pinging google, but not the solicitation packets I expected from above
Looking at my /etc/config/network I saw I had option igmp_snooping '1'
I tried setting this to 0 and IPv6 started working again.
I have a multicast feed from my ISP that i'd like to be able to use without flooding all of the ports, but this is more important.Turris OS 6.4.0https://gitlab.nic.cz/turris/os/build/-/issues/223File capabilities (setcap, getcap) missing in Turris OS 52023-03-03T02:02:31+01:00Ivan VilataFile capabilities (setcap, getcap) missing in Turris OS 5(Copying from forum entry with same topic, as this looks like the correct place to notify this.)
Hi! I recently upgraded my Omnia from Turris OS 3 to 5 (5.1.4 to be exact) and I noticed some breakage in containers. They seem to be cause...(Copying from forum entry with same topic, as this looks like the correct place to notify this.)
Hi! I recently upgraded my Omnia from Turris OS 3 to 5 (5.1.4 to be exact) and I noticed some breakage in containers. They seem to be caused by file capabilities not being enabled for file systems. For instance:
```
root@container:~# getcap /usr/bin/ping
Failed to get capabilities of file `/usr/bin/ping' (Operation not supported)
```
Container capabilities seem to be correct:
```
lxc.cap.drop = mac_admin mac_override sys_time sys_module sys_rawio
```
So the `setfcap` capability should be available to it. In fact, if I run the container's `getfcap` program from the host OS (with `chroot` and `ld.so` trickery) it yields the same error, so it doesn't look caused by the container itself.
This worked without issues in Turris OS 3. I guess that it's no big deal for OpenWRT/Turris OS itself (so it may be a good default for plain OWRT), but for containers it means that all kinds of contortions prone to security vulnerabilities are needed where previously a simple `setcap` was sufficient (like in the `ping` example, where it will probably end being made setuid root).
I think it would make sense to enable file capabilities for file systems in next OS updates (i.e. just enable support in the kernel).
Thank you very much for an excellent product and support!https://gitlab.nic.cz/turris/os/build/-/issues/246Missing file capabilities (setcap, getcap) in TurrisOS 5 on ext4 filesystem2023-03-03T02:02:26+01:00Thomas PerretMissing file capabilities (setcap, getcap) in TurrisOS 5 on ext4 filesystemHi,
I'm hitting the same error as #223 but (I think) for a different cause.
I reinstalled my Turris Omnia from TurrisOS 3.11.x (the latest available) to TurrisOS 5.1.9 with a new installation from scratch (I didn't tried to upgrade). I...Hi,
I'm hitting the same error as #223 but (I think) for a different cause.
I reinstalled my Turris Omnia from TurrisOS 3.11.x (the latest available) to TurrisOS 5.1.9 with a new installation from scratch (I didn't tried to upgrade). I have the NAS box setup with two HDD in mdadm raid 1 on top of which I have several lvm volumes all formatted with ext4 filesystem. The different filesystems were created with a previous TurrisOS version (3.10 or 3.11, I don't know).
When I run `getcap` command in an lxc container (in one of the previously mentioned ext4 FS) I always get the `Failed to get capabilities of file '/bin/ping' (Operation not supported)` error.
I checked that the kernel support ACL for ext4:
```shell
# zcat /proc/config.gz | grep ACL
CONFIG_EXT4_FS_POSIX_ACL=y
# CONFIG_REISERFS_FS_POSIX_ACL is not set
CONFIG_JFS_POSIX_ACL=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_F2FS_FS_POSIX_ACL is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_TMPFS_POSIX_ACL is not set
CONFIG_HFSPLUS_FS_POSIX_ACL=y
# CONFIG_JFFS2_FS_POSIX_ACL is not set
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFSD_V3_ACL is not set
CONFIG_CIFS_ACL=y
```
and that the filesystem is mounted with correct options:
```shell
# grep lxc /proc/mounts
/dev/mapper/vg_router-lxc /srv/lxc ext4 rw,relatime,data=ordered 0 0
# tune2fs -l /dev/mapper/vg_router-lxc | grep -E 'features|options|state'
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Default mount options: user_xattr acl
Filesystem state: clean
```
I tried to create
1. container on old created ext4[<sup>1</sup>](#fn1-7633) -> fails
1. container on newly created ext4[<sup>2</sup>](#fn2-7633) -> fails
1. container on btrfs -> no error
So it seems to come from the ext4 filesystem and TurrisOS 5.9 combination (I never hit this issue with TurrisOS 3).
@kkoci Any clue on that?
1. I remember that I lowered the `-m reserved-blocks-percentage` option from 5% to 1% [:leftwards_arrow_with_hook:](#fnref1-7633)
1. with default `mkfs.ext4` options [:leftwards_arrow_with_hook:](#fnref2-7633)https://gitlab.nic.cz/turris/os/build/-/issues/252DHCP issues on Turris 1.x2023-03-03T01:54:29+01:00Vojtech MyslivecDHCP issues on Turris 1.xThere are several reports about issues with DHCP on Turris 1.x in TOS 5.1.x.
- forum: [TOS 5.1.4, Turris 1.x DHCP problem](https://forum.turris.cz/t/tos-5-1-4-turris-1-x-dhcp-problem/14591), [Turris OS 5.3.8 is out!](https://forum.turri...There are several reports about issues with DHCP on Turris 1.x in TOS 5.1.x.
- forum: [TOS 5.1.4, Turris 1.x DHCP problem](https://forum.turris.cz/t/tos-5-1-4-turris-1-x-dhcp-problem/14591), [Turris OS 5.3.8 is out!](https://forum.turris.cz/t/turris-os-5-3-8-is-out/17066/3)
- [ticket#1250415](https://tracker.nic.cz/Ticket/Display.html?id=1250415)
It looks like disabling "Sentinel data collection" user lists options mitigate the issue. It could be related to `sentinel-firewall`.https://gitlab.nic.cz/turris/os/build/-/issues/403Syncthing: Failed to create folder root directory mkdir /Sync: permission denied2023-02-24T13:50:39+01:00Michal VyskocilSyncthing: Failed to create folder root directory mkdir /Sync: permission deniedUpon login syncthing application warns about the folder root directory. I haven't find anything in UI to fix that and this error keeps appearing. As this is an installation on Turris, the default should be /srv/Sync with a proper permiss...Upon login syncthing application warns about the folder root directory. I haven't find anything in UI to fix that and this error keeps appearing. As this is an installation on Turris, the default should be /srv/Sync with a proper permissions.https://gitlab.nic.cz/turris/os/build/-/issues/397reForris and LuCI inacessible after upgrade2023-01-01T17:02:12+01:00Michal HavranekreForris and LuCI inacessible after upgradeI cannot access web interface after upgrade to 6.0.1. I tried to revert schnapps, but it happens again after autoupdate. After accessing router's IP on http in browser, page with topbar appears, but no login because of javascript error b...I cannot access web interface after upgrade to 6.0.1. I tried to revert schnapps, but it happens again after autoupdate. After accessing router's IP on http in browser, page with topbar appears, but no login because of javascript error because the web tried to access packages with https (on http page, which is forbidden and killed by browser). After going to https, certificate confirmation is shown by browser and after exception is confirmed, https://{IP}/cgi-bin/luci/ is opened with 404 page. If I try to open http again, I'm redirected to https where the 404 is present. I tried to wait to some fix, but it upgraded again with no luck. I'm unable to manage my router. It's Omnia 2.0, no special settings or changes to the system as far as I remember.https://gitlab.nic.cz/turris/os/build/-/issues/382RPCD crash2022-11-03T17:37:21+01:00Stepan RechnerRPCD crashIn ticket #1498457, the user reported, that LuCI fails to load with a `Session expired` error note. He managed to figure out that it crashes on a RPC call:
>>>
I have managed to discover that the following ubus call causes rpcd to crash...In ticket #1498457, the user reported, that LuCI fails to load with a `Session expired` error note. He managed to figure out that it crashes on a RPC call:
>>>
I have managed to discover that the following ubus call causes rpcd to crash (and subsequent timeout):
```
# ubus call luci-rpc getWirelessDevices
Command failed: Request timed out
The tail of strace from rpcd:
open("/var/run/hostapd-phy0.conf", O_RDONLY|O_LARGEFILE) = 9
read(9, "driver=nl80211\nlogger_syslog=127"..., 1024) = 1024
read(9, "key_retries=0\nwpa_key_mgmt=WPA-P"..., 1024) = 1024
read(9, "lan0-2\nctrl_interface=/var/run/h"..., 1024) = 726
read(9, "", 1024) = 0
close(9) = 0
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 9
ioctl(9, SIOCGIFINDEX, {ifr_name="wlan0", ifr_ifindex=27}) = 0
close(9) = 0
sendmsg(7, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, msg_namelen=12, msg_iov=[{iov_base=[{nlmsg_len=28, nlmsg_type=nl80211, nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK, nlmsg_seq=1666818885, nlmsg_pid=27139}, "\x01\x00\x00\x00\x08\x00\x03\x00\x1b\x00\x00\x00"], iov_len=28}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 28
recvmsg(7, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, msg_namelen=12, msg_iov=[{iov_base=[{nlmsg_len=2248, nlmsg_type=nl80211, nlmsg_flags=0, nlmsg_seq=1666818885, nlmsg_pid=27139}, "\x03\x01\x00\x00\x08\x00\x01\x00\x00\x00\x00\x00\x09\x00\x02\x00\x70\x68\x79\x30\x00\x00\x00\x00\x08\x00\x2e\x00\x02\x00\x00\x00"...], iov_len=16384}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 2248
recvmsg(7, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, msg_namelen=12, msg_iov=[{iov_base=[{nlmsg_len=36, nlmsg_type=NLMSG_ERROR, nlmsg_flags=NLM_F_CAPPED, nlmsg_seq=1666818885, nlmsg_pid=27139}, {error=0, msg={nlmsg_len=28, nlmsg_type=nl80211, nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK, nlmsg_seq=1666818885, nlmsg_pid=27139}}], iov_len=16384}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 36
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV +++
```
Not sure how to interpret this.
>>>https://gitlab.nic.cz/turris/os/build/-/issues/317Turris Omnia completely inaccessible after automatic update to2022-01-04T22:26:40+01:00LinAGKarTurris Omnia completely inaccessible after automatic update toMy router just decided to update itself to Turris OS 5 automatically with no warning, and since then it's been completely inaccessible. There is no Wi-Fi network, and it not sending anything whatsoever on the wired network. I tried resta...My router just decided to update itself to Turris OS 5 automatically with no warning, and since then it's been completely inaccessible. There is no Wi-Fi network, and it not sending anything whatsoever on the wired network. I tried restarting it after it had been like that for over an hour, but that didn't change anything.https://gitlab.nic.cz/turris/os/build/-/issues/309SNMP identifier is generated with every bootup2021-11-16T16:08:16+01:00Karel KociSNMP identifier is generated with every bootupThe identifier is reportedly not being persistent between reboots.
This was reported by user.The identifier is reportedly not being persistent between reboots.
This was reported by user.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/build/-/issues/308Updater changed LAN IP address to default2021-11-12T21:45:39+01:00Stepan RechnerUpdater changed LAN IP address to defaultIt has happened (as reported to support), that after a software update, the LAN address of a device was changed to the default value `192.168.1.1`. Looks like a rare issue that is not easy to reproduce.
Internal links:
* [ticket](https:...It has happened (as reported to support), that after a software update, the LAN address of a device was changed to the default value `192.168.1.1`. Looks like a rare issue that is not easy to reproduce.
Internal links:
* [ticket](https://rt.nic.cz/Ticket/Display.html?id=1321107) with description (_Po 08.lis.2021 10:20:07_) and [diagnostics](https://rt.nic.cz/Ticket/Attachment/14254033/21056836/reporty.zip) - it happened with TOS 5.3 update on one Shield, once with another Shield in the past.
* [discussion in Mattermost](https://mattermost.nic.cz/turris/pl/azb8p39g7jbu5g5yiifkjaae4o)https://gitlab.nic.cz/turris/os/build/-/issues/298DHCP does not work after restart when external switch is connected2021-09-06T14:42:43+02:00Michal HlavacDHCP does not work after restart when external switch is connectedI bought [DLink DGS 108](https://eu.dlink.com/uk/en/products/dgs-108-8-port-gigabit-ethernet-switch#Specs) unmanaged switch and connected it to `lan4` port. After restart no machine connected by wire obtain IP address from DHCP.
I have ...I bought [DLink DGS 108](https://eu.dlink.com/uk/en/products/dgs-108-8-port-gigabit-ethernet-switch#Specs) unmanaged switch and connected it to `lan4` port. After restart no machine connected by wire obtain IP address from DHCP.
I have Turris Omnia with latest 5.x firmware.https://gitlab.nic.cz/turris/os/build/-/issues/227wan speed down to ~13-14Mbps after migration to TOS 5.1.42021-05-31T20:12:51+02:00Marc Elserwan speed down to ~13-14Mbps after migration to TOS 5.1.4Hi,
I updated my turris installation from 3.11.26 through Foris experimental update.
Apart from other glitches the main problem which made me go back to TOS 3.11 is that WAN Speed dropped from ~600Mbit to ~13Mbit on TOS 5.x
I have che...Hi,
I updated my turris installation from 3.11.26 through Foris experimental update.
Apart from other glitches the main problem which made me go back to TOS 3.11 is that WAN Speed dropped from ~600Mbit to ~13Mbit on TOS 5.x
I have checked /etc/config/network but couldn't see anything suspicious. I also the only special setup here's the 3g and ncm interfaces apart from this I have a very simple config. Not vlan's nothing just plain DHCP on wan side.
Here's the 3.11 config:
```
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fda6:7fef:b222::/48'
config interface 'lan'
option ifname 'eth0 eth2'
option force_link '1'
option type 'bridge'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.10.1'
config interface 'wan'
option ifname 'eth1'
option proto 'dhcp'
option metric '10'
option peerdns '0'
option hostname 'turris'
option ipv6 '1'
option dns '8.8.8.8 8.8.4.4'
config interface 'wan6'
option ifname '@wan'
option noserverunicast '1'
option proto '6to4'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 5'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6'
config interface 'guest_turris'
option enabled '1'
option type 'bridge'
option ifname 'guest_turris_0 guest_turris_1'
option proto 'static'
option ipaddr '10.111.222.1'
option netmask '255.255.255.0'
option bridge_empty '1'
config interface 'ncm'
option proto 'ncm'
option apn 'gprs.swisscom.ch'
option metric '20'
option username 'gprs'
option password 'gprs'
option device '/dev/cdc-wdm0'
option ipv6 '0'
option peerdns '0'
option auto '0'
config interface '3g'
option proto '3g'
option apn 'gprs.swisscom.ch'
option metric '20'
option username 'gprs'
option password 'gprs'
option service 'umts'
option device '/dev/ttyUSB0'
option ipv6 '0'
option maxwait '60'
option peerdns '0'
option dns '54.93.173.153 81.17.17.170'
option enabled '0'
option auto '0'
```
and heres 5.1.4:
```
config interface 'loopback'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
option ifname 'lo'
config globals 'globals'
option ula_prefix 'fda6:7fef:b222::/48'
config interface 'lan'
option force_link '1'
option type 'bridge'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.10.1'
list ifname 'lan0'
list ifname 'lan1'
list ifname 'lan2'
list ifname 'lan3'
list ifname 'lan4'
config interface 'wan'
option proto 'dhcp'
option metric '10'
option peerdns '0'
option hostname 'turris'
option ipv6 '1'
option dns '8.8.8.8 8.8.4.4'
option ifname 'eth2'
config interface 'wan6'
option noserverunicast '1'
option proto '6to4'
option ifname '@wan'
config interface 'guest_turris'
option enabled '1'
option type 'bridge'
option proto 'static'
option ipaddr '10.111.222.1'
option netmask '255.255.255.0'
option bridge_empty '1'
list ifname 'guest_turris_0'
list ifname 'guest_turris_1'
config interface 'ncm'
option proto 'ncm'
option apn 'gprs.swisscom.ch'
option metric '20'
option username 'gprs'
option password 'gprs'
option device '/dev/cdc-wdm0'
option ipv6 '0'
option peerdns '0'
option auto '0'
option ifname '/dev/cdc-wdm0'
config interface '3g'
option proto '3g'
option apn 'gprs.swisscom.ch'
option metric '20'
option username 'gprs'
option password 'gprs'
option service 'umts'
option device '/dev/ttyUSB0'
option ipv6 '0'
option maxwait '60'
option peerdns '0'
option dns '54.93.173.153 81.17.17.170'
option enabled '0'
option auto '0'
option ifname '/dev/ttyUSB0'
```
I also check ifconfig, cpu load etc. everything seems completely normal.
Also when checking eth2 with ethtool, I get this output:
Settings for eth2:
```
Supported ports: [ TP MII FIBRE ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: yes
```
I have absolutely no idea why WAN is so slow after updating from 3.11.26 to 5.1.4.https://gitlab.nic.cz/turris/os/build/-/issues/202/dev/pts readonly after lxc-stop2020-11-12T14:31:44+01:00Marius Durbaca/dev/pts readonly after lxc-stopas described in https://forum.turris.cz/t/devpts-readonly-after-lxc-stop/14151
I need some help fixing my lxc conf after 3to5 migration.
After issuing `lxc-stop -n mylxc` I'm unable to start it back:
```
root@turris:~# lxc-start -F -n m...as described in https://forum.turris.cz/t/devpts-readonly-after-lxc-stop/14151
I need some help fixing my lxc conf after 3to5 migration.
After issuing `lxc-stop -n mylxc` I'm unable to start it back:
```
root@turris:~# lxc-start -F -n mylxc
lxc-start: mylxc: conf.c: lxc_setup_ttydir_console: 1831 Read-only file system - Failed to set mode "0110" to "/dev/pts/3"
lxc-start: mylxc: conf.c: lxc_setup: 3625 Failed to setup console
```
The fix is to issue a
`mount -o remount,rw /dev/pts` then lxc-start works as expected.
My lxc.conf and default.conf are using the default values:
```
root@turris:~# cat /etc/lxc/lxc.conf
lxc.lxcpath = /srv/lxc
root@turris:~# cat /etc/lxc/default.conf
lxc.net.0.type = veth
lxc.net.0.link = br-lan
lxc.net.0.flags = up
lxc.net.0.name = eth0
# Some workarounds
lxc.include = /usr/share/lxc/config/common.conf
lxc.hook.start-host = /usr/share/lxc/hooks/systemd-workaround
# Template to generate fixed MAC address
lxc.net.0.hwaddr = x2:xx:xx:xx:xx:xx
```https://gitlab.nic.cz/turris/os/build/-/issues/175Mox: unable to put LAN port down on Mox C module2020-07-27T08:52:58+02:00Michal HruseckyMox: unable to put LAN port down on Mox C moduleIn MOX C, calling `ip l s down lan4` shows link down in kernel, but LEDs are still on and computer on the other end of cable shows link up.In MOX C, calling `ip l s down lan4` shows link down in kernel, but LEDs are still on and computer on the other end of cable shows link up.Marek BehunMarek Behunhttps://gitlab.nic.cz/turris/os/build/-/issues/83MOX WiFi PCIe crashed2019-10-14T13:08:43+02:00Siegfried LoefflerMOX WiFi PCIe crashedTonight I noticed that none of my devices couldn't connect to the PCIe WiFi module in the Mox any longer.
Attached logfile giv[logfile.txt](/uploads/6190cd7979c6eed2f315d81f1c5cddbb/logfile.txt)es some indications of what might have hap...Tonight I noticed that none of my devices couldn't connect to the PCIe WiFi module in the Mox any longer.
Attached logfile giv[logfile.txt](/uploads/6190cd7979c6eed2f315d81f1c5cddbb/logfile.txt)es some indications of what might have happened. Note I tried to reset the interface via luci "Restart" button for the Wireless interface (somewhere in the middle of the log file) but that didn't help.