Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Francois-Xavier Le Bail
On 22/03/2020 18:29, Guy Harris via tcpdump-workers wrote: > 5) Treat rpcap as "remote procedure call for libpcap" and put it under the > the-tcpdump-group team, and put pcap under the pcapng team as per the same > reason as 4). Ok.

Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Francois-Xavier Le Bail
On 21/03/2020 22:14, Guy Harris via tcpdump-workers wrote: > 1) has the slight disadvantage that the name for the team suggests it's for > pcapng only; it appears that teams can be renamed: > > >

Re: [Wireshark-dev] About transport name resolution with the new services file

2007-08-20 Thread Francois-Xavier Le Bail
--- Richard van der Hoff [EMAIL PROTECTED] wrote: On Sat, 18 Aug 2007, Francois-Xavier Le Bail wrote: Hi List, In version 0.99.6 we have, by example : Source Destination Protocol Info 10.0.0.2 62.210.65.158 TCP 3946 http [ACK] ... In version 0.99.7-SVN-22549 we have

Re: [Wireshark-dev] About transport name resolution with the new services file

2007-08-19 Thread Francois-Xavier Le Bail
--- Andrew Hood [EMAIL PROTECTED] wrote: Richard van der Hoff wrote: On Sat, 18 Aug 2007, Francois-Xavier Le Bail wrote: Hi List, In version 0.99.6 we have, by example : Source Destination Protocol Info 10.0.0.2 62.210.65.158 TCP 3946 http [ACK] ... In version

Re: [Wireshark-dev] About transport name resolution with the new services file

2007-08-19 Thread Francois-Xavier Le Bail
--- Andrew Hood [EMAIL PROTECTED] wrote: Francois-Xavier Le Bail wrote: --- Andrew Hood [EMAIL PROTECTED] wrote: It it wasn't for Windows' broken behaviour in letting any port be ephemeral, that might make some sense. I have been forced to set registry values to make Windows behave

[Wireshark-dev] About transport name resolution with the new services file

2007-08-18 Thread Francois-Xavier Le Bail
Hi List, In version 0.99.6 we have, by example : Source Destination Protocol Info 10.0.0.2 62.210.65.158 TCP 3946 http [ACK] ... In version 0.99.7-SVN-22549 we have : Source Destination Protocol Info 10.0.0.2 62.210.65.158 TCP backupedge http [ACK] ... The resolution from

Re: [Wireshark-dev] [PATCH] packet-bootp.c: enhancement to decode DHCP option 121

2007-08-02 Thread Francois-Xavier Le Bail
Hi, I Agree with you, patch sent. Regards, Francois-Xavier Le Bail --- Graham Bloice [EMAIL PROTECTED] wrote: Jaap Keuter wrote: Hi, Checked in. Thanx, Jaap Francois-Xavier Le Bail wrote: Hi, The following patch decode DHCP option 121. (RFC 3442) Output example

[Wireshark-dev] [PATCH] packet-bootp.c: enhancement to decode DHCP option 121

2007-07-24 Thread Francois-Xavier Le Bail
Hi, The following patch decode DHCP option 121. (RFC 3442) Output example : Option: (t=121,l=59) Classless Static Route Option: (121) Classless Static Route Length: 59 Value: 00C0A80301080AC0A80302090B80C0A8030310AC10C0A803... Subnet/MaskWidth-Router: default-192.168.3.1