
++hirakendu wrote:use 1.5.4 ...


I have this same problem, but for ipw2200. Is there a way to set the ethernet address to allow rtap0 to work?loeb-it wrote:When trying to bring up the rtap interface it does not work:
galadriel mithrandir # ifconfig rtap0 up
SIOCSIFFLAGS: Das Argument ist ungültig
This occurs with ipwraw driver and also with ipw3945 driver, so it seems to be a more general issue.
It also worked with kamikaze-sources before.
Anyone else tried?
Addon:
------------------------------------------------------
In 2.6.24 kernels an interface can only be brought up with a mac address set. Created patches to fix this for ipw3945 and ipwraw drivers.
ipw3945-2.6.24-rtap_up.patch:Code: Select all
*** linux_bak/drivers/net/wireless/ipw3945.c 2008-02-06 19:20:41.000000000 +0100 --- linux/drivers/net/wireless/ipw3945.c 2008-02-07 00:43:10.000000000 +0100 *************** *** 15131,15134 **** --- 15131,15142 ---- priv->config |= CFG_CUSTOM_MAC; memcpy(priv->mac_addr, addr->sa_data, ETH_ALEN); + + // hack to get rtap device up, since in 2.6.24 kernels the mac of an iface must be set + // setting to mac of the wifi interface + + if (rtap_iface) memcpy(priv->prom_net_dev->dev_addr, addr->sa_data, ETH_ALEN); + + // hack end + printk(KERN_INFO "%s: Setting MAC to %s\n", priv->net_dev->name, print_mac(mac, priv->mac_addr)); *************** *** 16284,16287 **** --- 16292,16305 ---- priv->prom_priv->ieee->iw_mode = IW_MODE_MONITOR; + // ToDo: find real mac here + + // Hack to get rtap device up, since in 2.6.24 kernels the mac of an iface must be set + // Setting to a dummy mac since I don't know where to get the real one. + // Since no packets are being sent to this interface, this is not really important. + + strcpy(priv->prom_net_dev->dev_addr,"0018DE95031A"); + + // hack end + rc = register_netdev(priv->prom_net_dev); if (rc) {
ipwraw-2.6.24-rtap_up.patch:Code: Select all
*** linux_bak/drivers/net/wireless/ipwraw.c 2008-02-06 23:41:16.000000000 +0100 --- linux/drivers/net/wireless/ipwraw.c 2008-02-07 00:43:06.000000000 +0100 *************** *** 7613,7616 **** --- 7613,7624 ---- priv->config |= CFG_CUSTOM_MAC; memcpy(priv->mac_addr, addr->sa_data, ETH_ALEN); + + // hack to get rtap device up, since in 2.6.24 kernels the mac of an iface must be set + // setting to mac of the wifi interface + + if (param_rtap_iface) memcpy(priv->prom_net_dev->dev_addr, addr->sa_data, ETH_ALEN); + + // hack end + printk(KERN_INFO "%s: Setting MAC to %s\n", priv->net_dev->name, print_mac(mac, priv->mac_addr)); *************** *** 8343,8346 **** --- 8351,8364 ---- priv->prom_net_dev->hard_start_xmit = ipw_prom_hard_start_xmit; + // ToDo: find real mac here + + // Hack to get rtap device up, since in 2.6.24 kernels the mac of an iface must be set + // Setting to a dummy mac since I don't know where to get the real one. + // Since no packets are being sent to this interface, this is not really important. + + strcpy(priv->prom_net_dev->dev_addr,"0018DE95031A"); + + // hack end + rc = register_netdev(priv->prom_net_dev); if (rc) {
Hi,HecHacker1 wrote:I have this same problem, but for ipw2200. Is there a way to set the ethernet address to allow rtap0 to work?loeb-it wrote:When trying to bring up the rtap interface it does not work:
galadriel mithrandir # ifconfig rtap0 up
SIOCSIFFLAGS: Das Argument ist ungültig
This occurs with ipwraw driver and also with ipw3945 driver, so it seems to be a more general issue.
It also worked with kamikaze-sources before.
Anyone else tried?
Addon:
------------------------------------------------------
In 2.6.24 kernels an interface can only be brought up with a mac address set. Created patches to fix this for ipw3945 and ipwraw drivers.
ipw3945-2.6.24-rtap_up.patch:Code: Select all
*** linux_bak/drivers/net/wireless/ipw3945.c 2008-02-06 19:20:41.000000000 +0100 --- linux/drivers/net/wireless/ipw3945.c 2008-02-07 00:43:10.000000000 +0100 *************** *** 15131,15134 **** --- 15131,15142 ---- priv->config |= CFG_CUSTOM_MAC; memcpy(priv->mac_addr, addr->sa_data, ETH_ALEN); + + // hack to get rtap device up, since in 2.6.24 kernels the mac of an iface must be set + // setting to mac of the wifi interface + + if (rtap_iface) memcpy(priv->prom_net_dev->dev_addr, addr->sa_data, ETH_ALEN); + + // hack end + printk(KERN_INFO "%s: Setting MAC to %s\n", priv->net_dev->name, print_mac(mac, priv->mac_addr)); *************** *** 16284,16287 **** --- 16292,16305 ---- priv->prom_priv->ieee->iw_mode = IW_MODE_MONITOR; + // ToDo: find real mac here + + // Hack to get rtap device up, since in 2.6.24 kernels the mac of an iface must be set + // Setting to a dummy mac since I don't know where to get the real one. + // Since no packets are being sent to this interface, this is not really important. + + strcpy(priv->prom_net_dev->dev_addr,"0018DE95031A"); + + // hack end + rc = register_netdev(priv->prom_net_dev); if (rc) {
ipwraw-2.6.24-rtap_up.patch:Code: Select all
*** linux_bak/drivers/net/wireless/ipwraw.c 2008-02-06 23:41:16.000000000 +0100 --- linux/drivers/net/wireless/ipwraw.c 2008-02-07 00:43:06.000000000 +0100 *************** *** 7613,7616 **** --- 7613,7624 ---- priv->config |= CFG_CUSTOM_MAC; memcpy(priv->mac_addr, addr->sa_data, ETH_ALEN); + + // hack to get rtap device up, since in 2.6.24 kernels the mac of an iface must be set + // setting to mac of the wifi interface + + if (param_rtap_iface) memcpy(priv->prom_net_dev->dev_addr, addr->sa_data, ETH_ALEN); + + // hack end + printk(KERN_INFO "%s: Setting MAC to %s\n", priv->net_dev->name, print_mac(mac, priv->mac_addr)); *************** *** 8343,8346 **** --- 8351,8364 ---- priv->prom_net_dev->hard_start_xmit = ipw_prom_hard_start_xmit; + // ToDo: find real mac here + + // Hack to get rtap device up, since in 2.6.24 kernels the mac of an iface must be set + // Setting to a dummy mac since I don't know where to get the real one. + // Since no packets are being sent to this interface, this is not really important. + + strcpy(priv->prom_net_dev->dev_addr,"0018DE95031A"); + + // hack end + rc = register_netdev(priv->prom_net_dev); if (rc) {
Fixed in latest master-devel. It includes last fix found on lkml.Civil wrote:http://bugzilla.kernel.org/show_bug.cgi?id=9924
Have it been fixed?
Happens with vanilla driver too?HecHacker1 wrote:I have this same problem, but for ipw2200. Is there a way to set the ethernet address to allow rtap0 to work?
Code: Select all
--- fs/ext4/super.c.orig 2008-02-09 19:39:11.000000000 +0100
+++ fs/ext4/super.c 2008-02-09 19:39:37.000000000 +0100
@@ -3357,7 +3357,7 @@
static struct file_system_type ext4dev_fs_type = {
.owner = THIS_MODULE,
- .name = "ext4dev",
+ .name = "ext4",
.get_sb = ext4_get_sb,
.kill_sb = kill_block_super,
.fs_flags = FS_REQUIRES_DEV,

Erm... no. Best way is using latest master-develkernelOfTruth wrote:Waninkoko, just a short question on that local root exploit:
http://it.slashdot.org/it/08/02/10/2011257.shtml
disabling kvm [*] Virtualization / KVM
should be enough to be immune to it, right ?

I think I need to reclone zen-sources (conflicted merge ftw !git clone --reference /path/to/your/linux-2.6.git/incarnation mirror_URL
Code: Select all
git clone --reference /usr/src/sources/linux-2.6/ git://repo.or.cz/linux-2.6/zen-sources.git
CC [M] drivers/net/wireless/rtl8187_dev.o
CC [M] drivers/net/wireless/rtl8187_rtl8225.o
drivers/net/wireless/rtl8187_rtl8225.c: In function ‘rtl8225_rf_set_tx_power’:
drivers/net/wireless/rtl8187_rtl8225.c:286: error: ‘struct ieee80211_channel’ has no member named ‘val’
drivers/net/wireless/rtl8187_rtl8225.c:287: error: ‘struct ieee80211_channel’ has no member named ‘val’
drivers/net/wireless/rtl8187_rtl8225.c: In function ‘rtl8225z2_rf_set_tx_power’:
drivers/net/wireless/rtl8187_rtl8225.c:503: error: ‘struct ieee80211_channel’ has no member named ‘val’
drivers/net/wireless/rtl8187_rtl8225.c:504: error: ‘struct ieee80211_channel’ has no member named ‘val’
drivers/net/wireless/rtl8187_rtl8225.c: At top level:
drivers/net/wireless/rtl8187_rtl8225.c:779: error: stray ‘\361’ in program
drivers/net/wireless/rtl8187_rtl8225.c:779:3: warning: no newline at end of file
drivers/net/wireless/rtl8187_rtl8225.c:779: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ at end of input
make[3]: *** [drivers/net/wireless/rtl8187_rtl8225.o] Error 1
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
Haven't tried, buit I think so, since the change, that you can't brin up an interface only if it has got a mac address set afaik was introduced with 2.6.24. Thus this should not be limited to zen-sources. I already posted it to the ipw2200 mailing list when posting the patches to the zen-sources thread.Waninkoko wrote:Happens with vanilla driver too?HecHacker1 wrote:I have this same problem, but for ipw2200. Is there a way to set the ethernet address to allow rtap0 to work?
PD: I have pushed a "proper" fix for ipw3945 and ipwraw. Later I'll do the same with ipw2200.

I can offer bandwidth, I have 11TB per month of transfer with dreamhost. According to this article setting up a git repository should be possible on their servers:rmh3093 wrote:Ok so all of our hosting attempts have sucked.... I am going to register zen-sources on sourceforge

I haven't tried vanilla in a long time... but if you want I can. Apparently I just need to set the ethernet address for my radio tap interface due to changes in 2.6.24 (although I am sure there were 2.6.23 kernels with the same problem, I just haven't complained about it).Waninkoko wrote:Happens with vanilla driver too?HecHacker1 wrote:I have this same problem, but for ipw2200. Is there a way to set the ethernet address to allow rtap0 to work?
PD: I have pushed a "proper" fix for ipw3945 and ipwraw. Later I'll do the same with ipw2200.
I compiled snd_hda_intel as a module and set the model in /etc/modules.d/alsatermite wrote:There's a bug with intel hda audio and alsa that isn't fixed yet. I have the same problem: can't change volumes...
Code: Select all
options snd-hda-intel model=lg
With iwl3945 driver I also cannot associate with (at least one) WEP network. The netwerks qou tried were WEP or WPA?jaclar wrote:Just compiled the kernel and iwlwifi with iwl4965 isn't able to associate with my accesspoint anymore. Get a "time out" error. With older kernel iwlwifi works smooth...
That's the reason I created the above patches for. They allow setting of the mac address for the rtap interface and set initially a fixed one. Since I didn't find out how to get the real mac address of the card I just set a fixed one...HecHacker1 wrote:I haven't tried vanilla in a long time... but if you want I can. Apparently I just need to set the ethernet address for my radio tap interface due to changes in 2.6.24 (although I am sure there were 2.6.23 kernels with the same problem, I just haven't complained about it).Waninkoko wrote:Happens with vanilla driver too?HecHacker1 wrote:I have this same problem, but for ipw2200. Is there a way to set the ethernet address to allow rtap0 to work?
PD: I have pushed a "proper" fix for ipw3945 and ipwraw. Later I'll do the same with ipw2200.
Maybe iwconfig can set the address... checking now.
EDIT: nope. iwconfig doesn't have a MAC address option. ifconfig does, but I get a "SIOCSIFFLAGS: Invalid argument" error and also a Unknown host error. ifconfig instructions are a bit unclear though.
I was until recently quite happy with the iwlwifi driver, worked like a charm for me. But what is this rtap interface?loeb-it wrote: With iwl3945 driver I also cannot associate with (at least one) WEP network. The netwerks qou tried were WEP or WPA?
For me that's (and the rtap interface) the reason for staying with the ipw driver...