AEBS IP Addressing

I am wondering if there is a way to override the default IP addresses of the AEBS.
For example, you can select a schema of DHCP addresses to be 192.168.x.x and assign the third octet to be 254. Can you override the final octet and force the AEBS to be 192.168.254.254?
The previous administrator before I took this job programmed the router at that address and I am switching us to an AEBS, but with LDAP running, several manually configured servers, etc... switching over all the gateway addresses will be a huge pain, and I'm wondering if there is a simpler way to do this.

For example, you can select a schema of DHCP addresses to be 192.168.x.x and assign the third octet to be 254.
Yes.
To change the WAN-side IP address: AirPort Utility > Manual Setup > Internet > Internet Connection > Configure IPv4: Manually, and then, enter the desired WAN-side IP addresses
To change the LAN-side DHCP-provided addresses: AirPort Utility > Manual Setup > Internet > DHCP > DHCP Range, and then, change the third octet to the desired value.
Can you override the final octet and force the AEBS to be 192.168.254.254?
Yes again on the WAN-side, sort of on the LAN-side by adjusting the DHCP Beginning & Ending Address range.

Similar Messages

AEBS, what addresses have been assigned?

I have been going through the Airport Utility over and over and can not
find a way to get a lists of all the addresses that the AEBS has assigned via
DHCP. Is it even possible to find this out? Even just a list of IP addresses
that it has used would be nice?

Open AirPort Utility and click Manual Setup
Click the Advanced (gear) icon
Click the Logging & Statistics tab below the icons
Click the Logs and Statitics tab at the bottom of the window
DHCP Clients displays the MAC address of each connected device on the network along with the assigned IP address for the device.
Wireless Clients displays the MAC address of each device connected via wireless with some other details as well
IF....you do not see a DHCP tab when you click Logs and Statistics, your AEBS is not handling the DHCP services for your network. Another device is.

"another device is using the same ip address.." - iOS devices won't connect to AEBS wifi.

I've got a Motorola modem/gateway - 3360 from WalMart. I have the AEBS working in bridge mode connecting my iMac & Printer fine, but my iOS devices won't connect.
While troubleshooting & trying all types of settings, I was able to get EITHER the iMac or the iOS devices connected to internet, but not both at same time.
Then I noticed I am getting "another device is using the same ip address.." message.
I have changed the AEBS ip address & had been able to get either the iMac or iOS devices working depending on which ip address I use.
BUT now, all my iOS devices dont connect to the internet regardless of the ip address of the AEBS.
All my iOS devices see the network, and accept the network password, but they do not connect to internet, circle just keeps spinning...
Any assistance is GREATLY appreciated.
Thanks for any assistance,
Dave

It looks like may have to go back to square one and delete my network & set it up from scratch if I don't figure it out.
If you do go this route, I would like to make a suggestion for your consideration, and that is to assign static IP addresses to devices that are "permanent" on your network or ones you want to make sure can be reachable at all times. These (again) would be servers, routers, wireless access points, network printers/scanners, NAS devices, etc.
I would recommend the following IP addressing scheme as a baseline and you are certainly free to deviate in any way you see fit to meet your networking requirements:
Reduce the number of IP handed out by DHCP. By default, most routers will provide 100-200 private IP addresses within their DHCP leasing scope. The AirPort, by default, assigns 10.0.1.2 thru 10.0.1.200 via DHCP. Your Motorola may assign 192.168.0.2 thru 192.168.0.150. Either way, I would reduce this to no more than fifty (50) total which should provide you with plenty of addresses even if you are hosting gaming convention at your home.
I use the following IP address scheme for the "permanent" network clients:
Network Printers: 10.0.1.200 - 209
NAS Devices: 10.0.1.210 - 219
Wireless Access Points or routers reconfigured as bridges: 10.0.1.220 - 229
Servers: 10.0.1.230 - 239
With the "permanent" devices pre-assigned with static Private IP address that are outside of the DHCP range, you shouldn't ever get an IP address conflict again.

Why is the AEBS bottlenecking my ReadyNAS devices leading to bad packets and TCP Retransmits?

