[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-bugs
Subject: [Wireshark-bugs] [Bug 16295] GRE packets source and destination IP displayed incorrectly
From: bugzilla-daemon () wireshark ! org
Date: 2019-12-25 22:37:58
Message-ID: bug-16295-15-gIgu8bt2Th () https ! bugs ! wireshark ! org/bugzilla/
[Download RAW message or body]
--15773134791.c74d703.9217
Date: Wed, 25 Dec 2019 22:37:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.wireshark.org/bugzilla/
Auto-Submitted: auto-generated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16295
--- Comment #4 from Guy Harris <guy@alum.mit.edu> ---
(In reply to Christopher Maynard from comment #3)
> This is rather easily resolved by modifying the displayed columns, perhaps
> even in a different "GRE" profile. Simply add Source and Destination custom
> columns using ip.src and ip.dst as the fields, but choose 1 for the Field
> Occurrence. In this way, the first occurrence will be displayed instead of
> the last occurrence (or feel free to leave the occurrence at the default of
> 0 to display both outer and inner addresses if you prefer).
If somebody wants the outer layer's addresses displayed, are they also going to
want the outer layer's Info value displayed, or are they going to want the
address columns not to match the Info column?
--
You are receiving this mail because:
You are watching all bug changes.
--15773134791.c74d703.9217
Date: Wed, 25 Dec 2019 22:37:59 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.wireshark.org/bugzilla/
Auto-Submitted: auto-generated
<html>
<head>
<base href="https://bugs.wireshark.org/bugzilla/" />
<style>
body, th, td {
font-size: 12px;
font-family: Arial, Helvetica, sans-serif; }
p, pre { margin-top: 1em; }
pre {
font-family: Bitstream Vera Sans Mono, Consolas, Lucida Console, \
monospace; white-space: pre-wrap;
}
table { border: 0; border-spacing: 0; border-collapse: collapse; }
th, td {
padding: 0.25em;
padding-left: 0.5em;
padding-right: 0.5em;
}
th { background: rgb(240, 240, 240); }
th.th_top { border-bottom: 1px solid rgb(116, 126, 147); }
th.th_left { border-right: 1px solid rgb(116, 126, 147); }
td.removed { background-color: #ffcccc; }
td.added { background-color: #e4ffc7; }
</style>
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - GRE packets source and destination IP displayed \
incorrectly" href="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16295#c4">Comment \
# 4</a> on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - GRE packets source and destination IP displayed \
incorrectly" href="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16295">bug \
16295</a> from <span class="vcard"><a class="email" \
href="mailto:guy@alum.mit.edu" title="Guy Harris <guy@alum.mit.edu>"> \
<span class="fn">Guy Harris</span></a> </span></b>
<pre>(In reply to Christopher Maynard from <a \
href="show_bug.cgi?id=16295#c3">comment #3</a>) <span class="quote">> This is \
rather easily resolved by modifying the displayed columns, perhaps > even in a \
different "GRE" profile. Simply add Source and Destination custom > \
columns using ip.src and ip.dst as the fields, but choose 1 for the Field > \
Occurrence. In this way, the first occurrence will be displayed instead of > the \
last occurrence (or feel free to leave the occurrence at the default of > 0 to \
display both outer and inner addresses if you prefer).</span >
If somebody wants the outer layer's addresses displayed, are they also going to
want the outer layer's Info value displayed, or are they going to want the
address columns not to match the Info column?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>
--15773134791.c74d703.9217--
[Attachment #3 (text/plain)]
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic