Hello,

Just switched to a Dream Machine SE and I am getting errors about a duplicate IP. It's two mac addresses both owned by the unRAID server.

 

The stuff I've found online mostly points to disabling "Host Access to Custom Networks" for docker which was already disabled:

 

With ifconfig I see bond0 and eth0 assigned to the mac address of the servers network card:

bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
        inet 192.168.0.200  netmask 255.255.255.0  broadcast 0.0.0.0
        ether e4:1d:2d:24:39:c0  txqueuelen 1000  (Ethernet)
        RX packets 1248780799  bytes 1808446219605 (1.6 TiB)
        RX errors 0  dropped 22179  overruns 454  frame 0
        TX packets 205059076  bytes 143180099899 (133.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
	
eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether e4:1d:2d:24:39:c0  txqueuelen 1000  (Ethernet)
        RX packets 1248780799  bytes 1808446219605 (1.6 TiB)
        RX errors 0  dropped 454  overruns 454  frame 0
        TX packets 205059076  bytes 143180099899 (133.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0	

 

However, for the mystery mac address I see vhost0.

vhost0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:fb:51:73:ed:04  txqueuelen 500  (Ethernet)
        RX packets 8869581  bytes 29481304941 (27.4 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3974  bytes 166908 (162.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

I do have a Windows 11 and Howe Assistant VM running but both have their own IPs. What is weird is that this duplicate IP w/ the same mac does not appear for long. It goes away for a while and then comes back seemingly randomly. 

I am seeing the same issue

I suspect this happened with my old router and it just didn't care. Ubiquiti is having a fit about it which makes it very noticeable but I have not noticed any ill effects. All my VMs have their own IPs and can be accessed. All docker containers can be accessed from the IP of the server with the port configured in the template. No idea why vhost0 is presenting itself as a different network adapter with the same IP.

15 hours ago, manofoz said:

I suspect this happened with my old router and it just didn't care. Ubiquiti is having a fit about it which makes it very noticeable but I have not noticed any ill effects. All my VMs have their own IPs and can be accessed. All docker containers can be accessed from the IP of the server with the port configured in the template. No idea why vhost0 is presenting itself as a different network adapter with the same IP.

it is supposedly used for the virtualization. I will try to disable virtualization when the parity check has run through. Then I will see if vhost0 goes away.

 

There are useful answers in this new thread:

 

 

On 3/7/2024 at 12:21 PM, murkus said:

 

There are useful answers in this new thread:

 

 

 

 

Thanks! I'll try out those settings you recommended. I am currently using:

Docker Settings:

Docker custom network type: macvlan

Host access to custom networks: Disabled

IPv4 custom network on interface bond0: Subnet: 192.168.0.0/24 Gateway: 192.168.0.1 DHCP pool: not set

 

Network Settings:

Enable bridging: No

 

Not sure if my IPv4 custom network setting with change to eth0 at some point but it's bond0 now. Other than that it just seems I need to enable bridging and switch to ipvlan. However, I'm still unclear as to what the duplicate IP is trying to host as I can access all of my dockers and VMs without issue. It pops up and goes away after like 4 minutes too which is weird. 

On 3/8/2024 at 11:41 PM, manofoz said:

 

Thanks! I'll try out those settings you recommended. I am currently using:

Docker Settings:

Docker custom network type: macvlan

Host access to custom networks: Disabled

IPv4 custom network on interface bond0: Subnet: 192.168.0.0/24 Gateway: 192.168.0.1 DHCP pool: not set

 

Network Settings:

Enable bridging: No

 

Not sure if my IPv4 custom network setting with change to eth0 at some point but it's bond0 now. Other than that it just seems I need to enable bridging and switch to ipvlan. However, I'm still unclear as to what the duplicate IP is trying to host as I can access all of my dockers and VMs without issue. It pops up and goes away after like 4 minutes too which is weird. 

 

@murkus I'm hesitant to try this - the server is heavily used and I'm not sure how IPv4 custom network on interface bond0: gets changed to eth0. I totally screwed things up last time I fiddled with the network settings (Added SFP+ NIC) and ended up with a monitor and KB&M on the floor sorting it out lol. 

Edited March 11, 20242 yr by manofoz

On 3/11/2024 at 3:11 PM, manofoz said:

 

@murkus I'm hesitant to try this - the server is heavily used and I'm not sure how IPv4 custom network on interface bond0: gets changed to eth0. I totally screwed things up last time I fiddled with the network settings (Added SFP+ NIC) and ended up with a monitor and KB&M on the floor sorting it out lol. 

I am not using bond0 because bonding makes no sense in my environment. If I would use bonding, I would just have replaced eth0 with bond0 everyhwere in my description.

Edited March 12, 20242 yr by murkus

On 3/12/2024 at 6:59 PM, murkus said:

I am not using bond0 because bonding makes no sense in my environment. If I would use bonding, I would just have replaced eth0 with bond0 everyhwere in my description.

Thanks. I didn't intentionally use bonding, I'll need to look into that.