Yes, that's the first thing I was suspicious about. If it doesn't do DHCP it also probably doesn't do NAT, and is in fact just a bridge, and in the end your IP must be configured by (or at least to fit within) the external network you're trying to connect to.
There may be a two-step shuffle involved -- maybe you have to connect to a default IP for the box to perform initial configuration? But after that revert to DHCP to get an IP from the network you're bridging from?
However, I've never worked with a wireless bridge box (I've implemented bridge code for ordinary router boxes, and was a voting member of the 802.1d committee when bridging was being standardized, but that's not actually of any use diagnosing this problem in a much later-generation device!).
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2011-09-01 01:56 pm (UTC)There may be a two-step shuffle involved -- maybe you have to connect to a default IP for the box to perform initial configuration? But after that revert to DHCP to get an IP from the network you're bridging from?
However, I've never worked with a wireless bridge box (I've implemented bridge code for ordinary router boxes, and was a voting member of the 802.1d committee when bridging was being standardized, but that's not actually of any use diagnosing this problem in a much later-generation device!).