Macintosh OSX, 802.1x and PEAP

I'm preparing to implement 802.1x port authentication for both wired and wireless connections. The authentication server is Windows 2003 IAS. In the test environment, Windows XP clients can connect fine, but I'm not sure how to configure this for Mac OSX workstations (10.4.6). Has anyone successfully done this? If so could you please explain the proceedure, or direct me to documentation that explains the process?

Assuming you're using NAC fraework then it's bad news, 802.1x won't work on a Mac. If you use 802.1x and L2IP in combination then wired Macs will work but wireless Macs will not. The reason is that the Cisco CTA for the Mac communicates with using EAP over UDP and this transport is not available when using 802.1x alone or over a wireless link with 802.1x or L2IP. The only way of catering for all client types at once (Windows wired and wireless, Mac wired and wireless) is L3IP.
The NAC Appliance "will" support wireless Macs in a future release but (I believe) doesn't at the moment.

Similar Messages

  • 802.1x and PEAP

    Dear All,
    We are going to use 802.1x PEAP and with MSCHAPv2 for authentication. The problem is we dont have and trusted CA server in our setup.
    So clents will not be able to verifiy the server certificate . Is there way to avoid checking of server side certificate or other solution? and what will be the imapct of avoiding this..
    Regards,
    TS.

    I believe this can be done in Windows by unchecking the "Validate Server  Certificate" setting under the Protected EAP Properties as shown below.
    That said it is recommended and also fairly easy to setup a root CA in their environment.  Please mark correct if this post helps

  • Macintosh clients, 802.1x and NAC.

    I'm prototyping a NAC setup which has to cater for Macintosh clients as well as Windows. I can get the Macs to authenticate via 802.1x (surprisingly easy using the built in software!) but what I can't do is setup a Posture Validation Rule to identify that the client is a Mac and not a Windows machine. I've tried using the Cisco:PA:OS-Version condition set specifying "contains" MAC. I've also tried "contains" 10 but it doesn't work. I think it probably doesn't work as the condition set depends on the CTA being installed on the Mac which it isn't (and it's not an option either).
    EDIT: Anyone tried installing the CTA on a MAC? It's horrific. Extract the files and run the install, OK so far. It then puts the config ini file in a directory no user (not even Admins) has permissions to so you can't modify it and BOY do you need to modify it!
    Any ideas?

    I'm on the home straight with this one. Essentially to get the CTA to work using the built in 802.1x supplicant on Windows or MacOS you need to run a mix of NAC L2 IP and NAC L2 802.1x. This requires a little extra config on the switch but nothing tragic (it's all in the (NAC Framework Configuration Guide).
    The reason for this is that the CTA requires a network channel to be open so it can run EAP over UDP (EOU) to do posture validation and the 802.1x part of the process gets the machine onto the network so the CTA can do it's stuff.
    With this setup in place and the CTA properly configured (as mentioned previously this is the permissions setup on the Mac created by the CTA install makes this far more difficult than it should be) the process works pretty well, popup messages work, browser launch and URL redirection work. Looks good.
    The fly in the ointment is wireless. The freebie CTA doesn't support it, no way. For a PC the answer is to buy the Cisco Secure Services Client which does support wireless and (I think) run that alongside the CTA (haven't fully worked this one out yet). If you have a wireless Mac, you're stuffed, Simple as that, which from my point of view is a real pain as the customer I'm developing this for wants posture validation for PCs and Macs, wired and wireless.
    Hope this helps someone somewhere avoid a little pain! : )

  • IMac 27" (late 2011), Mountain Lion, Bootcamp, and OSX partition disappearing and refusing to mount

    Hey all,
    I'm putting this as a question in the discussion forms for bootcamp as I'm not sure where else to put it, but I resolved an issue I was having and having spent all of yesterday and the day before reading through this community and some others looking for answers and mostly seeing "hope you have backups, time to format!" (which to me is not always the best answer), I thought I would put it here for search purposes (with all the key words I had to use) in case anyone else has a similar issue.
    My scenario was this:
    2011 27" iMac with Mountain Lion installed and Windows 7 installed on a boot camp partition.
    1) Haven't been in windows in a while, wanted to play some windows only steam games. Load windows 7. All is well. Have fun. Time to reboot into osx.
    2) Reboot using bootcamp toolbar icon.
    3) Wander away from computer. Come back to find windows 7 has loaded again. "That's weird", I think. Reboot again, this time hold down option key to select boot device.
    4) Discover the only options are the Bootcamp partition and the Recovery partition. OSX "Macintosh HD" partition has disappeared. Huh.
    5) Load recovery partition and load disk utility.
    6) Review disk utility to discover the Macintosh HD partition shows up in the list, but won't mount. Run verify and repair tools. Errors are as follows: Invalid node structure, invalid key length, invalid record count, etc etc. Running a repair fails - disk utility advises me to back up and erase the drive and that the partition is unrepairable. No offense disk utility, but I think I'll try a few more options first.
    7) Purchase DiskWarrior on advice of multiple posters in other threads and general online consensus of it being capable of fixing these sorts of errors. Go through process of loading bootable dvd.
    8) Diskwarrior cannot see the Macintosh HD partition. This is bad. Review more threads. Advice is that if diskwarrior can't fix it, hope you have backups and wipe the drive. Likely to be hardware failure. I'm skeptical of hardware failure, because windows is chugging along running fine if I boot into it, and I ran a scan of the windows partition and it came back clean. SMART status is also showing the drive is ok. However, running out of options and starting to lose hope.
    9) Follow advice in this support topic: http://support.apple.com/kb/ts1417?viewlocale=de_de Both safe mode and disk utility aren't options (safe mode won't work without it seeing the partition) so sounds like fsck is the final option.
    10) Start up in Single User Mode (http://support.apple.com/kb/HT1492). Run fsck per instructions. It reports back ok.
    11) Realize fsck is checking the recovery partition, and not my damaged OSX partition. Realize I don't know anything about unix commands and have no idea how to tell fsck to check a different partition.
    12) Learn that I need to find out what the drive id is for the damaged partition. Reboot, load up disk utility, select greyed out "macintosh HD" partition, click info. Write down the id: disk0s2 (likely to be the default for you as well if you have one drive in your imac and a default bootcamp install).
    13) Go back into single user mode and type the following (without quotes): "fsck_hfs -fy /dev/disk0s2"
    14) (Forgot to copy down exactly what it said at this point, but gist of it was that the drive had errors and isnt repairable). Feel like ****, thinking this is unlikely to resolve itself nicely.
    15) With nothing to lose, try to force fsck to rebuild the catalog - "fsck_hfs -rc -d /dev/disk0s2" I found this syntax on some forums and can't find the thread again. I have no idea what the -rc and -d do that -fy don't, but if someone can let me know, that'd be cool. Either way, this resulted in something actually happening. Tells me it is "rebuilding catalogue b-tree". Still, finishes with a bunch of errors about improperly linked files, more node errors, etc etc.
    16) Retry "fsck_hfs -fy /dev/disk0s2". It seems to be doing stuff now, even though there are lots of errors. Continue to re-run fsck using this syntax. Probably ran it 10-15 times. Takes over an hour. Finally, minimal errors being reported.
    17) Realize that perhaps I should try Diskwarrior again now, since I've managed to do soemthing to the partition with fsck.
    18) Run Diskwarrior from bootable DVD. Success! It now sees the damaged partition. Reports that it has a bunch of damaged crtitical files, and needs to be repaired, but hey, at least it can see it.
    19) Let Diskwarrior do its thing, and reboot.
    20) Boot from repaired OSX partition. Rejoice. Immediately plug back in the timemachine drive you foolishly unplugged to take away over the holidays and neglected to plug back in before you had commenced work on stuff you didnt want to lose through formatting, which is why you are so desperate to recover files rather than wiping and restoring from time machine backups and avoiding this whole mess.
    TL;DR - If Disk Utility and DriveWarrior fail you, try running fsck (using different syntax that apple recommends) as many times as it takes to get the partition to a stage where diskwarrior can see it. All advice I saw for similar questions was to erase, reinstall OSX, and restore from time machine backup. For those of you who are foolish like me and had files that werent time machine'd, or those who operate without, maybe try this.
    Hope this helps!

    What -rc & -d do.
    From: The fsck_hfs manual page.
    https://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages /man8/fsck_hfs.8.html
    -d      Display debugging information.  This option may provide useful information when fsck_hfs cannot repair a damaged file system.
    -r      Rebuild the catalog btree.  This is synonymous with -Rc.
    -R flags Rebuilds the requested btree.  The following flags are supported:
                             a       Attribute btree
                             c       Catalog btree
                             e       Extents overflow btree
    I had the same problem as you but unfortunately "fsck_hfs -rc -d /dev/disk0s2" is failing saying: "The volume   could not be verified completely." I believe it's supposed to be telling me the partition's name (normally "Macintosh HD") between 'volume' and 'could' because there's 3 spaces in between the words.
    "fsck_hfs -fy /dev/disk0s2" is failing with the same error.
    I tried "fsck_hfs -r -d /dev/disk0s2" since the c appears redundant with a lowercase R. and it again says it cannot be verified completely and adds "volume check failed with error 7". Which unfortunately is not documented on the fsck_hfs man page!
    Unfortunately for me, Diskwarrior still can't see my busted Mac OS partition.

  • 802.1x EAP-PEAP over Ethernet need help !!!

    I am trying to get wired 802.1x EAP-PEAP to work and after spending about 8 hours
    troubleshooting this, I am not sure what else to do.  Need help.  Here
    is the scenario:
    - Cisco Catalyst 3350 switch running IOS versionc3550-ipservicesk9-mz.122-44.SE6.bin,
    - Steelbelted/JUniper Radius Server version 6.1.6 on a windows 2003 server
    with IP address of 129.174.2.7.  This device is connected to the same switch above.
    Firewall is OFF on the server, allow ALL,
    - Windows 2003 Enterprise Server supplicant with the latest Service pack and patches.  Again,
    Firewall is OFF on the server, allow ALL.  Juniper has verified the configuration settings
    on the Supplicant machine.  The supplicant has a static IP address of 129.174.2.15, same subnet
    as the radius server, I just want enable EAP-PEAP so that user is forced to authenticate before
    the port is activate to be "hot".
    - Juniper TAC has verified the configuration on the Steelbelted radius for eap-peap
    and that everything is looking fine,
    I have verified that the switch can communicate fine with the radius server.
    - Configuration on the switch for 802.1x:
    aaa new-model
    aaa authentication dot1x default group radius
    radius-server host 129.174.2.7 auth-port 1812 acct-port 1813 key 123456
    interface FastEthernet0/39
      description windows 2003 Supplicant
      switchport access vlan 401
      switchport mode access
      dot1x port-control auto
      no spanning-tree portfast (does not matter if this is enable or disable)
    lab-sw-1#
    .May 20 07:52:47.334: dot1x-packet:Received an EAP request packet from EAP for mac 0000.0000.0000
    .May 20 07:52:47.338: dot1x-packet:dot1x_mgr_send_eapol :EAP code: 0x1  id: 0x2  length: 0x0005 type: 0x1  data:
    .May 20 07:52:47.338: EAPOL pak dump Tx
    .May 20 07:52:47.338: EAPOL Version: 0x2  type: 0x0  length: 0x0005
    .May 20 07:52:47.338: EAP code: 0x1  id: 0x2  length: 0x0005 type: 0x1
    .May 20 07:52:47.338: dot1x-packet:dot1x_txReq: EAPOL packet sent out for the default authenticator
    lab-sw-1#
    lab-sw-1#sh dot1x interface f0/39
    Dot1x Info for FastEthernet0/39
    PAE                       = AUTHENTICATOR
    PortControl               = AUTO
    ControlDirection          = Both
    HostMode                  = SINGLE_HOST
    Violation Mode            = PROTECT
    ReAuthentication          = Disabled
    QuietPeriod               = 60
    ServerTimeout             = 30
    SuppTimeout               = 30
    ReAuthPeriod              = 3600 (Locally configured)
    ReAuthMax                 = 2
    MaxReq                    = 2
    TxPeriod                  = 30
    RateLimitPeriod           = 0
    lab-sw-1#
    I am at a complete lost here.  don't know what else to do.  Someone with expertise in this realm please
    help me how to make this work.
    Many thanks in advance,

    #1:  dot1x system-auth-control is already in the switch configuration
    #2:  Not sure if you're already aware, the minute I entered "dot1x port-control auto", the command "dot1x pae authenticator" automatically appears on the interface configuration
    The case is being worked on by Cisco TAC.  One of the issues is the windows 2003 server supplicant refuses to work.  Windows XP supplicant uses machine-authentication instead of user-authentication.  Cisco TAC is looking into this issue.

  • 802.1x with PEAP fails on Unified

    We have an issue with a Fujitsu Siemens Amilo Laptop. It uses 802.1x with dynamic WEP and PEAP-MSCHAP (MS-IAS), Verisign Imported Certificate. It works fine in a Autonomous environment but fails in Unified environment. Other laptops work fine in both environments with the same setup. Debug on the WiSM shows the EAP request identity/start message send to the client. But there's no answer from the client; Reached Max EAP-Identity Request retries (21) for STA
    Any help is welcome!

    If the issue is with the certain brand of laptop, look at the wireless card firmware. What type of card are in these laptops? What configuration has changed between the Autonomous and the LWAPP (basic settings). What does the log show on the IAS server?

  • 802.1x EAP-PEAP - Radius Question

    We're going to be deploying a wireless solution to a customer at some point shortly. So far we have a WLC 2500 Series,
    1140 LAPs, and a 2960-S switch. We're going to have Windows 7, iPhone, iPAD devices, and I was going to implement
    802.1x EAP-PEAP. I'm going to need a RADIUS server, but I was just wondering is there a cheaper solution than just
    getting a Cisco ACS to run a simple RADIUS server which is all I need.
    Also, when the Supplicant sends its NAI in a EAP-ResponseIdentity message, what exactly is this username
    and how does it differ from the username you provide after the secure TLS tunnel has been configured.                  

    Hey John,
    Yes, in fact its all about feeling comfortable. So here is a video showing LOCAL PEAP on a WLC.
    http://www.youtube.com/watch?v=YIxG4OEfwtY
    The 2000 is becuase there is a database limit this includes MACS, LOCAL ACCOUNTS and AP MACs for AP policy. The mac is 2048 .. Here I blogged about this ..
    http://www.my80211.com/cisco-wlc-cli-commands/2009/12/27/configure-local-mac-authentication-on-cisco-wlcs.html
    So yes it sounds right and you should be good.
    Hope this makes you feel a little bit better with your direction. If this helps can you mark the question as answered ?
    Thanks John!
    "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
    ‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

  • Nokia E51 with 802.1x / EAP-PEAP & EAP-MSCHAPv2 pr...

    Hello,
    I'm trying to connect my phone to a Wireless AP (Cisco AP1130) using 802.1x, EPA-PEAP & EAP-MSCHAPv2 authentication.
    The RADIUS SERVER is M$ IAS.
    Authentication is working with a laptop, but it is not with my phone
    The only difference during the authentication process on the AP is that during Phase 1 my laptop is sending REALM\Username while my phone is sending Username@REALM.
    Does somebody know what should I change in my phone's configuration to make it work ?
    Thanks,
    Ceux qui aiment marcher en rangs sur une musique :
    ce ne peut être que par erreur qu'ils ont reçu un cerveau,
    une moelle épinière leur suffirait amplement. -- Albert Einstein

    Hi,
    Sorry for the late answer since I was "out of the office" for a while
    So here is the process to get the certificate.
    Log in to you IAS Server.
    Open the IAS Service Application.
    Go to "Remote Access Policies".
    Choose the policy that apply to "Wireless Connection"
    Click "Edit Profile" button.
    Choose "Authentication" Tab.
    Click "EAP Methods"
    Choose "Protected EAP (PEAP)" Entry & click "Edit" Button.
    The Next Window will show you the Certificate Issuer Name & Expiration Date.
    Then, click "Start" Button.
    Choose "Run".
    Type "mmc" in the "Run" box.
    Click "File" & Choose "Add/Remove Snap-In".
    Click "Add" Button.
    Choose "Certificates" entry, click "Add" Button & Choose "My User Account" in the "Certificates Snap-In" Window & click Finnish.
    Click "Close" & "OK" Button.
    Expand the "Certificates - Current User" Entry" & "Intermediate Certification Authorities" & Select "Certificate".
    The left window will show you a list of certificate. One of them should have the same name as the one in the "Certificate Issuer" Entry of the IAS Service Application.
    "Right click" on the certificate, choose "All Tasks", the "Export".
    In the new window, click "Next" Button.
    Choose "DER Encoded Binary X.509 (.cer) entry & click "Next" Button.
    Choose a suitable location.
    Click "Next" Button & "Finnish" Button.
    Certificate is now exported.
    You have to install it on your Phone now.
    The most simple way is to copy the certicate on a Web Server and access it with your phone.
    Hope that Help, if you did not already succeed.
    Ceux qui aiment marcher en rangs sur une musique :
    ce ne peut être que par erreur qu'ils ont reçu un cerveau,
    une moelle épinière leur suffirait amplement. -- Albert Einstein

  • 802.1x and the iPhone

    So I don't think this is possible right now to connect to an 802.1x network from the iPhone. I am posting for 2 reasons.
    1. Anybody figure out a way to do this?
    or if not...
    2. Apple, we really need this in a software update...

    802.1X [upper case X] is a network access mechanism or authentication protocol used with 802.11x [lower case x] wireless networking standards, such as…
    • 802.11a
    • 802.11b
    • 802.11g
    • 802.11n
    …and so on. It has been natively supportive in Mac OS X for Macintosh desktop and portable platforms since the release of OS X 10.3, but is not visible typically unless you launch the Internet Connect application to add and configure it.
    A general discussion of 802.1X can be found in this Wikipedia article.
    The oft confused 802.11x is nothing more than a generic representation of the group of wireless networking standards listed above.
    This really is a very substantial issue for many academic and business users, as access to their networks is typically controlled by an upstream Radius server and without support for configuring an 802.1X interface, they cannot connect their networks as recognized, authorized users.

  • OS X could not be installed on your computer. The OS X upgrade couldnt be started because the disk Macintosh HD is damaged and cant be repaired. After your computer restart, back up your data, erase your disk, and try installing again.

    OS X could not be installed on your computer. The OS X upgrade couldnt be started because the disk Macintosh HD is damaged and cant be repaired. After your computer restart, back up your data, erase your disk, and try installing again.

    Beware!  When you initialize your boot disk be sure that you specify "Journaled" and not "Case-sensitive, Journaled". Previous OSX installers would check this and give an error message. Mavericks does NOT! If you install using "Case-sensitive" many apps will not work.

  • OSX 10.10 and HP Officejet Pro 8500A not working

    I updated my operating system to Yosemite OSX 10.10 and now my printer will not print or scan.  When the click on the HP Utility it can not find the printer.  I looked in Finder but folder for HP is gone.  I went on HP's website but there are not drivers for version 10.10.  I tried to download a driver for previous version of OS X but it says not compatible.
    How do I get my printer back up on-line?
    Thanks for your help.

    The HP Printer Drivers v3.0 for OS X should help, or Software Update.
    It's shown as supported here: OS X: Printer and scanner software available for download

  • HT1338 I just installed OSX snow leapord and just want to be able to use icloud.  I up--graded my old macbook to 2 gigs and still can't get it to download icloud .  would go to osx mountain lion but can't do that either.  What do I have to do???

    I want to use icloud to sync w/my new apple tv.  bought osx snow leopard and installed it plus upgraded to 2 gigs memory for my
    old (2007) macbook.  still won't work. I need to get to at least osx 10.7.4 or to osx mountain lion.  Tried everything and can't get there.
    I'm not a computer whiz...quite a novice.  so, if you can help; please speak in layman language....ha   Thanks

    iCloud requires 10.7.2 or later.
    After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store. Access to the App Store enables you to download Mountain Lion if your computer meets the requirements.
    Upgrading to Lion
    If your computer does not meet the requirements to install Mountain Lion, it may still meet the requirements to install Lion.
    You can purchase Lion by contacting Customer Service: Contacting Apple for support and service - this includes international calling numbers. The cost is $19.99 (as it was before) plus tax.  It's a download. You will get an email containing a redemption code that you then use at the Mac App Store to download Lion. Save a copy of that installer to your Downloads folder because the installer deletes itself at the end of the installation.
         Lion System Requirements
           1. Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7,
               or Xeon processor
           2. 2GB of memory
           3. OS X v10.6.6 or later (v10.6.8 recommended)
           4. 7GB of available space
           5. Some features require an Apple ID; terms apply.

  • HT1338 Presently running mac osx 10.5.8. Recent Firefox update says it no longer works with osx 10.5 and it's no longer supported by apple. Any suggestins?

    Presently running mac osx 10.5.8. Recent Firefox update says it no longer works with osx 10.5 and it's no longer supported by apple. Any suggestins?

    Use an earlier version of Firefox, use Safari, or upgrade to a later version of OS X. Any Intel Mac can run Snow Leopard.
    Latest version of Safari for Leopard: http://support.apple.com/kb/DL1422
    Information for Firefox: http://support.mozilla.org/en-US/kb/firefox-no-longer-works-mac-os-10-4-or-power pc
    http://support.mozilla.org/en-US/kb/firefox-no-longer-works-mac-os-x-10-5

  • Macintosh HD is damaged and can't be repaired

    Hi,
    The other day i decided to purchase and download Mac OS X Lion off from the AppStore for my iMac 21"inch, however after i sucsessfully downloaded the OS it began to Installing, then when it passes 5 minutes of installing the window displays a word saying "Macintosh HD is damaged and can't be repaired" I AM PANICKING, it told me to restart the iMac so i follow the instruction then when i do restart the my iMac the apple logo goes flashing crazy with a some sort of "Your hard disk is screwed" sign. What should i do?! im thinking of re-installing the mac os x snow leopard again. But i dont no im going crazy this is a $1000 or more computer that im dealing here with . PLEASE IF SOMEBODY HAVE THIS SAME PROBLEM LETS FIND A SOLUTION TO THIS! :'(

    Hei guys thanks for the fast replies and tips, it finally worked! i decided to clean everything up by wiping all of my data which means 'start fresh' and re-install OS X Leopard. yes the OS X Lion works superb on my iMac, guess this is not an HDD failure or 'physic' damage. So much thanks!
    NOTE: Oh for those of you who are having this same problem as i do, keep in mind dont panic to much and act crazy with your Apple imac's or macbook's, ease up and do as i say:
    when it tells you,  "Macintosh HD is damaged and can't be repaired" do as it say, restart your device, once it is restarted quickly insert your Snow Leopard Installation Disc and it will take you to the 'installation screen' once your there you will see 'utility' up in the bar click that and click disc utility, once there click on your Macintosh HD and click on 'Verify Disc' & 'Repair Disk'. Then finally, restart your device again, If it runs smoothly then re-install OS X Lion off from the App Store (Again, and yes im not joking). If it doesnt run smoothly, re-install your Snow Leopard OS then install OS X Lion from the App Store.
    Cheers everybody! Thanks for the fast and very Helpful replies!

  • Cisco Systems vs "CSIRO" 802.11a and 802.11g infringed upon the '069 patent

    Hi,
    any news about Cisco Systems and the "CSIRO" 802.11a and 802.11g infringed upon the '069 patent ?
    http://www.buffalotech.com/products/wireless/
    Dear Customer
    As you may be aware, Commonwealth Scientific and Industrial Research Organisation ("CSIRO") sued Buffalo, Inc. and Buffalo Technology (USA), Inc. ("Buffalo"), for alleged infringement of United States Patent No. 5,487,069 ("the '069 patent"). Subsequently, CSIRO also asserted its patent against the entire wireless LAN industry, including, Microsoft, Intel, Accton, SMC and Netgear.
    In it's lawsuit against Buffalo, CSIRO claimed certain Buffalo wireless networking products compliant with IEEE standards 802.11a and 802.11g infringed upon the '069 patent. Buffalo believed at that time and continues to believe that there are no grounds for CSIRO's allegations of infringement. The United States district court, however, found Buffalo to infringe the '069 patent and enjoined the importation and sale of Buffalo's IEEE 802.11a and 802.11g compliant products.
    CSIRO's lawsuits are against the entire wireless LAN industry and could affect the supply of wireless LAN products by any manufacturer, not just Buffalo. The entire industry is resisting CSIRO's attempts to enjoin the sale of wireless LAN products. Recently, Microsoft, 3COM Corporation, SMC Networks, Accton Technology Corporation, Intel, Atheros Communications, Belkin International, Dell, Hewlett-Packard, Nortel Networks, Nvidia Corporation, Oracle Corporation, SAP AG, Yahoo, Nokia, and the Consumer Electronics Association filed briefs in support of Buffalo's position that injunctive relief is inappropriate in this case.
    During the period of time that the injunction is in effect (10/1/2007), Buffalo cannot offer for sale, sell, import, or use its IEEE 802.11a and 802.11g compliant products in the United States. A list of the products covered by the injunction is attached here . The injunction does not prohibit sales of pre-existing inventories of products by Buffalo's customers. In addition, Buffalo has secured CSIRO's agreement to permit the replacement of defective products under warranty. None of Buffalo's other products are currently affected by this injunction.
    While Buffalo believes that it will be successful in reversing the district court's decision and will obtain a stay of the injunction pending a decision on the merits, the Court of Appeals has not yet issued a decision. Should the Court of Appeals issue a decision staying the injunction, you will be promptly notified. After the stay is issued or a favorable decision on the merits is obtained, Buffalo will be able to resume the supply of IEEE 802.11a and 802.11g products
    Please rest assured that Buffalo continues to stand behind their products and will continue to support all of our loyal customers as it relates to product warranties, technical support and the like without interruption.

    I suspect after reading the patent and the litigation that you mentioned above, that the US District Court decision will be reversed as the patent appears to be very vague in its contsruction and verbage. Furthermore, the intent to hold the IEEE hostage on the ratification of 802.11n will not bode well in the court's eyes. If in fact the case is reversed, I believe that the members of CSIRO will be in danger of lost profits litigation from Buffalo. Stay tuned to this bat channel.

Maybe you are looking for