beta build , linksys wireless bug

[moshelog]

hey all ,

im using macbook pro with snow leopard last build .


i have router linksys WRT300N
and my security setting is psk2(wpa2)

after installing boxee beta i noitce everytime i get into it, it broke my wireless connection .

and i have to restart my router to get connection on my macbook

when i was in my friend house with my macbook .
everything was ok , he has edimax router 54G and use wep security setting .

thx
moshelog

[moshelog]

any idea ? im cluless ,
my router act ok with all kind of apps , but not with boxee ,
must be abug .

hope to see acomment on this

[NomadDNA]

any idea ? im cluless ,
my router act ok with all kind of apps , but not with boxee ,
must be abug .

hope to see acomment on this

Hey Mosh: For what it's worth I had a similar problem several months ago with my USRobotics router (801g). Every day I used boxee, I'd loose the connection on my internet, which, out of an unsupported bias, I blamed on my ISP.

I replaced the router with an Apple Airport Extreme and haven't had a problem since -- I theorize because the new router (dual band, 801n) can better handle large data transfer.

LinkSys produces a good piece of hardware, but you may want to consider upgrading. Using Boxee is heavily data intensive, and may be asking a lot from some routers.

[moshelog]

well i will consider this
but linksys N should be good router and should handle such an app like boxee
the disconnecting happen very fast
i connect to boxee and it happen ... so this is abug and not problem with data transmit .
can u tell me if u can stream mkv movies smooth ?

thx
moshelog

[NomadDNA]

well i will consider this
but linksys N should be good router and should handle such an app like boxee
the disconnecting happen very fast
i connect to boxee and it happen ... so this is abug and not problem with data transmit .
can u tell me if u can stream mkv movies smooth ?

thx
moshelog

A 801n router seems like it should handle the load. Again, I think if it were a problem with Boxee in general, everyone would be reporting this problem.

Regarding MKV files, I don't understand the appeal. I find them unnecessarily large, and my XP system has trouble coping with them. On the otherhand, I could see their appeal on better systems. So, to answer your question: No, I've never been able to stream .mkv files from my NAS smoothly -- but that's my processor's fault, not my router.

[TomyLo]

hey all ,

im using macbook pro with snow leopard last build .


i have router linksys WRT300N
and my security setting is psk2(wpa2)

after installing boxee beta i noitce everytime i get into it, it broke my wireless connection .

and i have to restart my router to get connection on my macbook

when i was in my friend house with my macbook .
everything was ok , he has edimax router 54G and use wep security setting .

thx
moshelog

Hey Mosh.

