Bug 2903 - Problem connecting when connection blocking is enabled
: Problem connecting when connection blocking is enabled
Status: RESOLVED WORKSFORME
Product: SB 2/3
Classification: Unclassified
Component: Slimproto
: 29
: PC Linux (other)
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-31 08:32 UTC by Michael Herger
Modified: 2006-02-01 09:29 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Herger 2006-01-31 08:32:39 UTC
I hope I won't out myself as a newby unable to read the docs... But there's an issue with the SB2 not connecting wirelessly to the server when connection blocking is enabled on the server. But this issue has been bothering me before, and I never reported...

In my productive environment consists of 1xSliMP3, 2xSB1 wireless, 1xSB2 wired, 1xSB2 wireless. They are on their own "DMZ" with the server only accepting connections from the player's IP addresses. This generally works fine, once the players are all connected. But on server restarts I usually have to disable connection blocking or the wireless SB2 would not connect. Once it's connected, I can enable blocking. SB1 and the wired SB2/SliMP3 are fine.

Interesting detail: the player did receive and install the firmware upgrade wirelessly without the need to disable blocking.

As I thought SB1 and SB2/3 used the same protocols I assume this a bug. Anybody able to reproduce the problem?
Comment 1 Blackketter Dean 2006-01-31 15:36:55 UTC
Subject: Re:   New: Problem connecting when connection blocking is enabled

What is connection blocking? 
  

Comment 2 Michael Herger 2006-01-31 15:58:33 UTC
Hmm... I wasn't very precise:

Server Settings/Security/BLOCK INCOMING CONNECTIONS
Comment 3 Blackketter Dean 2006-02-01 09:04:58 UTC
What is the allowed IP addresses setting set to?  What are the IP addresses of your players? Also, can you look at the debugging output for d_slimproto?
Comment 4 Michael Herger 2006-02-01 09:26:24 UTC
I can't reproduce it... I feel a little foolish. Maybe the factory reset I did last night (due to connection problems with fw 29) got rid of that "problem" as well. Thus the log looks fine today:

2006-02-01 18:18:47.8086 Slimproto accepted connection from: 192.168.1.130
2006-02-01 18:18:47.8100 Got Slimproto frame, op HELO, length 18, IO::Socket::INET=GLOB(0x9adec08)
2006-02-01 18:18:47.8104 Squeezebox says hello.
        Deviceid: 4
        revision: 29
        mac: 00:04:20:05:c6:0b
        bitmapped: 32768
        reconnect: 0
        wlan_channellist: 0000
2006-02-01 18:18:47.8105 Squeezebox also says.
        bytes_received: 0
2006-02-01 18:18:47.8113 creating new client, id:00:04:20:05:c6:0b ipport: 192.168.1.130:31347

And for the records - my IP whitelist: "127.0.0.1,192.168.0.*,192.168.1.128-131,192.168.1.2" (0.* is the LAN, 1.* the wireless dmz)
Comment 5 Blackketter Dean 2006-02-01 09:29:53 UTC
Ok, we'll mark this as worksforme, reopen if you can reproduce.