Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About moseschrist

  • Rank
    First Hebrew Hackintosh :)
  • Birthday 06/09/1986

Contact Methods

  • MSN
  • Website URL
  • ICQ

Profile Information

  • Gender
  • Location
    Israel, Haifa
  1. Intel Wireless driver

    i understood that i the encryption functions are in ieee80211_xmit() now there is a value called encrypt there which tells the function whether to try and encrypt or not. if the driver doesn't try to encrypt it automaticly goes to ieee80211_net_hard_start_xmit() which tries to send packets. if the driver tries to encrypt it first goes through all those tests and such to encrypt the packet and only then goes to net_hard_start_xmit(). the weird thing is that it crashes when we try to encrypt with the "excuse" of not being connected to a network [or at least that is the last line i see on the log]. but i don't see this error when i don't try to encrypt the packet. and it doesn't even crash. now, why is that weird you ask ? because in both times were not associated !!! so why it crashes is beyond me
  2. Intel Wireless driver

    i'm stuck on iwi2200 wep. i think i finished with rx functions with wep encryption. now the tx/xmit is left. i uploaded a driver source to the download page, i can't up to SVN for some reason... [it doesn't like my password] just a heads up there is no interface for entering a password yet, so you have to do it by hand in the file ieee80211_crypt_wep.c the last function there (init wep) allows you the enter the key. now this is important ! when creating a wep key you put in a phrase from which the key will be created you have to use 5 char length phrase to create a 64bit key. i used for my network 00000 as the key, but you can try your own. also, i use this site to create the key: http://www.andrewscompanies.com/tools/wep.asp and last but not least when you enter your "key" in the driver code you don't put in the created key, but the original phrase from which the key was created. and finally: this is not for all the users, you can' connect to wep protected networks yet, it can only decode recieved packets but not send coded packets so it's useless for you unless you wish to develop the code further. as i said in the beginning, you need to implement in tx a call for encrypt functions. see ieee80211_rx(), you can see there how it works on recieved packets.
  3. Intel Wireless driver

    about encryption: the error doesn't show if i don't decrypt the packet. only after. so what i'm doing is just writing the correct flag on the mbuf and it works [i think] anyways my problem now is with encrypt [i think] i have some more work to do on the encryption while decryption is almost done [i think] about nsGUI: i wanted to do a perferred network list for a long time... if no one implements this until i finish the WEP thingy i'll get it done... and for the invalid network, i didn't quite understood what you meant... also i will implement a way to send the key from nsGUI to the driver. what we will do is to send a new data structure, it will have two values: 1. network. 2. WEP data structure [can easily be extended to other encryptions when they are done]. this will have a new "number" in nsGUI kext control functions.
  4. Intel Wireless driver

    the following is a part of my log: Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: public + private key: ~]?00000‘I^C Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: k: 0, icv match Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: k: 1, icv match Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: k: 2, icv match Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: k: 3, icv match Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: E this packet dont have MBUF_PKTHDR do you know what it means ? it means that finally the decryption worked ! this whole wep thing is the most annoying encryption ever invented but hey ! it worked ! now i have to fix this little annoying error you see at the end a pray... so guys keep the faith, soon we WILL have encryption ! [even if it is the simplest one, but it's a start !]
  5. Intel Wireless driver

    jalavoui, i don't know if we should let users download the dmg from the svn, this way we can't upload unstable and test versions of already working drivers. for example, now i'm working on the whole wep encryption and if i want to upload a WIP i can't because then the users will download a WIP and that won't be nice for them since it crashes a lot !!! so i believe that for the iwi2200 driver we should put a "stable" version link and a WIP [unstable, SVN] version link. for the others since they arn't working at the moment there should be only an SVN link. anyways... i'm kinda stuck on this whole thing... i'm having a problem finding the public key inside the packet, this is since there should be a call for (mbuf_pullup() ) before the decryption, but i have no what values should i send so i'm pretty much guessing and for now i think i managed to reach 2/3 of the public key [hurray for me !] which may sound great but it's basicly 2 chars out of 3... while the rest should be inserted by the user. the good news are that i believe i found a way to insert the key, but first we need to make sure crypt/decrypt works. as usual, ideas,thoughts, sexual offers, they are all wellcome
  6. Intel Wireless driver

    funny thing... after adding crypt and decrypt functions to the driver [2200] and trying to associate it gave me an error because the driver wasn't in "privacy mode" so i added a line which tells the driver to move to "privacy mode" when associating with secure networks. surely still we can't associate, but that's not what nsGUI says it tells me i'm associated with the network even if i'm not anyways, it's a bug which will be fixed... but hey, were getting somewhere !
  7. Intel Wireless driver

    i think i have finished working on the ieee80211_crypt_wep.c port... i have added it to the project but still i have no idea how to make it work with the driver. jalavoui, maybe you know ? [or can shed some light on the issue] here is the file... add it to the project and it will compile... ieee80211_crypt_wep.cpp.zip
  8. Intel Wireless driver

    more mbuf "goodness" i'm looking for an equivalent to m_append and can't seem to find it, not even on kpi_mbuf.h the only thing i found is mbuf_prepend. ideas anyone ?
  9. Intel Wireless driver

    no, i'm not working on nsGUI now, i'm porting the ieee80211 linux lib with help of the ieee802111 bsd lib. almost done working on the packet encryption function. BTW, it's great to work again on this driver...
  10. Intel Wireless driver

    jalavoui, i'm having a slight trouble with the wep encryption implementation. i'm stuck on this line: data_len = m->m_pkthdr.len - off; [taken from here: http://fxr.watson.org/fxr/source/net80211/...11_crypto_wep.c line 334] where m is of type mbuf_t. now, this doesn't work on our code since one of the inclusion has a forward decleration of mbuf_t and so i can't access anyting directly. so my question is this, is there another way to get the data length inside the buffer ? or even better, is there another way to get the packet header from the buffer ?
  11. Intel Wireless driver

    hello there... just wanted to report back from the furious finals here in my UNI, two weeks from now and i'll be back in trying to do whatever i can to implement secure networks [WEP first] in our lovely lovely iwi2200 driver... already did some research in the BSD ieee80211 generic driver for some implementation tips... hopefully some of the stuff there will be more useful than the linux drivers since the BSD ones use the mbuf structure for data packets and this is what we use in our driver while the linux ones use the skb_buff structure in their packets.... so just wanted you guys to know, i'm not dead [yet] and i'll be back in two weeks...
  12. Intel Wireless driver

    hey guys, i just dropped by to explain why i haven't been here for so long... we have entered the finals period here in my university, and i was swamped by assignment and my job so i havn't had time to look at the code, let alone do any work... i'll be back hopefully next month, and and at worst case, by the end of august i'm here full power see you soon guys...
  13. Intel Wireless driver

    emymrin: the create network option should be activated when the card is in off mode and in adhoc mode. about the ip configuration: that problem occurs even on xp, i never managed to connect to an adhoc network without having to wait forever for ip configuration to end. i believe manually setting the ip is the only way to quicken the process.
  14. Intel Wireless driver

    guys, just wanted to let you know, my laptop suffered from a power surge which killed my HD so i just finished re-installing osx86 and windows, now i have to redownload xcode which will only happen tomorrow since my d/l speeds here are too slow and in my university i can d/l the whole xcode dmg in 1min...
  15. Intel Wireless driver

    this could be a problem with the installer, i'll check that out... can you tell me if the file iwi2200.kext exists in your /System/Library/Extensions/ folder ?