dloose;295205 Wrote:
> why does the SB v3 seem to top out at 3-5 Mb/sec (at least using the
> built-in test plug-in)?
It doesn't, that's just the network test plugin's maximum. Streaming
audio files, you'll never need to go higher than about 5 Mbps, which
would be 24/96 WAV (4608 kbps).
--
M
I'm just curious -
If maximum bandwidth of .11g is 54 Mb/s and typical throughput is about
19 Mb/s, why does the SB v3 seem to top out at 3-5 Mb/sec (at least
using the built-in test plug-in)? I'm using the SB in bridge mode to a
Denon 3808CI and get not-infrequent drop-outs.
--
dloose
seanadams;262463 Wrote:
> I am looking at our bridging implementation, and it is designed to
> forward to all ports in the event of a unicast packet whose MAC is not
> in its table. It is not clear to me if this is our problem or if
> something else is going on, so I am hesitant to open a bug wit
I am looking at our bridging implementation, and it is designed to
forward to all ports in the event of a unicast packet whose MAC is not
in its table. It is not clear to me if this is our problem or if
something else is going on, so I am hesitant to open a bug without
knowing any specifics.
It w
seanadams;262284 Wrote:
> Hmm. So here's an idea: try making that static ARP entry point to the
> broadcast MAC: "FF:FF:FF:FF:FF:FF".
>
> This is a very strange and generally inadviseable thing as if it works,
> it will let someone on the internet create broadcast traffic on your
> LAN. However
hau;262161 Wrote:
> The problem is that the packet which is sent from the internet is
> otherwise structured as a WOL packet, but in fact is a UDP packet sent
> to a certain address (unicast). (My ADSL router then forwards it
> internally to the specified address.)
>
Hmm. So here's an idea: tr
seanadams;262142 Wrote:
> The WOL packet is a broadcast so it shouldn't matter, but to answer your
> question I believe if it doesn't know it will behave like a hub and send
> it to all ports.
The problem is that the packet which is sent from the internet is
otherwise structured as a WOL packet,
hau;262108 Wrote:
> What happens when it doesn't know who's on which side?
>
The WOL packet is a broadcast so it shouldn't matter, but to answer
your question I believe if it doesn't know it will behave like a hub
and send it to all ports.
--
seanadams
--
seanadams;172362 Wrote:
> When the SB3 is operating in bridging mode, it keeps track of who is on
> the ethernet side and who is on the wireless side - it knows where to
> send a packet.
>
What happens when it doesn't know who's on which side?
Reason I'm asking this, is that I'm trying to us
So the last thing I tried was to power the router on last, but that
didn't help. Does anyone know why the router might be breaking the
'bridging' of the sb? I would have thought it should be completely
passive. I can't really use this configuration without a router, or a
switch in place - not s
I remember having a problem with a Netgear wireless bridge I bought for
linking my PS2 to my network.
The bridge couldn't connect to the network initially with WEP enabled,
but if I disabled WEP it worked, then set it to 64bit WEP, and still
worked, then 128bit still worked.
I just figured that
Mark Lanctot;179995 Wrote:
> ...how would that work? The player hasn't connected to the network yet,
> how can SlimServer push the data to it?
>
> I agree, entering in a passphrase is a pain, but I can't think of any
> alternatives.
You could only change things once the sb was on the network,
bludragon;179977 Wrote:
> btw, if I ever have to type a full length randomly generated WPA key in
> again using the sb remote I think I might just go nuts... Any change
> of putting network settings in the web interface (with appropriate
> WARNING for the foolish)?
...how would that work? The
Found a cable, took the hub out of the loop, and now it works.
btw, if I ever have to type a full length randomly generated WPA key in
again using the sb remote I think I might just go nuts... Any change of
putting network settings in the web interface (with appropriate WARNING
for the foolish)?
My set-up is:
NSLU2> SB3> Wireless (Netgear DG834, 128bit WEP)> PC1 (WinXP), PC2
(Linux).
I can ping all the units on the network and can access Slimserver
running on any of the network PCs and NSLU2 which is also a NAS from
the SB3.
I am using DHCP but each network device has a preallocated IP
I'm not using ad-hoc mode either. I tried downgrading to the firmware
with slimserver 6.5.0 (FW 65 I think), turned bridging off, then back
on, and it didn't work, then FW 55 (6.3.1), and it still didn't work.
When going back to FW 55 I needed to re-enter the WPA key.
I didn't have much time to
Ramage;179625 Wrote:
> Leaving my wireless bridge set-up in place, I upgraded the SB3 to FW 72.
>
>
> On restart, the bridge worked as expected. BTW upgrading to FW72 does
> not require the connection to be set up from scratch, so that the
> bridge settings were left in place from FW55.
>
> Th
In the test I did recently, bridging in FW72 worked fine _except_ in
Ad-hoc mode. No problems bridging to a Linksys AP.
If we're all seeing the same thing then we should open a bug.
--
seanadams
seanadams's Profile: http
Thanks Ramage,
If I get a chance later today I will try to revert to fw v55 to see if
it works.
--
bludragon
bludragon's Profile: http://forums.slimdevices.com/member.php?userid=1530
View this thread: http://forums.slimdev
Leaving my wireless bridge set-up in place, I upgraded the SB3 to FW 72.
On restart, the bridge worked as expected. BTW upgrading to FW72 does
not require the connection to be set up from scratch, so that the
bridge settings were left in place from FW55.
The problem seems to be that FW72 does n
Ramage;179405 Wrote:
> My test setup worked OK; however I was using SS v6.3.1 and SB3 FW
> version 55.
>
> I tried the same setup today but with SS 5.6.2 FW 72 and the wireless
> bridge did not work. Looks like the FW update may have broken it.
Tested my setup today after downgrading the SB t
Ramage;172228 Wrote:
> Just to test the feasibility of your proposal I set up the following:
>
> * NSLU NAS+Slimserver connected to SB3 with crossover ethernet cable
> * Set up wireless bridge to my main network.
>
> Entered all required IP addresses for my network and it worked
> perfectly.
>
ok, it officially doesn't work for me :-(
--
bludragon
bludragon's Profile: http://forums.slimdevices.com/member.php?userid=1530
View this thread: http://forums.slimdevices.com/showthread.php?t=31850
_
seanadams;172362 Wrote:
> That is not what should happen at all. When the SB3 is operating in
> bridging mode, it keeps track of who is on the ethernet side and who is
> on the wireless side - it knows where to send a packet.
>
> Telling it to connect wirelessly just means that you want to conf
If I connect my server to a squeezebox 2 with the ethernet cable, can I
then access the server wirelessly using the Wireless bridge function in
the squeezebox, without having to have a seperate wireless access card
in the server.
I just want to use a VERY simple stripped down server.
--
Puggie
25 matches
Mail list logo
