Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Briant73]

I have a new audio/video receiver that has Apple Airplay functionality built in.  Now the Airplay allows any Iphone/pod/pad/tunes device/computer on the same network to route music to the receiver without plugging in the device directly.  Great concept but the execution allows any computer or iphone in my house on the network to take over my receiver with no questions asked and start playing. 

So far I have failed to find a way to restrict or shut off Airplay on the device itself (other than disabling it's network).  So now I am asking for help if there is anyway through networking or my DIR-655 router to control/restrict this access?  What I would like in a perfect world is to keep all computers and wireless Apple I devices from connecting to the unit unless I allow it for that particular device/computer.  In an imperfect world I would accept just blocking wireless devices from it but still allowing them full network connectivity otherwise.

Some things I have thought of - Can I use static addressing for the A/V receiver but put it on a different subnet then what my router is set to? 
Is there some network control in the firewall that may limit access to the A/V receiver?

[FurryNutz]

If the router is giving IP addresses to the devices connected thru the AV rcvr or if they are connected to the 655, then set up Reserved IP addresses ON the router for ALL devices, Then setup a schedule for times you would like them to be connected and have access. Then use access control to apply the control policy to the devices with the scheduling you set up.

[Briant73]

If the router is giving IP addresses to the devices connected thru the AV rcvr or if they are connected to the 655, then set up Reserved IP addresses ON the router for ALL devices, Then setup a schedule for times you would like them to be connected and have access. Then use access control to apply the control policy to the devices with the scheduling you set up.

So if I'm understanding correctly, have all devices from dhcp inlcuding the A/V receiver have a reserved address (already done) and then -
Setup schedules for those devices (access all the time for most devices)
Access Control can then block say 2 computers and 3 iphones from accessing the A/V receiver?

I wasn't sure I could control devices (iphones/computers) on the network talking to another device (receiver) on the network through the dir655.

[FurryNutz]

Access Control only manages devices connecting to the internet.

[Briant73]

Access Control only manages devices connecting to the internet.

(AVR=audio video receiver)
So then that wouldn't work for me since what I'm trying to do is this
Disable network devices from connecting to AV receiver (connected to network), since Apple Airplay allows anyone with a network airplay compatible device to connect and use the receiver and there is no disable function on the AVR.
I am looking for a way to keep the AVR communicating to the internet/network but block those devices from communicating to it.  That is why I thought about different subnets.

[FurryNutz]

Does this AVR do wired or wireless? If wireless can the Wireless be shut off on the AVR?

Only other think I might suggests would be adding a 2nd AP to your network. Something like this:
ISP modem>655 router<Connect all devices that you dont' want to connect to the AVR to the 655.
                              <>655 router to DAP model device<AVR to DAP. Use a different IP address pool and sub net mask on the DAP to AVR.

You could even swap, connect AVR direct to 655 and all other devices to DAP.

DAP - http://amplifi.dlink.com/products/DAP-1525

[Briant73]

The AVR is wired.

[FurryNutz]

I might go wired with the AVR direct to the 655 and then install a DAP on the 655 and connect everything else to the DAP.

Let us know what you figure out.

[Briant73]

I might go wired with the AVR direct to the 655 and then install a DAP on the 655 and connect everything else to the DAP.

Let us know what you figure out.

That might work if I wanted to rewire everything because right now the 655 is in another part of the house with one line connecting from it to a 10/100/1000 dlink swtich near the AVR.  I just remembered I have an old 10/100 linksys wrt54g router just sitting doing nothing.  Any thoughts on using that?

[FurryNutz]

Set that Linksys up as an AP.  

http://forums.dlink.com/index.php?topic=40856.0

[Briant73]

Set that Linksys up as an AP.  

http://forums.dlink.com/index.php?topic=40856.0

Thanks I probably will have more questions but first need to make sure the linksys works.

[FurryNutz]

Keep us posted.

[Briant73]

Finally got the linksys wrt54g v5 out of storage and booted it up, checked it out, loaded latest linksys fw and everything seems OK on it.

So what I have done so far is follow http://www.smallnetbuilder.com/lanwan/lanwan-basics/30740-how-to-use-a-router-to-add-network-ports?start=1  best I could except for the last two steps so far.
1) Changed linksys from gateway to router
2) Gave the linksys a different third octet static ip address for the router
3) Set it to have it's own dhcp server on that
4) set the linksys wan ip to the Dlink subnet but outside it's dhcp server range
5) Disabled the firewall on the linksys also disabled wirelsss

What I haven't done is set up a port forwarding rule on the dlink or plug it altogether because I wanted to check if this sounds right before I move on to the next step. 
I will be doing the following for network plug in cable mode, dlink 655, cable to dlink switch, cable from switch to linksys, AVR device plugged into linksys.

[FurryNutz]

No sure if you need to use the WAN Ports vs LAN ports on the Linksys or not like DLink does. DLink routers don't use the WAN port and theres really no need for it when converting routers into APs. Just use the LAN port in back to connect between the Linksys and the DLink. Turn off everything on the linksys accept for wireless, since you don't need those features or will be using them. You'll be good.

[Briant73]

No sure if you need to use the WAN Ports vs LAN ports on the Linksys or not like DLink does. DLink routers don't use the WAN port and theres really no need for it when converting routers into APs. Just use the LAN port in back to connect between the Linksys and the DLink. Turn off everything on the linksys accept for wireless, since you don't need those features or will be using them. You'll be good.

I'm a bit confused now so if you don't mind a few questions
First an overview of my current network
Cable modem connects to my Dlink 655 router on the wan/internet port --  then I have 3 dlink gigabit switches conected to the 655 lan switch, and then various wired devices connected to the switches.
I am running dlink 655 wireless N for all wireless devices
My Audio Video REceiver is WIRED not wireless.
My Apple devices are both wired (itunes on computers) and wireless

So either I totally misunderstood what direction you are going for with or something I didn't convey correctly.  What I want to do is if possible is remove my Audio Video Reciever from being found by Airplay devices (itunes on computers/wirless I devices) but still allow the AVR to have network/internet access.

I thought what you were suggesting is using the Linksys between the AVR and the gigabit switch it's connected to to put it on a different subnet.  

So what I have done in preparation is the following
1) Changed linksys wrt54g from gateway to router
2) Gave the linksys a different third octet static ip address for the router
3) Set the linksys to have it's own dhcp server on for that octet set in step 2
4) set the linksys wan ip to the Dlink subnet but outside it's dhcp server range
5) Disabled the firewall and wireless on the Linksys

I have not plugged it in or set up port forwarding on the Dlink for the linksys.  

I figured I'd go over everything again to best explain how I want things to be, what I'm currenty doing and what I was understanding from what you were saying. 

I'm new to this and thank you for being patient so far with me.