toggle quoted messageShow quoted text
I have tried it both ways.. same results unfortunately... I don't even know if all of the packets are making it, I think that there is something funky in-between happening to the packets.
On Thu, Jan 2, 2020 at 4:55 PM Corey Dean N3FE <n3fe@...
I received your info. Before I made any changes, I pointed 3103 to look at a test hblink I had up and used your ID and password you provided for me and it came right up. I also saw traffic.
The only thing to me that looks different is you added a 192.168.x.x in the ip: area. Please remove that and restart the service. Let me know if that worked for you.
On Thu, Jan 2, 2020 at 6:22 PM JJ Cummings <cummingsj@...
No only the password... standby
On Thu, Jan 2, 2020 at 3:30 PM Corey Dean N3FE <n3fe@...
By change you didn’t change the I’d in that section where the password is did you? That will also create the issue.
On Thu, Jan 2, 2020 at 3:08 PM Steve N4IRS <szingman@...
Do I remember correctly a case issue with the OB password. I THINK I
had a mixed case PW and it would not work until we made it lower
On 1/2/2020 2:32 PM, Cort N0MJS via
And you tried changing it to something else as well,
Done and done - same results but I did ask the
BM folks to re-enter it, typing it manually... I wonder if
there isn't something weird happening where the packets are
being modified somewhere in the network, though I have
poured over that...
On Thu, Jan 2, 2020 at
11:53 AM Cort N0MJS via Groups.Io <email@example.com
password line in your configuration and type the whole
thing again. No copy and paste. If the other end is OPB
have them do the same thing. Copy/paste can introduce
non-printing characters that get sent.
I have been troubleshooting a
broken OB for a while now and see this in the
INFO 2020-01-02 11:28:08,480 (OBP-3103) *TIME
OUT* STREAM ID: 92891814 SUB: 3141379 PEER:
310885350 TGID: 310815 TS 1 Duration: 3.05
The OB folks say that they see password
mismatch errors on their side but we have
confirmed that the passwords match. I'm
wondering if it isn't some weird library issue
or what.. but it basically started happening
35 or so days ago.. lol what fun I'm having.
I have captured traffic throughout the network
to make sure the packets are making it out....
any thoughts are welcome!