Bad Packets Unrecovered TCP Retransmits TCP Retransmits w ReadyNAS NV NV+ and Airport Extreme Base Station 5th Generation
I got an Airport Extreme Base Station (AEBS), 5th generation this past November to bring my entire network up to gigE standards and extend my wireless range a bit. I have really liked the AEBS 5th Gen overall since I got it 3 months ago. It was easy to setup and update and things have been noticeably faster. I can also easily take my netbook, laptop, and iPad out to my shop some 80 feet away from my AEBS and still surf rather well wirelessly too. I couldn't do this even with my previous D-Link wireless-n setup.
In December I picked up an old ReadyNAS NV+ to go along with my old ReadyNAS NV. When I finally started to setup the new network for my business in February, I noticed in the logs that I was getting a large numbers of bad packets, TCP retransmits, and unrecovered TCP retransmits. Previously, I had never had errors of any sort with any older network setups using linksys, dlink and netgear routers during the last 6 years.
Eventually cables, switches, and routers can go bad which results in the errors I have been getting so I went through the "Troubleshoot My Performance Problem/Check for Network Errors" section of the link below to try and figure out what was causing my problem.
(http://www.readynas.com/?p=310#Troubleshoot)
My Initial Setup:
Airport Extreme Base Station (AEBS):
- 1 incoming Cat5e from Motorola Surfboard 6120,
- 2 Cat5e connections to my wifes work network with her business computer and VOIP phone.
- 1 Cat 5e interconnecting the AEBS to my wired network on the HP Procurve Switch.
The AEBS manages addresses via DHCP on my wired network for all of my devices on the HP Procurve 14008G Switch:
- 1 to NV
- 1 NV+
- 1 MacMini 2010
- 1 MacMini 2005
- 1 networked Epson R-3000 printer
1. Simple things first. Since I have always made all my own Cat 5e cable I figured I'd better get some better(?) cabling strait away. I went ordered new Cat 6 and Cat 6a cables to connect the NV, NV+, and my main Mac to the switch and connect the switch to the AEBS. The errors kept coming.
2. Then I separately connected each NAS unit directly to my computer by setting up the static IP on my computer first. Once I reconnected each ReadyNAS with the computer directly they defaulted to a static IP. Neither NAS had errors.
(http://sphardy.com/web/readynas/how-to-direct-connect-to-your-readynas/)
3. Errors were coming from either a bad Procurve 1400 switch or a bad AEBS. I hooked everything directly to my Airport Extreme and got lots of errors.
4. I decided to check the switch also. I altered each ReadyNAS's default static IP to one of my choosing individually. Then I hooked both ReadyNAS units to my HP Procurve 1400 switch. I hooked the switch directly to my computer and got no errors from either NAS. I continue to get no errors the next day.
5. When I first ran my tests I had Jumbo Frames turned Off. Currently, Jumbo Frames are On and there are still no errors and seems to be no slowness either.
Conclusion:
The Airport Extreme is the bottleneck causing the errors in my network.
Perhaps there is something I can alter which will rid me of the errors, but this type of error makes the AE seem to be pretty shoddy. A newer state-of-the-art router should not be bottlenecking my rather archaic slow network devices. Apparently, the 4th Gen AEBS's couldn't do Jumbo Frames, but this current model is supposed to, but I see no setting for changing the MTU.
Questions:
What could be causing the bottleneck?
Do I have a bad router?
How could I analyze this problem?
Has anyone else had similar issues and if so how were they resolved?
Current Setup:
All of my computers and NAS devices are hooked to my Procurve Switch each with its own Static IP.
The switch is working flawlessly with no Errors.
The network printer is now wireless and connected via the AEBS.
I am using wireless-n to connect to internet via the AEBS on my main machine.
I am sharing the internet connection with the other Mac Mini on the switch and any other machine I plug into the switch (not ideal).
Problem is:
I am not a systems administrator and don't really want to tinker with setting up Static IP's for the machines I hook and unhook to the switch.
I want the AEBS to manage addresses via DHCP so everything accessing my router will mindlessly be able to access all things on my network.
Can the AEBS be made to not produce errors or do I just have a lemon.

Hi Bob,
That's the strange thing. When I had both GHz channels working on one SSID, once in a while my iMAC would pick the 5 GHz channel (44 seems the best for me). I always use channel 1 for 2.4 GHz because I get the fastest speeds with it.
When the iMac would pick 5 GHz, the slowdown was very obvious. As I explained in my (long) first post, I immediately felt the difference. Now the $50K question - since the 5 GHz channel at that point was stronger than the 2.4 GHz one, why wasn't the speed faster? Why was it so slow compared to 2.4 GHz? That's what rattling my brain. If the 5 GHz signal's strong enough to get picked by my iMac, then why isn't there a commensurate speed increase? There must be something else going on here besides signal strength. If the 5 GHz spec says that I must have full strength to get 5 GHz speeds, then that makes sense. But I think it doesn't, that's why I believe I have a configuration problem somewhere, or a faulty AEBS.
I might add that my firmware's up-to-date in the AEBS and AX, and Airport Utility too.
I think heading to 4Runner's camp - even with high signal strength (and I would consider 3 of 4 bars high), the 5 GHz speeds aren't showing themselves.
Here's some snap's of my AEBX's setup:
I think my configuration's fine, although I've tried so many different options, I'm a little confused, but I know that changing the Multicast Rate doesn't have any noticeable effect on the speed. I also have "Use Wide Channels" checked, but as I said, the 5 GHz band is awfully slow for using both channels. I have set "N" only, so no "G" clients to slow it down.
Mind boggling!

Should I try to recyle my old AEBS to join a TC-based WDS network?

Actually, I tried to do this -- but with scary results. My query is:
1. Should I try again?
2. Is it worth the trouble and the potential trade-offs?
My stereo system in the far side of my home from the ISP access point where the TC sits and so the network needs a substantial boost in order to reliably play music -- and, perhaps, one day video-- wirelessly there.
I've got four legacy (g-level) AE's in addition to the old antenna-enhanced AEBS and, now, mated with a new TC.
I've set all this up as a WDS WPA/WPA2 network per Apple's sketchy documentation. (No point in dealing with Apple support; they max out help at three units on the network.)
Anyhow, one AE currently serves as a remote while the remaining 3 AE's have simply joined the AirPort network to pump out music in three separate rooms to three separate hi-fi systems. (I assume they are also extending the network's overall reach, as obviously is the solo AE remote, although I am not at all sure about this aspect.)
In any event, I thought, what the heck, why not also connect the old g-string AEBS to the network as a second remote. I duly added its MAC address to the TP's WDS table and made sure that its SSID, passwords, channel, etc. all matched up. I did not add the AEBS MAC address to the AE remote's table since I sought to use as the TC as a unitary hub.) Airport Utility found and set up the AEBS. But, in the process, AU could no longer discover any of the remaining units that had just been there. It took lots and lots of fiddling just to get them back as they had been working beforehand.
Query: Is there a sequence of loading that must be followed for such a dual remote setup? The AEBS would, I would hope, provide me with a solid -- instead of iffy signal -- to my main music listening room. (It packs more wireless punch than the new antenna-less TC.) How can I do this, however, safely -- without losing contact with my prior installed green-lighted AE units?
Thanks.
Message was edited by: ajglass

