Surfparadise Posted April 13, 2023 Share Posted April 13, 2023 (edited) I enabled VLAN in network configuration, but the vlan custom network in docker is not present. I configured the 254 vlan on my router, and seems to works. If I ping 192.168.254.1 from a client in my network it's reply, but If I try to ping it from my unraid terminal, it is not reachable. Anyone can help me? Thanks No problem on VMs: Edited April 13, 2023 by Surfparadise Quote Link to comment
samsausages Posted April 13, 2023 Share Posted April 13, 2023 (edited) Make sure you also have the vlan enabled on the settings > docker page. First define vlan in settings > network settings Then go to settings > docker Stop the docker service add the vlan start the docker service Now you should see it when you're adding containers. Might have to make sure to click the little "advanced" tab in the top right, don't remember if you need to be in advanced or not. Edited April 13, 2023 by samsausages Quote Link to comment
Surfparadise Posted April 13, 2023 Author Share Posted April 13, 2023 2 minutes ago, samsausages said: Make sure you also have the vlan enabled on the settings > docker page. First define vlan in settings > network settings Then go to settings > docker Stop the docker service add the vlan start the docker service Now you should see it when you're adding containers. Seems to be ok: Quote Link to comment
samsausages Posted April 13, 2023 Share Posted April 13, 2023 Only differences from mine, I define my gateway. I have "preserve user defined networks" set to yes. Also, use ipvlan, and do not use macvlan. macvlan is considered buggy right now and new versions default to ipvlan. Quote Link to comment
Surfparadise Posted April 13, 2023 Author Share Posted April 13, 2023 Just now, samsausages said: Only differences from mine, I define my gateway. I have "preserve user defined networks" set to yes. Also, use ipvlan, and do not use macvlan. macvlan is considered buggy right now and new versions default to ipvlan. I found this in the unraid logs: Apr 13 14:05:34 Unraid root: Error response from daemon: failed to allocate secondary ip address (server:192.168.254.0): Address already in use Quote Link to comment
samsausages Posted April 13, 2023 Share Posted April 13, 2023 My Network settings for my vlans look like this: FYI, I don't have any routes defined in my routing table for my vlans. I manually define IP addresses for each container I put on my vlans, I don't use DHCP. Quote Link to comment
Surfparadise Posted April 13, 2023 Author Share Posted April 13, 2023 46 minutes ago, samsausages said: My Network settings for my vlans look like this: FYI, I don't have any routes defined in my routing table for my vlans. I manually define IP addresses for each container I put on my vlans, I don't use DHCP. Fixed!: 1 Quote Link to comment
cosmas Posted February 4 Share Posted February 4 Hello, I had the same problem. I solved it this way: Unraid IP 192.168.1.20/16, GW 192.168.0.1 metric 1 VLAN IP 10.0.0.20/24, GW 10.0.0.1 metric 2 Quote Link to comment
dynamo666 Posted April 7 Share Posted April 7 I am having this same problem where the VLANs are not showing up. The following VLANs do not show up in the list for the individual docker container. Quote Link to comment
dynamo666 Posted April 9 Share Posted April 9 Got it to work by setting the IPv4 Address Assignment for VLANs under Settings page to be None Quote Link to comment
Recommended Posts
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.