MAC Adresse ändert sich mehrmals täglich

K

Kalone

Member
Feb 20, 2021
29
0
6
Hallo,

ich habe bereits nach dem Problem gesucht und konnte es leider nicht mit den Threads lösen, die ich dafür hier gefunden habe.

Es scheint so, als würde sich die MAC Adresse mehrmals am Tag ändern, hier der security output vom Freenas und die Netzwerkkonfiguration von meinem Proxmoxsystem:

Interface enp5s0 wurde erstmal deaktiviert, war eigentlich als Fallback gedacht, falls die Intel dual 10 Gbit nicht mehr funktionieren sollte.


Code: 
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from b4:96:91:07:6a:6c to bc:5f:f4:8a:b7:dc on cxgb0
arp: 192.168.0.8 moved from bc:5f:f4:8a:b7:dc to b4:96:91:07:6a:6c on cxgb0

Netzwerkkonfiguration:

Code: 
auto lo
iface lo inet loopback

iface enp5s0 inet static
        address 192.168.0.8/24
#Fallback

auto enp2s0f0
iface enp2s0f0 inet manual

auto enp2s0f1
iface enp2s0f1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.0.10/24
        gateway 192.168.0.12
        bridge-ports enp2s0f0
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address 192.168.0.11/24
        bridge-ports enp2s0f1
        bridge-stp off
        bridge-fd 0


Code: 
root@pve:~# ifconfig
enp2s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether b4:96:91:07:6a:6c  txqueuelen 1000  (Ethernet)
        RX packets 5113  bytes 963841 (941.2 KiB)
        RX errors 0  dropped 11  overruns 0  frame 0
        TX packets 3567  bytes 795257 (776.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp2s0f1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b4:96:91:07:6a:6e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
Wie @strehi bereits geschrieben hat, würde ich auch auf doppelt vergebene IP tippen.

Die MAC mit bc:5f gehört zu ASROCK, die mit b4:96 wiederum zu Intel.
 
  • Like
Reactions: Kalone
Hi, danke aber die IP 192.168.0.8 kommt nur einmal vor, auch andere Server haben diese IP nicht. Und ja du hast Recht, zweimal Intel und einmal Asrock MB.

Die Asrock habe ich mal deaktiviert und einen Neustart gemacht, ich glaube bis jetzt sieht es gut aus, Danke Euch beiden, falls noch mal Probleme auftreten sag ich Bescheid... aber komnisch war es dennoch...!?

Gruß
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back