NetBurner Community Forum

Hi,

I've been tasked with maintenance of an NB application on a 5234 board from 10 years ago. We have the application built and we can communicate with it however we cannot access the the system on port 20034 - we're getting RST ACK from the device. This is preventing us from using tools like TcpUpdate or wget as described in the production and deployment document.

I suspect something is missing from the application to allow whatever service would normally run on 20034 but we can't really find out what that could be.

Thanks,
Rob

Hello Rob,

You are correct, functions such as TCP Update will only work if it is correctly enabled in your application. If you are getting a rst, that usually means nothing is listening on that port number.

Does your source code call the function StartTcpUpdate() ?

Thanks Tom.

The code was not calling that function. When we added the call the device reported out of memory (100 Netburner Update:MOD5234 102 Starting update 204 Not Enough Memory). Perhaps the original developers remove the invocation because of that issue. We'll try to go through the code to find some optimisations that might help relieve the memory issue.

Rob

I think there is some confusion here between 3.0 and 2.X code.
5234 does not run 3.0
IE no wget on 20034.

You need to look at the 2.X releases.

The tool to configure and update is

ipsetup ->To configure.
autoupdate to update.

TCP update will not make wget work, only the tcpupdate applicaiton..
(Likely not needed, autoupdate is the default)

That makes sense, thanks for the help.

Rob