I am having the same freaking problem.. i have the Wrt350N and always drops my connection man :( sucks

[moshelog]

guys i wont replace router cuz of boxxe cant work with linksys router .

plz fix it .

[NomadDNA]

guys i wont replace router cuz of boxxe cant work with linksys router .

plz fix it .

There's not much that can be done without more information:

First, this *may* show up on the boxee log. Follow these directions and post any "ERRORS" on this thread that show up in the log:
http://support.boxee.tv/forums/49599/entries/43963

Second, some routers keep a record of connections and issues (right?). Access your routers preferences, and see if it provides error prompts.

[moshelog]

tomylo do that also plz .

[TomyLo]

tomylo do that also plz .

Hey guys.

Ok, i just did the debug thing... here's the boxee.log and the boxee_old.log

Click the link to download 731

[NomadDNA]

Hey guys.

Ok, i just did the debug thing... here's the boxee.log and the boxee_old.log

Click the link to download 731

So, this is your boxee log of when you lose your internet connection over your SMB network? If so, and keep in mind I'm not a Boxee programmer, I don't see any obvious erros that would explain your internet dropping.

Since you've done this much work, consider posting this on Jira along with a clear explanation of the problem. The programmers will review your issue.
jira.boxee.tv

Everyone else who has this problem should log on and vote for the problem so the issue gets bumped up in priority.

[TomyLo]

So, this is your boxee log of when you lose your internet connection over your SMB network? If so, and keep in mind I'm not a Boxee programmer, I don't see any obvious erros that would explain your internet dropping.

Since you've done this much work, consider posting this on Jira along with a clear explanation of the problem. The programmers will review your issue.
jira.boxee.tv

Everyone else who has this problem should log on and vote for the problem so the issue gets bumped up in priority.

Sounds good, I'll start posting on Jira... so I guess Jira is where the programmers for Boxee view all the logs right?

And this log that I just posted didn't crash or do anything, I just thought you guys wanted to see one of my logs... anyhoo, sorry for the confusion.

[NomadDNA]

And this log that I just posted didn't crash or do anything, I just thought you guys wanted to see one of my logs... anyhoo, sorry for the confusion.

Lol, yeah... Well, your boxee system appears to be working smoothly.

Run Boxee. Wait until your connection drops. Close boxee. Open your Boxee.log, look it over for ERRORS and WARNINGS (I somehow doubt you'll find anything other than "ERROR: Unable to find xxxx over network"). Then post on JIRA.

Again, like I said before. I had the same problem, and it stopped after upgrading my router.... Just saying...

[moshelog]

thx tomylo for the log



"Again, like I said before. I had the same problem, and it stopped after upgrading my router...."

nomaddna

u have to agree with me that we better found the bug then replace our hardware .

we both had linksys router and we have same prob .

im sure u dont want that every user with linksys router will have sae issue

thx
moshelog

[TomyLo]

I just got the error this morning check it out.

File Browser (i wasnt able to access any files)

http://i50.tinypic.com/se0ghc.png

Possibly due to the movie scaning going on in the movie folder?

http://i46.tinypic.com/2uo2ddi.png

Here's the log: http://www.filedropper.com/boxeelog


ERRORS


07:27:11 T:2694731008 M:1884663808 ERROR: (pthread_mutex_destroy(&m_mutex)): [XCriticalSection.cpp:84] 16


07:27:41 T:2963378176 M:1876062208 DEBUG: SMBDirectory->GetDirectory: Unable to open directory : 'smb://******@192%2e168%2e1%2e101'
unix_err:'16' error : 'Invalid argument'
07:27:41 T:2963378176 M:1876078592 DEBUG: GetDirectory - Error getting smb://192.168.1.101
07:27:41 T:2965491712 M:1876099072 DEBUG: SMBDirectory->GetDirectory: Unable to open directory : 'smb://******@192%2e168%2e1%2e1'
unix_err:'16' error : 'Invalid argument'

07:27:41 T:2965491712 M:1876099072 DEBUG: GetDirectory - Error getting smb://192.168.1.1


07:30:51 T:2959433728 M:1814609920 DEBUG: Boxee: 22/12/09 12:30:51#ERROR#bxcurl.cpp:720(HttpPostString)#curl _easy_perform failed ()!


There's more errors, but seems like the one in red is repetitive a number of times in the logs

[TomyLo]

On my desktop I have shortcuts to my Movies & TV Shows folders on the external drive (connected to the router)... and as I tried to double click on the icons it failed to connect, so for some reason there is a issue with Boxee & the wireless router.

http://i50.tinypic.com/w83wpj.png

[NomadDNA]

There's more errors, but seems like the one in red is repetitive a number of times in the logs

Rockin! Now we've got something.

I know you've done a lot of work, but the next step is easy: reporting to Jira.

Login to Jira, and post an error report which includes a concise description of the problem, screen shots (if you have any more), and your log. And, that's it! The programmers are really good about jumping on the problem within 24 hours.

[TomyLo]

Rockin! Now we've got something.

I know you've done a lot of work, but the next step is easy: reporting to Jira.

Login to Jira, and post an error report which includes a concise description of the problem, screen shots (if you have any more), and your log. And, that's it! The programmers are really good about jumping on the problem within 24 hours.

Done: http://jira.boxee.tv/browse/BOXEE-3795 so let's hope they fix it :)

[NomadDNA]

Done: http://jira.boxee.tv/browse/BOXEE-3795 so let's hope they fix it :)

::Fist pump::

Good deal.

[TomyLo]

::Fist pump::

Good deal.
Right back a'tcha playaaaa hahaha :cool:

[moshelog]

thx guys !

now lets wait

[NomadDNA]

**NOTICE** Potential problem with Boxee+Lynksys WRT Routers?

Another thread is also having trouble with Boxee over their Lynksys WRT router:
http://forum.boxee.tv/showthread.php?t=13656

The user reports that Netflix wont load on his WRT router at home, but works when he take it to his office.... I think this is more than just a coincidence.

[mwahal]

My router is Linksys WRT54GL running DDWRT.

I'm running Snow Leopard 10.6.2 on a hackintosh.

Netflix WORKS in Mac->Safari, in Mac->Firefox, in WindowsPC->IE, in WindowsPC->Firefox.

But its only NETFLIX which doesn't work in boxee. Everything else such as HULU which works. So, I don't know if its Linksys router issue.

One thing for sure, when you start Netflix video, there is some speed negotiations with netflix server. May be there is some code in boxee which fails just with the linksys and some other routers.

And I'm running alpha, not beta. Don't have access to the beta yet.

[moshelog]

i dont think we are talking about same problem .

we talking about router disconnect when u connect to boxee .

[TomyLo]

Man this sucks... here's another log error: http://www.filedropper.com/boxeelog2 i also posted an update on Jira, but when are the programmers going to work on this issue? It's sooooooooooooooooo annoying man

http://jira.boxee.tv/browse/BOXEE-3795

[triffle]

Hey everyone...

Lets think outside of the box...(boxee). Has anyone checked the router logs to see what is going on with that... I know that linksys routers will only allow 512 connections to the internet at one time... If this is exceeded then the connection will drop...

When you guys have this issue. Please leave boxee beta/alpha open. If you have another computer check and see if you can access the the router typically 192.168.1.1 in your browser of choice. (not the boxee browser please). For linksys goto administration>logs>click enable, then the view log button. check all of the logs... if you have a ton of outbound connections, and they are comming from the IP of the machine that is running boxee, this may be useful in the bug report... If they are coming from another machine, you have other issues..(unless its a server and you know what it is doing). If the logs are empty, reboot your router by killing the power to the device, wait 10-15 seconds and plug it back in... after it is up, try to see if boxee can see network shares/internet streams...

I have a Linksys WRT110 firmware 1.0.22 and have not had this issue..

[TomyLo]

Hey everyone...

Lets think outside of the box...(boxee). Has anyone checked the router logs to see what is going on with that... I know that linksys routers will only allow 512 connections to the internet at one time... If this is exceeded then the connection will drop...

When you guys have this issue. Please leave boxee beta/alpha open. If you have another computer check and see if you can access the the router typically 192.168.1.1 in your browser of choice. (not the boxee browser please). For linksys goto administration>logs>click enable, then the view log button. check all of the logs... if you have a ton of outbound connections, and they are comming from the IP of the machine that is running boxee, this may be useful in the bug report... If they are coming from another machine, you have other issues..(unless its a server and you know what it is doing). If the logs are empty, reboot your router by killing the power to the device, wait 10-15 seconds and plug it back in... after it is up, try to see if boxee can see network shares/internet streams...

I have a Linksys WRT110 firmware 1.0.22 and have not had this issue..
So I guess what you are saying is, the problem could be with the router rather than Boxee?

[triffle]

So I guess what you are saying is, the problem could be with the router rather than Boxee?

I am not sure if that is it, but i couldnt hurt to look. There have been a couple of log files on boxee's end but none on the "next hop". Especially if you cant get to it (the internet/network share). In most cases this is going to be the home router.

The logs could possibly see if boxee is trying to make a ton of connections the IDM to get cover art..blah blah... Or could be something completely different... But I think that relevant info (from the IP of the machine that boxee is installed on) like that would be really useful to the dev team.

But if you can just close boxee and you can hit the internet/network share... I dont think the router will tell you anthing useful besides if you got some kind of malware on your home network...(which is still kinda useful)

[electricwaffles]

Wanted to chime in that I was having the same issues since upgrading to the beta -- connection problems, occasionally jittery video. I decided to buy an Airport Extreme to replace my Linksys router, and I'm still having the same problems.

Yet, when I watch video in Hulu Desktop, I have no problems. How is it that Hulu video (and most other streams) suck in Boxee Beta, but fine in the Hulu Desktop app?

[rafaelmizrahi]

http://jira.boxee.tv/browse/BOXEE-3309

[jsil]

I'm having the same problem with the airport extreme and boxee beta. I keep having to put my computer to sleep to reconnect.

Happens several times a day

[Jpunt]

Just checking in: I'm having the same problems on a AirportExtreme(n/gbit) as well. This new beta-interface dragged me back from Plex, but my network (wireless/wired) drops out while running Boxee. Got it also connected through SMB. Hope you guys get this fixed, than I'll be back on Boxee! :)

[caughtbythefuzz]

I figured I'd chime in here as I downloaded Boxee last night and have yet to make it work over the internet at all.

When I start Boxee it immediately disables my router (linksys WRT54G) completely. When I say this I mean that I cannot use the network from my computer or any other computer or phone in the house. I have to physically reset the router to make it work again.

Some on this thread have suggested that it may be prudent to upgrade to an 801n router. I hardly think that the good people at Boxee would consider this to be an acceptable solution to the problem as these routers are still not common among the general public. Also, I think it would probably be considered unacceptable that Boxee disables the router for all other users. I won't upgrade to 801n because my ISP (AT&T) does not provide enough speed over the initial connection (DSL) to warrant such an upgrade, and the connection that I have right now is plenty fast enough to watch Hulu, Netflix, and any other internet video that is out there.

As far as I can see this problem is localized some sort of compatibility issue between Boxee and linksys routers... I hope that the engineers can solve whatever the problem is in the next release because Boxee looks like a kick-ass service.

[TomyLo]

Hey guys.

I gotta admit, I haven't been experiencing much (or any) problems since my first post... maybe the guys solved it after I posted a ticket on jira

[Jpunt]

The fact that a single application is able to disable your router is unacceptable indeed. Is there any info from the Boxee-guys about this? I removed the SMB-shares (and disabled it on my server), and I'm having the same problems.

[majidaz69]

i am having the same freaking problem i too blamed my isp and i am using airport express and time capsule as the routers so traffic loads shouldnt matter i suppose....

[dconti]

I figured I'd chime in here as I downloaded Boxee last night and have yet to make it work over the internet at all.

When I start Boxee it immediately disables my router (linksys WRT54G) completely. When I say this I mean that I cannot use the network from my computer or any other computer or phone in the house. I have to physically reset the router to make it work again.

Some on this thread have suggested that it may be prudent to upgrade to an 801n router. I hardly think that the good people at Boxee would consider this to be an acceptable solution to the problem as these routers are still not common among the general public. Also, I think it would probably be considered unacceptable that Boxee disables the router for all other users. I won't upgrade to 801n because my ISP (AT&T) does not provide enough speed over the initial connection (DSL) to warrant such an upgrade, and the connection that I have right now is plenty fast enough to watch Hulu, Netflix, and any other internet video that is out there.

As far as I can see this problem is localized some sort of compatibility issue between Boxee and linksys routers... I hope that the engineers can solve whatever the problem is in the next release because Boxee looks like a kick-ass service.

Check the firmware version on your router and see if there is an update available.

Many routers like the linksys and dlink models have major firmware issues. There is very little quality control on many of those products ensuring they support even common networking protocols, and many have firmware with memory leaks that cause them to exhaust memory and reboot after seeing certain types of traffic.

I don't know if boxee does UPnP searches by default but if it does that is a prime suspect as to traffic that would cause problems for some routers...

[ktroniq]

Hi guys,

Just wanted to see if there was any update on this issue. I'm also experiencing these problems when I start up Boxee. It immediately kills my wi-fi connection. I know I have a crap router but I agree with caughtbythefuzz that I shouldn't have to get a new router to fix this situation.

One attempt I made to try to fix this is I've tried changing the sources.xml file so that it doesn't access any of my dir with media files and that worked once but since then, it's on and off.

Any update on this would be greatly appreciated!

[Jpunt]

I'm having the exact same problems using a fairly new Airport Extreme (up to date), so I don't think buying a new router is gonna fix anything.

[djgsf]

I figured I'd chime in here as I downloaded Boxee last night and have yet to make it work over the internet at all.

When I start Boxee it immediately disables my router (linksys WRT54G) completely. When I say this I mean that I cannot use the network from my computer or any other computer or phone in the house. I have to physically reset the router to make it work again.

Some on this thread have suggested that it may be prudent to upgrade to an 801n router. I hardly think that the good people at Boxee would consider this to be an acceptable solution to the problem as these routers are still not common among the general public. Also, I think it would probably be considered unacceptable that Boxee disables the router for all other users. I won't upgrade to 801n because my ISP (AT&T) does not provide enough speed over the initial connection (DSL) to warrant such an upgrade, and the connection that I have right now is plenty fast enough to watch Hulu, Netflix, and any other internet video that is out there.

As far as I can see this problem is localized some sort of compatibility issue between Boxee and linksys routers... I hope that the engineers can solve whatever the problem is in the next release because Boxee looks like a kick-ass service.

I am having the exact same problem with my Linksys wrt54g. My firmware is completely up to date, and I only have this problem running Boxee (ie Plex runs just fine).

I have not been able to use Boxee at all, it looks like great software, wish I could use it!

[dgilbert2]

I have the same problem with by Sagem 2404 router.

When starting to use Boxee Beta, after a couple of minutes the wireless dies on my router!

However, I fixed mine when first loading Boxee by going straight to Settings, Media, Local Sources and then removing all sources. (Click on each one followed by "remove").

I then reboot computer and rooter.

Once I've done this everything on the router is fine afterwards.

Strange one though!!!!

[srroos]

I'm experiencing something similar, though the wireless doesn't die the connection is dropped and Boxee thinks that it has finished with the file. I am running across a wireless bridge to my router to a source on my desktop machine. Web based apps seem to work fine.

Any input would be appreciated.

[jeckle]

bump for any new news?

Also sending in my equipment data, perhaps it could help. I have 2 win 7 computers, 1 studio 15 laptop, and 1 desktop, also an apple tv, all with boxee beta latest build. All crash my WRT54G linksys router. The fix for me is just unplugging and plugging it back in. Boxee lasts playing video for about 1 minute, before the router completely shutting off (not physically, but connection wise) the router will not reboot itself (ive waiting many hours for it to come back on).

[danitaz]

I thought I'd just jump in here and let you know that this doesn't seem to be a WiFi only issue. My Mac Mini is connected over the ethernet port directly to a D-Link DES-1105 switch. I use Front Row as my main interface, with both Boxee and Plex installed for various tasks. Often, when running Boxee, I will lose my connection to the network, and the "fix" is to unplug the D-Link switch and plug it back in. Other devices on that switch (VOIP device for phones, TiVO and SlingBox) all continue to work, but the Mac Mini loses all network connectivity until I cycle the power to the switch.

I found this thread by searching for issues with network drops, and was actually surprised that this seems to be such a long-term issue, with no resolution. I found references to this back in 2008 even.

http://forum.boxee.tv/archive/index.php/t-256.html

Danita

[dconti]

A suggestion:

If you are hitting the "Boxee causes my network to disappear/router to reboot" problem, can you:

1) Ensure your router firmware is up to date

