Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

16 points

Airport Extreme Talk to Another Airport Extreme

I have two Airport Extreme. One is the newer 3Tb Time Machine which is is my prime router/backup and the other is a 4th Generation Extreme. I have most everything going through the Time Machine but I also have a piece of equipment connected through a Cat5/Ethernet cable to the other Airport Extreme so as to view the information on the connected equipment via the Airport Extreme for internet servicing.

Can Airport equipment talk to other Airport equipment without changing Base Stations? If so, how is the setup made?

Mac Pro (Mid 2012), OS X Mountain Lion (10.8.2), Other Mac's linked to Airport

Posted on Jan 26, 2013 8:03 AM

34 replies

budspwr Author

Level 1

16 points

Jan 31, 2013 4:03 PM in response to Bud Willner

Firefox stated the same: image content not allowed.

Jan 31, 2013 7:26 PM in response to Bud Willner

Bud Willner wrote:

I'll get on my other machine and send the shot want but for now I'll tell you what I got on the DVR: IP 010.000.001.003, Gateway 010.000.001.001, DNS 010.000.001.001. Not at all what I need. I changed the to 192.168.2.???. I don't recall the rest but it didn't lock in.

You cannot port forward to an IP not in the range of the router.. you cannot forward to 192.168.2.x unless the airport also is using that IP.. everything must be on the same IP range.

budspwr Author

Level 1

16 points

Jan 31, 2013 11:06 PM in response to budspwr

It likes JPEG.

Feb 1, 2013 1:37 AM in response to budspwr

There is no http port.. so you are using some software on the remote computer.. not a browser.

But that looks ok.. can the software you use recognise it has to connect to your public IP though.. not internal network.. so it has to connect to 203.202.201.200 (as example only) because you cannot use it if it doesn't link to remote IP.

budspwr Author

Level 1

16 points

Feb 1, 2013 5:53 AM in response to LaPastenague

Note that the previouse snap shot is of Apple Remote Desktop.

This one is of the Presonal Web Sharing. I have no idea where the IP addresses come from. Also, the http I mentioned earlier is in the DVR.

Feb 1, 2013 1:16 PM in response to budspwr

IP address is chosen pretty much at random.. fill that in yourself. And lock it.. do not just use a dhcp address.. it has to be reserved or static in the device. Remember you still cannot have two device port forwarding the same port. So you do not what to forward 80 to any place except your DVR.

budspwr Author

Level 1

16 points

Feb 1, 2013 3:24 PM in response to LaPastenague

I'm not doing well on following restructuring IP and port setttings.

I tried changing the IP address in the TC/TM but only the three digits are replacible. It seems the first three set of numbers are locked in somewhere else. You can see above that 10.0.1.32

If port 80 is used in the Personal Web Sharing, then I should be using 81 (for example) in the DVR. I have tried this but still no success.

Feb 1, 2013 3:43 PM in response to budspwr

Correct you must use DVR set to the right IP range.. you cannot use your DVR on 192.168.x.x if the TC is on 10.0.1.1 YOU MUST SET THE DVR to the same IP range.. ie it must be 10.0.1.x

You can set to dhcp on the DVR and it will get an IP from the TC.. then set the IP to static via dhcp reservations.

Generally you use MAC address as that is different for every device and a good means of identifying it.

budspwr Author

Level 1

16 points

Feb 2, 2013 8:55 AM in response to LaPastenague

LaPastenague,

I really thank you for your perseverance. It seems we have tried to solve a smaller issue in order to solve the main issue of two Airport Extremes talking to each other so as to allow two DRV's to be viewed on a remote computer while on vacation.

I would like to take a moment and put my thinking out here on what I have so far. Some of which may well be bunk.

I have a Time Capsule/Time Machine (TC/TM), two digital video recorders (DVR), and two Spare Airport Express (AE), one being a 1st generation and the other a 4th generation. As I see it, the TC/TM has two functions; TC to record LAN computer systems and changes on to an internal hard drive and ™ to act as a modem to the outer world. TM (acting as an Airport Express) has the necessary IP to do this which is coordinated with equipment on the LAN system of IP addresses.

The DVR is much the same. It has an internal hard drive to record camera(s) functionality. What the camera(s) sees can be viewed historically A second attribute is an internal modem which requires its own IP address in order to communicate with the outer world. The purpose of this second part is to allow viewing on remote computers. It is somewhat sluggish taking 45 second to make the trip from movement viewed by the camera(s) to be viewed on a remote computer. To do this, I feel theTM must function passively/transparently to allow the DVR modem to do its thing. How this is done would seem a bit confusing since it would be modem talking to a modem on the same LAN.

I am reviewing your last entry so this dissertation does not include references to it. I like the idea of DHCP IP range setting in the Airport Extreme.

Best I can tell is the server program the DVR must communicate with is 'eSee' which of course would be Chinese software as would be the server. It would be to my advantage if I could work with an American server/software. The DVR probably would not allow this and I feel the DVR firmware is geared to China.

The retailer states the DVR's must be wired directly to the Apple outgoing modem but at one time I was successful using one AE wired to the DVR. Unfortunately, it wasn't long until it seems a hacker ( my guess China) took down the hard drive and the IP. Everything was in Chinese language. I sent the unit to the retailer for reconstruction. It works fine as a camera recorder but we are now into the phase that doesn't work. The retailer is only partially working the problem. I believe we can do better.

On the second DVR, I plan to use one spare AE to communicate with the TM/AE using a different IP and Port number. This must wait until the first DVR successfully jumps the internet problem.

When working with Portforward, I select Apple as the manufacture of the TM/AE and select Airport Express as the equipment. From this point, the web page goes to a list of program to be forwarded. eSee is not listed. Everything is at a stopping point now. Iplanding does correctly see the IP address of the TM/AE as does the program you suggested. There is no IP address from the DVR.

It would be nice if the DVR's worked like the Smartphones/iPads, etc.

Feb 2, 2013 12:31 PM in response to budspwr

I don't think I can do anything much to help you.

Any units that rely on a server in China.. that is just bad!!

To have software that is unknown using some odd ports.. that is even harder.

I am just not sure how the system works but I would say the eSee is some form of dyndns. I know other brands of cameras that are using this system for dyndns.

The problem is Apple routers do not have their own dyndns system or not one you can easily access and use.

If this all works ok on your internal network.. ie you can watch the recorded pictures on the DVR, then install a VPN router. This will have to become the main router of the system. The existing apple routers can still work in bridge. But using VPN is the only way I can see to get around the problem.. and it will have a dyndns with one of the standard services.

Or pack up the units and send them back and buy DVR units that have standard IP setup and browswer access.

Feb 2, 2013 12:48 PM in response to LaPastenague

Thanks again for all your help even though it was awild goose chase.

I did find a eSee server but did not a trace on it. I also revampt the DHCP in TM and the DVR picked up the change so I know that part is working. The DVR has a dyndns section to work with so will try it.

I guess what I will do is just play around with it for entertainment.

By the way, did what I wrote look ok?

Feb 2, 2013 12:58 PM in response to Bud Willner

By the way, did what I wrote look ok?

I could follow it.. I had no idea the units were supposed to link to some server in China. I would like to know why they do that.. if it provides some teamviewer type of access to the units.. or is just a dyndns.. but it sounds like they should have been for domestic Chinese market and not exported. Needing to link to China for any reason would put them out of my consideration for security immediately. Any of these kind of things can be used two ways.. the reputation of the supplier is often linked to how to use it.. How useful for someone with bad intentions to have access to your home security.. that provides them with far too much info.. plus the ability to wipe whatever they do.

Feb 2, 2013 2:05 PM in response to LaPastenague

You are absolutly right. Please understand that It my feeling about the China server. After all that has happened, i.e., the DVR going down after viewing camera action what else could one think. The best I could do is just use the DVR as a recorder.

Thanks again for sticking with me. If there were a way to give you an 'ataboy'. It's just a verbal award we used during the space age.

Feb 5, 2013 11:58 AM in response to LaPastenague

I'mnot so sure on my Chinese thing nowe

I got it working in Windows7 by the dyndns.org/264 compression. Not sure on the compression number.

The DVR unit I got through with had a password I didn't fool with but the second unit didn't have correct number of caracters. I've got an email in to the retailers for a correct one (we hope).

The second unit is going through an Airport Extreme 4th gen. The only trouble I see is correct settings for port, etc. and maybe the password. I really don't know if the second unit info is passing through the TC because it doesn't pop up in Windows7 IE when the second units IP is used.

Thanks for your help again. Your suggestion on opening up DHCP was the key movement.

Feb 5, 2013 12:23 PM in response to Bud Willner

If you got one working.. then getting the other one working should be possible.. but remember you need a different port setting.. you cannot forward the same port to different destination IP.

If the software is designed without the ability to change ports then it won't work.. you must be able to assign different ports.

And there should be just one NAT router in the network.. never double NAT or you will never get it working.. both DVR must be on the same subnet.. connected to whichever router.. but they must be on a single flat network.

Airport Extreme Talk to Another Airport Extreme