Automatic MAC Detection Issue

I am trying to use the new Automatic MAC Detection functionality. I can configure the Bolt using a laptop via the webpage, and when it reboots after saving the settings it will auto detect my laptop MAC and IP Address properly [DHCP].

Screenshot 2022-06-24 092123
Screenshot 2022-06-24 092135

However when i then turn it off and connect it to a embedded device with a different NIC, it will detect the MAC Address properly, but won’t connect to the wireless network [DHCP]. It almost feels like it’s still trying to use the IP Address of the previously connected device. The AP acknowledges its requests but the Bolt doesn’t seem to accept the IP Address. These are my AP logs:

Jan 1 01:23:07 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPDISCOVER(br0) 00:20:4a:fc:51:ed
Jan 1 01:23:07 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPOFFER(br0) 192.168.1.128 00:20:4a:fc:51:ed
Jan 1 01:23:07 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPREQUEST(br0) 192.168.1.128 00:20:4a:fc:51:ed
Jan 1 01:23:07 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPACK(br0) 192.168.1.128 00:20:4a:fc:51:ed CFC51ED
Jan 1 01:23:37 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPDISCOVER(br0) 00:20:4a:fc:51:ed
Jan 1 01:23:37 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPOFFER(br0) 192.168.1.128 00:20:4a:fc:51:ed
Jan 1 01:23:37 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPREQUEST(br0) 192.168.1.128 00:20:4a:fc:51:ed
Jan 1 01:23:37 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPACK(br0) 192.168.1.128 00:20:4a:fc:51:ed CFC51ED
Jan 1 01:24:07 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPDISCOVER(br0) 00:20:4a:fc:51:ed
Jan 1 01:24:07 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPOFFER(br0) 192.168.1.128 00:20:4a:fc:51:ed
Jan 1 01:24:07 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPREQUEST(br0) 192.168.1.128 00:20:4a:fc:51:ed
Jan 1 01:24:07 DD-WRT daemon.info dnsmasq-dhcp[2665]: DHCPACK(br0) 192.168.1.128 00:20:4a:fc:51:ed CFC51ED

Any ideas? Thanks!

Hi @ckracht,

Thanks for letting us know about this. I will pass this on to the Anybus Wireless developers and ask if they have seen it before and if there is a fix. I’ll keep you posted.

Thanks!
Kyle

Also, is the embedded device set to DHCP?

Can you follow the instructions below to enable logging in the Bolt to see if we can get any other info from that?

Yes. The embedded device is set to DHCP.

I am not using a Wireless Bridge II. I am using a AWB2000-B with firmware 2.06.03.

The AP I have it connecting to is a Netgear Nighthawk Router (but I have tried other APs with the same issues). The AP and Bolt are sitting right next to each other, and there shouldn’t be any interference.

I am not sure where this log starts and stops, i followed the instructions to enable it, and cleared the log before starting. I don’t see anything in here that I understand. But the MAC of the embedded device not connecting to the AP is 00.20.4A.FA.BD.46 if that helps read the log.

 755,08174549,*WSIND:0,756
1076,08174549,*WSIND:14,1077
1076,08174549,*WSIND:1,1078
1077,08167817,DynamicHeap:7100/36796
1077,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
1077,08167831,*AMDUMP:Uptime:0d.0h.0m.1s
1077,0816783d,*AMDUMP:reset reason:7
1077,08167849,*AMDUMP:number of restarts:0
1077,08167855,*AMDUMP:num WLAN recoveries:0
2239,081735ab,*WSDIS:0,2243
2239,08174549,*WSIND:4,2243
2857,08171bb9,*WSMAC:00-20-4A-FA-BD-46
4926,081742fb,*WSCO:E4-B9-7A-55-78-AB,B0-7F-B9-9C-3F-8C,5173
4926,08174313,*WSCH:108
4926,08174549,*WSIND:5,5173
4927,08172e65,*WSRSS:0
5753,08172e65,*WSRSS:-4
6579,08172e65,*WSRSS:-4
7404,08172e65,*WSRSS:-4
8230,08172e65,*WSRSS:-4
8230,08172eb5,*WSTXRX:1,183,0,0,8777
9056,08172e65,*WSRSS:-4
9882,08172e65,*WSRSS:-4

