RevPi4 - Some questions/issues

[montigab78]

Hi,
I'm testing the new revPi4. So far I'm trying to check if all has been implemented by me (and my company) in the previous version is working.
I'm experiencing the following two issues:
1) Network configuration: we need to be able to change configuration via software, e.g dhcp/static IP on eth0 or eth1. After some time spent with NetworkManager I found that by switching back to dhcpcd management almost averything is still working. The only exception is the setting of wifi as an access point. With revPi3 we were able to add a wi-fi usb dongle and to use it in AP mode (using hostapd and dnsmasq). With the integrated wifi that does not work. Hostapd starts, but no network appears. We are basically following this guide: https://www.raspberrypi.com/documentati ... cess-point (except for the routing part, we don't need to be able to browse using revPi, we just need to be able to access its network to be able to access it via SSH). I'm attaching output from hostapd;
2) Watchdog: we were using hardware watchdog by removing the connection between WD and 0V, and then by periodically switching the setup byte. I can not find documentation about how to use watchdog with revPi4;

Thanks.
Gabriele

Hostapd.log

1689684035.811438: random: getrandom() support available
1689684035.811727: Configuration file: /etc/hostapd/hostapd.conf
1689684035.818557: nl80211: Using driver-based roaming
1689684035.818617: nl80211: TDLS supported
1689684035.818634: nl80211: Supported cipher 00-0f-ac:1
1689684035.818649: nl80211: Supported cipher 00-0f-ac:5
1689684035.818662: nl80211: Supported cipher 00-0f-ac:2
1689684035.818674: nl80211: Supported cipher 00-0f-ac:4
1689684035.818686: nl80211: Supported cipher 00-0f-ac:6
1689684035.818739: nl80211: Using driver-based off-channel TX
1689684035.818764: nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1
1689684035.818796: nl80211: Use separate P2P group interface (driver advertised support)
1689684035.818810: nl80211: Enable multi-channel concurrent (driver advertised support)
1689684035.818821: nl80211: use P2P_DEVICE support
1689684035.818833: nl80211: interface wlan0 in phy phy0
1689684035.819543: nl80211: Set mode ifindex 4 iftype 3 (AP)
1689684035.819592: nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
1689684035.819654: nl80211: Subscribe to mgmt frames with AP handle 0x5583bf58a0 (device SME)
1689684035.819674: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=04
1689684035.819721: nl80211: kernel reports: Match already configured
1689684035.819742: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.819756: nl80211: Register frame match - hexdump(len=1): 04
1689684035.819770: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=0501
1689684035.819811: nl80211: kernel reports: Match already configured
1689684035.819827: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.819841: nl80211: Register frame match - hexdump(len=2): 05 01
1689684035.819855: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=0503
1689684035.819895: nl80211: kernel reports: Match already configured
1689684035.819912: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.819925: nl80211: Register frame match - hexdump(len=2): 05 03
1689684035.819939: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=0504
1689684035.819979: nl80211: kernel reports: Match already configured
1689684035.819995: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.820008: nl80211: Register frame match - hexdump(len=2): 05 04
1689684035.820022: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=06
1689684035.820061: nl80211: kernel reports: Match already configured
1689684035.820078: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.820091: nl80211: Register frame match - hexdump(len=1): 06
1689684035.820104: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=08
1689684035.820143: nl80211: kernel reports: Match already configured
1689684035.820201: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.820222: nl80211: Register frame match - hexdump(len=1): 08
1689684035.820235: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=09
1689684035.820277: nl80211: kernel reports: Match already configured
1689684035.820294: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.820307: nl80211: Register frame match - hexdump(len=1): 09
1689684035.820320: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=0a
1689684035.820360: nl80211: kernel reports: Match already configured
1689684035.820377: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.820390: nl80211: Register frame match - hexdump(len=1): 0a
1689684035.820403: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=11
1689684035.820475: nl80211: kernel reports: Match already configured
1689684035.820492: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.820505: nl80211: Register frame match - hexdump(len=1): 11
1689684035.820518: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=12
1689684035.820557: nl80211: kernel reports: Match already configured
1689684035.820574: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.820586: nl80211: Register frame match - hexdump(len=1): 12
1689684035.820599: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5583bf58a0 match=7f
1689684035.820638: nl80211: kernel reports: Match already configured
1689684035.820655: nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
1689684035.820668: nl80211: Register frame match - hexdump(len=1): 7f
1689684035.820725: nl80211: Failed to subscribe for mgmt frames from SME driver - trying to run without it
1689684035.820776: nl80211: Enable Probe Request reporting nl_preq=0x5583bf58a0
1689684035.820790: nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x5583bf58a0 match=
1689684035.820832: nl80211: kernel reports: Match already configured
1689684035.820849: nl80211: Register frame command failed (type=64): ret=-114 (Operation already in progress)
1689684035.820862: nl80211: Register frame match - hexdump(len=0): [NULL]
1689684035.820901: nl80211: Failed to enable Probe Request frame reporting in AP mode
1689684035.821299: rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
1689684035.822530: nl80211: Add own interface ifindex 4 (ifidx_reason -1)
1689684035.822555: nl80211: if_indices[16]: 4(-1)
1689684035.822589: phy: phy0
1689684035.822605: BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
1689684035.822634: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
1689684035.822748: Previous country code IT, new country code IT
1689684035.823061: nl80211: Regulatory information - country=IT (DFS-ETSI)
1689684035.823080: nl80211: 2400-2483 @ 40 MHz 20 mBm
1689684035.823095: nl80211: 5150-5250 @ 80 MHz 23 mBm (no outdoor)
1689684035.823110: nl80211: 5250-5350 @ 80 MHz 20 mBm (no outdoor) (DFS)
1689684035.823125: nl80211: 5470-5725 @ 160 MHz 26 mBm (DFS)
1689684035.823139: nl80211: 5725-5875 @ 80 MHz 13 mBm
1689684035.823153: nl80211: 57000-66000 @ 2160 MHz 40 mBm
1689684035.823192: nl80211: Added 802.11b mode based on 802.11g information
1689684035.823214: nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484[DISABLED]
1689684035.823236: nl80211: Mode IEEE 802.11a: 5170[DISABLED] 5180 5190[DISABLED] 5200 5210[DISABLED] 5220 5230[DISABLED] 5240 5260[NO_IR][RADAR] 5280[NO_IR][RADAR] 5300[NO_IR][RADAR] 5320[NO_IR][RADAR] 5500[NO_IR][RADAR] 5520[NO_IR][RADAR]
1689684035.823256: nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484[DISABLED]
1689684035.823269: Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
1689684035.823282: Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
1689684035.823294: Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
1689684035.823306: Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
1689684035.823317: Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
1689684035.823329: Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
1689684035.823341: Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
1689684035.823353: Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
1689684035.823364: Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
1689684035.823376: Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
1689684035.823388: Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
1689684035.823399: Allowed channel: mode=1 chan=12 freq=2467 MHz max_tx_power=20 dBm
1689684035.823437: Allowed channel: mode=1 chan=13 freq=2472 MHz max_tx_power=20 dBm
1689684035.823450: Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=23 dBm
1689684035.823462: Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=23 dBm
1689684035.823474: Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=23 dBm
1689684035.823485: Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=23 dBm
1689684035.823497: Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
1689684035.823509: Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
1689684035.823521: Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
1689684035.823533: Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
1689684035.823545: Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
1689684035.823557: Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
1689684035.823568: Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
1689684035.823580: Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
1689684035.823592: Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
1689684035.823603: Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
1689684035.823615: Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
1689684035.823626: Allowed channel: mode=0 chan=12 freq=2467 MHz max_tx_power=20 dBm
1689684035.823638: Allowed channel: mode=0 chan=13 freq=2472 MHz max_tx_power=20 dBm
1689684035.823653: Completing interface initialization
1689684035.823665: Mode: IEEE 802.11g Channel: 7 Frequency: 2442 MHz
1689684035.823678: hostapd_handle_dfs_offload: iface->cac_started: 0
1689684035.823690: hostapd_handle_dfs_offload: freq 2442 MHz does not require DFS. Continue channel/AP setup
1689684035.823702: Proceed with AP/channel setup
1689684035.823715: nl80211: Set freq 2442 (ht_enabled=0, vht_enabled=0, he_enabled=0, bandwidth=20 MHz, cf1=2442 MHz, cf2=0 MHz)
1689684035.823731: * freq=2442
1689684035.823743: * he_enabled=0
1689684035.823755: * vht_enabled=0
1689684035.823766: * ht_enabled=0
1689684035.823777: * channel_type=0
1689684035.823834: RATE[0] rate=10 flags=0x1
1689684035.823850: RATE[1] rate=20 flags=0x1
1689684035.823861: RATE[2] rate=55 flags=0x1
1689684035.823873: RATE[3] rate=110 flags=0x1
1689684035.823884: RATE[4] rate=60 flags=0x0
1689684035.823896: RATE[5] rate=90 flags=0x0
1689684035.823907: RATE[6] rate=120 flags=0x0
1689684035.823919: RATE[7] rate=180 flags=0x0
1689684035.823931: RATE[8] rate=240 flags=0x0
1689684035.823942: RATE[9] rate=360 flags=0x0
1689684035.823954: RATE[10] rate=480 flags=0x0
1689684035.823966: RATE[11] rate=540 flags=0x0
1689684035.823978: hostapd_setup_bss(hapd=0x5583bf3bf0 (wlan0), first=1)
1689684035.823991: nl80211: flush -> DEL_STATION wlan0 (all)
1689684035.824034: nl80211: Station flush failed: ret=-14 (Bad address)
1689684035.824099: wpa_driver_nl80211_set_key: ifindex=4 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
1689684035.824149: nl80211: set_key failed; err=-22 Invalid argument)
1689684035.824200: Failed to clear default encryption keys (ifname=wlan0 keyidx=0)
1689684035.824249: wpa_driver_nl80211_set_key: ifindex=4 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
1689684035.824857: wpa_driver_nl80211_set_key: ifindex=4 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
1689684035.824906: nl80211: set_key failed; err=-22 Invalid argument)
1689684035.824921: Failed to clear default encryption keys (ifname=wlan0 keyidx=2)
1689684035.824964: wpa_driver_nl80211_set_key: ifindex=4 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
1689684035.825008: nl80211: set_key failed; err=-22 Invalid argument)
1689684035.825023: Failed to clear default encryption keys (ifname=wlan0 keyidx=3)
1689684035.825037: Using interface wlan0 with hwaddr c8:3e:a7:10:a6:3c and ssid "revpi4_wifi"
1689684035.825050: Deriving WPA PSK based on passphrase
1689684035.825063: SSID - hexdump_ascii(len=11):
72 65 76 70 69 34 5f 77 69 66 69 revpi4_wifi
1689684035.825123: PSK (ASCII passphrase) - hexdump_ascii(len=22):
41 61 72 64 76 61 72 6b 42 61 64 67 65 72 48 65 AardvarkBadgerHe
64 67 65 68 6f 67 dgehog
1689684035.836804: PSK (from passphrase) - hexdump(len=32): 9b dc 61 07 47 0f 06 59 85 c5 87 a7 6e bf 7b 18 5a d8 98 ca 34 36 2c 7a ad 1c 03 81 00 63 f7 53
1689684035.836871: random: Got 20/20 random bytes
1689684035.836887: Get randomness: len=32 entropy=0
1689684035.837011: GMK - hexdump(len=32): 2f 64 bc 84 d9 36 69 bd 2f fb e5 a2 f2 56 4b 5f 06 6b 19 36 49 c9 4f c7 b0 6e e7 5c c0 13 ea 8f
1689684035.837038: Get randomness: len=32 entropy=0
1689684035.837133: Key Counter - hexdump(len=32): b2 75 8d 15 cc 06 ce 56 69 dd b6 81 ad 2a 43 79 de c7 3e 95 80 ee 10 5a bb ad d4 47 46 49 ef c7
1689684035.837158: WPA: Delay group state machine start until Beacon frames have been configured
1689684035.837289: nl80211: Set beacon (beacon_set=0)
1689684035.837306: nl80211: Beacon head - hexdump(len=62): 80 00 00 00 ff ff ff ff ff ff c8 3e a7 10 a6 3c c8 3e a7 10 a6 3c 00 00 00 00 00 00 00 00 00 00 64 00 11 04 00 0b 72 65 76 70 69 34 5f 77 69 66 69 01 08 82 84 8b 96 0c 12 18 24 03 01 07
1689684035.837338: nl80211: Beacon tail - hexdump(len=37): 2a 01 04 32 04 30 48 60 6c 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 7f 04 00 00 00 02
1689684035.837363: nl80211: ifindex=4
1689684035.837374: nl80211: beacon_int=100
1689684035.837386: nl80211: beacon_rate=0
1689684035.837397: nl80211: rate_type=0
1689684035.837408: nl80211: dtim_period=2
1689684035.837419: nl80211: ssid=revpi4_wifi
1689684035.837436: * beacon_int=100
1689684035.837449: * dtim_period=2
1689684035.837461: nl80211: hidden SSID not in use
1689684035.837473: nl80211: privacy=1
1689684035.837484: nl80211: auth_algs=0x1
1689684035.837496: nl80211: wpa_version=0x2
1689684035.837508: nl80211: key_mgmt_suites=0x2
1689684035.837520: nl80211: pairwise_ciphers=0x10
1689684035.837532: nl80211: group_cipher=0x10
1689684035.837544: nl80211: beacon_ies - hexdump(len=6): 7f 04 00 00 00 02
1689684035.837558: nl80211: proberesp_ies - hexdump(len=6): 7f 04 00 00 00 02
1689684035.837572: nl80211: assocresp_ies - hexdump(len=6): 7f 04 00 00 00 02
1689684035.931113: wlan0: Deauthenticate all stations at BSS start
1689684035.931721: nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> 0 (Success)
1689684035.931762: WPA: Start group state machine to set initial keys
1689684035.931774: WPA: group state machine entering state GTK_INIT (VLAN-ID 0)
1689684035.931788: Get randomness: len=16 entropy=0
1689684035.931943: GTK - hexdump(len=16): b7 08 b9 37 f3 96 54 cf 72 4f d9 ae 1d 21 32 1c
1689684035.931968: WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
1689684035.932046: wpa_driver_nl80211_set_key: ifindex=4 (wlan0) alg=3 addr=0x556a7f5f50 key_idx=1 set_tx=1 seq_len=0 key_len=16
1689684035.932072: nl80211: KEY_DATA - hexdump(len=16): b7 08 b9 37 f3 96 54 cf 72 4f d9 ae 1d 21 32 1c
1689684035.932091: broadcast key
1689684035.934325: nl80211: Set wlan0 operstate 0->1 (UP)
1689684035.934377: netlink: Operstate: ifindex=4 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
1689684035.934438: nl80211: TX queue param set: queue=0 aifs=1 cw_min=3 cw_max=7 burst_time=15 --> res=-95
1689684035.934455: Failed to set TX queue parameters for queue 0.
1689684035.934492: nl80211: TX queue param set: queue=1 aifs=1 cw_min=7 cw_max=15 burst_time=30 --> res=-95
1689684035.934508: Failed to set TX queue parameters for queue 1.
1689684035.934546: nl80211: TX queue param set: queue=2 aifs=3 cw_min=15 cw_max=63 burst_time=0 --> res=-95
1689684035.934561: Failed to set TX queue parameters for queue 2.
1689684035.934599: nl80211: TX queue param set: queue=3 aifs=7 cw_min=15 cw_max=1023 burst_time=0 --> res=-95
1689684035.934614: Failed to set TX queue parameters for queue 3.
1689684035.934627: wlan0: interface state COUNTRY_UPDATE->ENABLED
1689684035.934644: wlan0: AP-ENABLED
1689684035.934657: wlan0: Setup of interface done.
1689684035.934706: ctrl_iface not configured!
1689684035.934757: RTM_NEWLINK: ifi_index=4 ifname=wlan0 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684035.934847: RTM_NEWLINK: ifi_index=4 ifname=wlan0 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684035.934905: VLAN: RTM_NEWLINK: ifi_index=4 ifname=wlan0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684035.934921: VLAN: vlan_newlink(wlan0)
1689684035.934948: VLAN: RTM_NEWLINK: ifi_index=4 ifname=wlan0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684035.934962: VLAN: vlan_newlink(wlan0)
1689684036.124933: RTM_NEWLINK: ifi_index=6 ifname=eth1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
1689684036.124983: VLAN: RTM_NEWLINK: ifi_index=6 ifname=eth1 ifi_family=0 ifi_flags=0x1002 ()
1689684036.124998: VLAN: vlan_newlink(eth1)
1689684036.153002: RTM_DELLINK: ifi_index=6 ifname=eth1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
1689684036.153060: RTM_DELLINK: Interface 'eth1' removed
1689684036.165379: VLAN: RTM_DELLINK: ifi_index=6 ifname=eth1 ifi_family=0 ifi_flags=0x1002 ()
1689684036.165462: VLAN: vlan_dellink(eth1)
1689684037.020944: RTM_NEWLINK: ifi_index=7 ifname=eth1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
1689684037.021082: VLAN: RTM_NEWLINK: ifi_index=7 ifname=eth1 ifi_family=0 ifi_flags=0x1002 ()
1689684037.021118: VLAN: vlan_newlink(eth1)
1689684037.175284: RTM_NEWLINK: ifi_index=7 ifname=eth1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1003 ([UP])
1689684037.175358: VLAN: RTM_NEWLINK: ifi_index=7 ifname=eth1 ifi_family=0 ifi_flags=0x1003 ([UP])
1689684037.175373: VLAN: vlan_newlink(eth1)
1689684039.263001: RTM_NEWLINK: ifi_index=7 ifname=eth1 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684039.263092: VLAN: RTM_NEWLINK: ifi_index=7 ifname=eth1 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684039.263109: VLAN: vlan_newlink(eth1)
1689684039.263703: RTM_NEWLINK: ifi_index=7 ifname=eth1 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684039.263735: VLAN: RTM_NEWLINK: ifi_index=7 ifname=eth1 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684039.263749: VLAN: vlan_newlink(eth1)

