- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interface WAN2
Sorry for my English. On the wan2 interface, I removed the ip address from the ISP but still pays it, even though the interface is disabled and the configuration of the ip address setting is removed. In addition, all policies and objects that have used this interface have been removed. It looks as if the Fortress FortiGate still remembered these settings. The sample address that was set is 1.1.2.2. and after executing the 'execute ping 1.1.2.2' command, it still responds even though it does not appear anywhere in the whole configuration. You have ideas for solving this problem. # show system interface wan2 config system interface edit "wan2" set vdom "root" set allowaccess ping set type physical set scan-botnet-connections block set alias "WAN-SatFilm" set role wan set snmp-index 4 next end # dia sys cmdb refcnt show system.interface.name wan2 (this command gives an empty result) # execute ping 1.1.2.2 PING 1.1.2.2 (1.1.2.2): 56 data bytes 64 bytes from 1.1.2.2: icmp_seq=0 ttl=255 time=0.0 ms 64 bytes from 1.1.2.2: icmp_seq=1 ttl=255 time=0.0 ms 64 bytes from 1.1.2.2: icmp_seq=0 ttl=255 time=0.0 ms 64 bytes from 1.1.2.2: icmp_seq=1 ttl=255 time=0.0 ms
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hm maybe its cached in still active sessions?
You might clear the session cache to get rid of these...
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This must be a VIP definition then, it proxy-arps for the external address. You ping from the LAN, right? If you get a response when pinging from the 'net, it's a proxy with your ISP.