10250,08167817,DynamicHeap:7100/36796
10250,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
10250,08167831,*AMDUMP:Uptime:0d.0h.0m.10s
10250,0816783d,*AMDUMP:reset reason:7
10250,08167849,*AMDUMP:number of restarts:0
10250,08167855,*AMDUMP:num WLAN recoveries:0
10708,08172e65,*WSRSS:-4
11534,08172e65,*WSRSS:-4
12360,08172e65,*WSRSS:-4
12360,08172eb5,*WSTXRX:1,183,0,0,13282
13186,08172e65,*WSRSS:-4
14012,08172e65,*WSRSS:-4
14838,08172e65,*WSRSS:-4
15664,08172e65,*WSRSS:-4
16490,08172e65,*WSRSS:-4
16490,08172eb5,*WSTXRX:1,183,0,0,17787
755,08174549,*WSIND:0,756
1076,08174549,*WSIND:14,1077
1076,08174549,*WSIND:1,1078
1077,08167817,DynamicHeap:7100/36796
1077,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
1077,08167831,*AMDUMP:Uptime:0d.0h.0m.1s
1077,0816783d,*AMDUMP:reset reason:a
1077,08167849,*AMDUMP:number of restarts:1
1077,08167855,*AMDUMP:num WLAN recoveries:0
2239,081735ab,*WSDIS:0,2243
2239,08174549,*WSIND:4,2243
4920,081742fb,*WSCO:00-20-4A-FA-BD-46,B0-7F-B9-9C-3F-8C,5169
4920,08174313,*WSCH:108
4920,08174549,*WSIND:5,5170
4920,08172e65,*WSRSS:0
5746,08172e65,*WSRSS:-4
6570,08172e65,*WSRSS:-4
7395,08172e65,*WSRSS:-4
8219,08172e65,*WSRSS:-4
8219,08172eb5,*WSTXRX:2,495,0,0,8774
9044,08172e65,*WSRSS:-4
9868,08172e65,*WSRSS:-4
10238,08167817,DynamicHeap:7100/36796
10238,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
10238,08167831,*AMDUMP:Uptime:0d.0h.0m.10s
10238,0816783d,*AMDUMP:reset reason:a
10238,08167849,*AMDUMP:number of restarts:1
10238,08167855,*AMDUMP:num WLAN recoveries:0
10693,08172e65,*WSRSS:-4
11517,08172e65,*WSRSS:-4
12341,08172e65,*WSRSS:-9
12341,08172eb5,*WSTXRX:3,807,1,42,13279
13166,08172e65,*WSRSS:-9
13990,08172e65,*WSRSS:-14
14815,08172e65,*WSRSS:-38
15067,08171c1d,*WSIP:192.168.1.143
755,08174549,*WSIND:0,756
1077,08174549,*WSIND:14,1079
1077,08174549,*WSIND:1,1079
1078,08167817,DynamicHeap:7100/36796
1078,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
1078,08167831,*AMDUMP:Uptime:0d.0h.0m.1s
1078,0816783d,*AMDUMP:reset reason:a
1078,08167849,*AMDUMP:number of restarts:2
1078,08167855,*AMDUMP:num WLAN recoveries:0
2240,081735ab,*WSDIS:0,2244
2240,08174549,*WSIND:4,2244
4554,081742fb,*WSCO:00-20-4A-FA-BD-46,B0-7F-B9-9C-3F-8C,4769
4554,08174313,*WSCH:108
4554,08174549,*WSIND:5,4769
4555,08172e65,*WSRSS:0
5379,08172e65,*WSRSS:-19
6205,08172e65,*WSRSS:-33
7030,08172e65,*WSRSS:-38
7854,08172e65,*WSRSS:-38
7854,08172eb5,*WSTXRX:8,567,10,1302,8372
8679,08172e65,*WSRSS:-38
9504,08172e65,*WSRSS:-38
10243,08167817,DynamicHeap:7100/36796
10243,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
10243,08167831,*AMDUMP:Uptime:0d.0h.0m.10s
10243,0816783d,*AMDUMP:reset reason:a
10243,08167849,*AMDUMP:number of restarts:2
10243,08167855,*AMDUMP:num WLAN recoveries:0
10329,08172e65,*WSRSS:-39
11153,08172e65,*WSRSS:-39
11978,08172e65,*WSRSS:-39
11978,08172eb5,*WSTXRX:14,927,16,1626,12877
12802,08172e65,*WSRSS:-39
13627,08172e65,*WSRSS:-39
14451,08172e65,*WSRSS:-39
15276,08172e65,*WSRSS:-39
16100,08172e65,*WSRSS:-39
16100,08172eb5,*WSTXRX:21,1347,17,1668,17382
16924,08172e65,*WSRSS:-39
17749,08172e65,*WSRSS:-39
18573,08172e65,*WSRSS:-39
19303,08167817,DynamicHeap:7100/36796
19303,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
19303,08167831,*AMDUMP:Uptime:0d.0h.0m.20s
19303,0816783d,*AMDUMP:reset reason:a
19303,08167849,*AMDUMP:number of restarts:2
19303,08167855,*AMDUMP:num WLAN recoveries:0
19398,08172e65,*WSRSS:-39
20223,08172e65,*WSRSS:-39
20223,08172eb5,*WSTXRX:27,1707,17,1668,21887
21046,08172e65,*WSRSS:-39
21872,08172e65,*WSRSS:-39
22696,08172e65,*WSRSS:-39
23521,08172e65,*WSRSS:-39
24345,08172e65,*WSRSS:-39
24345,08172eb5,*WSTXRX:33,2067,17,1668,26392
25170,08172e65,*WSRSS:-39
25994,08172e65,*WSRSS:-39
26818,08172e65,*WSRSS:-39
27643,08172e65,*WSRSS:-39
28363,08167817,DynamicHeap:7100/36796
28363,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
28363,08167831,*AMDUMP:Uptime:0d.0h.0m.30s
28363,0816783d,*AMDUMP:reset reason:a
28363,08167849,*AMDUMP:number of restarts:2
28363,08167855,*AMDUMP:num WLAN recoveries:0
28467,08172e65,*WSRSS:-39
28467,08172eb5,*WSTXRX:34,2127,17,1668,30897
29292,08172e65,*WSRSS:-39
30117,08172e65,*WSRSS:-39
30942,08172e65,*WSRSS:-39
31766,08172e65,*WSRSS:-39
32591,08172e65,*WSRSS:-39
32591,08172eb5,*WSTXRX:41,3051,23,2592,35402
33415,08172e65,*WSRSS:-39
34239,08172e65,*WSRSS:-39
35064,08172e65,*WSRSS:-39
35888,08172e65,*WSRSS:-39
36713,08172e65,*WSRSS:-39
36713,08172eb5,*WSTXRX:50,3555,23,2592,39906
37425,08167817,DynamicHeap:7100/36796
37425,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
37425,08167831,*AMDUMP:Uptime:0d.0h.0m.40s
37425,0816783d,*AMDUMP:reset reason:a
37425,08167849,*AMDUMP:number of restarts:2
37425,08167855,*AMDUMP:num WLAN recoveries:0
37537,08172e65,*WSRSS:-39
38362,08172e65,*WSRSS:-39
39187,08172e65,*WSRSS:-38
40012,08172e65,*WSRSS:-38
40836,08172e65,*WSRSS:-38
40836,08172eb5,*WSTXRX:56,3915,27,2832,44411
41661,08172e65,*WSRSS:-38
42485,08172e65,*WSRSS:-38
43310,08172e65,*WSRSS:-38
44135,08172e65,*WSRSS:-38
44959,08172e65,*WSRSS:-38
44959,08172eb5,*WSTXRX:62,4275,30,3012,48916
45784,08172e65,*WSRSS:-38
46486,08167817,DynamicHeap:7100/36796
46486,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
46486,08167831,*AMDUMP:Uptime:0d.0h.0m.50s
46486,0816783d,*AMDUMP:reset reason:a
46486,08167849,*AMDUMP:number of restarts:2
46486,08167855,*AMDUMP:num WLAN recoveries:0
46608,08172e65,*WSRSS:-38
47432,08172e65,*WSRSS:-38
48257,08172e65,*WSRSS:-38
49081,08172e65,*WSRSS:-38
49081,08172eb5,*WSTXRX:69,4695,31,3072,53421
49906,08172e65,*WSRSS:-38
50730,08172e65,*WSRSS:-38
51555,08172e65,*WSRSS:-38
52379,08172e65,*WSRSS:-38
53204,08172e65,*WSRSS:-38
53204,08172eb5,*WSTXRX:73,4935,31,3072,57926
54028,08172e65,*WSRSS:-38
54853,08172e65,*WSRSS:-38
55546,08167817,DynamicHeap:7100/36796
55546,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
55546,08167831,*AMDUMP:Uptime:0d.0h.1m.0s
55546,0816783d,*AMDUMP:reset reason:a
55546,08167849,*AMDUMP:number of restarts:2
55546,08167855,*AMDUMP:num WLAN recoveries:0
55677,08172e65,*WSRSS:-38
56502,08172e65,*WSRSS:-38
57327,08172e65,*WSRSS:-37
57327,08172eb5,*WSTXRX:77,5679,35,3824,62431
58152,08172e65,*WSRSS:-37
58977,08172e65,*WSRSS:-37
59802,08172e65,*WSRSS:-37
60626,08172e65,*WSRSS:-37
61451,08172e65,*WSRSS:-37
61451,08172eb5,*WSTXRX:84,6063,37,3996,66936
62276,08172e65,*WSRSS:-37
63101,08172e65,*WSRSS:-37
63928,08172e65,*WSRSS:-37
64613,08167817,DynamicHeap:7100/36796
64613,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
64613,08167831,*AMDUMP:Uptime:0d.0h.1m.10s
64613,0816783d,*AMDUMP:reset reason:a
64613,08167849,*AMDUMP:number of restarts:2
64613,08167855,*AMDUMP:num WLAN recoveries:0
64754,08172e65,*WSRSS:-37
65579,08172e65,*WSRSS:-37
65579,08172eb5,*WSTXRX:87,6366,37,3996,71441
66170,08172e65,*WSRSS:-37
66996,08172e65,*WSRSS:-37
67821,08172e65,*WSRSS:-37
68647,08172e65,*WSRSS:-37
69473,08172e65,*WSRSS:-37
69473,08172eb5,*WSTXRX:87,6366,37,3996,75946
70299,08172e65,*WSRSS:-37
71124,08172e65,*WSRSS:-37
71949,08172e65,*WSRSS:-37
72775,08172e65,*WSRSS:-37
73449,08167817,DynamicHeap:7100/36796
73450,08167823,*AMDUMP:Firmware version:2.06.03 [13:54:44,Feb 25 2022]
73450,08167831,*AMDUMP:Uptime:0d.0h.1m.20s
73450,0816783d,*AMDUMP:reset reason:a
73450,08167849,*AMDUMP:number of restarts:2
73450,08167855,*AMDUMP:num WLAN recoveries:0
73600,08172e65,*WSRSS:-37
73600,08172eb5,*WSTXRX:87,6366,37,3996,80451
74425,08172e65,*WSRSS:-37
75252,08172e65,*WSRSS:-37

