I was recently going to my UniFi Devices list and noticed that Unraid had two lines listed with the same IP address. I am trying to figure out where this MAC address is coming from. ifconfig shows it listed as "vhost0". vhost0's IP always matches eth0 which is the fiber connection I intend to use. 

 

Supermicro MB has three BbE ports and I have a 2 port Intel SFP+ NIC that has only has one fiber connection to the network. 

 

I have checked all docker containers and VM for this MAC address but can't be found. 

tower-diagnostics-20240331-1512.zip

I believe this is normal if you use macvlan with bridging disabled, try ipvlan if it works for you.

14 hours ago, JorgeB said:

I believe this is normal if you use macvlan with bridging disabled, try ipvlan if it works for you.

macvlan is the only way docker containers show up in Unifi so I want to keep that. I did enable bridging and restarted eth0 but I still have two MAC address for the server. Before the server had 02:e1:d6:c9:90:76 (unknown mac I'm trying to figure out) and 90:e2:ba:2e:01:bd (mac address listed in network settings) and now I the first one changed to 16:5d:31:7f:75:65 and 90:e2:ba:2e:01:bd. 

 

If I block 16:5d:31:7f:75:65, the UI becomes unresponsive until I unblock it. If I block the MAC address listed in network settings 90:e2:ba:2e:01:bd, it makes not difference. 

 

15 hours ago, JorgeB said:

I believe this is normal if you use macvlan with bridging disabled, try ipvlan if it works for you.

This seems to be the case for me I am using macvlan with bridging disabled.  What really threw my for a loop is my netgear RAXE 500 actually sees both them for the same ip while my old router did not.

7 minutes ago, Gragorg said:

This seems to be the case for me I am using macvlan with bridging disabled.  What really threw my for a loop is my netgear RAXE 500 actually sees both them for the same ip while my old router did not.

It's pretty odd that Unraid network settings says the MAC address for the server is 90:e2:ba:2e:01:bd and if I go into my UniFi console and block that device, the server functions normally. But if I block the mystery device that shares the same IP (16:5d:31:7f:75:65) the server becomes unresponsive. Honestly the only reason I'm looking into this is the fact that UniFI Console shows a message that two devices are sharing the same IP.

8 hours ago, Pstark said:

I did enable bridging and restarted eth0

With macvlan you need to DISABLE bridging on eth0 to have stability.  Was it a typo when you said enable?

On 4/2/2024 at 4:03 AM, itimpi said:

With macvlan you need to DISABLE bridging on eth0 to have stability.  Was it a typo when you said enable?

It was not a typo but I have since disabled it. 

So... Did you ever fix this? I am having the same problem, but I do not know if it's really a problem...

my solution as its how vhost br taps eth0 is to edit the go file and set a seperate IP address:

example:
root@BMM-Unraid:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 1000
    link/ether bc:24:11:a1:95:73 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.254/24 metric 1 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::be24:11ff:fea1:9573/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
4: vhost0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500
    link/ether 02:56:98:cd:46:72 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.150/24 scope global vhost0
       valid_lft forever preferred_lft forever
    inet6 fe80::56:98ff:fecd:4672/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
root@BMM-Unraid:~# 

 

cd /boot/config
nano go

# Reset and configure vhost0 interface
ip link set vhost0 down                       # Bring vhost0 down
ip addr flush dev vhost0                      # Remove any existing IPs
ip addr add 192.168.2.150/24 dev vhost0       # Assign the desired IP
ip link set vhost0 up                         # Bring vhost0 up

^so i have unraids static assgin my unraid host and tell the tunel early in boot to use a differenet ip address so i don't have 2 ip to 2 different services...

I also recomend editing docekr and Vm setting for netwrok 

and if you have it lxc:

 

only if you have will only have 1 nic...

Edited November 24, 20241 yr by bmartino1
code fix