Skip to main content
billylo
billylo
New Member
January 22, 2019
Solved

Physical Lan Interface configuration

  • January 22, 2019
  • 2 replies
  • 5731 views

https://forum.fortinet.com/tm.aspx?m=116066

 

i have see above thread for changing switch mode to interface mode, but cant find the line  " set internal-switch-mode switch" and change that to " set internal-switch-mode interface" in Firmware Version v5.0,build0252, anyone help? thanks.

 

Current situation:

i am using FortiWIFI 90D, start with switch mode, with "internal" ip:192.168.0.x/24, now want to add a subnet 192.168.2.x/24, how can i do?

1. i try add a static route 192.168.2.x/24, with gateway 0.0.0.0, device:internal

2. create policy 

Incoming Interface:internal (LAN) Source Address:all Outgoing Interface:internal (LAN) Destination Address:all Schedule:always Service:ALL Action:ACCEPT

 

but didn't work, and i try add a router with WAN IP: 192.168.0.10, internal ip:192.168.2.1, dhcp enabled:192.168.2.100-200, all subnet pc can go internet, can ping 192.168.0.x/24 , but 192.168.0.x/24 can't ping 192.168.2.x/24 network, i want to set both 192.168.0.x/24 and 192.168.2.x/24 can communicate each other, what should i do? thanks.

Best answer by Dave_Hall

Default settings in the config are usually not shown unless you perform something like "show full".  If this was a new fgt with little to no configuration you may be better off factory resetting the fgt and making the switch to interface mode changes from a "fresh" config.

 

If the WAN2 port is not used for anything, you could always create the 192.168.2.x subnet on that.  WAN2 is just a port label.

2 replies

Dave_Hall
Dave_HallAnswer
New Member
January 22, 2019

Default settings in the config are usually not shown unless you perform something like "show full".  If this was a new fgt with little to no configuration you may be better off factory resetting the fgt and making the switch to interface mode changes from a "fresh" config.

 

If the WAN2 port is not used for anything, you could always create the 192.168.2.x subnet on that.  WAN2 is just a port label.

Toshi_Esumi
SuperUser
Toshi_Esumi
SuperUser
January 22, 2019

The build0252 is 5.0.5. But the interface mode was introduced with 5.2. So you have to upgrade to at least 5.2.x to be able to use interface mode.

ede_pfau
SuperUser
ede_pfau
SuperUser
January 22, 2019

@Toshi:

The build0252 is 5.0.5. But the interface mode was introduced with 5.2. So you have to upgrade to at least 5.2.x to be able to use interface mode.
The choice between switch and interfaces was already part of FOS v4.0 back in 2009. Sorry, but take my word for it, as I am an old man.

 

Nevertheless, v5.0 is more than 5 years old and IMHO shouldn't be used on a contemporary security device anymore.

Toshi_Esumi
SuperUser
Toshi_Esumi
SuperUser
January 22, 2019

Probably because I was dealing with 60D at that time. Maybe hardware dependent.

Terms & ConditionsAccessibility statement