Yes, I understand. That was just a link to the instructions to set up logging, which are the same for all Wireless Bolts and Bridges.

Thank you for all the info. It’s very helpful. I will pass this on to the developers and run some tests to see if we can recreate the problem so it can be fixed.

We didn’t get a lot in the logs, the Bolt has limited memory space. You can send the logs to a syslog server, but don’t worry about that for now. If we can reproduce it, we can collect the logs.

In the meantime, until there’s a solution, you can set it up “the old way” by manually entering the IP address. Let me know if you have any questions.

Oh, I almost forgot. One thing to please try:

Check the response that you get with ‘ATS3018?’.

It is probably 30 or so. Try changing it to 250 and rebooting:

ATS3018=250
AT*AMREBOOT

The old way of doing it was to just fill in the MAC Address manually. I don’t fill in the IP Address (leave it as 0.0.0.0) because we use DCHP for these devices 99% of the time.

My current one is set to 20. What does changing this to 250 do?

ATS3018 sets the number of packets to inspect to find the IP address.

Is the Bolt connected directly to the Embedded module with no switch or anything in between?

Correct. The Bolt is directly connected via ethernet cable to a ethernet only radio which is set to obtain IP Address through DHCP.

Just making sure because it won’t work through a switch. There can only be one MAC address on the network it’s connected to.