[dirk]

Hello montigab78, warm welcome to the Revolution Pi Community!

Since Bullseye, you can configure the network is via the network manager in various ways, e.g. interactively with "nm-tui". Take a look at the release notes here https://revolutionpi.com/tutorials/downloads

Unfortunately, I cannot say anything about Access Point Mode. This is not a feature we are promoting. Since we use the WLAN interface of the Compute Module in the Connect 4 (which is identical to the Raspberry Pi 4), I suggest that you look for instructions here in the forum or online.

The watchdog in the Connect 4 is implemented as a "real" watchdog in Linux for the first time. This can be used, for example, with the watchdog program. The corresponding interface is "/dev/watchdog". It is also possible to use it in the programming language of choice by simply opening the interface. If no keepalive occurs within the set interval, the watchdog will hit.

Here is an example in Python

Code: Select all

usage: watchdog-example.py [-h] [-w watchdog-device] [-t TIMEOUT] -m
                           {test,get,set} [-k]
optional arguments:
  -h, --help          show this help message and exit
  -w watchdog-device  watchdog device (defaults to /dev/watchdog1).
  -t TIMEOUT          timeout in seconds
  -m {test,get,set}
  -k, --keep-alive    Send cyclic keepalive signal to watchdog.  

watchdog-example.zip

watchdog example Python

(980 Bytes) Downloaded 554 times

Test of the watchdog with a timeout of 15 seconds

Code: Select all

sudo python3 watchdog-example.py -m test -t 15

After about 14–15 seconds, the watchdog should reset the system.

Technically interested people can find more details in the official Watchdog API of the Linux kernel: https://www.kernel.org/doc/Documentatio ... og-api.txt

[montigab78]

Hi Dirk,
thanks for the reply. I did investigate a little bit more on the two issues.

About watchdog, I have read the documentation at the link you attached. I also did some test with your python script, however, I have some questions:
- where does /dev/watchdog1 come from? In all the docs I found in the web I read about /dev/watchdog and /dev/watchdog0, it this something you added in some way?
- I ran the python script the way you suggested and the revPi was rebooted, but I also tried to run it with these parameters:
sudo python3 watchdog-example.py -k -m test
I then hit CTRL-C to kill the script, but no reboot occurred after some seconds. Isn't the device to be rebooted once the script opens the watchdog file and then stops keeping it alive?


About the wi-fi, in AP mode, that's really weird, I was able to set it up correctly in a Raspberry Pi 4 with the exact tool that I'm trying with RevPi 4 (and that I'm using also with revPi3 and a USB wifi dongle).
The main difference that I note in hostapd log is that in revPi4 there are some lines about eth1 in the very end of the configuration:

1689684036.124933: RTM_NEWLINK: ifi_index=6 ifname=eth1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
1689684036.124983: VLAN: RTM_NEWLINK: ifi_index=6 ifname=eth1 ifi_family=0 ifi_flags=0x1002 ()
1689684036.124998: VLAN: vlan_newlink(eth1)
1689684036.153002: RTM_DELLINK: ifi_index=6 ifname=eth1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
1689684036.153060: RTM_DELLINK: Interface 'eth1' removed
1689684036.165379: VLAN: RTM_DELLINK: ifi_index=6 ifname=eth1 ifi_family=0 ifi_flags=0x1002 ()
1689684036.165462: VLAN: vlan_dellink(eth1)
1689684037.020944: RTM_NEWLINK: ifi_index=7 ifname=eth1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
1689684037.021082: VLAN: RTM_NEWLINK: ifi_index=7 ifname=eth1 ifi_family=0 ifi_flags=0x1002 ()
1689684037.021118: VLAN: vlan_newlink(eth1)
1689684037.175284: RTM_NEWLINK: ifi_index=7 ifname=eth1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1003 ([UP])
1689684037.175358: VLAN: RTM_NEWLINK: ifi_index=7 ifname=eth1 ifi_family=0 ifi_flags=0x1003 ([UP])
1689684037.175373: VLAN: vlan_newlink(eth1)
1689684039.263001: RTM_NEWLINK: ifi_index=7 ifname=eth1 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684039.263092: VLAN: RTM_NEWLINK: ifi_index=7 ifname=eth1 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684039.263109: VLAN: vlan_newlink(eth1)
1689684039.263703: RTM_NEWLINK: ifi_index=7 ifname=eth1 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684039.263735: VLAN: RTM_NEWLINK: ifi_index=7 ifname=eth1 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
1689684039.263749: VLAN: vlan_newlink(eth1)

if I run hostapd on a revPi3 with usb wifi there is nothing about eth1, and maybe that's why the AP is visible. Is there any difference in how eth1 is configured in revPi4?

Thanks.

Gabriele

[montigab78]

Hi Dirk,
just a quick follow-up after some more digging.
About wi-fi AP: I finally managed to make it work by: 1) using an external antenna, 2) updating firmware to the latest bullseye image you released (the device I got was released with a beta version), and 3) setting to use the external antenna via revpi-config tool.
Apparently when using internal antenna the device has not enough power to support AP mode (can it be?). I'm saying this because as soon as I turn the antenna off the wi-fi network disappears.

About watchdog: I managed to make it work by using /dev/watchdog directly. I have some c# process that opens that file and writes 0 or 1 alternatively every 10 seconds (default time for dev/watchdog is 15 seconds) and the device stays up. As soon as I kill the process the device is rebooted.

Still waiting for some reply from you, if you have any note, however I can say revPi4 is validated for what we need.

Thanks

Gabriele

[p.rosenberger]

Hi Gabriele,

the internal WiFi antenna is on the CM4 and the CM4 is between two circuit boards. So it is expected that there is no good reception with it. This why we provide the external antenna port.

We have found an issue with the watchdog. There seems to be some strange condition with the RTC (which implements the watchdog) on some devices. We are currently investigate this issue. We hope to provide a fix for this in the near future.

Best Regards
Philipp

[p.rosenberger]

Hi Gabriele,

sorry for the late reply. We have released a new kernel package which should fix the watchdog issue. An

Code: Select all

apt update && apt upgrade

will install the new kernel.

Best Regards,
Philipp