fortiwifi 60d

[benhakim2010]

hi.

it's like half an year that i have this problem. i'm trying with Fortinet support but there is no luck.

after 5-10 min using wifi. it's dead.

there is no ping to the firewall.

PING 192.168.100.254 (192.168.100.254): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3

i try a lot of things. but nothing helps. 

i'm using the last version of FortiOs 5.4

[CyberNorris]

When you turn off wifi and back on, is that on the client or the FG? Is it only one client or all? I've run into Apple devices that will quit working on WiFi on occasion and need to have WiFi turn off and back on.

[benhakim2010]

cybernorris wrote:

When you turn off wifi and back on, is that on the client or the FG? Is it only one client or all? I've run into Apple devices that will quit working on WiFi on occasion and need to have WiFi turn off and back on.

client.

it's happen 5-10 min. on each client. if i connect to wifi after 10min. it's dead.

[CyberNorris]

If you're patient, will WiFi start working again after a while?

Honestly, I occasionally had this on a FWF60D at my house. It usually worked for longer than 10 minutes, but occasionally the client would lose the ability to talk to the WiFi, even though it was still connected. Sometimes it would be fine for days. Other times it was under an hour... I never specifically timed it. Turning WiFi off and back on causes a new DHCP lease (though I seriously doubt it's a DHCP issue). 

I know this isn't your solution, but I now have a FG-60D-POE and a FAP-221C that has never given me this type of problem. I now recommend this setup rather than a FWF.

[benhakim2010]

so you now what i talking about...and it's not only wifi. also LAN.

because i setup it tougher.

my current dhcp lease time is : 604800

 and i also make MAC Reservation with ip to each client.

that's not solution. i paid for this device include wifi.

so why i need this firewall if it's not working as well?

cybernorris wrote:

If you're patient, will WiFi start working again after a while?

Honestly, I occasionally had this on a FWF60D at my house. It usually worked for longer than 10 minutes, but occasionally the client would lose the ability to talk to the WiFi, even though it was still connected. Sometimes it would be fine for days. Other times it was under an hour... I never specifically timed it. Turning WiFi off and back on causes a new DHCP lease (though I seriously doubt it's a DHCP issue). 

I know this isn't your solution, but I now have a FG-60D-POE and a FAP-221C that has never given me this type of problem. I now recommend this setup rather than a FWF.

[CyberNorris]

I only experienced this on Apple clients (iPad and Mac Mini). My wife's Windows laptop never did it.

I understand your frustration ... but never found a solution. It worked much more often than not. When it did fail, if I didn't reset WiFi, it would start working again after a few minutes.

DHCP wouldn't be the issue because the systems already have an IP address that wouldn't expire anytime soon.

I never sniffed to see if traffic was still being sent to the client from the FG or not. I suspect it was. I got to where I blamed the client, not the FG... but never really tested it all that hard.

When a WiFi client fails, you could sniff on the FG to see if traffic from the LAN still goes out to the WiFi. I never experience this on the LAN side.

[benhakim2010]

emnoc wrote:

Qs:

Was it everr working b4

can you downgrade back to  a 5.2.x

What's the  wireless cfg

is allowaccess ping  enable on the FWF wireless interface

Does the wireless monitor show your associated to the FWF60D

did you execute any  diag debug flow  output

1. it wasn't works perfect, i use 5.0/ and then 5.2

looks the same problem

2. yea i allowed wifi ping to FG

3. i try but no luck to catch for issue