October 30, 20178 yr I recently upgraded to 6.4 because I have been trying to get docker to work with a VLAN ip. I had added VLANs fine, but all the ips pointed to Unraid itself, which made running a container on port 80 on one of those VLAN IPs not work, since it complained about the port already being used (by unraid itself). So, I went in to network settings and saw that the IP address for Unraid had /24, and that the routing table all looked like 192.168.xx.0 / 24 -- for all 3 interfaces (br0, br0.201, br0.202 -- the latter two being VLANs). My thought was that maybe Unraid, by virtue of having /24 for its own domain was 'consuming' those VLAN ips, and so I made the real boneheaded move and set it to /28, and set the vlans to /30. First off: yes, I am an idiot. I realize now that what I probably did was tell unraid that that IP exists only on a /28 group and so the bit it is getting are being garbled. Networking is not my strong suit. I have a monitor + keyboard plugged in to the box, and I see the shell prompt up, but I am at a loss as to what I need to do to fix this. Any assistance?
October 30, 20178 yr Author Phew, figured it out. I went in to /boot/config/networking.cfg and then went down and found NETMASK[0] and saw it was something like '255.255.255.240' for eth0 and '255.255.255.252' for my two VLANs. That looked wrong, so I deduced that that must be what the /24 -> /28 and /30 settings affected. I changed them to 255.255.255.0 and restarted (shutdown -r now) and it booted up and was fine.
October 30, 20178 yr Instead of "shutdown -r now" do "reboot" to ensure a proper restart of the system.
Archived
This topic is now archived and is closed to further replies.