Problem with MAC address publication

[Heodrene]

Hi all,

Since this morning I have a weird problem :( Some users complain that they can't surf from LAN to Internet. I found the problem : my default gateway is 192.168.0.254 (MAC : 00:09:0F:09:00:02) but when I type in a MSDOS the arp -a command, I see that the MAC is 00:09:0F:09:00:0B for the same IP 192.168.0.254.

Our fortigate Appliance has 3 hardware switchs :

- 1 : LAN (ports 1 & 2) ;

- 2 : DMZ (ports 3 & 4) ;

- 3 : PHONE (ports 5 & 6).

The bad MAC is from PHONE hardware switch.

I reboot Appliance = NOK

Version is 5.2.3build670.

Please help :)

Best regards,

Jacques

[ede_pfau]

hello,

are you 100% sure that your notebook is not connected to ports 5 or 6, as this would explain the situation.

On another suspicion, can you disable Device indentification on the internal ports if you have that enabled at the moment? There are unconfirmed clues that DI interferes with DHCP in v5.2.3.

[Heodrene]

:) Yes I'm sure.

Furthermore, the IP address is not the same (2 différents subnets).

The FortiGate is online since one month without any problem, this one appears now neither why nor how. I tried to downgrade in v5.2.2build642, the problem is the same.

[ede_pfau]

I know this is some effort: could you downgrade to 5.0.12? I bet the issue is gone then.

[Heodrene]

Before read your last post, I disabled devices identification = NOK

I downgraded in v5.2.2 = NOK

Then I upgraded again in v5.2.3 = new problem, no route between the different interfaces works.

So, after a factory reset, I restore the last conf = NOK

Then a new factory reset again and I copy/paste line-by-line our last configuration = OK

For the moment, the issue [strike]is[/strike] are fixed...

... but I'd like to understand what happened...

[JohnAgora]

Hello,

Did you have any answer on the topic? Maybe from the TAC?

Thanks!

[rwpatterson]

Did you compare a non-working saved backup with the working saved backup?

[Heodrene]

Hi All,

No, I didn't compare the 2 configurations and I didn't open a ticket with the TAC because the issues were fixed when I copied line by line the configuration.

Actually we work with v5.4.0 without any problem ;)

Regards,

Jacques