2.6.16-rc2 still misses your patch. Was there a special reason not to
send it
to Linus?
cu,
Knut
On Fri, Jan 27, 2006 at 07:07:34AM +0100, Knut Petersen wrote:
Well, there are no problems if SuSEfirewall2 is disabled. But have a look
at the loaded modules:
ipt_MASQUERADE 3968 1
On Mon, Jan 30, 2006 at 04:15:51PM -0800, Stephen Hemminger wrote:
> Okay, what is the hardware version:
> dmesg | grep skge
> Maybe that chip rev is no good.
skge 1.3 addr 0xd042c000 irq 169 chip Yukon-Lite rev 7
skge eth0: addr 00:10:f3:06:83:d4
skge 1.3 addr 0xd042 irq 193 chip Yukon-L
On Tue, 31 Jan 2006 01:16:59 +0200
Pekka Pietikainen <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 27, 2006 at 11:22:42PM +1100, Herbert Xu wrote:
> > OK, although we can't rule out sky2/netfilter from the enquiry, I've
> > identified two bugs in ppp/pppoe that may be responsible for what you
> > are s
On Fri, Jan 27, 2006 at 11:22:42PM +1100, Herbert Xu wrote:
> OK, although we can't rule out sky2/netfilter from the enquiry, I've
> identified two bugs in ppp/pppoe that may be responsible for what you
> are seeing. So please try the following patch and let us know if the
> problem still exists (
Herbert Xu wrote:
When we pull the PPP protocol off the skb, we forgot to update the
hardware RX checksum. This may lead to messages such as
dsl0: hw csum failure.
Similarly, we need to clear the hardware checksum flag when we use
the existing packet to store the decompressed result.
Herbert Xu wrote:
> On Fri, Jan 27, 2006 at 07:07:34AM +0100, Knut Petersen wrote:
>
>>Well, there are no problems if SuSEfirewall2 is disabled. But have a look
>>at the loaded modules:
>>
>>ipt_MASQUERADE 3968 1
>>pppoe 15360 2
>>pppox 4616 1 pppoe
>
On Fri, Jan 27, 2006 at 07:07:34AM +0100, Knut Petersen wrote:
>
> Well, there are no problems if SuSEfirewall2 is disabled. But have a look
> at the loaded modules:
>
> ipt_MASQUERADE 3968 1
> pppoe 15360 2
> pppox 4616 1 pppoe
OK, although we can't
* Herbert Xu wrote:
Does the problem go away if you disable conntrack by unloading its module?
Please try to capture the offending ICMP packet with tcpdump and show us
what it looks like.
Well, there are no problems if SuSEfirewall2 is disabled. But have a look
at the loaded modules:
ipt_M
Knut Petersen <[EMAIL PROTECTED]> wrote:
>
> "ethtool -K eth0 rx off" does cure my problem with sky2.
>
> Anybody is invited to send patches as the problem is 100% reproducible here.
Does the problem go away if you disable conntrack by unloading its module?
Please try to capture the offending IC
On Tue, 24 Jan 2006 10:43:57 +0100
Knut Petersen <[EMAIL PROTECTED]> wrote:
> Stephen Hemminger schrieb:
>
> >Could you try turning off rx checksumming (with ethtool).
> > ethtool -K eth0 rx off
> >
> >There probably still are (generic) bugs in the netfilter code for CHECKSUM_HW
> >socket buf
Stephen Hemminger schrieb:
Could you try turning off rx checksumming (with ethtool).
ethtool -K eth0 rx off
There probably still are (generic) bugs in the netfilter code for CHECKSUM_HW
socket buffers.
"ethtool -K eth0 rx off" does cure my problem with sky2.
Anybody is invited to
Stephen Hemminger wrote:
O
It seems that the SuSE Firewall locked something
I started with kernel 2.6.15-git7, tried 2.6.15.1 and 2.6.16-rc1*.
At the moment I do use a kernel 2.6.15-git7 patched with an updated sky2
(v.013).
I could not find a single working sky2 configuration.
O
>
> It seems that the SuSE Firewall locked something
>
> I started with kernel 2.6.15-git7, tried 2.6.15.1 and 2.6.16-rc1*.
> At the moment I do use a kernel 2.6.15-git7 patched with an updated sky2
> (v.013).
> I could not find a single working sky2 configuration.
>
Are you using the f
13 matches
Mail list logo
