Duet3 6HC MAC ID change when upgading to RRF 3.4
-
@dc42
As noted in the release note of RRF 3.4, the process of upgrading causes a change in the MAC ID that a Duet3 6hc (and a Duet mini5) sends to the network. I am trying to understand what change was made that causes this.
The reason I seek to understand exactly what happens during the upgrade is because the upgraded Duet3 seems to operate differently on my network after the upgrade.
I have a Duet2Wifi and a Duet3 6HC. Looking on my network attached client list (on a UbiquitPro), the Duet2 is always there when powered up. This is what I have come to expect. ALL my network devices do this except for the now upgraded Duet3 6HC. I believe that before the upgrade, the Duet3 6HC was listed like all other devices - always present as long as things were powered up (which is 24/7/365 with me). After upgrading both Duets, there is no change in how the Duet2 is listed in my 'attached client' list but the Duet3 on the other hand is playing 'Silly Sam' with me. If I send an M999 to the Duet3 it shows up on the attached client list but if I leave it sit for some time the listing in the attached client list goes away. I can still talk to the Duet via the web interface but the listing just disappears. As soon as I issue an M999, the listing shows up again. If I just talk to the Duet3, for example I ask it to 'home all', the command gets executed but the attached client list on my network will still not show the printer as attached. Issuing the M999 will bring it back.I don't like mysteries and even though functionality is not necessarily impacted, it is driving me nuts. The reason I say that it isn't necessarily impacting operation is that if you don't happen to know the IP number assigned and you don't happen to have the web interface open already, you then can't open the web interface without the IP number. This was a simple case of looking at the attached client list in the past but now it requires me setting up a link via the serial port and sending an M552 in order to determine the IP number I need to open the web interface.
I tried downgrading to RRF 3.3 but this same thing happens in 3.3 ... but I would have bet money that before the upgrade to 3.4 everything was working fine. I would like to be able to report conclusively that the upgrade to 3.4 caused this issue but since I can't recreate the expected functionality by downgrading to 3.3, I can't say what exactly is happening.I realize this is a rather exotic question but it would be nice to figure this out.
-
@jens55 here's the original issue https://forum.duet3d.com/topic/25427/m540-and-mac-address-problems-on-duet-3?_=1648156969222
The Mac address was not being calculated correctly so two 6HCs could have the same MAC address -
@jay_s_uk thanks! ..... doesn't sound like it should cause the issues I am seeing but I think this is getting well above my knowledge level
-
Of course I couldn't leave well enough alone
I thought that maybe going back to RRF3.2 might tell me something new. Everything updated just fine but I can not get to the web interface any more. I have verified the IP number via serial port, I can ping the IP number but I get an 'unable to connect' message when I try to load the web interface.
How do I fix this ? -
Did you also change the DWC files back to 3.2?
-
@phaedrux
No, I took the complete RRF 3.2 zip file and installed that. I was under the impression that all the required files are in the zip archive.
What file do I need to install? Is it just something that I can put onto the memory card via another computer or do I need to install it via the serial port somehow?Thanks!
BTW, even with 3.2 installed, the attached client list dropped the printer even though there is a connection. I am now thinking about how far I can go back without causing major issues - can I install RRF 3.0 without screwing things up (I am using tool boards but I don't care if they actually work for this test)
-
If you used the zip it should have the DWC files as well.
Clear your browser cache perhaps?
If in doubt, manually replace the DWC files in the WWW folder with the DWC zip from 3.2 just in case.
There were some folder changes between 3.2 and 3.3.
-
OKidoki ..... moral of the (not admitting anything) story is that senility can really creep up on you when you are not paying attention.
I found the original SD card that was shipped with the Duet3 .... and using that card the printer is doing the same thing (disappearing on the network client list) as what I am currently complaining about. I have no clue why it's doing it and at this point I have decided not to care any more. I obviously never tripped over the issue since I had always assigned a fixed IP and knew it by heart. With the change in IP address due to the upgrade, I discovered the 'disappearing' issue and thought it was new.
As for why I wasn't able to get to the web interface after downgrading to RRF 3.2 ..... I am not admitting what happened but let's never speak of it again
-
it's likely the duet 3 network stack doesn't talk to the router on a regular enough basis to keep it in the ARP cache table. Since you are on a local network, the router is not involved when a local machine talks to DWC. M999 will trigger a DHCP request which will put the machine into the ARP cache table again.
Since the Duet2Wifi connects via WiFi, it probably affects the router differently due to the different implementation of the network stack and/or because the wifi traffic gets seen by the router and it keeps the ARP cache table entry due to that.
