Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Richard Sharpe]

On Sat, Nov 11, 2017 at 11:38 AM, Richard Sharpe
 wrote:
> On Sat, Nov 11, 2017 at 11:11 AM, Guy Harris  wrote:
>> On Nov 11, 2017, at 11:06 AM, Richard Sharpe  
>> wrote:
>>
>>> Sure. The immediate problem though is that acinclude.m4 assumes that
>>> checking for pcap_open is sufficient and required to enable
>>> HAVE_PCAP_REMOTE.
>>
>> If you don't have pcap_open(), you probably don't have remote support, which 
>> is why it's required.
>>
>> I suppose it isn't "sufficient" in the sense that one could, in principle, 
>> build a version of libpcap that has pcap_open() but that only supports local 
>> capture, but that's rather unlikely.
>>
>>> Having hacked my way around that, it is clear from the resulting build
>>> failures that a more recent version of libpcap is required :-(
>>
>> That's the universe's way of telling you that perhaps, sometimes, you should 
>> trust that autotools knows what it's doing, and not try to hack around it. 
>> :-)
>
> Well, I am trying to figure out the simplest required things to get
> this working on Linux ...
>
> Now that I have the latest version of libpcap from the repo built and
> installed, I seem to have library issues, but I can figure those out
> ...

Building the latest version of libpcap with --enable-remote seems to
make things work.

Wireshark 2.5.xxx brings up the remote capture interface stuff and
tries to connect to the device I nominated, which gave back a
connection refused ... since nothing is listening on the port I
nominated ...

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Richard Sharpe]

On Sat, Nov 11, 2017 at 11:11 AM, Guy Harris  wrote:
> On Nov 11, 2017, at 11:06 AM, Richard Sharpe  
> wrote:
>
>> Sure. The immediate problem though is that acinclude.m4 assumes that
>> checking for pcap_open is sufficient and required to enable
>> HAVE_PCAP_REMOTE.
>
> If you don't have pcap_open(), you probably don't have remote support, which 
> is why it's required.
>
> I suppose it isn't "sufficient" in the sense that one could, in principle, 
> build a version of libpcap that has pcap_open() but that only supports local 
> capture, but that's rather unlikely.
>
>> Having hacked my way around that, it is clear from the resulting build
>> failures that a more recent version of libpcap is required :-(
>
> That's the universe's way of telling you that perhaps, sometimes, you should 
> trust that autotools knows what it's doing, and not try to hack around it. :-)

Well, I am trying to figure out the simplest required things to get
this working on Linux ...

Now that I have the latest version of libpcap from the repo built and
installed, I seem to have library issues, but I can figure those out
...

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Guy Harris]

On Nov 11, 2017, at 11:06 AM, Richard Sharpe  
wrote:

> Sure. The immediate problem though is that acinclude.m4 assumes that
> checking for pcap_open is sufficient and required to enable
> HAVE_PCAP_REMOTE.

If you don't have pcap_open(), you probably don't have remote support, which is 
why it's required.

I suppose it isn't "sufficient" in the sense that one could, in principle, 
build a version of libpcap that has pcap_open() but that only supports local 
capture, but that's rather unlikely.

