Bug 11020 - Problems connecting Duet to SqueezeNetwork using 2wire 3800 HGV-B
: Problems connecting Duet to SqueezeNetwork using 2wire 3800 HGV-B
Status: RESOLVED WONTFIX
Product: SB Controller
Classification: Unclassified
Component: SqueezeNetwork
: unspecified
: Other Other
: P2 normal (vote)
: 7.4.0
Assigned To: Ross Levine
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-09 15:52 UTC by Walker LaRon
Modified: 2009-03-23 18:17 UTC (History)
9 users (show)

See Also:
Category: ---


Attachments
2 Wire 3800 HGV-B Manual (3.16 MB, application/pdf)
2009-02-09 15:52 UTC, Walker LaRon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Walker LaRon 2009-02-09 15:52:36 UTC
Created attachment 4786 [details]
2 Wire 3800 HGV-B Manual

Environment:

2wire 3800 HGV-B with most updated firmware

Updated Firmware in Squeezebox Controller and Receiver (via new SC 7.3.2 version)

Symptom:

We have had several customers who cannot get the Squeezebox Duet to connect directly to SqueezeNetwork when using to 2wire 3800 HGV-B router.

Customer has contacted AT&T to help with their router setting and firewalls, to no avail.  (They have stated that AT&T will NOT help at all)

Troubleshooting:

-Tried Bridged mode, will connect fine, but would never connect to SqueezeNetwork directly

-Tried Wireless mode, controller and receiver will connect, but can never get to SqueezeNetwork directly

-Tried Hybrid Mode, will connect to network, but will never connect to SqueezeNetwork directly

-Tried playing Internet Radio from SqueezeCenter, it can play fine.  

Overall, the customer's just can't connect their Squeezebox Duet's directly to SqueezeNetwork


Please note that I have had at least 2 customers try turning off Wireless Encryption (when trying totally wireless mode and hybrid mode)

If have also tried extensively working with a customer walking through his router settings, to no avail.  Per the customers, AT&T advised them they the will not help with firewall setting, or adding exceptions to their firewalls, and there is no way to turn the firewall off.


Thanks,

LaRon
Comment 1 James Richardson 2009-02-10 08:31:29 UTC
Ross: can you look into this one please.
Comment 2 Ross Levine 2009-02-11 13:40:47 UTC
James can you help me acquire one of these please? Anoop in support tells me there have been 3-5 cases of this. As Uverse expands we will likely see more of this.
Comment 3 Walker LaRon 2009-02-26 17:44:13 UTC
Ticket# 090218-001886

Customer is unable to connect to SqueezeNetwork directly with Squeezebox Duet.

Has 2Wire 2701-HG-B

Customer stated it worked once (as other customers have stated) and then it just stopped working.

Customer cannot play any music from Music Services or Internet Radio from SqueezeCenter either - it times out after about 5-7 seconds.

Tried Wireless, Hybrid, and Bridge mode, to no avail.

Can play files from his computer no problems.

Spoke with Engineering, adding the 2Wire 2701-HG-b router to this bug, as these routers are nearly identical.

Thanks,

LaRon
Comment 4 Ross Levine 2009-02-27 14:37:46 UTC
3800 HGV-B explicitly requires Uverse service to reach Internet. This renders in house testing of Squeeze Network connection issues impossible. 

LaRon will need to test this as he has access to a 3800 in a Uverse install. From what we can see here the firewall is difficult to work with, hopefully AT&T / 2Wire will address this in future firmware. Hopefully LaRon will find a workaround. :-)
Comment 5 Walker LaRon 2009-03-02 18:58:11 UTC
3800 HGV-B router
SqueezeCenter 7.3.2
SB Controller firmware r3993
SB receiver firmware 58
Laptop running Fedora 10 - wireless
Computer running XP Pro - wired directly into 2wire

SB Receiver 7 feet away from router
SB Controller - At least 15 feet away from router through a wall

Hello All,

