Comments

• 

  over 6 years ago by pvorel | Reply

  First draft has been sent to tcpdump ML:

  [tcpdump-workers] [RFC LIBPCAP PATCH 0/1] LINKTYPELINUXSLL2 implementation

  [tcpdump-workers] [RFC TCPDUMP PATCH 0/2] LINKTYPELINUXSLL2 implementation

×
Edit Comment 3546
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
First draft has been sent to tcpdump ML: [[tcpdump-workers] [RFC LIBPCAP PATCH 0/1] LINKTYPE_LINUX_SLL2 implementation](https://lists.sandelman.ca/pipermail/tcpdump-workers/2018-July/001012.html) [[tcpdump-workers] [RFC TCPDUMP PATCH 0/2] LINKTYPE_LINUX_SLL2 implementation ](https://lists.sandelman.ca/pipermail/tcpdump-workers/2018-July/001014.html)
 
×
Reply to pvorel
First draft has been sent to tcpdump ML:
[tcpdump-workers] [RFC LIBPCAP PATCH 0/1] LINKTYPELINUXSLL2 implementation
[tcpdump-workers] [RFC TCPDUMP PATCH 0/2] LINKTYPELINUXSLL2 implementation
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  over 6 years ago by pvorel | Reply

  Post Hackweek state: although my LINKTYPELINUXSLL2 implementation was not accepted (maintainer wrote own, much better implementation), I've learned a lot about libpcap and tcpdump internals + how libpcap/tcpdump community works (accepted some doc LINKTYPELINUXSLL2 related patches).

  I was an impulse for maintainers to finish this long waiting implementation of feature Display/filter on packet direction and interface name: original bug #125 on sourceforge.net was created in 2009, it's migration to github #127 leaded just to the LINKTYPELINUXSLL2: Linux "cooked" capture encapsulation v2 specification.

  ATM the specification has been published and got allocated DLT and LINKTYPE numbers (both my patches) and got implemented on libpcap and tcpdump side.

  The actual code displaying packet name (my patch) is waiting as PR for comments or accepting (https://github.com/the-tcpdump-group/tcpdump/pull/689).

×
Edit Comment 3612
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Post Hackweek state: although my LINKTYPE_LINUX_SLL2 implementation was not accepted (maintainer wrote own, much better implementation), I've learned a lot about libpcap and tcpdump internals + how libpcap/tcpdump community works (accepted some doc LINKTYPE_LINUX_SLL2 related patches). I was an impulse for maintainers to finish this long waiting implementation of feature **Display/filter on packet direction and interface name**: [original bug #125 on sourceforge.net](https://sourceforge.net/p/libpcap/bugs/125/) was created in 2009, it's migration to [github #127](https://github.com/the-tcpdump-group/libpcap/issues/127) leaded just to the [LINKTYPE_LINUX_SLL2: Linux "cooked" capture encapsulation v2 specification](http://www.tcpdump.org/linktypes/LINKTYPE_LINUX_SLL2.html). ATM the specification has been published and got allocated DLT and LINKTYPE numbers (both my patches) and got implemented on libpcap and tcpdump side. The actual code displaying packet name (my patch) is waiting as PR for comments or accepting ([https://github.com/the-tcpdump-group/tcpdump/pull/689](https://github.com/the-tcpdump-group/tcpdump/pull/689)).
 
×
Reply to pvorel
Post Hackweek state: although my LINKTYPELINUXSLL2 implementation was not accepted (maintainer wrote own, much better implementation), I've learned a lot about libpcap and tcpdump internals + how libpcap/tcpdump community works (accepted some doc LINKTYPELINUXSLL2 related patches).
I was an impulse for maintainers to finish this long waiting implementation of feature Display/filter on packet direction and interface name: original bug #125 on sourceforge.net was created in 2009, it's migration to github #127 leaded just to the LINKTYPELINUXSLL2: Linux "cooked" capture encapsulation v2 specification.
ATM the specification has been published and got allocated DLT and LINKTYPE numbers (both my patches) and got implemented on libpcap and tcpdump side.
The actual code displaying packet name (my patch) is waiting as PR for comments or accepting (https://github.com/the-tcpdump-group/tcpdump/pull/689).
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview