-
Posts
368 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Mainfrezzer
-
-
For every client thats only supposed to see and talk to the server, remote access to server is right choice.
For every client that supposed to talk to the server and vpn clients, youre looking at a hub and spoke setting.
Granted, that one you would have to modify manually too, since it by default gives a CIDR of /24.
Solving everything you want within 1 single tunnel setup will be a manual endeavor regardless. The GUI cannot help you with that "complex" setup in a easy way. Cause you can just circumvent the "limitations" quite quickly, as noticed yourself. That needs a lot of rules added to properly isolate. -
The your choice of "remote access to server" is the wrong preset. Cause that's clearly not what you want.
-
Of course it doesnt, you chose "remote access to the server". That only gives you access to the server, nothing else.
Also, youre looking in the wrong section for that^^ since the endpoint that you highlighted gives you the server ips on their respective subnets which you can use to reach it. -
This issue still lives within 6.12.10
Furthermore, there seems to be a bigger problem with Wireguard and Unraid in regards to ipv6.
I noticed that ipv6 is absolutely unusable if you want to use "VPN tunneled access for docker" since the docker bridge that gets created is ipv4 only. -
Seems to be related to this issue
https://forums.unraid.net/topic/154069-services-not-starting-after-61218-upgrade-pid-files-cannot-be-created/- 1
-
6 hours ago, ljm42 said:
Sorry, I'm not sure what you're referring to here, is this done or are you asking for a change? : )
Its working as intended in this RC again.
https://forums.unraid.net/bug-reports/stable-releases/6125-display-settings-header-show-description-broken-r2672/- 1
-
-
While this is specifically for tunnled access, the same would apply for lan access, depending on if you use ipvlan or macvlan you can do the following.
- 1
-
On 11/21/2023 at 6:25 PM, SimonF said:
CONFIG_USB_NET_CDC_NCM: CDC NCM has been included in 6.12.5rc1
IT WORKS!
- 1
-
yeah,might be. Ive strong hunch, at least in my case, thats its cause by containers that use other containers as network. But i have no clue because theres absolutely nothing to find in the logs for any of this.
-
the same happens on the older versions, 6.11.5 for example. bit odd but you can just leave/close the page after you know its done the job.
-
the intel gpu driver. thats about it.
it does work in all other linux distros i tested, 6.1 lts kernel. Its just unraid throwing a fuzz with 6.12. And the forum has multiple mentions of it being busted with the current release. But interesting that the tp link version works while the ugreen one doesnt.
6.11.5 output:
root@Magnon-Box:~# ethtool eth1 Settings for eth1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No 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: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 10Mb/s Duplex: Half Auto-negotiation: on Port: MII PHYAD: 3 Transceiver: internal Supports Wake-on: pg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: no root@Magnon-Box:~#
-
The output stays the same and bash gives permission denied on eth0, nothing about eth1 to see
Heres the output of 6.11.5 for comparison
root@Magnon-Box:~# lsusb -vvs 002:003 Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.20 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x0b95 ASIX Electronics Corp. idProduct 0x1790 AX88179 Gigabit Ethernet bcdDevice 2.00 iManufacturer 1 ASIX iProduct 2 AX88179A iSerial 3 008A3212 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0046 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 184mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 0 iInterface 4 Network_Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 11 bMaxBurst 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 2 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x0016 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x0000fd1e BESL Link Power Management (LPM) Supported BESL value 3328 us Deep BESL value 61440 us SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x02 Latency Tolerance Messages (LTM) Supported wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 1 Lowest fully-functional device speed is Full Speed (12Mbps) bU1DevExitLat 10 micro seconds bU2DevExitLat 2047 micro seconds can't get debug descriptor: Resource temporarily unavailable Device Status: 0x001c (Bus Powered) U1 Enabled U2 Enabled Latency Tolerance Messaging (LTM) Enabled root@Magnon-Box:~# cat /sys/class/net/eth*/device/uevent DRIVER=r8169 PCI_CLASS=20000 PCI_ID=10EC:8168 PCI_SUBSYS_ID=1849:8168 PCI_SLOT_NAME=0000:03:00.0 MODALIAS=pci:v000010ECd00008168sv00001849sd00008168bc02sc00i00 DEVTYPE=usb_interface DRIVER=ax88179_178a PRODUCT=b95/1790/200 TYPE=255/255/0 INTERFACE=255/255/0 MODALIAS=usb:v0B95p1790d0200dcFFdscFFdp00icFFiscFFip00in00 root@Magnon-Box:~#
6.11.5 throws the following in syslog
"kernel: usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd"
"kernel: ax88179_178a 2-2:2.0 eth1: register 'ax88179_178a' at usb-0000:00:15.0-2, ASIX AX88179 USB 3.0 Gigabit Ethernet"
while 6.12.x just does
"kernel: usb 4-5: new SuperSpeed USB device number 3 using xhci_hcd" -
1 minute ago, SimonF said:
Thanks, Would you be able to supply output of the following?
cat /sys/class/net/eth*/device/uevent
cat /sys/class/net/eth*/device/uevent DRIVER=e1000e PCI_CLASS=20000 PCI_ID=8086:153A PCI_SUBSYS_ID=103C:18E5 PCI_SLOT_NAME=0000:00:19.0 MODALIAS=pci:v00008086d0000153Asv0000103Csd000018E5bc02sc00i00
-
the ax88179 drivers been not working in the whole of 6.12
https://forums.unraid.net/bug-reports/stable-releases/6122-network-adapter-not-appearing-network-settings-r2548/
Bus 004 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.20 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x0b95 ASIX Electronics Corp. idProduct 0x1790 AX88179 Gigabit Ethernet bcdDevice 2.00 iManufacturer 1 ASIX iProduct 2 AX88179A iSerial 3 008A3212 bNumConfigurations 3 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0046 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 184mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 0 iInterface 4 Network_Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 11 bMaxBurst 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0068 bNumInterfaces 2 bConfigurationValue 2 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 184mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 13 bInterfaceProtocol 0 iInterface 0 CDC Header: bcdCDC 1.10 CDC Union: bMasterInterface 0 bSlaveInterface 1 CDC Ethernet: iMacAddress 5 F8E43B8A3212 bmEthernetStatistics 0x00000000 wMaxSegmentSize 1514 wNumberMCFilters 0x0000 bNumberPowerFilters 0 CDC NCM: bcdNcmVersion 1.00 bmNetworkCapabilities 0x2b 8-byte ntb input size max datagram size net address packet filter Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 11 bMaxBurst 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 bInterfaceProtocol 1 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 5 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0062 bNumInterfaces 2 bConfigurationValue 3 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 184mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 6 Ethernet Networking bInterfaceProtocol 0 iInterface 0 CDC Header: bcdCDC 1.10 CDC Union: bMasterInterface 0 bSlaveInterface 1 CDC Ethernet: iMacAddress 5 F8E43B8A3212 bmEthernetStatistics 0x00000000 wMaxSegmentSize 1514 wNumberMCFilters 0x0000 bNumberPowerFilters 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 11 bMaxBurst 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 5 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x0016 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x0000fd1e BESL Link Power Management (LPM) Supported BESL value 3328 us Deep BESL value 61440 us SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x02 Latency Tolerance Messages (LTM) Supported wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 1 Lowest fully-functional device speed is Full Speed (12Mbps) bU1DevExitLat 10 micro seconds bU2DevExitLat 2047 micro seconds can't get debug descriptor: Resource temporarily unavailable Device Status: 0x001c (Bus Powered) U1 Enabled U2 Enabled Latency Tolerance Messaging (LTM) Enabled
-
i placed a pull request for the plugin which will fix the issue.
In the meantime you can fix the compose issue by downloading the compose.manager-package-2023.09.13.txz from your usb. Get the "compose.sh" fromcompose.manager-package-2023.09.13.txz\compose.manager-package-2023.09.13.tar\usr\local\emhttp\plugins\compose.manager\scripts\
modify the line 57 from
eval docker compose $files -p "$name" up -d 2>&1
to
eval docker compose $files -p "$name" up --force-recreate -d 2>&1
put the compose.sh back into the archive. Let, hopefully youre using 7zip, 7zip rebuild the archive.
Delete the original .txz from the usb, place the modified on the usb (hopefully with dynamix file manager) and then open the terminal
md5sum /boot/config/plugins/compose.manager/compose.manager-package-2023.09.13.txz
copy the md5 sum that appears and modify the md5 checksum on line 8 in the compose.manager.plg within the /config/plugins folder of the usb.
It should be <!ENTITY packageMD5 "771a0a5b9d3f8b002ccaca86a38af635"> if i did manage to not sneak in some spaces.
And then reboot.
Edit: If youre willing to trust me, here are the 2 files so you dont have to do it manually.plugins.zip -
Ive spend some time on it and youre indeed correct, this is an issue. Sadly not unraid specific, it a compose issue, it just wasnt noticed before.
"docker-compose up --force-recreate" -
This looks more like a configuration error.
I dont know how your compose is set up, but given that you dont have preserve custom networks on, i assume traefik is creating the bridge traefik.
Since Aria2 and qbittorrent start before traefik, this is to be expected. Change the autostart order. -
I do wonder what platform you're using. My j4125 system does consume 1w more compared to 6.11.5 (14,4 - 15 watt idle). I've double checked that multiple times now.
Oddly enough, a i3-4130 system I've consumes less power(6,6 watt) compared to 6.11.5(8ish watt)
-
On 8/28/2023 at 10:41 PM, ljm42 said:
Can you please provide screenshots showing the issue? Also diagnostics.
Im currently unable to test that. Ive been testing the the RC-Candidate on a Telekom DSL line and im no longer physically there and reverted back to a stable version before leaving. (ive static ip assignment on my usual place)
Hope somebody else could test in my place.
to sum up what happend: Due to the Telekom and their unstable connection i got assigned a lot of new ipv6 prefix assignments. dhcpcd worked fine as usual when host access was disabled but, if i enabled host access, it would only add new routes, never delete old ones. The whole network settings pages was filled with ipv6 networks on eth0. -
Seems like when Host Access to custom networks is enabled, Unraid doesnt remove old routes/unused routes of ipv6 networks
-
1 hour ago, sonic6 said:
i think this is because of the changing ipv6 prefix. fe80 prefixes changes in germany after DC's
so this isn't usable for a static route?
@bonienl can you take a look into that?That was spot on. The GUA prefix changed. Did notice that wireguard didn't use ipv6 anymore. the eth0 changed correctly but the vhost still used the old ipv6 address, which I reckon is being used.
-
-
Still not working in 6.12.3. 6.11.5 was working flawlessly.
Update: AX88179 is still not working in 6.12.4
[6.12.10] Wireguard "AllowedIPs" isnt accepted by the WebUI
in Stable Releases
Posted · Edited by Mainfrezzer
10.253.3.0/27 that is not a single point. It is not remote access to a server, thats remote access to a hub.
10.253.3.1/32 would be remote access to a server.
Of course it would not save your setting. Because its nonsensical in a "remote access to server setting". (it only saves the servers local tunnel ip and real subnet ip, no matter what ip you write in, because the client only needs to know the servers ip.)
Your manual modification is something completely different than what the gui offered.
The GUI is the most basic tool you can use to setup wireguard. It has a few presets and safeguards the user from themselves and ensures basic functionality.
Anything above the basic "point Client to Server" or "point Client to Server Network" requires manual configuation.
If it were a comprehensive advanced tool. Your modification on the client side with allowing 10.253.3.0/27 would have resulted in unreachable.