This is the standard template you can use when posting about an SLB / firmware problem. If at all possible, before posting an issue, see if you have the most up-to-date version of gSender and of the SLB firmware. If you donât, see if you can get the latest versions (firmware and gSender) and repeat the same problem again: it may be possible that the problem youâve found may have already been solved. If youâre on the latest version and you still see the problem the definitely let us know! Delete this when you make your own post
Firmware version: Unknown?
Sender: gSender 1.4.6
Steps to reproduce:
Connect to SLB with Ethernet
Close gSender without disconnecting
Open gSender and try to reconnect Ethernet
If you turn off the SLB and turn on, you can connect but it appears that the SLB doesnât drop/disconnect the old session so closing gSender and re-opening cannot reconnect.
@hamanjam FWIW, Jim, I just followed your 3 steps and I can re-connect the ethernet connection every time. How are you connecting? Are you connecting directly from the PC to the SLB or are you going through a router?
Iâm going directly to the SLB. I saw the same issue helping someone in Zoom the other night and they were seeing the same thing. I can grab a video later if that helps
@hamanjam Sorry for the delay in replying, Jim. I watched the video and I am a bit confused by the ip addresses. I wonât be able to get to my machine until this evening. Then I can compare my numbers with yours and get back to you.
I just noticed that when I double click to stop the endless connection process using IP and then exit Gsender it executes Homing twice. ( I had clicked the Homing button twice just for grins). Itâs Like it cached the attempts. Weird
@hamanjam This will be one for tech support. Iâm curious. If you disconnect before closing gSender, then close gSender and open it, can you connect?
FWIW, there are a couple of differences between your settings and mine. I used the default address for mine 192.158.5.1, and set the card to 192.128.5.5. You have used 192.168.6.1. Iâm not saying that makes any difference. Itâs just an observation. The other difference between your setup and mine is that you have set up remote access using an ip address. I donât have remote access enabled.
If you donât mind another question, what are your settings for $301, 302, 303 and 304?
Iâm sure that tech support will be able to address this. I suggest that you open a support ticket.
Just to clarify, my home network is 192.168.5.x on the first Ethernet adapter so I put the Longmill on 192.168.6.1 on the second standalone adapter. I keep a separate connection between the gsender machine and LongMill just to avoid any latency issues (I am a Technical Architect by day so I have a lot of servers on the network and multiple VLANs so best to keep separate)
MiniPC running gSender:
Ethernet adapter 1 = 192.168.5.47 (Connected to Ethernet switch to rest of network)
Netmask=255.255.255.0
Gateway=192.168.5.1
gSender Remote: 192.168.5.47:8000 (Not really used because I RDP into machine)
Ethernet adapter 2 = 192.168.6.2 (Connected directly to SLB)
Netmask=255.255.255.0
@hamanjam I would think that there is enough here now for Sienci to be able to look into the issue, Jim.
Just for my education, if you donât mind, if you disconnect before closing gSender, can you then re-open gSender and re-connect. Or, do you still need to power cycle the SLB?
I thought it would reconnect if I disconnected first, but it doesnât appear to. I disconnected and left it for about two hours and when I came back, itâs not connecting. Iâm installing wireshark to see if I can scan the adapter to see if anything is happening and Iâll open a case with support
@hamanjam Tks for that, Jim. It will be interesting to see what it works out to be. I played again this pm and canât duplicate it no matter what order I do things in.
If everyone with SLB upgrades to gSender 1.4.7 they will get locked out when the newer gSener boots up. Like you mentioned, one has to power off the SLB first.
I noticed today that if I uncheck âreconnect automaticallyâ and then restart gsender, I can connect without rebooting the SLB. Watching wireshark packet traces, I see where the SLB sends an âRSTâ back to gSender along with the firmware settings but maybe gSender isnât ready just yet so it canât process. Unchecking the reconnect gives it enough time to come fully up so when I connect, it is all in sync.
I assumed your ethernet switch to be an âunmanaged ethernet switchâ? because my âunmanaged Netgear switchâ doesnât work! So I took the switch out of the equation.
On my minipc running gSender
One of my ethernet adapters(1) connects to my dhcp server at 192.168.50.xxx
I modified the SLB Firmware settings to match the ones you used.
Iâm not running a switch between the miniPC and the SLB. The switch type would be irrelevant if you were to use one. (best practices were to not put the SLB on the network due to potential latency and congestion) At best, you would get an ARP table with a more managed type switch but itâs not necessary. The issue I was seeing was the telnet RST response wasnât being handled as soon as gSender was starting. Turning off the auto-connect appeared to allow the software enough time to fully start and process the command.
The behavior is different when you first turn on the SLB since there is no need to send a RST (reset) command. Itâs all about how the telnet session is handled by gSender and the SLB. Using timeouts and keepalives would force a reset if the connection was broken but then you introduce the possibility of latency or a hung program stopping a running job.
@hamanjam I might be off base here, but I recall that the newest gSender version might have implemented a fix for this issue. Have you tried upgrading and seen if itâs dealt with the bug or not?
Sorry @chrismakesstuff, I thought I replied earlier. The release immediately following this thread resolved the connection issue I was seeing. I can now connect/reconnect with no issues in any of the scenarios I had listed above.
Delete this when you make your own post 