Just going back to the orignal reason the poster asked this question, a
car based Slimserver.
Has anyone got experience of runing a hard-drive continuously in a
car.
I'd have thought the constant shocks would dramatically shorten the
lifespan of a HD. The roads in this country vary from good
oreillymj wrote:
Just going back to the orignal reason the poster asked this question, a
car based Slimserver.
Has anyone got experience of runing a hard-drive continuously in a
car.
I'd have thought the constant shocks would dramatically shorten the
lifespan of a HD. The roads in this country
Strange, I'm on my 2nd hard drive in the laptop I've had for 2yrs. And
I consider my self careful. It spends most of it's life on my, in
hibernation or fairly stable on my lap.
And the laptop has those sensors which detect movement and tell the
drive to spin down.
The 2nd drive was installed
oreillymj wrote:
Strange, I'm on my 2nd hard drive in the laptop I've had for 2yrs. And
I consider my self careful. It spends most of it's life on my, in
hibernation or fairly stable on my lap.
And the laptop has those sensors which detect movement and tell the
drive to spin down.
The 2nd
Eric Carroll;173946 Wrote:
The simple fact is that the cut through time (time from first bit in to
first bit out with no queueing delay) on a two port bridge (which is
what the SB3 is) is measured in microseconds.
I think that could only be true of an hardware ethernet switch (in
seanadams;174097 Wrote:
One thing that is interesting about the Ubicom platform we use is that
they implement the ethernet MAC in software.
I assumed you used a Ethernet MAC chipset, which are relatively cheap
these days and can do hardware cut through, but software is even less
expensive.
Since I happen to have a shielded RF test enclosure in front of me with
an access point and a Squeezebox in it, here are the actual numbers. I
have the computer wired directly to the squeezebox, and squeezebox
connecting to the access point with bridging enabled.
First, ping the Squeezebox
Very nifty! And I guessed 24 Mb/s with no measurement, no data and just
a virtual napkin...
This is getting to be too much like work. :-) I think I will go listen
to my Transporter :-)
--
Eric Carroll
Transporter-Bryston 3B SST-Paradigm Reference Studio 60 v.4
SB3-Rotel RB890-BW Matrix 805
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.
Sean,
If I may say as a guy who does IP networking for a living,
Mark Lanctot;172391 Wrote:
About the only drawback to this arrangement is if you have another
Squeezebox on the wireless portion because it'll be a 2-hop arrangement
- which isn't a problem for some people though.
Mark,
Some points that I hope are not already clear but hopefully address a
Eric Carroll;173946 Wrote:
If you were going multiple times over the same wireless network, that
would be an issue, but that is not what is happening in this example.
Hmm? I thought it was?
NAS (SlimServer) - SB (acting as bridge) to router, one wireless hop.
Router/AP to another SB,
Ah, my apologies. By router you mean Wireless Access Point, which can be
a router or a bridge. Mine happens to be a bridge so I thought you meant
a different topology. My bad I didn't read carefully enough.
In the case you are talking about looks like this?
SlimServer - SB(bridge) - Wireless -
Mark Lanctot;173957 Wrote:
Hmm? I thought it was?
NAS (SlimServer) - SB (acting as bridge) to router, one wireless hop.
Router/AP to another SB, wireless, 2nd wireless hop.
Well, my bad, that will teach me to respond without reading more
carefully, and I know better. Sorry.
router
azinck3 wrote:
Peter;172405 Wrote:
azinck3 wrote:
Peter;172381 Wrote:
Sean, wouldn't that also imply that an SB running in bridge mode
could
function as a poor man's access point by connecting to a wireless PC
in
ad-hoc mode?
Regards,
Peter
sounds great guys, once I have re-read this thread a few times and
absorbed the content properly I should know exactly what its capable
of. For this project its more a case of I'll have a SB2 there and will
occasionally need a wireless bridge so it would save both cash and
equipment if the SB2
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.
I am able to connect the SB directly
Ramage 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.
I am able to connect
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.
I am
Mark Lanctot wrote:
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
Peter;172348 Wrote:
Perhaps someone changed the squeezebox firmware to allow this. If Ramage
wants to make sure the traffic between the SB and the slimserver is not
going over the wireless interface (twice) he could try switching off
the
WAP. If it still works then the traffic
Mark Lanctot;172337 Wrote:
I'm amazed this all works?
Because this is a convoluted wireless arrangement. Say the SB3 wants
to send something to SlimServer. It can't do this over its crossover
cable because you've told it to use the wireless interface and bridge
the Ethernet port. So it
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
Mark Lanctot wrote:
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
seanadams wrote:
Mark Lanctot;172337 Wrote:
I'm amazed this all works?
Because this is a convoluted wireless arrangement. Say the SB3 wants
to send something to SlimServer. It can't do this over its crossover
cable because you've told it to use the wireless interface and bridge
the
I did check my test setup with the wireless access point disabled and
the NSLU slimserver continued to work with the SB3 over the wired xover
cable. When the wireless link was restored, access from the PC to the
NSLU was restored.
I was quite impressed by the functionality, confirmed by Sean.
Peter;172381 Wrote:
Sean, wouldn't that also imply that an SB running in bridge mode could
function as a poor man's access point by connecting to a wireless PC in
ad-hoc mode?
Regards,
Peter
I think you're right, but that it would be quite an interesting poor
man who has a squeezebox,
Peter;172380 Wrote:
I hope you have now learned to never underestimate a SqueezeBox, Marc!
;)
Most definitely. What's interesting about this is that this is above
and beyond what is required. The Squeezebox operating in bridge mode
really doesn't need to check if there are any packets
azinck3 wrote:
Peter;172381 Wrote:
Sean, wouldn't that also imply that an SB running in bridge mode could
function as a poor man's access point by connecting to a wireless PC in
ad-hoc mode?
Regards,
Peter
I think you're right, but that it would be quite an interesting poor
man who
Peter;172405 Wrote:
azinck3 wrote:
Peter;172381 Wrote:
Sean, wouldn't that also imply that an SB running in bridge mode
could
function as a poor man's access point by connecting to a wireless PC
in
ad-hoc mode?
Regards,
Peter
I think you're right, but that it
Peter;172381 Wrote:
Sean, wouldn't that also imply that an SB running in bridge mode could
function as a poor man's access point by connecting to a wireless PC in
ad-hoc mode?
Yes it can. In fact you can even connect two Squeezeboxes to each other
in ad-hoc mode with bridging enabled,
I think you are asking whether the SB2 can be used as a Wireless Access
Point to access your server.
There are a number of threads on this forum dealing with this, and the
bottom line is that the SB2/3 can not be used as a WAP.
--
Ramage
P2 266MHz,Linux ClarkConnect 3.2, SlimServer Version:
Thanks
I had searched but most of what I'd found dealt with using the SB as a
bridge and I couldn't find anything quite as specific as I wanted.
--
Puggie
Puggie's Profile:
Ramage wrote:
I think you are asking whether the SB2 can be used as a Wireless Access
Point to access your server.
Not necessarily. Perhaps he wants his server to access the access point
through the SB3. Unusual solution but it might well work.
Regards,
Peter
I want to be able to do a rsync between 2 servers to keep their music
folders identical (I will update the main server then rsync to the
secondary server). I want to access the secondary server using the SB2
as its wireless connection.
does that make sense?
to expand the application a little,
Your intentions are now a little clearer.
I think you will be able to do what you want, as the SB2 will connect
the server in the car to your wireless network in the house and the
second server.
Quite a novel project.
Good luck
--
Ramage
P2 266MHz,Linux ClarkConnect 3.2, SlimServer
Cool! I'm trying to set up a single server for home with all my music
stored as FLAC to retire my cd collection, I can then access this from
anywhere in the house (and work), all my music at the touch of a
button. I then want to duplicate this in the car so I have all my music
available there too
Puggie wrote:
Cool! I'm trying to set up a single server for home with all my music
stored as FLAC to retire my cd collection, I can then access this from
anywhere in the house (and work), all my music at the touch of a
button. I then want to duplicate this in the car so I have all my music
You have been through the wireless setup menus and made sure you have
bridging mode on - haven't you?
--
Patrick Dixon
www.at-tunes.co.uk
Patrick Dixon's Profile: http://forums.slimdevices.com/member.php?userid=90
View
Patrick Dixon;160368 Wrote:
You have been through the wireless setup menus and made sure you have
bridging mode on - haven't you?
Absolutely.
Some diagnostics could help here. There's no lights on the SB2 ethernet
port so a status menu that could flash when packets came in/out would be
very
raintonr;160376 Wrote:
Absolutely.
Ah... erm... or so I thought!
OK, so this gets a bit weird... I was originally running an old 6.5beta
of Slimserver when beginning to set this up. From memory this was dated
a couple weeks before the official 6.5 release. SB2s were on firmware
62.
I am 100%
Here's how it SHOULD work:
- you connect a crossover wire to the SB Ethernet port, and connect the
other end to the device you want to bridge.
- on reset* if you request to connect to SlimServer wirelessly, the
next option would be to bridge the connection. Note you have to
connect to
Here's how it SHOULD work:
- you connect a crossover wire to the SB Ethernet port, and connect the
other end to the device you want to bridge.
Yup - done that. When you change region on the SB2 or power cycle it
the machine on the other end of cable sees LINK down then up.
- on reset* if you
raintonr;160517 Wrote:
Yup - connected two machines with it as a test - works just fine.
This can be a bit misleading though. There are two basic types of
Ethernet cables: straight and crossover.
A straight cable is going to be pin 1 - pin 1, pin 2 - pin 2, etc.
A cross will follow the
snarlydwarf;160525 Wrote:
This can be a bit misleading though. There are two basic types of
Ethernet cables: straight and crossover.
It is defo a crossover cable and have used it to connect two machines
which do not auto-detect and get them to talk.
Have tried connecting both of these
Just a thought, but howabout swapping the 2 SBs over, just to see if
it's a hardware problem with the one SB.
--
Patrick Dixon
www.at-tunes.co.uk
Patrick Dixon's Profile:
Related?
http://bugs.slimdevices.com/show_bug.cgi?id=4557
http://bugs.slimdevices.com/show_bug.cgi?id=3660
--
MrC
MrC's Profile: http://forums.slimdevices.com/member.php?userid=468
View this thread:
http://bugs.slimdevices.com/show_bug.cgi?id=4557
Don't think so... doesn't appear to pass any packets ever.
http://bugs.slimdevices.com/show_bug.cgi?id=3660
Don't think so... doesn't matter whether the packets are DHCP or
otherwise. Setting the IP address of LB2 manually didn't have any
Hiya :)
I hope you don't mind me joining in a bit, I've tried some pinging
here:
Laptop = L
Desk top = D
Ping loopback address 127.0.0.1
L - sent 4 received 4 lost 0% average 0ms
D - same
Ping own address
L - same
D - same
Ping gateway
L - sent 4 received 4 lost 0% ave 4ms
D - same
Could not wait:
D pinging SB 4 4 0 1ms
L pinging SB 4 4 0 179ms / 5ms / 7ms
To work :)
--
Deaf Cat
Deaf Cat's Profile: http://forums.slimdevices.com/member.php?userid=515
View this thread:
Deaf Cat:
Which device is going through an SB as a wireless bridge?
I can recall that ping times through the SB weren't bad, 1-4 ms.
As I said, speed doesn't seem to be the problem, something else is.
--
Mark Lanctot
Ah I'm still at the starting blocks I'm afraid, not got as far a using
the SB as a bridge yet, just sorting getting the things talking to each
other through the router with no low level cock ups at the moment.
Still getting 25% loss now and then when pinging the laptop from the
desk top but the
Deaf Cat Wrote:
Mark, I take it you get no losses, when pinging?
No losses that I can recall with the SB as a bridge. It seems the
first ping is the longest, something needs to wake up to respond to
further pings.
--
Mark Lanctot
BTW, after the original setup you can go back to network setup by
holding the LEFT button. But if wireless bridging is turned on I don't
see a way to turn it off. Maybe if I would connect it to a wired
network so I'm able to select wired networking, then later changing
wireless network again -
tommypeters Wrote:
BTW, after the original setup you can go back to network setup by
holding the LEFT button. But if wireless bridging is turned on I don't
see a way to turn it off. Maybe if I would connect it to a wired
network so I'm able to select wired networking, then later changing
OK, so I need to plug something in to be able to turn it off. I'll check
if it's enough with just plugging in a cable, or a cable connected to
something powered on - I guess the former.
--
tommypeters
tommypeters's
tommypeters Wrote:
OK, so I need to plug something in to be able to turn it off. I'll check
if it's enough with just plugging in a cable, or a cable connected to
something powered on - I guess the former.
If you don't have anything plugged in it was never enabled in the first
place.
If you
When I just plugged in a cable, nothing happened, as you wrote. If it
was connected to something powered I got that question, and could
disable bridging - which was enabled before.
When I earlier checked Current Network Settings it said Bridge
wireless to ethernet: Yes. Now it says no.
It
In my experience and with some research I don't believe your router will
see the MAC address of the network device bridged through your SB3. I've
used multiple routers with multiple different bridge wireless clients
all with the same results.
I have a Tivo bridged through my SB3 and the router
joek Wrote:
In this case, you may have problems with a router trying to provide a
dhcp ip mapped to a specific MAC address when the device is behind the
SB3 bridge.
In small environments, there is no need to use dhcp unless you are
moving devices between networks (i.e. laptop).
I'm using
Mark,
Debug your network troubles at a lower level, since the lowest layers
are required to work correctly before higher services can. Forget
samba, browsers, etc. for the time being.
This could be a number of problems. Your fast to WAN, slow to LAN
speeds can be misleading because your
Thanks MrC. I was afraid I'd have to resort to low-level diagnostics.
I have some work to do this afternoon and will start attacking this
later.
Thanks for your help.
--
Mark Lanctot
Mark Lanctot's Profile:
Well cancel the red alert.
As soon as I wire the Ubuntu PC directly into the router, everything
works as expected. File sharing from/to, SlimServer web GUI,
everything.
This points the finger at the SB3, unfortunately. It's strange - it
works fine for Internet access, downloading files at
seanadams Wrote:
This possibly sounds like it's getting excessive packets queued up
somewhere and running out of memory, but that's just a guess. Can you
get it to hang by using the bridge mode when it's NOT playing music?
Sean, sorry about the slow reply - but I've just got the time to
I did some 'speed tests'
(http://forums.slimdevices.com/showpost.php?p=75876postcount=4) in
bridged mode. The tests saturated the connection (about 14 Mbps in my
case), but only for about 30 seconds or so.
Worked flawlessly for me.
How long does it take to cause a crash in your case?
--
GregD Wrote:
I use my SB2 as a wireless bridge - connecting the SlimServer PC via
100M ethernet. This work fine - and will play music forever without
problems.
However if I do something very intensive dragging data off the
SlimServer PC which uses SB2 as it's wireless bridge - I get an
Michaelwagner Wrote:
seanadams Wrote:
You know you need a crossover cable, right?
Oops. Is that documented anywhere?
From the Squeezebox Manual:
USING SQUEEZEBOX2 AS A WIRELESS BRIDGE
Squeezebox2 Wireless has both 802.11g and ethernet connections. You can
easily connect non-wireless
Thanks for all the help!
After going back and reading the manual, I noticed it does say
CROSSOVER cable. I think that might need to be printed in BOLD. My
previous wireless bridge ran off a standard ethernet cable. I'll pick
one up and try it again.
Thanks
--
swertens
With your ethernet cable plugged in, and connected to something with an
active link, hold down the Left on the remote for 5 seconds to get
back to network setup. You should then see the option to enable the
bridge.
--
MrC
Thanks MrC I'll try it again. The key words are (active link) I hope.
--
swertens
swertens's Profile: http://forums.slimdevices.com/member.php?userid=3591
View this thread:
Nope, any other suggestions?
--
swertens
swertens's Profile: http://forums.slimdevices.com/member.php?userid=3591
View this thread: http://forums.slimdevices.com/showthread.php?t=20445
Try a reset. Pull the plug, plug it back in and immediately hold down
the Add key on the remote.
If going through the network setup doesn't give you the option to
enable bridging, i suspect your cable problematic, or the system at the
other end does not have an active link.
--
MrC
You know you need a crossover cable, right?
--
seanadams
seanadams's Profile: http://forums.slimdevices.com/member.php?userid=3
View this thread: http://forums.slimdevices.com/showthread.php?t=20445
You can upgrade the WRT54G to act as in client mode by using one of a
number of free firmware upgrades (www.linksysinfo.com is a good way
into this). So you could buy another wrt54G or upgrade your main
router to a later model and flash your original. I run two WRT54G -
both with Sveasoft
73 matches
Mail list logo
