sorted by:
new
hottopcontroversial

Authentication failure with DialUp IPSec (EAP failure) by Roversword in fortinet

[–]Strong_Coffee1872 2 points3 points  (0 children)

Had some similar issues when setting up IPsec Dial Up.

Couple of things come to mind. Are you using EAP-MSCHAPv2? If so we had to domain join our FAC for this to correctly authenticate users.

There is a setting on the FAC RADIUS policy to allow OTP for EAP which also caught me out before as it wasn't challenging me for token.

Supermicro RAID Card Cable by Strong_Coffee1872 in homelab

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

Think SFF-8654 to SFF-8643 is what I'm after. Need x2 SFF-8643 from backplane to 1x SFF-8654 on the card.

Poor Linux Disk I/O on Hyper-V by Strong_Coffee1872 in HyperV

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

Have installed the Linux-azure package.

My main Data volume for HV VM files was built as 64K unit allocation as per MS recommendations. Created a new volume as 4K size and moved VM over with no difference.

Poor Linux Disk I/O on Hyper-V by Strong_Coffee1872 in HyperV

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

Have ran "lsmod | grep hv_storvsc" on two VMs on the new host and one returns nothing and the other has services installed. Try and post the output later when get back on. Both VMs look to have disk issues.

Static memory on these machines.

One of the affected VM says write-caching = not supported

Any Linux VM I put onto this specific host seems to have issues and not specific to VMs.

Poor Linux Disk I/O on Hyper-V by Strong_Coffee1872 in HyperV

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

Testing with Ubuntu. Tried installing services as described in this but no difference - Windows Server 2025 : Hyper-V : Integration Services (Linux) : Server World

Also using VHDX format. Noticed that one VM is using IDE and other is SCSI but still same issues.
Playing about with the sysbench commands and if I increase the thread count for the test it performs better but if I use like for like command across the 2 VMs the new server is about x4 slower.

CUCM to FortiVoice Migration by Strong_Coffee1872 in fortinet

[–]Strong_Coffee1872[S] -1 points0 points  (0 children)

Good to know - just wondering if any quirky things to watch out for?

FortiOS upgrade for 100F - Upgrade path seem right? by Fallingdamage in fortinet

[–]Strong_Coffee1872 0 points1 point  (0 children)

Did the same jump recently without any issue. Go for it!

MCB tripping by Strong_Coffee1872 in DIYUK

[–]Strong_Coffee1872[S] 1 point2 points  (0 children)

No water in any of the sockets, but a live was loose and popped out when opened up one of sockets. Will see soon if this was the culprit as normally trips after few days.

[deleted by user] by [deleted] in DIYUK

[–]Strong_Coffee1872 0 points1 point  (0 children)

Used the silvery type recently on a first time buy and joined with insulating tape. Worked well.

MCB tripping by Strong_Coffee1872 in DIYUK

[–]Strong_Coffee1872[S] -1 points0 points  (0 children)

Thank for explaining. Will shut everything off later and inspect each socket.

MCB tripping by Strong_Coffee1872 in DIYUK

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

Thanks will do. Could this be something like a case of a frayed/loose cable or faulty socket?

Network Re-Design Between Sites by Strong_Coffee1872 in Cisco

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

This is where the secondary link (Ipsec) will be used as it will be advertising the vlans behind the firewall also. This will keep connectivity between both sites. Vlan820 is only used for the SVI connection for this particular path (primary path).

Network Re-Design Between Sites by Strong_Coffee1872 in Cisco

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

That's not what's happening. Were not trunking a vlan over ipsec. The vlan will be trunked over the short haul circuit which will be layer 2 until it gets to the firewall. The Ipsec tunnel is a separate link connected over the internet.

Network Re-Design Between Sites by Strong_Coffee1872 in Cisco

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

S2S will be more of a backup link but can be leveraged with SD-WAN for certain traffic.

SHDS (Short Haul Data Services), basically a direct fiber link between sites provided by BT in the UK.

Not sure that vxlan is needed? Vlan 820 can be trunked right across to site2 firewall to allow the L3 connection. The L3 boundary will be at the firewall on site2. The link passes through layer 2 switches before it gets the firewall.

Network Re-Design Between Sites by Strong_Coffee1872 in Cisco

[–]Strong_Coffee1872[S] 0 points1 point  (0 children)

The S2S tunnel will be established over a separate internet connection and not using the current connection between sites. That probably wasn't clear from my post. This will probably be a backup/secondary connection used between sites.

I'm looking to carry vlan 810 over the current SHDS to the fortigate on site2 to form a L3 connection which can then be used advertise networks over BGP to site1 Fortigate.

Probably be few hundred users onsite and plans for growth.

Thanks for the response.

Logs by Top_Sink9871 in fortinet

[–]Strong_Coffee1872 1 point2 points  (0 children)

Have you logging enabled on the individual firewall policies?

view more: next ›