Comment # 4
on bug 13086
from Pascal Quantin
(In reply to Fayçal NOUSHI from comment #3)
> Thanks for looking into this Pascal. Yes, the issue is both found on json
> and ek outputs.
> The fix looks similar to the rest of the fields in this case such as eth.dst
> or eth.src. It would be coherent with what's already there.
Actually this field is also impacted by my change (it suffers from the same
issue). Previously it was displayed as:
"eth.dst": {
"eth.dst_resolved": "JuniperN_a6:54:5f",
"eth.addr": "00:05:85:a6:54:5f",
"eth.addr_resolved": "JuniperN_a6:54:5f",
"eth.lg": "0",
"eth.ig": "0"
},
> The fix looks
> fine to me... that said, I've yet to dive into Wireshark code :-)
> May I know what file would this fix be on ?
epan/print.c but d'ont worry I'm gonna push the change in a minute or so.
You are receiving this mail because:
- You are watching all bug changes.