Forum Posts

seanwo
Sep 18, 2022
In Interceptor Carrier Board
Posting my solution in case anyone else is having issues getting their shares (smb/time machine) to be auto discoverable on OMV6 on the "wan" interface. So I was having a problem getting my Time Machine share on PiNAS to show up automatically on my Mac after configuring it in OpenMediaVault 6 (OMV6). This service discover is handled by the Avahi Daemon Service. "Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite." -http://avahi.org/ In OMV6, you need to add an interface in the Network>Interfaces section for it to be included avahi configuration. /etc/avahi/avahi-daemon.conf: allow-interfaces: However, since the standard "wan" interface on the interceptor creates a "wan" VLAN for the first network adapter, there is no straight forward way to add it to the OMV6. If you try to add eth0 and then reboot, you will be in a world of hurt since swconfig (used by the OS) and netplan (used by OMV6) start fight over eth0 and the result is no network access. The solution to this problem is to add "wan" to the "allow-interfaces: section of the avahi configuration file. This configuration file is managed by OMV6 so it will overwrite any changes you make. As such you need to follow the procedure to add this as an OMV6 environment variable via these instructions: https://docs.openmediavault.org/en/6.x/various/advset.html Update the OMV_AVAHIDAEMON_ALLOW_INTERFACES environment variable to get OMV6 to include the "wan" VLAN as an allowed interface: sudo omv-env set -- OMV_AVAHIDAEMON_ALLOW_INTERFACES "wan" sudo omv-salt stage run prepare sudo omv-salt stage run deploy I suggest rebooting after that procedure. Once added as an environment variable, service discovery on my Mac started working for the Time Machine share. /etc/avahi/avahi-daemon.conf now contains: allow-interfaces=wan and the network on my local mac shows:
Getting Avahi to work on OMV6 w/ Interceptor on wan VLAN (Service Discovery) content media
2
1
19
seanwo
Sep 14, 2022
In Interceptor Carrier Board
Finally got parts in and did a little electronics origami. In case anyone is interested, my parts list are at the top of my GitHub how-to (work in progress as I proceed with software setup). The plan is to run OMV with MergerFS and SnapRAID. Primary use will be for over the network TimeMachine backups and as a FileServer for my Plex server. I was trying to keep the cost to build it low but make it clean. It is a personal home project for fun. https://github.com/seanwo/how-to/blob/master/pinas/pinas.md 360 view with the project box cover off: 360 view with the project box cover on: Basically, I am just routing the cables out into back of the project box to the the top bay of a cheap 5 bay enclosure. I am routing the Front Fan, USB, HDMI, Networking, SATA, and Drive power to/from the project box/drive enclosure: Here is a shot from all angles of the finished project: Fun build!
My DIY PiNAS Build content media
1
0
31
seanwo
Aug 31, 2022
In Interceptor Carrier Board
Can some throw out a few debugging suggestions. I am unable to get my new board on the network. Steps: Clean install on new hardware using interceptor-os-22.08.12.29.img.gz System boots after install No DHCP ip address on WAN port dmesg has the following errors: [ 11.260506] rtl8367b rtl8367rb: cannot find mdio node phandle [ 11.260586] rtl8367b rtl8367rb: using GPIO pins 44 (SDA) and 45 (SCK) [ 11.262084] rtl8367b rtl8367rb: unknown chip num:6000 ver:1000, mode:1000 [ 11.262114] rtl8367b rtl8367rb: chip detection failed, err=-19 ifconfig shows no inet ipv4 address on wan: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::e65f:1ff:feda:6448 prefixlen 64 scopeid 0x20<link> ether e4:5f:01:da:64:48 txqueuelen 1000 (Ethernet) RX packets 479 bytes 32137 (31.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 64 bytes 7460 (7.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.90.0.1 netmask 255.255.255.0 broadcast 10.90.0.255 inet6 fe80::e65f:1ff:feda:6448 prefixlen 64 scopeid 0x20<link> ether e4:5f:01:da:64:48 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 20 bytes 1590 (1.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 128 bytes 9984 (9.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 128 bytes 9984 (9.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wan: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::e65f:1ff:feda:6448 prefixlen 64 scopeid 0x20<link> ether e4:5f:01:da:64:48 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22 bytes 3621 (3.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 The network cable plugged into port A (WAN) and other devices can acquire ip4 dhcp address from that cable. I have no mac filtering on router. Port light up as seen in picture. Any debugging suggestions? Anyone running the 8/12 OS build yet? Can someone give me a link to the previous OS img for testing to see if it is driver support in the new OS build? Thank you!
rtl8367rb: chip detection failed, err=-19 (interceptor-os-22.08.12.29.img) content media
1
3
38
 

seanwo

More actions