linux-net  

Messages by Thread

• • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Ingo Molnar
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Jarek Poplawski
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Ingo Molnar
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Jarek Poplawski
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Ingo Molnar
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Jarek Poplawski
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Ingo Molnar
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Marcin Ślusarz
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Stephen Hemminger
  • Re: 2.6.23-rc2: WARNING: at kernel/irq/resend.c:70 check_irq_resend() Jean-Baptiste Vignaud
• Re:[patch] genirq: temporary fix for level-triggered IRQ resend Jean-Baptiste Vignaud
• PROBLEM: 8139too with MMIO hangs the system Zach Carter
• Multiple targets with same IP address? Brian Candler
  • Re: Multiple targets with same IP address? pankaj jain
  • Re: Multiple targets with same IP address? Brian Candler
  • Re: Multiple targets with same IP address? pankaj jain
  • Re: Multiple targets with same IP address? Brian Candler
  • Re: Multiple targets with same IP address? Adam M
• limit on number of logical interfaces pankaj jain
  • Re: limit on number of logical interfaces Stephen Hemminger
  • Re: limit on number of logical interfaces pankaj jain
  • Re: limit on number of logical interfaces Stephen Hemminger
• eepro100 - Nobody Cares (hardware?) ericj
  • Re: eepro100 - Nobody Cares (hardware?) Jeff Garzik
  • Re: eepro100 - Nobody Cares (hardware?) ericj
  • Re: eepro100 - Nobody Cares (hardware?) ericj
  • Re: eepro100 - Nobody Cares (hardware?) Frantisek Rysanek
• [no subject] nano bug
• ip addr show not showing all addresses Martin Volf
• ethtool version 6 released Jeff Garzik
• Re: Pin-pointing the root of unusual application latencies John Sigler
• NETIF_F_SG vs NETIF_F_FRAGLIST Eli Cohen
• [PATCH 0/2][RFC] Update network drivers to use devres bphilips
  • [PATCH 1/2][RFC] Update net core to use devres. bphilips
  • [PATCH 2/2][RFC] Update e100 driver to use devres. bphilips
  • Re: [PATCH 0/2][RFC] Update network drivers to use devres David Miller
• Linux TCP modifications Pallab Dutta
• Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK Sam Ravnborg
  • Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK Patrick McHardy
  • Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK Al Boldi
  • Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK Patrick McHardy
  • Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK Al Boldi
  • Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK Patrick McHardy
  • Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK Al Boldi
  • Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK Patrick McHardy
• Re: [PATCH] Netfilter Kconfig: Expose IPv4/6 connection tracking options by selecting NF_CONNTRACK David Miller
• Hotplug and Multipath routes = lost route Dâniel Fraga
  • Re: Hotplug and Multipath routes = lost route Bernd Eckenfels
  • Re: Hotplug and Multipath routes = lost route Dâniel Fraga
  • Re: Hotplug and Multipath routes = lost route Bernd Eckenfels
  • Re: Hotplug and Multipath routes = lost route Dâniel Fraga
  • Re: Hotplug and Multipath routes = lost route Patrick McHardy
  • Re: Hotplug and Multipath routes = lost route Dâniel Fraga
  • Re: Hotplug and Multipath routes = lost route Bernd Eckenfels
  • Re: Hotplug and Multipath routes = lost route Dâniel Fraga
• PFIFO to contain more pkts than allowed by TCP peer? Daniel Schaffrath
• Re: posible latency issues in seq_read Eric Dumazet
  • Re: posible latency issues in seq_read Chris Friesen
• IPR2 + Netfilter: stateful _routing_ on inbound DNAT, in dual-homed setup? Frantisek Rysanek
  • Re: IPR2 + Netfilter: stateful _routing_ on inbound DNAT, in dual-homed setup? Patrick McHardy
• tg3 issues patric
  • Re: tg3 issues pradeep singh
  • Re: tg3 issues Neil Horman
• Stalled connection (need help to debug) Oleg Verych
  • Re: Stalled connection (need help to debug) Kok, Auke
• iproute2-2.6.22-070710.tar.gz is a tar bomb Dan Nicholson
  • Re: iproute2-2.6.22-070710.tar.gz is a tar bomb Stephen Hemminger
  • Re: iproute2-2.6.22-070710.tar.gz is a tar bomb Dan Nicholson
• bluetooth socket problem amnuay . mu
• Realtek RTL8111B serious performance issues john
• UDP/IP via Ethernet in real time (config-preempt patch) M. Koehrer
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Kok, Auke
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Stephen Hemminger
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Christopher Fowler
  • Re[2]: UDP/IP via Ethernet in real time (config-preempt patch) Dan Searle
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Stephen Hemminger
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Christopher Fowler
  • Re[2]: UDP/IP via Ethernet in real time (config-preempt patch) M. Koehrer
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Stephen Hemminger
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Neil Horman
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) M. Koehrer
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Bill Davidsen
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) M. Koehrer
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Neil Horman
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) M. Koehrer
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Christopher Fowler
  • Re: UDP/IP via Ethernet in real time (config-preempt patch) Neil Horman
• No cmsg for SOCK_STREAM? Daniel Schaffrath
  • Re: No cmsg for SOCK_STREAM? Rémi Denis-Courmont
• questions about netlink socket Jing Huang
  • Re: questions about netlink socket Paul Moore