If the problem persists:

2) Add the following info in an entry to the bug in jira (http://jira.boxee.tv/browse/BOXEE-4441):
-- Model of your router and the firmware revision
-- If you are using SMB and, if so, if your HD is plugged directly into your router, or if its separate
-- What version of boxee and what OS you run boxee on

This does a couple of things to help out. One, it starts a database of routers with compatibility problems that the boxee guys can then notify people of with release notes, end users can see if there is a known compat problem ahead of time, etc.
Two, it helps the boxee guys know which products and network topologies users are most likely to hit issues with, so they have an idea of what to test with when making changes to networking code.

Also, a general question (for this thread) - can anyone repro this problem by using a different media app to crawl their smb share? For example, if you add the share to WMP and let it crawl, does it create the same problem?

[danitaz]

2) Add the following info in an entry to the bug in jira (http://jira.boxee.tv/browse/BOXEE-4441):
-- Model of your router and the firmware revision
-- If you are using SMB and, if so, if your HD is plugged directly into your router, or if its separate
-- What version of boxee and what OS you run boxee on



I will do that today.


Also, a general question (for this thread) - can anyone repro this problem by using a different media app to crawl their smb share? For example, if you add the share to WMP and let it crawl, does it create the same problem?

So, just to be a bit more clear here, I'll outline my network (which while not totally unique, might be a bit more complex than some, because I run a business out of my home, and have multiple servers here).

1. Comcast's cable modem is attached to an Astaro Security Gateway, which of course is in turn attached to a gigabit switch.
2. Most of the server hardware is in the server closet in the basement. However, there is an ethernet cable running to a closet on the first floor where the wireless router is located - and granted, it's older - a WRT54G v2 with firmware v4.21.1, which is the latest firmware for this particular wireless router.
3. The WRT65G also has a 4 port 10/100 switch, and is then connected from there up through the wall to the second floor to the D-Link DES-1105 switch. That switch currently services a VOIP box for ViaTalk, a TiVO Series 3, a Slingbox and the Mac Mini in question here.

When Boxee causes my connection to die, I simply have to unplug the D-Link DES-1105 switch to get connectivity back. So, I'm not sure what relationship it has to the Linksys wireless router, since that doesn't have any problems during the process, but there is indeed a wireless router "in the mix" so to speak.

Now, our media server is an OES2 (SuSE Linux) server, which shares up the volumes via CIFS (which is of course SMB). All Macs in the house use CIFS to connect to the shares on this server. It is used frequently throughout the day by everyone. The types of applications that access these shares are iTunes, Windows Media Player (rarely), Roxio Toast Video Player (to play Tivo transfer files that are also on the network), MultiPlex, EyeTV, and now also Boxee and Plex. Boxee is the only application that causes the problem. All other applications can access files on the shares all day long with no problems. The only other app on the Mac that I think will "crawl" is Plex (I think??). On the Mac Mini, Boxee is indeed the only app that causes any troubles like this.

I've just checked out one of the few Windows PCs here to see what would happen if I connected to that share and let it crawl. Took about a minute, and no disconnection from the network at all.

Danita

[dconti]

I am down to two theories as to what is happening on your specific case:

A) The switch cannot handle the flood of ARP traffic that happens when boxee scans your subnet and locks up. The switch actually does have to do work to support the ARP broadcasts and it may not be able to handle the 12.5 broadcast packets/ms. If this is the case, my best suggestion for a band-aid is to use the arp tool to manually fill the arp table with entries for non-existent machines on your subnet (open a terminal and do man 8 arp; check the -f option). This will stop the ARP flood at boxee startup.