I would save the current configuration for each device from Airport Utility to file. That way, you can always reimport the settings and get everything back to the current situation quickly if you need to.
You say you didn't add the AEBS to the AE's remote table, but if you have a single network with the TC as the single hub, should the AE even have a remote table? It is configured as a WDS remote, correct?
- cfr

AEBS not acting normally

I’m having some problems with my AEBS network. My server is no longer accessible via VPN.
I have a Comcast cable modem, that goes into an AEBS, that goes on to a switch. I updates the AEBS with the latest Apple software/firmware update sand the system has gone haywire. I would appreciate any help in the resolution.
The Comcast cable modem has a gateway address of 10.1.10.1, the router address is 10.1.10.1
The AEBS used to have an IP address of 10.1.10.162, but after upgrading it with the Apple software/firmware5.7 update, when I go to Airport Admin Utility, the AEBS shows an IP address of 254.128.0.0. And I can’t log into it, If I select OTHER, then a drop down window with IP address 10.0.1.1 shows up. If I enter my AEBS password it opens. In the summary screen it shows the AEBS IP address as 10.1.10.46 with a router address of 10.1.10.1. The AEBS is set to “Share a single IP address using 10.0.1.1 addressing”.
Now for the server. The server shows an IP address of 10.0.1.7. The server had been set to have a manual address of 10.1.10.99. The Comcast cable modem has port forwarding set so VPN access is forwarded to IP address 10.1.10.99 , the server. Of course it does not work now because of the server address of 10.0.1.7. if I set the server manually to 10.1.10.99, it does not have internet access.
HELP! What the heck happened to my AEBS and how do I fix this, so we can have VPN access to the server (OSX 10.3.9)?
I run the Ethernet cable thru the AEBS to the switch so that the both the Comcast firewall and the AEBS firewall protect the server. Am I being overly cautious? I could connect the server direct to the Comcast modem but then it would be on the other side of the AEBS and I think the office computers that attach to the network thru the AEBS would not be able to see it and be cut off from their files.
Comcast has given me a static IP address I can use for the server, but is the server firewalll strong enough to protect it?
I recognize the issue is in the IP addresses but not sure where to start.

