I have posted before here (regarding 6.12 and 6.12.1) but apparently this also appies with 6.12.2. You can find the original Thread here: (in german though)
I have had Unraid running for weeks/months without any problem on 6.11.X - That was why i updated without hesitation when 6.12 came along.
As soon as I updated to 6.12 my server kept crashing. For no apparent reason. That's why i updated to 6.12.1 as soon as it came along (it came along very quickly)
I tried several things (keep reading to find out what) the server was running somewhat stable but my reverse proxy didn't work anymore, so you can take the last sentece and replace 6.12.1 with 6.12.2, That's why i updated to 6.12.2 as soon as it came along (and again: it came along very quickly)
Now honestly I just want to go back to 6.11.x because it seems everything is messed up and I think it is somewhat of a network problem.
I have a Fritzbox with a DHCP and a certain setup.
10.10.10.1 is my Fritzbox ( Modell: FRITZ!Box 7590 FRITZ!OS:7.56-Version aktuell)
The Fritzbox has a DHCP with the following setup:
Home Network Settings:
IPv4-Adress 10.10.10.1
Subnetmask 255.0.0.0
DHCP-Server
Range
from 10.10.100.1
to 10.10.100.255
Valid 10 Days
Local DNS-Server: 10.10.10.1
(it used to be 10.10.10.2 my adguard docker container but since the server kept crashing I had to bypass it for other devices to stay online)
10.10.10.10 is my Unraid Server It has a couple of dockers (mostly bridge, 2 custom br0, and a couple of VMs)
My Important Docker Containers (among others - all which are not mentioned run in bridge mode):
- Adguard-Home IP 10.10.10.2 Network mode: br0
- ApacheGuacamole IP 10.10.10.10 Network mode: bridge (used to be another ip in 6.11.X and br0)
- mariadb IP 10.10.10.10 Network mode: bridge
- Nextcloud IP 10.10.10.10 Network mode: bridge (used to be another ip in 6.11.X and br0)
- openVPN-as IP 10.10.10.10. Network mode: bridge (I need it because I have somthing which only works with openVPN and not Wireshark unfortunately)
- swag IP 10.10.10.10 Network mode: bridge (used to be another ip in 6.11.X and br0)
- tvheadend IP 10.10.10.18 Network mode: br0 (not important as much but it is my only other br0 container so I wanted to include it in the list)
- vaultwarden IP 10.10.10.10 Network mode: bridge (used to be another ip in 6.11.X and br0)
As said those are my most important ones.
I do have a couple of VMS nothing fancy
mainly 2 Windows VMS in the 10.10.10 Network
Home Assistant 10.10.11.1 (why 10.10.11.1 you may ask - i like a clean cut so that i have all smart home devices in 10.10.11.X range)#
Now here comes the weirdest part:
Ever since the 6.12 Update the fritzbox is acting up:
Usually I had a port forwarding to the swag container (back when it had the br0 setting to its IP)
Also one port forwarding to openVPN-as
All my devices/docker containers were corretly named automatically by the fritzbox. That is ever since 6.12 completely gone:
If i switch to macvlan: My Server is suddenly listed twice (2 different mac adresses though)
with arp -a I figured out that one "Server" is infact Ad-guard
tvheadend isn't showing up at all - not in the fritzbox nor with arp-a however i can access the webinterface locally
When I try to add a portforwarding to my server/swag with the right ports the fritzbox gives me
"Es ist ein Fehler aufgetreten.
Fehlerbeschreibung: Fehler beim Speichern (Daten inkonsistent)."
An Error occured.
Description: Error while saving (data inconsistent).
So back to ipvlan:
Everything seems to work just fine (and i almost deleted this thread i had written)... until something happenend... I don't know what causes this exactly but in my fritzbox, messes up the Ips of my server and it's docker containers... This is especially weird since i have set the ip of the server to static and also have checked the box to always assign the same ip on the fritzbox.
In the Overview of the fritzbox it shows up correctly:
When I click on edit it shows a differen IP
as for example seen here:
This would be the tvheadend container... Sometimes (i don't know how this works) it shows up as the adguard container
The problem is that the port forwarding is then switched to this ip....
I would love to give a few containers a dedicated ip adress if possible.
The thing is: I have a mainboard with 3(!) Network ports... of which 2 are not connected as I had trouble getting everything to work in the past. Here are my specs:
and of course a diagnostics zip is included here as well as syslog.
For now i have deactivated adguard and tvheadend. (yay... ads and no tv... )
I really love if someone could help me (and possibly many many other german, austrian and swiss users as fritzbox is the nonplusultra consumer device here)
server-syslog-20230701-0714.zip server-diagnostics-20230701-0911.zip
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.