Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - farmersLSD

#1
Short story:
I can ping out and into LAN from the firewall.  I don't get a response from my workstation to internet OR firewall.

#2
General Discussion / Routes - what should I do?
May 06, 2019, 06:16:47 PM
Question about routes.  I can change this, I just set it up to access the firewall if the LAN settings weren't correct.  Not a firewall expert here, but can usually figure it out.  On our Fortinet, we have to statically assign the route from 17.16.0.0/16 to 192.168.1.2 as the Gateway.  Our internal network being 172.16.0.0/16 and the gateway being our core switch at 192.168.1.1.

Here are our routes now:
https://i.imgur.com/xDZKGvX.png

Should I just delete the Management LAN and use the LAN interface and set it's route to 172.16.0.0/16 with a gateway of 192.168.1.2?

I just want easily be able to access to make changes in the event I don't have something correct. 

Under Interfaces, I have the LAN Interface set to 192.168.1.2 as the Gateway.  Just not sure, looking at the routes, if I needed to do anything else.  Since it shows link#, and 192.168.1.0/24 and 172.16.0.0/16 have different links.

Hopefully that's clear enough. 
#3
Was checking to see if this is possible or not.  I have had issue getting others to work.  Endian works, but it doesn't like my hardware (Dell R610 with quad-port NIC.  Doesn't see the NICs as Active).

I would like it to read Active Directory OUs or Groups so users are filtered accordingly.