Re: bce(4) and lagg(4) fix [was: bce(4) sees all incoming frames as 2026 bytes in length]

2009-04-30 Thread pluknet
2009/4/30 Nikolay Denev : > On Apr 30, 2009, at 3:04 PM, Nikolay Denev wrote: > [snip] >>> >>> I think I got it. >>> >>> It seems that the mbuf fields m_pkthdr.len and m_len are not updated to >>> the real packet size pkt_len. >>> Well, actually they are updated, but only if we have ZERO_COPY_SOCKE

Re: bce(4) sees all incoming frames as 2026 bytes in length

2009-04-30 Thread pluknet
2009/4/30 Nikolay Denev : > On Apr 29, 2009, at 7:04 PM, pluknet wrote: > >> 2009/4/29 Niki Denev : >> >>> bce1: mem >>> 0xf800-0xf9ff irq 16 at device 0.0 on pci3 >>> bce1: Ethernet address: 00:22:19:xx:xx:xx >>> bce1: [ITHREAD] >>> bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 1

Re: bce(4) and lagg(4) fix [was: bce(4) sees all incoming frames as 2026 bytes in length]

2009-04-30 Thread Nikolay Denev
On Apr 30, 2009, at 3:04 PM, Nikolay Denev wrote: [snip] I think I got it. It seems that the mbuf fields m_pkthdr.len and m_len are not updated to the real packet size pkt_len. Well, actually they are updated, but only if we have ZERO_COPY_SOCKETS defined. After I added this : m0->m_p

bce(4) and lagg(4) fix [was: bce(4) sees all incoming frames as 2026 bytes in length]

2009-04-30 Thread Nikolay Denev
On Apr 30, 2009, at 2:56 PM, Nikolay Denev wrote: On Apr 29, 2009, at 7:04 PM, pluknet wrote: 2009/4/29 Niki Denev : bce1: mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3 bce1: Ethernet address: 00:22:19:xx:xx:xx bce1: [ITHREAD] bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit,

Re: bce(4) sees all incoming frames as 2026 bytes in length

2009-04-30 Thread Nikolay Denev
On Apr 29, 2009, at 7:04 PM, pluknet wrote: 2009/4/29 Niki Denev : bce1: mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3 bce1: Ethernet address: 00:22:19:xx:xx:xx bce1: [ITHREAD] bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); B/C (0x04040105); Flags( MFW MSI ) bce1: f

Re: bce(4) sees all incoming frames as 2026 bytes in length

2009-04-29 Thread pluknet
2009/4/29 Niki Denev : > bce1: mem > 0xf800-0xf9ff irq 16 at device 0.0 on pci3 > bce1: Ethernet address: 00:22:19:xx:xx:xx > bce1: [ITHREAD] > bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); B/C > (0x04040105); Flags( MFW MSI ) > > bce1: flags=8843 metric 0 mtu 1500 >

Re: bce(4) sees all incoming frames as 2026 bytes in length

2009-04-29 Thread Niki Denev
On Wed, Apr 29, 2009 at 4:59 PM, pluknet wrote: > 2009/4/29 Nikolay Denev : >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hello, >> >> I have the following problem with the new bce(4) driver on a 7.2-PRERELEASE >> from a few days ago. >> When I run tcpdump on the bce interface on the m

Re: bce(4) sees all incoming frames as 2026 bytes in length

2009-04-29 Thread pluknet
2009/4/29 Nikolay Denev : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > > I have the following problem with the new bce(4) driver on a 7.2-PRERELEASE > from a few days ago. > When I run tcpdump on the bce interface on the machine, all incoming frames > are shown as 2026 in size, >

bce(4) sees all incoming frames as 2026 bytes in length

2009-04-29 Thread Nikolay Denev
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I have the following problem with the new bce(4) driver on a 7.2- PRERELEASE from a few days ago. When I run tcpdump on the bce interface on the machine, all incoming frames are shown as 2026 in size, but on the sending machine tcpdump repo