Ethernet

[penguinpages]

Following the very well done deployment guide [HowTo] Debian 9 with OpenMediaVault 4 | First working step by step tutorial for everyone. Beginner friendly. (google.com)

Ran now into issue where my goal was to take the two 1Gb NICs.. Create bond.  Bind two VLAN interfaces to that bond, and bind static IPs to those VLANs.  I did this in the VM based (newer? version), and it worked fine, but on the physical NAS I think we have a few issues here

1) The MAC of "eth0"  indicates a single NIC.  With .1 and .2 sub interfaces of two IPs 

root@gnubee-n1:/rom/rom# ip ad
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 90:50:5a:55:3a:50 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::9250:5aff:fe55:3a50/64 scope link
       valid_lft forever preferred_lft forever
3: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 90:50:5a:55:3a:50 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0.1
       valid_lft forever preferred_lft forever
    inet6 fe80::9250:5aff:fe55:3a50/64 scope link
       valid_lft forever preferred_lft forever
4: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 90:50:5a:55:3a:50 brd ff:ff:ff:ff:ff:ff
    inet 172.16.100.144/24 brd 172.16.100.255 scope global eth0.2
       valid_lft forever preferred_lft forever
    inet6 fe80::9250:5aff:fe55:3a50/64 scope link
       valid_lft forever preferred_lft forever

... where did my second nic go? 

My switch agrees there is only one NIC active L2,

MAC display:  Ports 35 and 36 are the NAS

Expected lspci to help me .. uh.. no nic?  <scratches head> 

root@gnubee-n1:/rom/rom# lspci
00:00.0 PCI bridge: Device 0e8d:0801 (rev 01)
00:01.0 PCI bridge: Device 0e8d:0801 (rev 01)
00:02.0 PCI bridge: Device 0e8d:0801 (rev 01)
01:00.0 IDE interface: ASMedia Technology Inc. ASM1061 SATA IDE Controller (rev 02)
02:00.0 IDE interface: ASMedia Technology Inc. ASM1061 SATA IDE Controller (rev 02)
03:00.0 IDE interface: ASMedia Technology Inc. ASM1061 SATA IDE Controller (rev 02)

This implies the modules are compiled into the kernel for the NIC

root@gnubee-n1:/rom/rom# lsmod
Module                  Size  Used by
sdhci                  20973  0
mmc_core               79878  1 sdhci
softdog                 1696  0
fuse                   71552  1
ip_tables              10189  0
x_tables               11911  1 ip_tables

# dmesg showing a few module notes about interfaces but not hardware details. But this looks like network feature modules

[    8.125357] NET: Registered protocol family 17
[    8.134504] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    8.160258] 8021q: 802.1Q VLAN Support v1.8
[    8.172573] Waiting 5 sec before mounting root device...
[    8.331702] usb 1-2: new high-speed USB device number 2 using xhci-mtk
[    8.481960] usb 1-2: New USB device found, idVendor=1a40, idProduct=0101
[    8.495608] usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    8.510134] usb 1-2: Product: USB 2.0 Hub
[    8.519140] hub 1-2:1.0: USB hub found
[    8.526878] hub 1-2:1.0: 4 ports detected
[    9.613554] mtk_soc_eth 1e100000.ethernet eth0: port 4 link up
[   10.361566] mtk_soc_eth 1e100000.ethernet eth0: port 0 link up
[   13.191758] md: Waiting for all devices to be available before autodetect
[   13.205587] md: If you don't use raid, use raid=noautodetect

My guess..  the module is suppose to be compiled into the kernel for both NICs.. they are not the same????  or have some different setting and only one now shows.

Hoping I am missing something basic here.

[Neil Brown]

On the GB-PC1 there is one network interface on the CPU - usually "eth0".  It is attached to an switch which then connects to the two RJ-45 ports.

On 4.4 kernels., these appear as "eth0.1" and "eth0.2".  On the 5.x kernels that I (try to) support they appear as "ethblue" and "ethblack".

It looks like the gui that you are using to enable  bonding refuses to work with the name "eth0.1" and "eth0.2".  That is sad.  They certainly can be configued into a bond using command-line tools.

[penguinpages]

I ended up giving up to get OpenMedia Vault to work... but that was somewhat because I was concerned that I would be pushing CPU already with services that adding GUI overhead would make more issues.  They really did have a nice UI, but GUI for this use case is too far abstracted from hardware to be synergistic.

What I will do is post my deployment guide.  Most steps are based on  https://feeding.cloud.geek.nz/posts/installing-debian-buster-on-gnubee2/   but then use of https://neil.brown.name/gnubee/gnubee-5.10.1-gbpc1.bin  after system is upgraded to buster.  BTW.. this combo does allow you to just do a simple dirty DD to SD card.. and move all boot off the SD.

In that configuration things seem solid.  Now it is just the cadre of NFS / SMB / FTP hosting and permission and configuration issues plus layering in all the post setup needed tasks such as NUT, SMART , NTP , eMail on error, swap

Again.. I will post once I get things a bit more polished and bugs worked out in post setup steps.

Thanks for your work on kernel and others on email that have helped..  

[Miles Raymond]

Thanks! This is a great guide! If you already have a base debian image, could you post it so that anyone could write it to an SD card to get started?

The main gnubee.org website really needs to be updated. I've found a lot of great information in this Google Groups, but it seems like there isn't anyone around to update the main page with all this great info. I have seen referrals to a wiki, but no URI to load.

[Jeremey Wise]

Let me work on this next week.

The image I have is just what I posted.. but over last year been applying updates , as well as layering in more services.   But not looked at this in a few months.

The main issue I have with this controller is the software NIC. It is the main limitation for performance and scale.   It has been solid.. but that limitation keeps raising head for plex and recovery tasks, and so that is why I shelved adding more to it.

--
You received this message because you are subscribed to a topic in the Google Groups "GnuBee" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gnubee/rBiZmZRRAsU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gnubee+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gnubee/d8f9c3af-f881-4ae6-bc44-36547cb15e4an%40googlegroups.com.

--

jereme...@gmail.com