tf8252 Wrote: 
> But I AM CONNECTING to Slimserver wirelessly via my laptop...which is on
> the same network.

That's because the traffic is only going through the router once.  It
has a clear path from SlimServer to the laptop.

Let's get a fresh start.  Using my Amazing Clipart Skillz (tm) I drew
two crude diagrams to indicate what's going on.

The first one shows conventional network topology.  Every device has a
single link to the router, either wired or wireless - they are
equivalent in this context and you could replace wireless links with
wired links and wired links with wireless links if you wished.    Note
that each device has a clear path through the router to each other
device and traffic only passes through your router once.  Even Internet
traffic gets passed through the router only once and has a clear path to
each network device.

The second diagram shows your current situation.  It's clear that you
should theoretically have SqueezeNetwork access because Internet
traffic passes through your router only once and has a clear path. 
It's also clear that your laptop will have access to SlimServer -
laptop traffic destined for SlimServer goes wirelessly out to the
router, then wirelessly out to the Squeezebox, which then bridges it to
the SlimServer NAS.  One clear path.  Similarly, your laptop has
Internet access and any devices wired to the router will be able to see
the Internet and any other devices.

What's convoluted is the path data takes from the SlimServer NAS to the
Squeezebox.  It will have to go from the NAS to the Squeezebox (note the
Squeezebox won't do anything with bridged traffic except pass it back
and forth) to the router.  Then it will have to be sent back again to
the Squeezebox.  Commands from the Squeezebox to SlimServer follow a
similar convoluted path - data cannot be sent along the network cable
to the NAS directly because the Squeezebox has been instructed to use
the wireless connection to SlimServer.  If you chose the wired
connection, it would work.  But instead it has to send its data
wirelessly to the router, which then sends the data back to the
Squeezebox, this time destined to the bridged device, the SlimServer
NAS.  The bridging function then attempts to direct the traffic to the
bridged connection.  It's a chicken-and-egg thing.  This is simply too
confusing and too convoluted to work properly, especially for a device
that depends on its server as heavily as a Squeezebox does.

If you were to choose the wired connection to SlimServer, this would
work, but it would create other problems.  You will have told the
Squeezebox to deactivate its wireless connection, therefore it won't
communicate with the router.  It's actually on its own private network
cut off from the Internet and cut off from the rest of your network. 
Therefore, it would have no SqueezeNetwork access and the SlimServer
NAS would have no connection with the rest of your network for control
purposes, streaming purposes and file transfer purposes.

Hopefully this gives you an idea.

Regarding your present issues, it's nothing more than configuration
stuff.  Since you had SqueezeNetwork access your wireless connection
was functional.  Reset the Squeezebox, reboot devices, etc.  Everything
has a clear path to everything else now, it will work.


+-------------------------------------------------------------------+
|Filename: network diagram2.jpg                                     |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=1096|
+-------------------------------------------------------------------+

-- 
Mark Lanctot
------------------------------------------------------------------------
Mark Lanctot's Profile: http://forums.slimdevices.com/member.php?userid=2071
View this thread: http://forums.slimdevices.com/showthread.php?t=22400

_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to