Simon,
Does the packet injection allow hostapd to use nl80211 instead of the
wlan0ap interface to send management frames?
It's intended that it does that, yes.
Important features for this
include requesting a transmit status - i.e. the ability for
hostapd/wpa_supplicant to know if the
At 01:15 15/09/2006, Stephen Hemminger wrote:
On Thu, 14 Sep 2006 17:51:50 +0100
Tony Jeffree [EMAIL PROTECTED] wrote:
Steve/Brian -
You've probably seen Mick Seaman's comments on this by now - as he points
out in his email, tinkering with existing STP implementations is not
likely
to be
Hi Tim,
Hi Jeff,
[EMAIL PROTECTED] wrote:
On Thu, Sep 14, 2006 at 05:39:08PM +0200, Ingo Oeser wrote:
Ingo Oeser wrote:
I get the following message when trying to transfer big files
(via FTP or SCP) since Linux 2.6.16.27. It didn't happen with Linux
2.6.13.4.
[702238.242237]
On Fri, Sep 15, 2006 at 09:06:02AM +1000, Philip Craig wrote:
Patrick McHardy wrote:
Joerg Roedel wrote:
On Thu, Sep 14, 2006 at 11:21:22AM +1000, Philip Craig wrote:
Joerg Roedel wrote:
+ To configure tunnels an extra tool is required. You can
download
+ it from
It looks like diffs array is write-only. It also looks like ipv4
occurences use some csum_fold() trickery. Was is forgotten here? Should
diffs be removed?
20 static unsigned int ip6t_hl_target(struct sk_buff **pskb,
21 const struct net_device *in,
On Thu, Sep 14, 2006 at 08:46:07AM -0700, [EMAIL PROTECTED] wrote:
On Thu, Sep 14, 2006 at 05:39:08PM +0200, Ingo Oeser wrote:
Is it possible to have the maximum value right from the start?
May I tune it somewhere to be the maximum from the start?
This will (if I recall) increase transmit
On Thu, Sep 14, 2006 at 12:58:30AM +, Jesse Huang wrote:
[...]
@@ -262,8 +262,6 @@ enum alta_offsets {
ASICCtrl = 0x30,
EEData = 0x34,
EECtrl = 0x36,
- TxStartThresh = 0x3c,
- RxEarlyThresh = 0x3e,
Why ?
FlashAddr = 0x40,
FlashData = 0x44,
It appears to be intentionally, but I don't see a reason for it.
Can you try if this patch makes it work as expected?
[PACKET]: Don't truncate non-linear skbs with mmaped IO
Non-linear skbs are truncated to their linear part with mmaped IO.
Fix by using skb_copy_bits instead of memcpy.
[PATCH 4/9] s390: qeth driver fixes [1/6]
From: Frank Pavlic [EMAIL PROTECTED]
- Drop incoming packets with vlan_tag set
if card-vlangrp is not set.
- use always vlan_hwaccel_rx to pass
vlan frames to the stack.
- fix recovery problem. Device was
[PATCH 8/9] s390: qeth driver fixes [5/6]
From: Frank Pavlic [EMAIL PROTECTED]
fix kernel panic in qdio queue handling.
qeth_qdio_clear_card() could be invoked by 2 CPUs
simultaneously (for example reboot event and recovery).
Signed-off-by: Frank Pavlic [EMAIL PROTECTED]
[PATCH 5/9] s390: qeth driver fixes [2/6]
From: Frank Pavlic [EMAIL PROTECTED]
- fixed error handling in create_device_attributes
- fixed some minor bugs in IPv4
and IPv6 address checking
Signed-off-by: Frank Pavlic [EMAIL PROTECTED]
---
drivers/s390/net/qeth.h |
Hi Jeff,
this is a RESEND of the nine s390 network driver patches.
I finally found that my kmail corrupted almost every patch
I sent the last time. Please apply these 9 patches and forget
about my first attempt! Sorry for the delay, I had some fights
with sendmail, IMAP and mutt configuration.
[PATCH 3/9] s390: Makefile cleanup
From: Frank Pavlic [EMAIL PROTECTED]
remove CONFIG_MPC from Makefile which was
introduced accidently in the past.
Signed-off-by: Frank Pavlic [EMAIL PROTECTED]
---
drivers/s390/net/Makefile |1 -
1 files changed, 0 insertions(+), 1
[PATCH 2/9] s390: netiucv driver fixes
From: Frank Pavlic [EMAIL PROTECTED]
- missing lock initialization added
- avoid duplicate iucv-interfaces to the same peer
- rw-lock added for manipulating the list of
defined iucv connections
Signed-off-by: Frank Pavlic
[PATCH 6/9] s390: qeth driver fixes [3/6]
From: Frank Pavlic [EMAIL PROTECTED]
fixed kernel panic caused by qeth driver:
Using a bonding device qeth driver will realloc
headroom for every skb coming from the bond device.
Once this happens qeth frees the original
[PATCH 9/9] s390: qeth driver fixes [6/6]
From: Frank Pavlic [EMAIL PROTECTED]
- Hipersockets has no IPV6 support, thus prevent issueing
SETRTG_IPV6 control commands on Hipersockets devices.
- fixed error handling in qeth_sysfs_(un)register
Signed-off-by: Frank Pavlic
[PATCH 7/9] s390: qeth driver fixes [4/6]
From: Frank Pavlic [EMAIL PROTECTED]
- fix kernel crash due to race,
set card-state to SOFTSETUP after
card and card-dev are initialized properly.
- remove CONFIG_QETH_PERF_STATS, use sysfs attribute instead,
Frank Pavlic [EMAIL PROTECTED] wrote:
[PATCH 6/9] s390: qeth driver fixes [3/6]
From: Frank Pavlic [EMAIL PROTECTED]
fixed kernel panic caused by qeth driver:
Using a bonding device qeth driver will realloc
headroom for every skb coming from the bond device.
yes it would but the problem in qeth is not only bonding related.
We just have found it in a bonding scenario . But this kernel
panic could also occur without bonding.
But thanks for reviewing it
On Fri, Sep 15, 2006 at 08:51:25AM -0700, Jay Vosburgh wrote:
Frank Pavlic [EMAIL PROTECTED]
Kernels 2.6.13, 2.6.17.7 2.6.17.13...
I've been unable to capture outbound packets from local eth2,
generated by pktgen using the just previous and latest releases
of tcpdump libpcap. All incoming pktgen pkts are seen just fine.
Pkts are UDP.
Any clues to save me some time fixing this,
Simon Barber wrote:
Why is it necessary to set phymode to B? - a G client can connect
perfectly well to a B AP.
We need this information for rate scaling and we need to send the NIC
different command depends on the AP connection type.
Mohamed
Simon
-Original Message-
From: [EMAIL
[EMAIL PROTECTED] wrote:
Kernels 2.6.13, 2.6.17.7 2.6.17.13...
I've been unable to capture outbound packets from local eth2,
generated by pktgen using the just previous and latest releases
of tcpdump libpcap. All incoming pktgen pkts are seen just fine.
Pkts are UDP.
Any clues to save me
Hi All,
Thank you Jeff.
We have incorporated feedbacks which received. I'll be sending updated
patchset in subsequent emails.
-Amit
Signed-off-by: Amit S. Kale [EMAIL PROTECTED]
MAINTAINERS |7
drivers/net/Kconfig |5
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_hw.c
linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_hw.c
--- linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_hw.c1969-12-31
16:00:00.0 -0800
+++
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/MAINTAINERS linux-2.6.18-rc7/MAINTAINERS
--- linux-2.6.18-rc7.orig/MAINTAINERS 2006-09-15 09:27:56.0 -0700
+++ linux-2.6.18-rc7/MAINTAINERS2006-09-15 09:32:05.0 -0700
@@ -2060,6 +2060,13
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_init.c
linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_init.c
--- linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_init.c 1969-12-31
16:00:00.0 -0800
+++
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_isr.c
linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_isr.c
--- linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_isr.c 1969-12-31
16:00:00.0 -0800
+++
But it's not the AP connection type that determines what rates are
available - it's the available rate set - this is independent of whether
the card is B or G. A G AP may only advertise B rates, even though it's
a G AP. I still don't see any need to change the phytype.
Simon
-Original
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_ethtool.c
linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_ethtool.c
--- linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_ethtool.c
1969-12-31 16:00:00.0 -0800
+++
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_hw.h
linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_hw.h
--- linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_hw.h1969-12-31
16:00:00.0 -0800
+++
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_hdr.h
linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_hdr.h
--- linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_hdr.h 1969-12-31
16:00:00.0 -0800
+++
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic.h
linux-2.6.18-rc7/drivers/net/netxen/netxen_nic.h
--- linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic.h 1969-12-31
16:00:00.0 -0800
+++
diff -Narup -X linux-2.6.18-rc7.orig/Documentation/dontdiff
linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_phan_reg.h
linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_phan_reg.h
--- linux-2.6.18-rc7.orig/drivers/net/netxen/netxen_nic_phan_reg.h
1969-12-31 16:00:00.0 -0800
+++
[PATCH] Add Broadcom PHY support
This patch adds a driver to support the bcm5421s and bcm5461s PHY
Kernel version: linux-2.6.18-rc6
Signed-off-by: Amy Fong [EMAIL PROTECTED]
Index: linux-2.6.18-rc6/drivers/net/phy/broadcom.c
===
I see your point here, although some one will file some bugs against the
driver about showing G while associating with B-mode AP. By the way how
can you figure if the AP is B/G other than the rates?
Simon Barber wrote:
But it's not the AP connection type that determines what rates are
On Friday 15 September 2006 19:50, mabbas wrote:
I see your point here, although some one will file some bugs against the
driver about showing G while associating with B-mode AP. By the way how
can you figure if the AP is B/G other than the rates?
IIRC, only 802.11g APs will send the extended
36 matches
Mail list logo
