Bug#267765: doesn't properly show VLAN frames
Marc Haber [EMAIL PROTECTED] writes: I will try a Debian kernel on the weekend. It will be a waste of time, since the bug will be reproducible, but, oh well. Ok to close this bug? -- ,''`. : :' :Romain Francoise [EMAIL PROTECTED] `. `' http://people.debian.org/~rfrancoise/ `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267765: doesn't properly show VLAN frames
On Mon, Oct 10, 2005 at 08:04:01PM +0200, Romain Francoise wrote: Marc Haber [EMAIL PROTECTED] writes: I will try a Debian kernel on the weekend. It will be a waste of time, since the bug will be reproducible, but, oh well. Ok to close this bug? As long as the behavior is documented somewhere so that people know that they're bitten by a bad driver, yes. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267765: Re: Bug#267765: doesn't properly show VLAN frames
On Wed, Mar 16, 2005 at 08:41:17PM +0100, Romain Francoise wrote: Marc Haber [EMAIL PROTECTED] writes: The last two lines are all what is dumped for the ping on the VLAN interface. One notices two problems: (1) only outgoing frames show (2) the outgoing frames don't show as VLAN tagged frames. It is impossible to distinguish the tagged frame from an untagges frame. Could you try with the filter '(icmp or arp) or vlan'? That doesn't change anything. The setup has, however, changed. I am now testing on current sid, with a 2.6.12.5 kernel, tcpdump 3.9.3-2 and libpcap0.8 0.9.3-1. The network interface in question is: :02:0e.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M_2 Gigabit Ethernet (rev 03) Subsystem: Hewlett-Packard Company: Unknown device 088c Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11 Memory at 9000 (64-bit, non-prefetchable) [size=64K] Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable- and the driver being used is: Aug 23 09:13:17 scyw00225 kernel: tg3.c:v3.31 (June 8, 2005) Aug 23 09:13:17 scyw00225 kernel: eth0: Tigon3 [partno(BMC5705mA3) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:12:79:56:70:af Aug 23 09:13:17 scyw00225 kernel: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[0] TSOcap[1] Aug 23 09:13:17 scyw00225 kernel: eth0: dma_rwctrl[763f] The behavior cannot be reproduced on a reference system, which has the same software, but different hardware (an E100). Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267765: doesn't properly show VLAN frames
Marc Haber [EMAIL PROTECTED] writes: The behavior cannot be reproduced on a reference system, which has the same software, but different hardware (an E100). OK, so this is a tg3 bug after all. I'm unsure what to do next, shall I close the bug? Or are you using a Debian kernel image I could reassign the bug to? -- ,''`. : :' :Romain Francoise [EMAIL PROTECTED] `. `' http://people.debian.org/~rfrancoise/ `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267765: doesn't properly show VLAN frames
On Tue, Aug 23, 2005 at 06:49:08PM +0200, Romain Francoise wrote: Marc Haber [EMAIL PROTECTED] writes: The behavior cannot be reproduced on a reference system, which has the same software, but different hardware (an E100). OK, so this is a tg3 bug after all. Maybe, maybe not. Does libpcap have a possibility to work around? I'm unsure what to do next, shall I close the bug? Or are you using a Debian kernel image I could reassign the bug to? I will try a Debian kernel on the weekend. It will be a waste of time, since the bug will be reproducible, but, oh well. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267765: doesn't properly show VLAN frames
Marc Haber [EMAIL PROTECTED] writes: $ sudo tcpdump -i eth2 -qn icmp or arp tcpdump: listening on eth2 13:41:10.883402 arp who-has 192.168.129.9 tell 192.168.129.1 13:41:10.884116 arp reply 192.168.129.9 is-at 0:f:20:17:3c:c0 13:41:10.884124 192.168.129.1 192.168.129.9: icmp: echo request (DF) 13:41:10.884669 192.168.129.9 192.168.129.1: icmp: echo reply (DF) 13:41:16.496210 arp who-has 192.168.131.9 tell 192.168.131.1 13:41:16.497702 192.168.131.1 192.168.131.9: icmp: echo request (DF) The ping on the untagged VLAN is dumped OK. One sees all four frames: ARP request/reply, ICMP echo request/reply. The last two lines are all what is dumped for the ping on the VLAN interface. One notices two problems: (1) only outgoing frames show (2) the outgoing frames don't show as VLAN tagged frames. It is impossible to distinguish the tagged frame from an untagges frame. Could you try with the filter '(icmp or arp) or vlan'? Thanks, -- ,''`. : :' :Romain Francoise [EMAIL PROTECTED] `. `' http://people.debian.org/~rfrancoise/ `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