Did you try changing ATS3018?

With the adjustment I seem to be able to see it on the network for a very brief period of time before it becomes unavailable again. Just keeps reconnecting and disconnecting.

Does the device work if you set a static IP address in the Bolt?

Does it get an IP address if you connect it to the router with Ethernet?

Does your router have the ability to capture packets?

Have you tried factory resetting the Bolt?

Can you send me a copy of the Bolt’s config file?

I’m not sure I follow your questions. Remember I am trying to connect to the device that is being cloned, not the Bolt itself.

I cannot set a static IP Address in the Bolt. When you select “Automatic configuration” the Cloned IP Address becomes un-editable. I’ve set a Static IP Address on the connected device instead of using DHCP, and it still doesn’t seem to connect properly to the Wireless AP.

If I try to connect the Bolt to the AP via Ethernet, it will not obtain an IP Address because it’s trying to clone the Router, it creates a network loop…

Unsure on capturing packets. I’ve tried multiple Wireless Networks though, and none of them will allow the Bolt to have access. However if I do not use the automatic MAC detection, it works properly.

I have tried factory resetting the Bolt, which doesn’t seem to affect anything.

How do I send a config file? Do you mean a backup?

I am asking if your device works when you set the MAC/IP address manually here:
image

Was asking if your device gets an IP address if you set it to DHCP and connect it to a network directly with ethernet.

Yes, a backup of the device is what I was referring to.

Yes it does work when setting the cloned information manually:
image

Yes the device gets on the network properly when it is connected via Ethernet using DHCP:

Attached is a backup of the Bolt:
backup.dat (2.6 KB)

Can you let me know the model of the embedded device you are using? Maybe we can get one to test with?

Currently we are using this:

Do you have the latest firmware installed on that device? It looks like they have made some updates to the DHCP functionality according to release notes.

https://ltrxdev.atlassian.net/wiki/spaces/LTRXTS/pages/106922715/Latest+firmware+for+the+MatchPort-NR

I didn’t. I had 6.10.0.1, but updated to 6.10.0.3 and it didn’t seem to make a difference. Same issues.