> Is this really supposed to be done in the HW driver / support code level,
> or is it supposed to be done in the protocol (IP / ARP) level??
oops I was half asleep
Driver sets
skb->mac.raw
skb->pkt_type
skb->protocol
(see net/ethernet/eth.c)
skb->h.raw and
On Wed, 31 Jan 2001, Alan Cox wrote:
>
> It should be set before netif_rx() is called on the packet. Typically that
> means the driver or its support code sets protocol and nh.raw and if a
> second header is pulled up then they are set again by whichever code does that
> and calls netif_rx
On Wed, 31 Jan 2001, Alan Cox wrote:
> > What I'd like to know is: what exactly causes this msg?? It seems that
> > it's printed when someone sends a packet without properly setting
> > skb->nh.raw first, but who's supposed to set skb->nh.raw?? The HW driver??
> > The data link (HDLC) driver??
> The msg comes from net/core/dev.c, and this device is using the Cisco HDLC
> protocol in drivers/net/hdlc.c . However, AFAIK, 0008 and 0608 represent
> IP and ARP (respectively), not Cisco HDLC. So ...
>
> What I'd like to know is: what exactly causes this msg?? It seems that
> it's printed
On Wed, 31 Jan 2001, Alan Cox wrote:
What I'd like to know is: what exactly causes this msg?? It seems that
it's printed when someone sends a packet without properly setting
skb-nh.raw first, but who's supposed to set skb-nh.raw?? The HW driver??
The data link (HDLC) driver?? The
On Wed, 31 Jan 2001, Alan Cox wrote:
It should be set before netif_rx() is called on the packet. Typically that
means the driver or its support code sets protocol and nh.raw and if a
second header is pulled up then they are set again by whichever code does that
and calls netif_rx again
Is this really supposed to be done in the HW driver / support code level,
or is it supposed to be done in the protocol (IP / ARP) level??
oops I was half asleep
Driver sets
skb-mac.raw
skb-pkt_type
skb-protocol
(see net/ethernet/eth.c)
skb-h.raw and
Hello,
I have a customer who's getting tons of these msgs in his LOGs:
kernel: protocol 0008 is buggy, dev hdlc0
kernel: protocol 0608 is buggy, dev hdlc0
The msg comes from net/core/dev.c, and this device is using the Cisco HDLC
protocol in drivers/net/hdlc.c . However, AFAIK, 0008 and 0608
Hello,
I have a customer who's getting tons of these msgs in his LOGs:
kernel: protocol 0008 is buggy, dev hdlc0
kernel: protocol 0608 is buggy, dev hdlc0
The msg comes from net/core/dev.c, and this device is using the Cisco HDLC
protocol in drivers/net/hdlc.c . However, AFAIK, 0008 and 0608
Hi,
>>>>> "Ivan" == Ivan Passos <[EMAIL PROTECTED]> writes:
Ivan> Hello,
Ivan> I have a customer who's getting tons of this msg in his
Ivan> LOGs:
Ivan> kernel: protocol 0008 is buggy, dev hdlc0
Ivan> The msg comes from net
Hello,
I have a customer who's getting tons of this msg in his LOGs:
kernel: protocol 0008 is buggy, dev hdlc0
The msg comes from net/core/dev.c, and this device is using the Frame
Relay protocol in drivers/net/hdlc.c .
What I'd like to know is:
- What exactly causes this msg?? It seems
Hello,
I have a customer who's getting tons of this msg in his LOGs:
kernel: protocol 0008 is buggy, dev hdlc0
The msg comes from net/core/dev.c, and this device is using the Frame
Relay protocol in drivers/net/hdlc.c .
What I'd like to know is:
- What exactly causes this msg?? It seems
12 matches
Mail list logo