> Having hacked my way around that, it is clear from the resulting build
> failures that a more recent version of libpcap is required :-(

That's the universe's way of telling you that perhaps, sometimes, you should 
trust that autotools knows what it's doing, and not try to hack around it. :-)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Richard Sharpe]

On Sat, Nov 11, 2017 at 10:52 AM, Guy Harris  wrote:
> On Nov 11, 2017, at 10:45 AM, Richard Sharpe  
> wrote:
>
>> I notice that the latest libpcap git repo calls pcap_open_rpcap from
>> pcap_open_live ... but I did not check if that is available in 1.5.3
>> that I have on my dev VM ...
>
> pcap_open_rpcap() itself is probably not available in the 1.5.3 you have; 
> it's part of the remote capture support, and that simply wasn't present *at 
> all* in libpcap until recently.  You'll *have* to build a newer libpcap, and 
> use that, on your development VM if you want to do remote captures.

Looks that way based on the results from below.

>> Anyway, assuming that those things work (for some value of "work") the
>> real problem is that the test in Wireshark's acinclude.m4 only checks
>> for pcap_open and not pcap_open_live ...
>
> Because libpcap has *always* had pcap_open_live() - if you have libpcap at 
> all, you have pcap_open_live().

Sure. The immediate problem though is that acinclude.m4 assumes that
checking for pcap_open is sufficient and required to enable
HAVE_PCAP_REMOTE.

Having hacked my way around that, it is clear from the resulting build
failures that a more recent version of libpcap is required :-(

>> However, my first interest is in getting the GTK stuff to show up and
>> that is controller by HAVE_PCAP_REMOTE ..
>
> To get it to show up *anywhere* in *shark you'll need a newer version of 
> libpcap - or an older version with the remote-capture support patched in.  
> You will *not* get it with any of the existing libpcap releases and, unless 
> the supplier of the distribution on your development VM has patched it in, 
> you won't get it with the libpcap in that distribution.
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe



-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] File load timing

[Paul Offord]

Ah - we should spread the word. A couple of people mentioned it at #sf17eu



Sent from Samsung Mobile on O2


 Original message 
From: Stig Bjørlykke 
Date: 11/11/2017 18:45 (GMT+00:00)
To: Developer support list for Wireshark 
Subject: Re: [Wireshark-dev] File load timing

On Sat, Nov 11, 2017 at 7:28 PM, Paul Offord  wrote:
> While we are on the subject of stuff disappearing, what's happened to the
> file load timing thing in the status line?

It's default turned off.

Preferences -> Appearance -> Layout -> Status Bar settings -> Show
file load time


--
Stig Bjørlykke
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

__

This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not 
necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be 
guaranteed to be secure or error-free as information could be intercepted, 
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The 
sender therefore does not accept liability for any errors or omissions in the 
contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour 
House, Coopers End Lane, Stansted, Essex CM24 1SJ

__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
_
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Guy Harris]

On Nov 11, 2017, at 10:45 AM, Richard Sharpe  
wrote:

> I notice that the latest libpcap git repo calls pcap_open_rpcap from
> pcap_open_live ... but I did not check if that is available in 1.5.3
> that I have on my dev VM ...

pcap_open_rpcap() itself is probably not available in the 1.5.3 you have; it's 
part of the remote capture support, and that simply wasn't present *at all* in 
libpcap until recently.  You'll *have* to build a newer libpcap, and use that, 
on your development VM if you want to do remote captures.

> Anyway, assuming that those things work (for some value of "work") the
> real problem is that the test in Wireshark's acinclude.m4 only checks
> for pcap_open and not pcap_open_live ...

Because libpcap has *always* had pcap_open_live() - if you have libpcap at all, 
you have pcap_open_live().

> However, my first interest is in getting the GTK stuff to show up and
> that is controller by HAVE_PCAP_REMOTE ..

To get it to show up *anywhere* in *shark you'll need a newer version of 
libpcap - or an older version with the remote-capture support patched in.  You 
will *not* get it with any of the existing libpcap releases and, unless the 
supplier of the distribution on your development VM has patched it in, you 
won't get it with the libpcap in that distribution.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] File load timing

[Stig Bjørlykke]

On Sat, Nov 11, 2017 at 7:28 PM, Paul Offord  wrote:
> While we are on the subject of stuff disappearing, what's happened to the
> file load timing thing in the status line?

It's default turned off.

Preferences -> Appearance -> Layout -> Status Bar settings -> Show
file load time


-- 
Stig Bjørlykke
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Richard Sharpe]

