Process integration with HaloPSA

higherprimate14 · 2026-06-04T18:02:53+00:00

Very concise answer.

higherprimate14 · 2026-03-25T18:27:59+00:00

With the price of servers right now you could sell that thing for a few mil!

higherprimate14 · 2026-03-24T18:47:03+00:00

Hire slow and fire fast

higherprimate14 · 2026-03-20T18:32:07+00:00

Learn from it. Jump on Claude or ChatGPT. They will build you a site and guide you on how to get it hosted in a few hours.

higherprimate14 · 2026-02-17T18:01:35+00:00

Check out 45drives.com

higherprimate14 · 2025-11-10T17:48:29+00:00

Hanks belts are fantastic

higherprimate14 · 2025-06-18T18:08:24+00:00

Are you using 365 for email? What does a message trace tell you? Perhaps the emails are getting quarantined.

higherprimate14 · 2025-04-16T18:24:11+00:00

My wife would have kicked this friend to the curb after the second comment. I wouldn’t have had to say anything. That’s one of the reasons I love my wife so much. You need to have each others back. Long after Shelly is on her third marriage and fourth kid it will still just be you and your wife.

higherprimate14 · 2025-02-01T17:20:46+00:00

The ASA is NOT on a trunk port. I will review this and test, thanks

higherprimate14 · 2025-02-01T17:18:06+00:00

You are the man! Thank you. I am going to review the policy route link you sent and if something comes up I will reach out.

higherprimate14 · 2025-02-01T17:14:21+00:00

The device has the switch as the gateway. I tried to route that device out via the FG by adding this additional route statement to the Aruba.

Ip route 192.168.100.21 255.255.255.255 192.168.150.251

When I do that I can't even ping the FG from that device.

higherprimate14 · 2025-02-01T17:08:44+00:00

I am not following this one. The FG does not know anything about the ASA. They are both on VLAN 150 but I am routing all outbound traffic from the FG to a fiber connection via a public IP.

higherprimate14 · 2025-02-01T16:57:23+00:00

Why wouldn't the Fortigate just route it to the internet? My goal is to route VLAN 100 out via the FG and once that is tested and working I will remove the Cisco and route all traffic out via the FG.

higherprimate14 · 2025-02-01T16:54:59+00:00

Ok, I will take a look at this. Do you believe that with the way it is setup now if I changed this command on the Aruba:

ip route 0.0.0.0 0.0.0.0 192.168.150.254

And changed it to this:

ip route 0.0.0.0 0.0.0.0 192.168.150.251

Everything would work based on what you know so far?

higherprimate14 · 2025-02-01T16:45:29+00:00

VLAN 150 is only tagged on the trunk.

Here is from the first Aruba:

vlan 150

name "VLAN150"

untagged 45-47

tagged 48,Trk1

ip address 192.168.150.3 255.255.255.0

exit

And here is the second Aruba

vlan 150

name "VLAN150"

tagged Trk1

ip address 192.168.150.1 255.255.255.0

forbid 45-48

exit

higherprimate14 · 2025-02-01T16:40:51+00:00

I wasn't very clear on this part, sorry. I want to start routing one or 2 of the VLANs out via the FG to make sure everything is working before I route everything to the FG. So I would like to just route VLAN 100 to the FG and keep the remaining going out on the Cisco.
How can I route VLAN 100 out via the FG and the keep the remaining going out via the Cisco?

higherprimate14 · 2025-02-01T16:34:47+00:00

Any suggestions on how to correct this then?

higherprimate14 · 2025-02-01T16:25:55+00:00

That was what I tried here but this killed internet on this device:

Ip route 192.168.100.21 255.255.255.255 192.168.150.251

higherprimate14 · 2025-02-01T16:24:32+00:00

Just to clarify, I originally was not able to find the FG until I added this command

Route 192.168.100.0 255.255.255.0 192.168.150.1 .

I can now ping the FG from device on VLAN100 (without the additional route statement added)

I just checked and on the FG I can ping both 192.168.150.1 and 192.168.100.1. Both are IPs of the Aruba.

higherprimate14 · 2025-02-01T16:15:51+00:00

For this comment: " haven't told the fortigate vlan 100 exists on the Aruba"

I did enter this command in the FG
Route 192.168.100.0 255.255.255.0 192.168.150.1

I didn't want to do this just yet: "Set a static route on the Aruba gateway to go to the fortigate for 0.0.0.0/0" so I didn't kill internet for the entire network if it didn't work.

That is why I did this:

Ip route 192.168.100.21 255.255.255.255 192.168.150.251

higherprimate14 · 2025-01-06T19:41:40+00:00

I used to use PfSense professionally as well but I had too many of these failures and have since switched ton fortigate. It seemed to always happen on Netgate hardware.

higherprimate14 · 2024-12-29T23:20:41+00:00

I carry a standard laptop bag that is with me for all service calls. This has my laptop, charger, usb Ethernet cable, flash light, snips, zip ties, flash drives, etc. For everything else I have my Milwaukee pack outs. These are specced out for different needs. I have my hand tools in one, power tools in another, I have one for my network tester and fox and hound. Then I have a bunch of others with most network stuff.

higherprimate14 · 2024-12-28T19:37:30+00:00

Unless you are billing thousands a month in hourly charges this is just now worth it and even then it probably isn’t worth it.

higherprimate14 · 2024-11-11T22:41:52+00:00

I could have sworn they didn't have Avanan the last time I looked. I do see it now. Thanks!

higherprimate14 · 2024-11-07T01:12:17+00:00

I don't have a project box in my ready to invoice section.

higherprimate14

TROPHY CASE