This can happen if adware is installed without your knowledge.
Updating tO OS X Yosemite is not necessary.
1. Use free AdwareMedic to remove adware
    http://www.adwaremedic.com/index.php
   Install , open, and run it by clicking “Scan for Adware” button   to remove adware.
   Once done, quit AdwareMedic.
             or
   Remove the adware manually by following the “HowTo” from Apple.
   http://support.apple.com/en-us/HT203987
2. Safari > Preferences > Extensions
    Turn those off and relaunch Safari.
    Turn those on one by one and test.

AEBS system gone haywire -HELP!

I’m having some problems with my AEBS network. My server is no longer accessible via VPN.
I have a Comcast cable modem, that goes into an AEBS, that goes on to a switch. I updates the AEBS with the latest Apple software/firmware update sand the system has gone haywire. I would appreciate any help in the resolution.
The Comcast cable modem has a gateway address of 10.1.10.1, the router address is 10.1.10.1
The AEBS used to have an IP address of 10.1.10.162, but after upgrading it with the Apple software/firmware5.7 update, when I go to Airport Admin Utility, the AEBS shows an IP address of 254.128.0.0. And I can’t log into it, If I select OTHER, then a drop down window with IP address 10.0.1.1 shows up. If I enter my AEBS password it opens. In the summary screen it shows the AEBS IP address as 10.1.10.46 with a router address of 10.1.10.1. The AEBS is set to “Share a single IP address using 10.0.1.1 addressing”.
Now for the server. The server shows an IP address of 10.0.1.7. The server had been set to have a manual address of 10.1.10.99. The Comcast cable modem has port forwarding set so VPN access is forwarded to IP address 10.1.10.99 , the server. Of course it does not work now because of the server address of 10.0.1.7. if I set the server manually to 10.1.10.99, it does not have internet access.
HELP! What the heck happened to my AEBS and how do I fix this, so we can have VPN access to the server (OSX 10.3.9)?
I run the Ethernet cable thru the AEBS to the switch so that the both the Comcast firewall and the AEBS firewall protect the server. Am I being overly cautious? I could connect the server direct to the Comcast modem but then it would be on the other side of the AEBS and I think the office computers that attach to the network thru the AEBS would not be able to see it and be cut off from their files.