On Sat, Nov 11, 2017 at 10:25 AM, Guy Harris  wrote:
> On Nov 11, 2017, at 9:55 AM, Richard Sharpe  
> wrote:
>
>> Hmmm, the problem really seems to be that my dev environment fails to
>> find pcap_open so it cannot support rpcap.
>>
>> That is, both HAVE_PCAP_OPEN and HAVE_PCAP_REMOTE are not defined, but
>> HAVE_PCAP_REMOTE is not defined because HAVE_PCAP_OPEN is not defined.
>>
>> Now to see if a more recent version of libpcap that 1.5.3 has what I need.
>
> I infer from "libpcap" that this isn't WinPcap and thus this isn't Windows.
>
> Until recently, rpcap support was not a standard part of libpcap.
>
> The tip of the libpcap master branch (1.9.0-PRE-GIT) does include libpcap 
> support, but it's not configured in by default on UN*X, as I haven't audited 
> the code to make sure it has no buffer overflow risks or other security 
> issues.  If you configure it with autotools, you have to configure with 
> --enable-remote; if you configure it with CMake, you have to configure it 
> with -DENABLE_REMOTE=YES.  (Yes, CMake; I added CMake support to have 
> something that handles building both on UN*X and on Windows.  I also plan to 
> add CMake support to tcpdump at some point.)

Yeah. Linux.

I notice that the latest libpcap git repo calls pcap_open_rpcap from
pcap_open_live ... but I did not check if that is available in 1.5.3
that I have on my dev VM ...

Anyway, assuming that those things work (for some value of "work") the
real problem is that the test in Wireshark's acinclude.m4 only checks
for pcap_open and not pcap_open_live ...

However, my first interest is in getting the GTK stuff to show up and
that is controller by HAVE_PCAP_REMOTE ..

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] File load timing

[Paul Offord]

While we are on the subject of stuff disappearing, what's happened to the file 
load timing thing in the status line?



Sent from Samsung Mobile on O2

__

This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not 
necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be 
guaranteed to be secure or error-free as information could be intercepted, 
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The 
sender therefore does not accept liability for any errors or omissions in the 
contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour 
House, Coopers End Lane, Stansted, Essex CM24 1SJ

__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Guy Harris]

On Nov 11, 2017, at 9:55 AM, Richard Sharpe  wrote:

> Hmmm, the problem really seems to be that my dev environment fails to
> find pcap_open so it cannot support rpcap.
> 
> That is, both HAVE_PCAP_OPEN and HAVE_PCAP_REMOTE are not defined, but
> HAVE_PCAP_REMOTE is not defined because HAVE_PCAP_OPEN is not defined.
> 
> Now to see if a more recent version of libpcap that 1.5.3 has what I need.

I infer from "libpcap" that this isn't WinPcap and thus this isn't Windows.

Until recently, rpcap support was not a standard part of libpcap.

The tip of the libpcap master branch (1.9.0-PRE-GIT) does include libpcap 
support, but it's not configured in by default on UN*X, as I haven't audited 
the code to make sure it has no buffer overflow risks or other security issues. 
 If you configure it with autotools, you have to configure with 
--enable-remote; if you configure it with CMake, you have to configure it with 
-DENABLE_REMOTE=YES.  (Yes, CMake; I added CMake support to have something that 
handles building both on UN*X and on Windows.  I also plan to add CMake support 
to tcpdump at some point.)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] NEWS flle

[Peter Wu]

Hi Martin,

On Sat, Nov 11, 2017 at 06:25:25PM +0100, Martin Kaiser wrote:
> CMake has a target "news" that copies the release notes into a NEWS file
> in the source directory. NEWS is under version control and hasn't been
> updated in the repository for a while.

It is updated as part of the release process, see for example:

git show v2.4.2:NEWS

> Should we remove NEWS from the repository? Should we modify the CMake
> target to leave the source directory alone (which would mean deleting
> the target itself, all it does it copy the release notes to NEWS)?

It is probably fine to remove it from master, similar to the ChangeLog
file. Maybe the ChangeLog file could be removed completely since the
user should be able to get much more detail from git.
-- 
Kind regards,
Peter Wu
https://lekensteyn.nl
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Richard Sharpe]

On Sat, Nov 11, 2017 at 8:19 AM, Pascal Quantin
 wrote:
