Hi Richard (and Bill)
It is historic... at the first, there is only limited fixed field and
tagged field...
and on last 802.11 spec, there is > 100 tagged field...
If you have a solution to avoid a big switch...
i have already think to put each case on separate function... but for some
case,
Hi Roland,
Like Pascal say, we talk on last Sharkfest about Automated build/Gerrit and
Infrastructure Stuff..
And it is complicated, need to make some change on actually infrastructure
but missing time...
I think, we will see after Wireshark 2.0 to make some change on
infrastructure.
(the idea
On Thu, Sep 10, 2015 at 12:42 AM, Alexis La Goutte
wrote:
> Hi Richard (and Bill)
>
> It is historic... at the first, there is only limited fixed field and tagged
> field...
> and on last 802.11 spec, there is > 100 tagged field...
>
> If you have a solution to avoid a
Hi list,
I proposed a change[1] to remove the duplication for resolved addresses
(not necessarily using that code) in the UI:
Src: 192.0.2.1, Dst: 192.0.2.2
Instead of:
Src: 192.0.2.1 (192.0.2.1), Dst: 192.0.2.2 (192.0.2.2)
This change (rightfully) raised concerns that it would break
Ursprüngliche Nachricht
Von: bugzilla-dae...@wireshark.org
Datum: 01.09.2015 18:30 (GMT+01:00)
An: wireshark-b...@wireshark.org
Betreff: [Wireshark-bugs] [Bug 11443] tshark crash when specifying
ssl.keys_list on cli
Gerrit Code Review
changed
Hi,
2015-09-10 13:50 GMT+02:00 João Valverde :
> Hi list,
>
> I proposed a change[1] to remove the duplication for resolved addresses
> (not necessarily using that code) in the UI:
>
> Src: 192.0.2.1, Dst: 192.0.2.2
>
> Instead of:
>
> Src: 192.0.2.1
2015-09-10 22:31 GMT+02:00 Guy Harris :
>
> On Sep 10, 2015, at 1:05 PM, Pascal Quantin
> wrote:
>
> > Just a random thought (as I'm far from being a script expert). In case
> only one of the 2 IP address is resolved, would it be harder to parse?
> >
On Sep 10, 2015, at 1:05 PM, Pascal Quantin wrote:
> Just a random thought (as I'm far from being a script expert). In case only
> one of the 2 IP address is resolved, would it be harder to parse?
> Src: 192.0.2.1, Dst: localhost (127.0.0.1)
Is it harder to parse
On Sep 10, 2015, at 1:33 PM, Pascal Quantin wrote:
> 2015-09-10 22:31 GMT+02:00 Guy Harris :
>
>> Perhaps the default packet detail output should be oriented towards being
>> read by humans, with the output of -T psml, -T ldml, and -T fields being
On 09/10/2015 09:05 PM, Pascal Quantin wrote:
Hi,
2015-09-10 13:50 GMT+02:00 João Valverde
>:
Hi list,
I proposed a change[1] to remove the duplication for resolved
addresses (not necessarily using that
On 09/10/2015 09:51 PM, João Valverde wrote:
On 09/10/2015 09:05 PM, Pascal Quantin wrote:
Hi,
2015-09-10 13:50 GMT+02:00 João Valverde
>:
Hi list,
I proposed a change[1] to remove the duplication for
Hi
In our company we have our own Wireshark tools and plugins, which use the
main wireshark repository. To ensure that those do not break (and if they
break we can fix them in due time), we synchronize with the Wireshark repo
every night and build it with our own tools on Windows and Linux.
And
Le 10 sept. 2015 8:00 AM, "Roland Knall" a écrit :
>
> Hi
>
> In our company we have our own Wireshark tools and plugins, which use the
main wireshark repository. To ensure that those do not break (and if they
break we can fix them in due time), we synchronize with the Wireshark
Le 10 sept. 2015 8:35 AM, "Roland Knall" a écrit :
>
> Hi Pascal
>
> That was nothing against you or the way this patch was handled. We use
Gerrit here ourselves together with Jenkins, and the scenario you describe
actually happened here as well. Therefore it was decided, that
14 matches
Mail list logo