Wireshark-users: Re: [Wireshark-users] Wireshark-users Digest, Vol 140, Issue 9
From: Hamilton Butcher <hammythebutcher01@xxxxxxxxx>
Date: Tue, 16 Jan 2018 15:45:57 +0000 (UTC)
From: wireshark-users-request@xxxxxxxxxxxxx
Sent: 5:00AM, Tuesday, January 16
Subject: Wireshark-users Digest, Vol 140, Issue 9
To: wireshark-users@xxxxxxxxxxxxx
Send Wireshark-users mailing list submissions to wireshark-users@xxxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://www.wireshark.org/mailman/listinfo/wireshark-users or, via email, send a message with subject or body 'help' to wireshark-users-request@xxxxxxxxxxxxx You can reach the person managing the list at wireshark-users-owner@xxxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of Wireshark-users digest..." Today's Topics: 1. Not recognizing upgrade (Todd Adamson) 2. Re: Not recognizing upgrade (Jaap Keuter) 3. Re: Not recognizing upgrade (Hugo van der Kooij) ---------------------------------------------------------------------- Message: 1 Date: Mon, 15 Jan 2018 10:46:22 -0600 From: Todd Adamson To: wireshark-users@xxxxxxxxxxxxx Subject: [Wireshark-users] Not recognizing upgrade Message-ID: Content-Type: text/plain; charset=utf-8; format=flowed My installation of 2.4.3 is not recognizing that 2.4.4 is available. Can someone check to see if there is something missing on the host site? This happening recently where one of the files was not updated to indicate a newer file existed. Todd ------------------------------ Message: 2 Date: Tue, 16 Jan 2018 10:15:09 +0100 From: Jaap Keuter To: Community support list for Wireshark Subject: Re: [Wireshark-users] Not recognizing upgrade Message-ID: Content-Type: text/plain; charset="utf-8" > > On 15 Jan 2018, at 17:46, Todd Adamson wrote: > > My installation of 2.4.3 is not recognizing that 2.4.4 is available. Can someone check to see if there is something missing on the host site? This happening recently where one of the files was not updated to indicate a newer file existed. > > Todd > Hi, The update URL (https://www.wireshark.org/update/0/Wireshark/2.4.3/Windows/x86-64/en-US/stable.xml ) is nicely pointing to 2.4.4 at this moment. Is that what matches your situation? Thanks, Jaap -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 16 Jan 2018 10:15:51 +0000 From: Hugo van der Kooij To: Community support list for Wireshark Subject: Re: [Wireshark-users] Not recognizing upgrade Message-ID: Content-Type: text/plain; charset="utf-8" This message contains a digitally signed email which can be read by opening the attachment. Hugo van der Kooij network engineer QSight IT T : +31 15 888 0 345 F : +31 15 888 0 445 E : hugo.van.der.kooij@xxxxxxxxx I : http://www.qsight.nl Arnhem - Delft - Veldhoven -------------- next part -------------- An embedded message was scrubbed... From: Hugo van der Kooij Subject: RE: [Wireshark-users] Not recognizing upgrade Date: Tue, 16 Jan 2018 10:15:51 +0000 Size: 13213 URL: ------------------------------ Subject: Digest Footer _______________________________________________ Wireshark-users mailing list Wireshark-users@xxxxxxxxxxxxx https://www.wireshark.org/mailman/listinfo/wireshark-users ------------------------------ End of Wireshark-users Digest, Vol 140, Issue 9 ***********************************************
- Prev by Date: Re: [Wireshark-users] Not recognizing upgrade
- Next by Date: Re: [Wireshark-users] Not recognizing upgrade
- Previous by thread: Re: [Wireshark-users] Not recognizing upgrade
- Next by thread: [Wireshark-users] filter application layer frames during capture kernel (SIP)
- Index(es):