I was able to get the Squeezebox Duet to connect directly to SqueezeNetwork by performing the following:

Factory resetting the Squeezebox Controller and Player
Connecting the Squeezebox Controller to the network via Wireless
Once the Controller was connected:

-Logged on to the 2wire 3800 HGV-B router via the web interface
-Clicked on the "Firewall" section at the top
-Located the "Attack Detection" section and uncheck "Invalid ICMP Detection"
-Click the "Save" button to save these changes
-Click on the "Home Network" option on top
-Locate the Squeezebox Controller under the "Local Devices" Section
-Click the "Edit Firewall Settings" link next to the Squeezebox Controller
-Click on the "Add a new user-defined application" link


Once here:
Locate the "Application Name" section and name it SqueezeCenter

Under Protocol:      Choose "TCP"
For Port Range:      From: 3483  - To: 3483
Protocol TimeOut:    86400
Map to Host Port     3483 
Application Type:    None (default)

Click "Add Definition"

This will save the new exception.

Under Protocol:      Choose "UDP"
For Port Range:      From: 3483  - To: 3483
Protocol TimeOut:    600
Map to Host Port     3483 
Application Type:    None (default)

Click the "Add Definition"

This will add another exception to the same exception you have just created

Under the Definition list Section you should see the 2 created exceptions.

Click the "Back" button

This will bring you back to the "Edit Firewall Settings" page

From here, locate the "Select a computer" section, and select your "Squeezebox Controller"  from the Drop-down menu

Locate the "Edit Firewall settings for this computer" section
- Click "Allow individual application(s)" radial 
- Highlight "SqueezeCenter" in the menu (should be the first application in the list)
Click the "Add" button

This will link the exceptions you have created to the Squeezebox Controller.

From here, you should be able to continue with the Squeezebox Duet set up.  Once you connect your Squeezebox Player to your network, you should now be able to connect directly to SqueezeNetwork.

After I was able to connect to SqueezeNetwork directly, I performed the following tests:

Factory reset the Squeezebox Controller and Player
- Reconnected via Wireless - connected no problems
- Changed music source to connect to Fedora 10 machine, no problem
- Changed music source to connect to XP machine, no problem
- Changed music source back to connect to SqueezeNetwork, no problem

Left overnight, and picked up Squeezebox Controller.  I did have a problem connecting back to the Squeezebox Player, but all I did was turn off the Squeezebox Controller, turn it back on, reconnect to the Squeezebox Player, and had no problems after that.

I then repeated the above steps, playing music for time periods from each computer, as well as SqueezeNetwork, and did not have any other issues.


I hope this information is helpful.

LaRon
Comment 6 Ross Levine 2009-03-03 17:05:56 UTC
Great work LaRon. I look forward to hearing feedback from other users with this Residential Gateway. 

Support: Please update this bug as data comes in.
Comment 7 Walker LaRon 2009-03-05 20:17:37 UTC
Ticket # 090306-002597

3800 HGV-B
Windows XP

Walked customer through steps, worked without a hitch.

Connected to SqueezeNetwork no problems, and was able to switch to SqueezeCenter no problems.


*******Please note that there is a change in the steps*******

After you "Click on the "Firewall" section at the top", you must
"Click on the "Advanced" Settings link at the top",  to get to the
"Locate the "Attack Detection" section and uncheck "Invalid ICMP Detection""

Thanks,

LaRon
Comment 8 James Richardson 2009-03-23 17:44:07 UTC
Ross: since LaRon has a work around now, do we still need to keep this one open for 7.4? or just have TS make an FAQ on how to get it to function properly.
Comment 9 Ross Levine 2009-03-23 18:17:23 UTC
I think we should consider re-opening this later based on Support's metrics. LaRon has a workaround; we have received word back from customers that the workaround is sufficient. It would be nice to hear more data back from Support as it comes in. 

I'm marking this as WONTFIX because there is likely nothing we can do. I spoke to 2wire and they have no QA department for me to communicate with. :-(