>
>
> Le 11 nov. 2017 17:15, "Richard Sharpe"  a
> écrit :
>
> On Sat, Nov 11, 2017 at 7:50 AM, Pascal Quantin
>  wrote:
>> Hi Richard,
>>
>> 2017-11-11 16:45 GMT+01:00 Richard Sharpe :
>>>
>>> Hi folks,
>>>
>>> I am hearing from one user that they could no longer use rpcap from
>>> 2.0.2 of Wireshark, and I see that while I can enable it in configure
>>> (--with-remote-pcap) it does not seem to show up in the
>>> Capture->Interface or Capture->Options.
>>>
>>> Does anyone know how to get it to work or if it works?
>>
>>
>> I have not used it myself lately, but the configuration dialog is still
>> present. Go to Capture -> Options -> Manage Interfaces -> Remote
>> Interfaces
>> tab.
>
> Hmmm, you are correct for 2.4.2, however, for the latest Master that
> does not seem to work, at least on the GTK version ...
>
> Still investigating.
>
>
> Nobody is working on GTK version, that is deprecated. Expect it to work less
> and less over time.
> The menu is present in Qt version for master branch also but as I said I
> have not used it since more than a year. Nobody reported that it is broken
> yet, but it could be because it is not used that much.

Hmmm, the problem really seems to be that my dev environment fails to
find pcap_open so it cannot support rpcap.

That is, both HAVE_PCAP_OPEN and HAVE_PCAP_REMOTE are not defined, but
HAVE_PCAP_REMOTE is not defined because HAVE_PCAP_OPEN is not defined.

Now to see if a more recent version of libpcap that 1.5.3 has what I need.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] NEWS flle

[Martin Kaiser]

Dear all,

CMake has a target "news" that copies the release notes into a NEWS file
in the source directory. NEWS is under version control and hasn't been
updated in the repository for a while.

Should we remove NEWS from the repository? Should we modify the CMake
target to leave the source directory alone (which would mean deleting
the target itself, all it does it copy the release notes to NEWS)?

Best regards,

   Martin
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Pascal Quantin]

Le 11 nov. 2017 17:15, "Richard Sharpe"  a
écrit :

On Sat, Nov 11, 2017 at 7:50 AM, Pascal Quantin
 wrote:
> Hi Richard,
>
> 2017-11-11 16:45 GMT+01:00 Richard Sharpe :
>>
>> Hi folks,
>>
>> I am hearing from one user that they could no longer use rpcap from
>> 2.0.2 of Wireshark, and I see that while I can enable it in configure
>> (--with-remote-pcap) it does not seem to show up in the
>> Capture->Interface or Capture->Options.
>>
>> Does anyone know how to get it to work or if it works?
>
>
> I have not used it myself lately, but the configuration dialog is still
> present. Go to Capture -> Options -> Manage Interfaces -> Remote
Interfaces
> tab.

Hmmm, you are correct for 2.4.2, however, for the latest Master that
does not seem to work, at least on the GTK version ...

Still investigating.


Nobody is working on GTK version, that is deprecated. Expect it to work
less and less over time.
The menu is present in Qt version for master branch also but as I said I
have not used it since more than a year. Nobody reported that it is broken
yet, but it could be because it is not used that much.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Richard Sharpe]

On Sat, Nov 11, 2017 at 7:50 AM, Pascal Quantin
 wrote:
> Hi Richard,
>
> 2017-11-11 16:45 GMT+01:00 Richard Sharpe :
>>
>> Hi folks,
>>
>> I am hearing from one user that they could no longer use rpcap from
>> 2.0.2 of Wireshark, and I see that while I can enable it in configure
>> (--with-remote-pcap) it does not seem to show up in the
>> Capture->Interface or Capture->Options.
>>
>> Does anyone know how to get it to work or if it works?
>
>
> I have not used it myself lately, but the configuration dialog is still
> present. Go to Capture -> Options -> Manage Interfaces -> Remote Interfaces
> tab.

Hmmm, you are correct for 2.4.2, however, for the latest Master that
does not seem to work, at least on the GTK version ...

Still investigating.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Making zlib a required dependency

[João Valverde]

Hi,

On 11-11-2017 15:21, Pascal Quantin wrote:

Hi João,

2017-11-11 16:04 GMT+01:00 João Valverde 
>:


I pushed a change making zlib 1.2.3 or greater a required build
dependency:

https://code.wireshark.org/review/#/c/24352/1


Why this change?  Is it because you fear we might not test the 
conditional compilation without zlib often enough? Or is it because you 
believe almost (all?) already compile with zlib anyway.