I'm running out the door, so don't have time for a detailed response.... Just this:
You should run NAT only in one box (the ISP's router or the AEBS).
Your network should be reconfigured so that either the ISPs router/modem does your NAT or the AEBS (with a pblic IP on the AEBS WAN port)
In doing this, if you change the IP of your server, be sure to use the changeip script (man changeip).
Post questions if you have any.
I can expand upon this later.
Jeff

Set Date & Time Automatically

I have an Airport Extreme tied to a cable modem. I also have an Airport Express setup using WDS (remote base station). On both the Exteme and the Express I have checked "Set Data & Time Automatically" and selected "time.apple.com".
The Extreme finally has the correct date and time. (And I assume year.) However, the Express keeps loggin this error; "No address for NTP server time.apple.com." (I am using the "AirPort Management Utility" to view the logs for each Airport.)
I tried typing in the raw ip address for time.apple.com but it didn't change anything. Other then this minor issue both Airports are working fine.
What am I doing wrong?
Mac OS X (10.3.9)

Your setup is similar to mine but my Express is in Client Mode not WDS. Here are some of the log entries I see. After it powers up the time is wrong and it reports the same as you of "No address for NTP server time.apple.com." but after a short time it does!
Dec 31 17:00:00 Severity: 5 Joined BSS [my AEBS-MAC address]
Dec 31 17:00:01 Severity: 5 Initialized (firmware 6.3).
Dec 31 17:00:11 Severity: 3 No address for NTP server time.apple.com.
Dec 31 17:00:11 Severity: 5 Internet configuration leased (host 10.0.0.5/24 gateway 10.0.0.1 dns1 [my DNS servers] lease 1080).
Jan 11 06:24:04 Severity: 5 Clock synchronized to network time server time.apple.com (adjusted +1136985823 seconds)
Jan 11 06:27:31 Severity: 5 Disconnected from network.
Jan 11 06:27:41 Severity: 5 Joined BSS [my AEBS-MAC address]
Jan 11 06:27:49 Severity: 5 Internet configuration leased (host 10.0.0.5/24 gateway 10.0.0.1 dns1 [my DNS servers] lease 1080).

Public and Priviate network from same cable modem - more questions please

A couple of weeks ago I asked about having both a privite network and a public wireless network that would work from one cable modem. The requirement is that the private network not be seen or be "hackable" by users on the public network.
Duane gave us the approach to use and we think we have it right, but because the security of our private net is so important, we want to make sure. We will not do the public network if the security of our private network is in danger.
Here is how things look:
Cable modem --> Router 1 WAN port
Router 1 regular ports --> Private Network -and- Router 2 WAN port
Router 2 regular port --> AirPort Extreme WAN port
We have our public network set up as WPA Personal and we broadcast the network name. The password for this network will be shared wiith users as they enter our public area where they can use their PCs. The default login/password on both routers and the AirPort Extreme have been changed. Connecting via AirPort to the public network I can see Router 2 but not Router 1 or any of my computers, printers, etc. when I browse the network via the Finder.
Do I have it right?
Does this setup give users on the public network any way to get to my private network, computers, and files? Are there any tests/experiments that I could run to further validate this setup?
How secure is it?
Am I asking for problems by offering a public network that shares some of the resources of the private network - modem, MAC address, IP addresses of routers, etc.
From the public net we have attempted to use the IP addresses of the computers on the private network without success.
The best answer I could receive is that there is no way to hack the private from the public. If this is not the answer, how secue am I.
Tim

When you state "Router 1 regular ports(8) feeding Private Network..." do you mean that there is another private router or are the private clients directly connected to router 1?
If you have a private router, the public devices connected to the AirPort Extreme base station (AEBS) could address and reach anything on Router 1 including the private router's WAN side.
The firewall in private router should block any of the public access to clients of private router. So any traffic from private router should be safe as long as the public has no physical access to router 1 nor router 2's WAN port.
If the private clients are directly connected to router 1, then the public clients can directly access any of your private clients. The traffic among private clients and from private clients to Internet would be secure (as long as my previous note about physical access is true).

AEBS and Comcast (can I clone a MAC address?)

I am currently an Earthlink DSL subscriber. I love Earthink, but DSL is giving me all kinds of trouble. Covad owns the lines in my area and they are aweful... in any case...
I am going to switch to Comcast Cable Broadband. I have set up many people in the area with Comcast and a wireless router. It seems that Comcast does not do this everywhere, but in my area they "bind" to the MAC address of the NIC that you use to setup the connection (MAC Address Authentication).
If I want to use NAT on my router, it will not work unless I can spoof the MAC address. This is easily done with a Netgear or Linksys router. This does not seem to be a setting in the Airport Admin Utility.
Is there a hidden setting or a third party utility that I can use for spoofing the WAN MAC address on my Airport Extreme Base Station?
I could switch to a different wireless router or put a small router between my Cable modem and the AEBS, but I would rather not add a layer of hardware or switch hardware if I don't have to (I really like my AEBS).
Thanks for any advice.
WT

It should be possible, if manual registration of the MAC address of connected equipment is required on Comcast's service in your area, to get them to either clear the binding to allow a new device (ie the Base Station) to associate with the connection, or to ask them to manually register the MAC address of the Base Station's WAN port. I realize you would rather not have to deal with Comcast's tech support people, but (as pointed out above) the only other option is to use a different wireless router that does support MAC address cloning.

AEBS associates client hostnames with DHCP-supplied IP addresses?

Hi,
I have 3 Mac's, a Windows and a Linux machine on my home network.
I'm looking at getting an Airport Extreme Base Station.
I understand it does DNS forwarding and caching out-of-the-box.
I'd love to know if the Airport Extreme when acting as a DHCP server for the network will associate the client host names with the IP addresses it dishes out.
In other words, if I name my iMac "slartibartfast" will the AEBS pick up on this, and allow me ping and ssh to slartibartfast by name from the other machines on the network?
Note that I'm not talking about Bonjour here - I'm talking about DNS names.
I believe on the Mac to give it a DNS host name I have to do
scutil --set HostName slartibartfast
Thanks,
Sarah

Unfortunately, Apple dropped a number of features and functions in the "upgrade" to AirPort Utility 6.x in Lion and Mountain Lion.
If you are still running Lion, download and install AirPort Utility 5.6 for Mac OS X Lion to get those features back. Just keep both AirPort Utility 5.6 and 6.1 on your Mac and use the one that you need.
If you are using Mountain Lion on your Mac, things get more complcated since Apple will not officially allow you install AirPort Utility 5.6 on that operating system.
The workaround is to use a utility like Pacifist to manually extract the application and then manually install it in the Utilities folder. It will run fine this way.
More details here:
http://www.macworld.com/article/1167965/mountain_lion_and_the_ancient_airport_ba se_station.html
Another workaround....if you have Time Machine backups.....is to back in time to locate AirPort Utility 5.6 and restore it to the desktop. Then drag it into the Utilities folder.

[Windows] list MAC addresses of ethernet-connected devices to AEBS?

I have an ethernet connected device (among others) that is running headless, so I need to create a static IP ("DHCP Reservation") based on the MAC address to SSH into the device.
This device is connected to my AEBS with an ethernet cable, and I cannot figure out where in the Airport Utility app lists MAC addresses connected by ethernet. This is very easy if it were a wirelessly connected device but it appears the Airport Utility -> Advanced -> Logging and Statistics tab -> "Logs and Statistics" only holds information of wirelessly connected devices.
I am connecting to my AEBS with the most updated Airport Utility for Windows v5.6.1
So, where do you find the MAC addresses listed of ethernet-connected devices using Windows Airport Utility?

but it appears the Airport Utility -> Advanced -> Logging and Statistics tab -> "Logs and Statistics" only holds information of wirelessly connected devices.
That would be true if the AEBS is configured in Bridge Mode. In this case, another device....you likely call this your modem....is providing DHCP information to all connected devices. That is the device where you need to locate MAC Addresses and set up Static IP addresses.....not the AEBS.
If your AirPort Extreme is in charge of providing DHCP services, then the window in Airport Utility will have a DHCP tab, which will display all of this information for both wired and wireless devices. If you don't see a DHCP tab....this is yet another confirmation that the AEBS is in Bridge Mode.

MAC addresses of ethernet-connected devices to AEBS?

I have an ethernet connected device (among others) that is running headless, so I need to create a static IP ("DHCP Reservation") based on the MAC address to SSH into the device.
This device is connected to my AEBS with an ethernet cable, and I cannot figure out where in the Airport Utility app lists MAC addresses connected by ethernet. This is very easy if it were a wirelessly connected device but it appears the Airport Utility -> Advanced -> Logging and Statistics tab -> "Logs and Statistics" only holds information of wirelessly connected devices.
I am connecting to my AEBS with the most updated Airport Utility for Windows v5.6.1

but it appears the Airport Utility -> Advanced -> Logging and Statistics tab -> "Logs and Statistics" only holds information of wirelessly connected devices.
That would be true if the AEBS is configured in Bridge Mode. In this case, another device....you likely call this your modem....is providing DHCP information to all connected devices. That is the device where you need to locate MAC Addresses and set up Static IP addresses.....not the AEBS.
If your AirPort Extreme is in charge of providing DHCP services, then the window in Airport Utility will have a DHCP tab, which will display all of this information for both wired and wireless devices. If you don't see a DHCP tab....this is yet another confirmation that the AEBS is in Bridge Mode.

AEBS allocates "high" IP address. Why?

I've had a lot of issues with my AEBS recently - thanks for all who have helped with my previous posts.
This may be an issue, or it may not, but I'm trying to understand why my AEBS allocates DHCP IP addresses at the top of the range and then appears to work backwards... In other words it starts with10.0.1.199, and then allocates .198, .197 etc.
In the past, I'm certain it started with 10.0.1.2 and worked upwards using 1.3, 1.4 etc.
My DHCP beginning address is set to 10.0.1.2
Ending address is 10.0.1.200. If I change this to, for example, 10.0.1.50, it will allocate .50 first, then work backwards.
I've reset the AEBS to factory defaults with all ethernet and wireless clients off. Same result.
Is this usual, or is it indicative of some other issues? My AEBS randomly crashes, so I'm trying to eliminate every possibility.

My apologies if my question was unclear.
I was trying to establish if all AEBS do this, or if it was indicative of a fault with my constantly crashing base station.
Do all AEBS do this?

Help Needed - Remote Disk Access via MobileMe for AEBS

OK, I've done a lot of reading in this forum, but didn't find a resolution to my problem.
Here are my configuration:
1) ADSL Router(2Wire 2700HGV-2) in bridged mode
2) Airport Extreme Base Station (Simultaneous Dualband) with 7.4.1 firmware acting as the router using PPPOE
3) External USB disk formatted using Mac OS format attached to AEBS
Working:
1) Within the LAN, can access the disk without any problem
2) Over the WAN, Back to my Mac works fine for all my Mac computers
Not Working:
Over the WAN, I can see the AEBS in the shared section, however, upon clicking it, it always tells me that the connection failed after about 30 seconds, even when I try to use "connecting as".
Anyone has tried this feature and it worked? Really appreciate if you can help as I am going to be on trip soon and I wish to access the disk from Internet when I am over there.
Thank you!

