DuetWifi-error: filename too long

dc42

@printHorst said in DuetWifi-error: filename too long:

if anybody could comment on why it is formatted in such a weird way, that would be appreciated too

Change your terminal emulator program settings so that it accepts LF (linefeed) along as a line terminator, instead of expecting CR LF.

printHorst

thanks again for your replies and explanations!

regarding CR and/or LF: I am surprised since macOS should use LF. either way, I did not find a setting in 'terminal' to somehow change how to interpret the text sent from the Duet. it's a bit annoying but not too critical and also, except for the initial setup (and this debugging), I do not need the USB+terminal communication.

the ocsp requests on the other hand are really bad. the status info 'filename too long ...' just completely flushes the screen in the WebControl and I did not find any systematics to when they appear and when not. when they do, it is impossible to work with the printer.
regarding switching the requests off: thanks for the link, however it is very outdated and the setting in the keychain manager does not exist anymore. it also seems like a bad idea to switch of this security feature of the OS(?). I guess that rather this behavior of the OS should be expected and dealt with by the Duet. It sounds like this might be taken care of in version 3.01?

@dc42 said in DuetWifi-error: filename too long:

[...] It will also send a 404 response back, so whatever is making that request may only make it once.

Still, there must be many more users using the Duet 2 Wifi in Access Point Mode with macOS and I assume they are not all having this issue. Maybe I should start a new thread to ask around?

Any other hints/ideas are very welcome! Thanks again

dc42

Try the RRF 3.01 post RC11 firmware binary at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

printHorst

Thanks @dc42 -- would I be able to continue to use all my config.g, homex/y/z.g, etc. files?

Phaedrux

@printHorst Not without modification. I would suggest baking up your current configuration, and then using the web configurator tool to generate a new config file set for 3.0 using your settings for testing. They may still need some manual tweaking as well for 3.0. If it doesn't work out you can reflash to the 2.x firmware and restore your config backup.

Trideo

Hi there, any news about that? We are experimenting the same issue with MacOs on DUETwifi 2 and reprap firmware 2.04.
Thanks
Simon

Phaedrux

@Trideo said in DuetWifi-error: filename too long:

Hi there, any news about that? We are experimenting the same issue with MacOs on DUETwifi 2 and reprap firmware 2.04.
Thanks
Simon

Sorry there is a number of issues discussed in this thread. I suggest you create a new thread of your own and detail your issue specifically. Include all the relevant information like duet type, firmware and dwc versions, config files, etc.

Trideo

Thanks for answering.
I'll do that.
Actually some of our clients (we are selling printers) are experimenting this issue. Communication isn't that smooth with them so, I'll do my best!

Thanks
Simon

dc42

@Phaedrux said in DuetWifi-error: filename too long:

@Trideo said in DuetWifi-error: filename too long:

Hi there, any news about that? We are experimenting the same issue with MacOs on DUETwifi 2 and reprap firmware 2.04.
Thanks
Simon

Sorry there is a number of issues discussed in this thread. I suggest you create a new thread of your own and detail your issue specifically. Include all the relevant information like duet type, firmware and dwc versions, config files, etc.

If you are referring to the "Filename too long" messages in response to OCSP-over-HTTP requests made by Kaspersky AV with very long pseudo-filenames, RRF 3.1 and later include code to recognise these requests and ignore them.

Trideo

@dc42 Exactly! I'm referring to it "Filename too long" when connected in access Point Mode. We are currently preparing a "migration" to RRF 3.x but it wont be ready until several weeks.
I would like to give a quick solution to mi clients.
One of them answered me that he doesn't use Kaspersky AV....
Thanks for your support !
Simon