B) Your linksys router sees the flood of ARP traffic coming across the port and somehow gets into a state where power cycling the switch fixes it. You could prove/prove this by unplugging the uplink on your switch, waiting 10 seconds, then plugging it back in without power cycling.

A last thing to try would be plugging the mac mini directly into the router and bypassing the switch to see if that works; if it does i would put my vote on (A) which realistically requires a change from the boxee team (although the hack above would work short term).

[dgilbert2]

I really have had enough of this now.

Boxee crashes both a Sagem and Netgear router.

Not predictable but usually when starting up Boxee.

I hope this gets sorted out soon, until then I've stopped using Boxee, its just too unreliable, sorry!

Log file attached if it helps.

[Jpunt]

After updating to 0.9.20.10708, I'm still having the exact same problem. I've quit using SMB and mount my Drobo over AFP, but after a while my internet/network (ethernet) connection is being destroyed by something that Boxee is doing (while scraping?). I'm using a pretty new Airport Extreme here. Any idea's or calming words on this huge bug?

[dconti]

Hi jpunt - not sure what OS you run, but would it be possible for you to temporarily set up an outbound block rule for UDP port 137, then try running boxee again? If you are on windows it should be possible to do this with the built in firewall.

This will basically prevent you from using smb, but may help root out what is causing the problem.

Thanks

[mixedape]

Hi jpunt - not sure what OS you run, but would it be possible for you to temporarily set up an outbound block rule for UDP port 137, then try running boxee again? If you are on windows it should be possible to do this with the built in firewall.

This will basically prevent you from using smb, but may help root out what is causing the problem.

Thanks

TY TY TY! I've been having the same problem with my mac and BTHomeHub. I use little snitch so I created a new rule with the above settings and now everything works great!

[dconti]

Ok, cool. Realize that this rule will prevent you from using smb shares at all (sorry), but this is just until there is a fix in boxee for this.

[marcel]

anyone having this issue and using a mac please contact me at marcel{at}boxee{dot}tv

[Jpunt]

I didn't get an email-notification, so I totally missed your reply, sorry! I'm on OSX and I've got LittleSnitch running, so I'll give it a try. Thanks!