• incorrect source address for local TCP connections? Frank van Maarseveen
  • Re: incorrect source address for local TCP connections? Stephen Hemminger
  • Re: incorrect source address for local TCP connections? Frank van Maarseveen
  • Re: incorrect source address for local TCP connections? Bernd Eckenfels
  • Re: incorrect source address for local TCP connections? Bernd Eckenfels
  • Re: incorrect source address for local TCP connections? Frank van Maarseveen
  • Re: incorrect source address for local TCP connections? Frank van Maarseveen
  • Re: incorrect source address for local TCP connections? Brian Haley
  • Re: incorrect source address for local TCP connections? Frank van Maarseveen
  • Re: incorrect source address for local TCP connections? Bill Davidsen
  • cell phone bluetooth connection amnuay . mu
• Linux 2.6.22: Leak r=1 1 Sami Farin
• cifs mount fails David Harel
  • Re: cifs mount fails Bernd Eckenfels
  • Re: cifs mount fails Randy Dunlap
• Problem with tc hashing filters Stanislav Kruchinin
• socket close skaller
  • Re: socket close Eric Dumazet
  • Re: socket close skaller
  • Re: socket close Rhythmic Fistman
  • Re: socket close Eric Dumazet
  • Re: socket close skaller
  • Re: socket close Eric Dumazet
  • Re: socket close skaller
  • Re: socket close Charlie Brady
  • Re: socket close skaller
  • Re: socket close Rhythmic Fistman
  • Re: socket close skaller
• routing with multiple default routes Bill Davidsen
  • Re: routing with multiple default routes Charlie Brady
  • Re: routing with multiple default routes Christopher Fowler
  • Re: routing with multiple default routes Bernd Eckenfels
  • Re: routing with multiple default routes Bill Davidsen
  • Re: routing with multiple default routes Christopher Fowler
  • Re: routing with multiple default routes Christopher Fowler
  • Re: routing with multiple default routes Bill Davidsen
  • Re: routing with multiple default routes Bill Davidsen
  • [A BUG?]: routing with multiple default routes Bill Davidsen
  • Re: [A BUG?]: routing with multiple default routes Patrick McHardy
  • Re: [A BUG?]: routing with multiple default routes Bill Davidsen
  • Re: [A BUG?]: routing with multiple default routes Patrick McHardy
• receive errors Eli Cohen
  • Re: receive errors Bernd Eckenfels
  • Re: receive errors Bernd Eckenfels
  • Re: receive errors Eli Cohen
  • Re: receive errors Eli Cohen
• can't reach other hosts via IPv6 Matteo Croce
• [no subject] Matteo Croce
• How can I get the source MAC address from a TCP socket? Dan Searle
  • Re: How can I get the source MAC address from a TCP socket? Matti Aarnio
  • Re: How can I get the source MAC address from a TCP socket? Topher
  • Re: How can I get the source MAC address from a TCP socket? Dan Searle
• Dropped ICMP REDIRECTS Lior Dotan
• arp_find() and arp_set_predefined() Robert Bailey
• Maximum Number of IP Addresses David Jones
• [no subject] Josep
  • Re: pradeep singh
• module for getting underlying ethernet hardware and IP address... Tej Parkash
• tc with netem on 64bit systems Oliver Cook
  • Re: tc with netem on 64bit systems Stephen Hemminger
  • Re: tc with netem on 64bit systems David Miller
  • Re: tc with netem on 64bit systems Stephen Hemminger
  • Re: tc with netem on 64bit systems David Miller
• Re: [PATCH] Conntrack SIP Problem Patrick McHardy
  • Re: [PATCH] Conntrack SIP Problem Jerome Borsboom
  • Re: [PATCH] Conntrack SIP Problem Patrick McHardy
• Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Stephen Hemminger
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Marcin Ślusarz
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Al Boldi
  • Re: 2.6.20->2.6.21 - networking dies after random time Jean-Baptiste Vignaud
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Jean-Baptiste Vignaud
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Marcin Ślusarz
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar
  • Re: 2.6.20->2.6.21 - networking dies after random time Linus Torvalds
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar
  • Re: 2.6.20->2.6.21 - networking dies after random time Thomas Gleixner
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Alan Cox
  • [PATCH][netdrvr] lib8390: comment on locking by Alan Cox Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: [PATCH][netdrvr] lib8390: comment on locking by Alan Cox Re: 2.6.20->2.6.21 - networking dies after random time Alan Cox
  • Re: [PATCH][netdrvr] lib8390: comment on locking by Alan Cox Re: 2.6.20->2.6.21 - networking dies after random time Jeff Garzik
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar
  • Re: 2.6.20->2.6.21 - networking dies after random time Alan Cox
  • Re: 2.6.20->2.6.21 - networking dies after random time Marcin Ślusarz
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Thomas Gleixner
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar
  • Re: 2.6.20->2.6.21 - networking dies after random time Marcin Ślusarz
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar
  • Re: 2.6.20->2.6.21 - networking dies after random time Marcin Ślusarz
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar
  • Re: 2.6.20->2.6.21 - networking dies after random time Marcin Ślusarz
  • Re: 2.6.20->2.6.21 - networking dies after random time Jarek Poplawski
  • Re: 2.6.20->2.6.21 - networking dies after random time Marcin Ślusarz
  • Re: 2.6.20->2.6.21 - networking dies after random time Ingo Molnar

• Earlier messages
• Later messages