Heres my setup

Cable Modem --- Linksys BEFSR41 --- Minitar and PC 1 connected

Linksys has a static ip of 192.168.1.1, Also runs BPA Login, and DHCP
Minitar has a static ip of 192.168.1.2
PC1 connected VIA CAT5 gets a DHCP IP
PC2,3,4 connected VIA Wireless Does not get a DHCP IP


2 days ago every one would get a DHCP IP, Suddnly no wireless clients get a DHCP IP
No settings have changed

Minitar Settings

----------------

* Management IP
IP Address : 192.168.1.2
Subnet Mask : 255.255.255.0
Gateway Address : 192.168.1.1
DHCP Server : DISABLED

--------------------

Any reason why ?
I've tried a factory reset, turn off for 12 hours, etc etc

for not i am running them all on static IP's\


*edit 2.53 code

Hi Ice

No idea but it sounds like the MNWAPB did something strange and the DHCP server disabled itself.

I personally have not seen this happen however as I can see the IP addresses are not correct to suggest a factory reset was performed as it would have been on the 192.168.2.* subnet if that was the case.

After the factory reset though the DHCP server would have been enabled only.

I just wonder if anyone else has seen this.

Also were the passwords on the unit the default password. Only assuming but is there anychance someone was on the unit playing with settings?

SB

Strange that it was working and now is not. can you make the minitar a DHCP client of the Linksys? If you can then it will set "nameserver 192.168.1.1" in /etc/resolv.conf and should then forward DHCP ANNOUNCE packets from the wireless clients through to the Linksys.

You should also be able to assign a static IP for it so it always has the address you want.

As you can see.. i said the Linksys is the DHCP
and the minitar has a Static IP

And after a factory reset I change the ip settings back

Ah, yes I can see the Minitar has a static IP.

If you configure it as static from the Minitar configuration menu then it will not request an address from the Linksys and not get any of the other goodies that come back in the DHCP OFFER response (A DHCP response contains a bunch of other information apart from the address the requestor should use, netmask, list of routes, DNS servers etc.)

I suppose I should have been clearer in my post, what I was suggesting was to configure the Linksys to server a static address to the Minitar so that when it made a request it got back the address you wanted it to get + all the other information the Linksys can provide.

The other thing you could try is to also have DHCP on in the Minitar and serve a different subset of the available addresses than the Linksys, you have plenty to play with

Hi all,

I've been watching this and similar threads with interest, as I have a similar setup to Ice_Cold, yet haven't had any problems.

Current setup:

ADSL Modem
|
Netscreen 5GT (firewall/router, static IP on LAN side) <--- DHCP Server
|
10/100 Switch
|-----MNWAPB (static IP) <-wireless-> Laptop (requesting DHCP from Netscreen)
|
|----- Various PC's (all static IP's)

I've yet to have a problem with the DHCP requests not getting through...
The Minitar is running as an AP and is using the as-supplied 2.39 firmware (I haven't got around to upgrading it yet).

I wonder if this problem is a hiccup in the later firmwares?

Andrew

Still having the problems Ice Cold ?

S

Yes monkey... Still am

Only way to track something like this down is through packet captures on the wireless client and somewhere on the LAN segment (monitor port if you have one for example) so you can see if it's a problem with the requests or the responses.

S.