Don't have strong feelings about this, but it's that, plus its ubiquity 
and portability, plus maintenance and readability, plus the fact that 
not having it makes for a degraded product, without support for 
compressed capture files and dissection of trivially compressed 
protocols, so it doesn't seem worth not requiring it IMO.


When looking at the -dev mailing list history, some people were (are?) 
still building Wireshark without zlib (see for example the thread 
starting here: 
https://www.wireshark.org/lists/wireshark-dev/201209/msg00187.html or 
the fact that people once in a while upload patches to fix build without 
zlib).


The question would be why. That message mentions Wireshark is much 
faster when built without zlib, I was not aware of that and I find it 
pretty surprising.


Obviously if you're doing compression it's going to be slower, that goes 
without saying.



Regards,
Pascal.


___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
  mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] rpcap support seems to have disappeared ...

[Pascal Quantin]

Hi Richard,

2017-11-11 16:45 GMT+01:00 Richard Sharpe :

> Hi folks,
>
> I am hearing from one user that they could no longer use rpcap from
> 2.0.2 of Wireshark, and I see that while I can enable it in configure
> (--with-remote-pcap) it does not seem to show up in the
> Capture->Interface or Capture->Options.
>
> Does anyone know how to get it to work or if it works?
>

I have not used it myself lately, but the configuration dialog is still
present. Go to Capture -> Options -> Manage Interfaces -> Remote Interfaces
tab.

BR,
Pascal.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] rpcap support seems to have disappeared ...

[Richard Sharpe]

Hi folks,

I am hearing from one user that they could no longer use rpcap from
2.0.2 of Wireshark, and I see that while I can enable it in configure
(--with-remote-pcap) it does not seem to show up in the
Capture->Interface or Capture->Options.

Does anyone know how to get it to work or if it works?

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Making zlib a required dependency

[Pascal Quantin]

Hi João,

2017-11-11 16:04 GMT+01:00 João Valverde :

> I pushed a change making zlib 1.2.3 or greater a required build dependency:
>
> https://code.wireshark.org/review/#/c/24352/1
>
Why this change?  Is it because you fear we might not test the conditional
compilation without zlib often enough? Or is it because you believe almost
(all?) already compile with zlib anyway.
When looking at the -dev mailing list history, some people were (are?)
still building Wireshark without zlib (see for example the thread starting
here: https://www.wireshark.org/lists/wireshark-dev/201209/msg00187.html or
the fact that people once in a while upload patches to fix build without
zlib).

Regards,
Pascal.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Making zlib a required dependency

[João Valverde]

I pushed a change making zlib 1.2.3 or greater a required build dependency:

https://code.wireshark.org/review/#/c/24352/1

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] SPDX-License-Identifier blurbs

[Gerald Combs]

My tentative plan is to convert a directory at a time and to split larger 
directories (e.g. epan/dissectors) into chunks. I'm not sure we should convert 
3800 files in one commit:

$ git pull
$ git grep -l 'This program is free software' | wc -l
3812

On 11/10/17 1:04 PM, Jaap Keuter wrote:
> Hi,
> 
> Maybe start off by checking other files, eg.the documentation files first.
> The dissectors are the easy targets.
> 
> Thanks,,
> Jaap
> 
>> On 10 Nov 2017, at 10:44, Darien Spencer > > wrote:
>>
>> Since this patch was merged, should we start replacing (manually or
>> automaticly) the license info in other files such as dissectors?
>>  
>> *Sent:* Wednesday, November 08, 2017 at 6:09 PM
>> *From:* "Gerald Combs" >
>> *To:* "Developer support list for Wireshark" > >
>> *Subject:* [Wireshark-dev] SPDX-License-Identifier blurbs
>> Earlier today I gave a short talk about navigating Wireshark's source
>> code. One thing I mentioned is that we have quite a bit of boilerplate at
>> the top and bottom of most files, and in the past this has confused git
>> when copying and renaming files (for me, at least).
>>
>> I've uploaded a change at https://code.wireshark.org/review/#/c/24302/
>> which starts the process of replacing the GPLv2-or-later blurb at the top
>> of various files with "SPDX-License-Identifier: GPL-2.0+". Is there any
>> reason we shouldn't go ahead with this?
> 
> 
> 
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> 

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe