Skip to main content
rgrove
rgrove
New Member
January 13, 2022
Question

IOT client unable to connect to Internet

  • January 13, 2022
  • 3 replies
  • 3166 views

Hello, 

 

I recently installed my newly obtained Fortigate 61E, and updated to 7.0.3. I setup an IOT VLAN for my IOT devices. All of the devices can connect to the internet just fine, except for one exact device. After rebooting the device, that device will connect to the internet for a little while, then appears to lose connection. The entire time, the device can be pinged on the LAN with it's DHCP reservation. Looking for any recommendations, as I'm a bit new to this. 

 

Thanks in advance!

3 replies

bondnylium
bondnylium
New Member
January 14, 2022

Hi, I'm a new too. I had thought this was more of a logging issue, since logs showed "detected-only", but then I noticed that the action was "content-disarmed" so I looked in the CLI. Trying to turn content disarm "On" in the GUI gives me the error "Value conflicts with system settings.". So I can't use the GUI to turn this on and off.

 

 

 

 

driving directions

Yukilosa
Yukilosa
New Member
September 21, 2023

Pinging the device on the LAN where it has a DHCP reservation is possible at all times. I'm looking for suggestions because I'm just starting off. amanda the adventurer

mle2802
Staff
mle2802
Staff
September 22, 2023

Hi @Yukilosa, 

Can you execute the following command on FortiGate:

diag debug reset
diag debug flow filter addr X.X.X.X (IOT device IP)
diag debug flow show ip en
diag debug flow show func en
diag debug console time ena
diag debug ena
diag debug flow trace start 999

Regards,
Minh




Kush_Patel
Staff
Kush_Patel
Staff
September 23, 2023

Hello,

 

it would be a good idea to run those commands on CLI when IOT device can reach the internet and when it can not to troubleshoot the issue.

 

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-First-steps-to-troubleshoot-connectivity/ta-p/192560

 

Regards.

ElizabethDavies
ElizabethDavies
New Member
June 3, 2025
@Kush_Patel wrote:

Hello,

 

it would be a good idea to run those commands on CLI when IOT device can reach the internet and when it can not to troubleshoot the issue.

 

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-First-steps-to-troubleshoot-connectivity/ta-p/192560

Another angle worth considering is managing or at least monitoring such behavior via ios apps, especially in setups where devices don’t have proper interfaces of their own. Some frameworks make it easy to build lightweight mobile tools to supplement diagnostics.

 

Regards.

That’s a great link, it’s definitely helpful to go through Fortinet’s structured steps for troubleshooting. In cases like this, especially with devices that only briefly connect before dropping, deeper logging and contextual data can make all the difference. Sometimes the issue is tied to power-saving features or flaky firmware on the IoT device itself, but without proper tracking, it’s hard to pinpoint.

Terms & ConditionsAccessibility statement