It defaulted to 192.168.1.x I believe. However, I changed it to use 10.0.1.x, which is the standard addressing used by Apple networking hardware and a valid private networking range. I tried connecting the Time Capsule in a variety of ways, to include DHCP. My preference was to use WDS, but it never really worked out. I’m curious what you mean by “hardware confusion.” It seems like you’d have a really poor device if it couldn’t keep track of hardware and IP addresses properly without slowing down. There was no level of “hardware confusion” when I plugged the Airport Extreme into the network.
To be clear, the slow down was independent of the Time Capsule. The Cisco router’s performance bottomed out when I was connecting to it wirelessly and changing the radio mode settings from b/g/n to g/n.
I’m curious what you mean by “hardware confusion.”
For example you have 2 devices that are capable of providing DHCP services (new router and the old time capsule). The time capsule needs a wan address from your new router in your room, and then it probably NATs it’s own DHCP network (your linux server and laptop in your office). If the time capsule happens to be giving DHCP addresses which are the same as the addresses that the router it is connecting to is giving, you’ll get some issues.
RE: IP Scheme by Anonymous :: NR0 :: Show
I’m curious what you mean by “hardware confusion.”
For example you have 2 devices that are capable of providing DHCP services (new router and the old time capsule). The time capsule needs a wan address from your new router in your room, and then it probably NATs it’s own DHCP network (your linux server and laptop in your office). If the time capsule happens to be giving DHCP addresses which are the same as the addresses that the router it is connecting to is giving, you’ll get some issues.