[mythtv-users] mythfilldatabase not updating since last week's boot
Bill Meek
keemllib at gmail.com
Sat Nov 25 02:10:48 UTC 2017
On 11/24/2017 07:32 PM, Barry Martin wrote:
>
>
>> Figured out how to get a text file from WireShark - and just posted one just now with my attempt to contact SchedulesDirect.? It's at
>> https://pastebin.com/vZjyZ9Fq?? Hope it make sense.
>> It does.
>>
>> Look at frames 138 & 139, the very start of the connection. The backend is sending a SYN
>> to port 80, as it should:
>>
>> 138 37.412640180 192.168.0.13 54.85.117.227 TCP 74 44732 ? 80 [SYN] Seq=0 Win=29200 Len=0 ...
>> 139 37.465501093 54.85.117.227 192.168.0.13 ICMP 102 Destination unreachable (Port unreachable)
>>
>> Schedules Direct returns Destination unreachable. That matches up with
>> the earlier post with the error in the mfdb log. You should be getting
>> a SYN, ACK back.
>
> OK, here comes a stupid question, Bill -- more of a verification of my guess: the problem appears to be SchedulesDirect (54.85.117.227) can't
> get/isn't giving an ACK (acknowledgement) to my Backend (MythBE1, 192.168.0.13), right? I'm also guessing I'm (MythBE1) or this end probably
> isn't the problem?? Reading David's reply, quoted below, SchedulesDirect is being the problem.
You've got it. We're talking about the "Three Way Handshake". A SYN is sent, a SYN/ACK is returned
(normally) and then the the client returns an ACK. I understand that Wireshark has a 'bit' of a
learning curve. In the GUI, look at the headings and you'll see the Source and Destination
columns. That should nail it for you.
https://en.wikipedia.org/wiki/Handshaking#TCP_three-way_handshake
--
Bill
More information about the mythtv-users
mailing list