When I signed up as a beta tester for Long Island Cablevision's new
broadband service in 1995 (this was a very early operation; I was still
running Windows 3.1 with the Trumpet Winsock add-on for networking),
that was how their network worked. I was able to browse all the
neighbors' computers on
garym wrote:
> And I'm thinking of some unbelievable security issues if in fact your
> entire apartment complex is in fact a single network. You really need
> your own router.
Yeah of-course I would check if one of the niegbours NAS boxes has an
open samba share :) they may show in network neig
Mnyb wrote:
> This points to another reason to why should have your own router if your
> neighbours can interfer ,your "local" lan is really the lan for the
> whole apartment complex which means that you are on the same network ,
> this also means that your lms server and web-UI is avaible to all
squeeze1234 wrote:
> Comcast at this location doesn't hand out long lifetime leases. Their
> current DHCP leases only last for 24 hours. So it's very likely that
> I'll run into an address conflict when I try to sneak in and assign a
> fixed address to my device from within the range of their DH
squeeze1234 wrote:
> Comcast at this location doesn't hand out long lifetime leases. Their
> current DHCP leases only last for 24 hours. So it's very likely that
> I'll run into an address conflict when I try to sneak in and assign a
> fixed address to my device from within the range of their DH
Hello,
I too am in the same situation as hip2b2. I convinced my wife to get me
the Radio as a Christmas present, and I set it up to replace our alarm
clock, but it does not function well as such.
Do you know when the patch will be updated for the latest Radio
firmware?
- Regards,
rmjb
garym wrote:
> It would be nice to know why this problem is occuring, but why not
> switch to the fixed IP and just leave it (don't do the factory reset
> afterwards). I use fixed IP addresses on all the items in my house that
> don't ever leave, including all my hardware Squeezebox players.
Co
squeeze1234 wrote:
> I did this experiment like you suggested (and like garym had suggested
> earlier in this thread.)
>
> 1. I turned off my Squeezebox.
> 2. I disconnected the incoming Comcast ethernet cable from my desktop
> switch
> 3. I forced a factory reset of the Squeezebox
> 4. The radi
Mnyb wrote:
> An experiment, disconect the incoming cable from Comcast but keep it
> conected to the switch, redo the ethernet setup on radio, dhcp will now
> fail and the script for static ip will now be used, set a static-ip in
> the 192.168.x.y range.
> [...]
> Now what would it do if you redo
