Dahua Mac Address different than what is on the sticker

[JoshFink]

Can someone tell me what I'm missing here? Usually I grab a camera, put the MAC address in my DHCP reservations and assign an IP that way. I'm not a huge fan of hardcoded IP's.

Today I had a little bit of a hiccup. I used the sticker on the outside of the camera and grabbed the IP address but it wouldn't get the correct IP via DHCP. I used config tool to find the camera and then went into the IP address that it showed and I noticed that in Network -> TCP/IP that the MAC address is different than what shows on the sticker. The stick starts with 3C:2B:8C and the camera is showing via the web 14:a7:8b

To me, this is just strange but I wanted a second opinion.

Thanks,

Josh

 

[SouthernYankee]

Where did buy the camera?

 

[JoshFink]

Where did buy the camera?

@EMPIRETECANDY

 

[aristobrat]

Seems to happen a lot, but I've never seen an explanation for why. There are other threads about this (with no real answer other than "it's normal"), if you want to do some searching.

 

[JoshFink]

Seems to happen a lot, but I've never seen an explanation for why. There are other threads about this (with no real answer other than "it's normal"), if you want to do some searching.

Thanks.. I searched but didn't find anything. Coming from the Enterprise networking world I could never imagine this happening but I understand this is a little different. It's a sticker, I get it, but I guess my curiosity wants to know why..

 

[alastairstevenson]

my curiosity wants to know why..

Presumably mixed up in manufacturing.
If you can telnet into the camera and the busybox has the 'fw_printenv' command you might find the MAC address being defined in the bootloader environment variables, like so :

> printenv
bootcmd=kload 0x82000000; bootm 0x82000000
bootdelay=1
baudrate=115200
ipaddr=192.168.1.108
serverip=192.168.1.1
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
wifiaddr=00:12:34:56:78:91
da=tftp 0x82000000 dhboot.bin.img; flwrite;tftp dhboot-min.bin.img;flwrite
dr=tftp 0x82000000 romfs-x.squashfs.img; flwrite
dk=tftp 0x82000000 kernel.img; flwrite
du=tftp 0x82000000 user-x.squashfs.img; flwrite
dw=tftp 0x82000000 web-x.squashfs.img; flwrite
dp=tftp 0x82000000 partition-x.cramfs.img;flwrite
dc=tftp 0x82000000 custom-x.squashfs.img; flwrite
up=tftp 0x82000000 update.img; flwrite
tk=tftp 0x82000000 uImage; bootm
dh_keyboard=1
loglevel=4
pd=tftp 0x82000000 pd-x.squashfs.img; flwrite
ethact=gmac
BSN=3E0616FPAX03953
HWID=IPC-HDW4431C:01:02:05:23:1A:00:01:0A:01:00:00:258:00:00:00:00:00:01:00:00:100
devalias=IPC-HDW4431C-A-V2
ID=3F024CBPAA01072
ethaddr=E0:50:8B:B2:A6:24
filesize=27E040
fileaddr=82000000
appauto=1
bootargs=mem=87M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06-svn3638 (Feb 28 2017 - 04:38:07)

Environment size: 1115/131068 bytes
>

 

[JoshFink]

Presumably mixed up in manufacturing.
If you can telnet into the camera and the busybox has the 'fw_printenv' command you might find the MAC address being defined in the bootloader environment variables, like so :
>[/CODE]

Thanks. I appreciate it.