Hi rekeno
Thanks for your post. I have the exact some problem. I'm sitting at work with my MacBook. At home there's my Airport Extreme and a Mac Pro.
I can see both in my "Shared" section AND they also have different IPv6 tunnel addresses:
[15:07 root@pm1] ping6 macpro.XXX.members.mac.com
PING6(56=4088 bytes) fd22:3569:a8da:4c12:217:f2ff:fed4:6de0 --> fd44:bbdd:fce3:3be9:21d:4fff:fe4b:b80
16 bytes from fd44:bbdd:fce3:3be9:21d:4fff:fe4b:b80, icmp_seq=0 hlim=64 time=54.748 ms
Works.
[15:14 root@pm1] ping6 airport.XXX.members.mac.com
PING6(56=4088 bytes) fd22:3569:a8da:4c12:217:f2ff:fed4:6de0 --> fdfe:d7a4:759a:a360:21b:63ff:fef5:30a2
^C
--- airport.XXX.members.mac.com ping6 statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
This times out.
Interestingly I can use Screen Sharing to my MacPro and do the same:
[15:17 mau@macpro] ping6 airport.XXX.members.mac.com
PING6(56=4088 bytes) fd44:bbdd:fce3:3be9:21d:4fff:fe4b:b80 --> fdfe:d7a4:759a:a360:21b:63ff:fef5:30a2
16 bytes from fdfe:d7a4:759a:a360:21b:63ff:fef5:30a2, icmp_seq=2 hlim=64 time=0.721 ms
This works AND it uses the SAME IPv6 address.
I have also checked that my IPv6 tunnel configuration is allowed in the Airport Utility.
Do you see the same behaviour? Can you run the same commands?
Thanks a lot!
Patrick

AEBS IP Addressing

Similar Messages

Maybe you are looking for