|
I don't know the details of the equipment. The "usual" reasons for not doing what you've suggested are...
A routers job is to "route" between distinct networks. It effectively "joins" networks together.
Connecting as you've suggested creates two LAN's in your infrastructure (incidently, two separate IP subnets (address) ranges would be required.)
Routing is a computationally more complex process than "switching" so traffic between devices on each LAN will be a bit slower routed than switched.
Thence, SOHO routers usually implement a firewall/NAT between their WAN and LAN ports. So devices on your "time capsule" LAN wouldn't be able to "see" devices in the "airport" LAN. Also there would be a routing issue in the time capsule as it would need something called a "static route" to find the airport LAN. (Some SOHO routers won't let you define static routes.)
Thence, with the same SSID you'd have problems when roaming as your clients would have to grab a new IP address every time they roamed, which is a bit ugly and time consuming.
As I say, I don't know your kit, but I'd suspect that setting the airport in to "bridged" mode has effectively turned off all the routing, firewall, NAT, etc. etc. and turned the "WAN" port into another "LAN" port essentially making it into a 4 port switch and Wifi combi, which is what we advocate above.
It should be easy enough to tell: If you examine the IP address, subnet mask and default gateway of some devices connected to both your time capsule and airport networks, we can tell whether they are participating in a single LAN or separate ones. |
|