AEBS 802.11n, Crashing while using bittorrent

I have a problem with my new AEBS. The AEBS n Giga is connected via ethernet to my G5. About 2 or 3 times a day my entire network will go down. The AEBS light goes off completely and the Airport Utility cannot find it. The only way to get it back is to power cycle it. I called Apple and was told this is a "known issue" and that I would just have to wait for a firmware update to correct the problem. I'm not happy.... I plan on calling and insisting on a replacement as this problem doesn't seem to happen with EVERY unit. My friend bought one the same day and store that I did and he has no problems.

Update:

Apple exchanged it and I got a new one today. I plugged it in only to have the exact same problems!!!! The "geniius' at the bar said he had the same problem and it was his modem. Whatever.... Mine's going on ebay today. Too bad, cause when it worked it was great!

nescio - YOU ROCK!!! nice job of troubleshooting. Switching to local solved it for me too.

cheers

Hello!

I am having this green led / AEBS disappears problem also. I got another AEBS from service, same problem. Yes, I use Azureus, but now I am not sure has AEBS problems also without it. But with Azureus I got often this lockup.

*Now I ask did the IPv6 setting finally solve this. Some of you has now had this setting about 10 days. Have you seen this problem after change?*

Thank you.
ps. Finland's service does not even try to solve this. They just give another AEBS...

nescio - YOU ROCK!!! nice job of troubleshooting. Switching to IPv6 to "local" solved it for me too!!!! 24 hours and still going. I can still port forward manually.

cheers

If only it was that simple for me. Anyone know what's the warranty on this? Maybe i can exchange it for a new one..

Set up the base station as nescio posted (i.e. changing the IPv6 setting to "Local") and also set up the DHCP reservation as eMi posted and now my Base station is working as it should be. Thanks to the both of them for the info. It saved me a lot of time and, I am guessing, a lot of calls to tech support.

I went to an apple authorized reseller yesterday and asked them about the freezing problem and they told me that the only solution would be to try different bittorrent clients. I don't know if that's really going to work, but it seems like thats the only think i haven't tried yet.

Anyone think that their ISP, namely Comcast, might have something to do with this?
Check out this article: http://news.yahoo.com/s/ap/20071023/apon_hi_te/comcast_data_discrimination_4;ylt=AuEC9yPdJCZKT3ultbNvtcgE1vAI

Seems that Comcast is doing their best to screw with people's P2P file sharing...

How do you set the DHCP settings. Do I use the same address that I used to port forward Azureus or the router address?

Yes, use the same address as the port is forwarded to.

Could it be your ISP? Have you seen the reports within the past few days: "Comcast has been "caught" blocking BitTorrent traffic in some areas, according to tests performed by the Associated Press. The news organization claims to have confirmed that Comcast is blocking—or at least seriously slowing down—BitTorrent transfers, regardless of whether the content is legal or not."

Also, I had a problem with my APEn losing connections (wouldn't download purchased iTunes TV shows) and discovered it was a conflict with my 2.4GHz cordless phone fighting for the wireless channel. Once I changed the channel from 'automatic' to a specific choice (1 through 11), the problem went away.

Message was edited by: SlippySlope

Wow, this is a common issue. As much as I'd like to believe that my ISP is at fault for my AEBS crashing/lock-ups, I don't think this is a likely outcome from their purported experimentation with traffic shaping/sandvine hardware.

I've disabled the IPv6 tunnel on my AEBS and will report back on the success/failure of that approach ('ve also turned IPv6 adressing off on my Mac; System Prefs -> Network -> TCP/IP -> Configure IPv6). It seems most other people with these same symptoms (AEBS locks up, status light remains green), are having success disabling the IPv6 tunnel feature.

Incidently, the factory AEBS IPv6 configuration makes your firewall vulnerable to incoming traffic over IPv6, so there are security reasons why you might want to change this setting, in addition to the possibility that Apple's IPv6 implementation causes issues with P2P software:

http://arstechnica.com/journals/apple.ars/2007/2/14/7063

Rajesh Sharma wrote:
I haven't had any crashes for weeks. I did have them with my first router and with this one as well, but something I did stopped them - I wish I could say what it was.

Yes, that is what happened to me too - but after a complete re-setup of my AEBS (due to a new DSL connection) I just couldn't rembember all the settings and fooled around until I found the IPv6-fix. That worked for me since then, although I have some occurences that the MBP takes a long time to connect to the wlan on wake-up. Manually I can connect at once and the connection stays up, but it is not completely satisfying yet :-/

Setting the IPv6 Mode: Link-local only in AEBS settings solved this issue for me.

Airport Utility->Internet->Advanced->IPv6->"Link Local Only"

FYI.. the AEBS NAT Port-mapping feature is working without any problems after disabling the IPv6 'Tunnel' Mode.

OMG - The OP's post could've been written by me. BUT - I don't think it's torrent related!

In the last 3 weeks this has been my full time job.....

1. Had comcast crawl all over my house, wires, pole to search for a problem.
2. 2 Extremes, 1 Netgear router
3. 3 Modems
4. Spend hours upon hours with AppleCare product specialists and it's now been referred to Engineering.
5. Conversed with Comcast to get assurance they weren't hassleing me.

3 weeks ago, I started running a couple simple legal torrents. After months of perfect performance, the Extreme (n gigabit) started blowing out to where I'd have to unplug it up to 6 times a day. The first suspects after eliminating the modem/comcast was the Extreme. I was told to exchange it by AppleCare cuz they did EVERYTHING possible over the phone to fix it. Take it to store - works fine there. Get a new one anyway. FUNILY, in the interim of returning to new Extreme - I ran a G Netgear which did NOT blow out.

I changed my port mapping and felt that fixed it. No. With Leopard, I was transferring some data to do a clean install - problems came back. I'm averaging only about 4 times a day now. Feeling is that any type of movement of data triggers this. Naaaaa - cuz it's happening while just checking EMAIL.

BUT BUT BUT..... then I figured out that that airport update recently came out about 3 weeks or so ago which is when I started having the problem. My only current thought is the new firmware update is horrendous. I also wonder that given the MANY problems people are having with Leopard with this -if they never updated a few weeks ago - but were forced the update with the Leopard install.

I'm going to try to find that darned firmware. I have 7.2.1 right now. Anyone have a link? The link above is for something else. AND - I'd like to know if all those who reported this issue on this thread - have found ANY fix?