Messages

1

22.7 Legacy Series / NetFlow nf_input_snmp index ?

« on: January 06, 2023, 11:36:02 pm »

Hi

Trying to work with netflow data that I am sending to Graylog.  I want to separate it into streams so I can work with it easier, etc.  Is there a way in the firewall (gui or CLI) that I can see what index number for nf_input_snmp matches the actual interfaces?  I have a lot of VLANs, so I want to make sure I am getting it right.  Thanks in advance!

2

22.7 Legacy Series / NAXSI FMT to Syslog?

« on: November 28, 2022, 10:26:02 pm »

Curious if anyone knows if it's possible to send Naxsi logs to syslog?  I'm not seeing options specific to Naxsi.  While I see NGINX access and error logs, I'm not seeing NAXSI_FMT events.  Thanks!

3

22.1 Legacy Series / 1:1 NAT over routed IPsec

« on: July 20, 2022, 11:31:57 pm »

Trying to convert an existing VPN from policy to route-based.  The tunnel works fine, but when I enable my 1:1 NAT rule, the traffic never actually leaves the firewall.  It's funny, if I do a tcpdump on the VTI, it appears that traffic is leaving.  However, it's not as I don't see the ESP frames leave my WAN interface, nor are they seen at the remote site.  Disable the NAT and traffic flows.

To use the 1:1 NAT on the policy-based tunnel, I had to add the "real" local host into the Manual SPD entries field of the phase2 entry, however that is not present on routed tunnels.  I'm at a loss.

4

22.1 Legacy Series / Re: PPPoE/WAN Address changed after upgrade to 22.1

« on: March 23, 2022, 04:02:36 pm »

Which repo would this be an issue for on github?  core?

5

22.1 Legacy Series / Re: Hairpin nat on different interfaces. HOW ?

« on: March 22, 2022, 04:53:49 pm »

I have a couple Port-Forward rules doing this same thing.  I don't know if it will make a difference since I have several public IPs which are just Virtual IPs, which I use for my "Destination".  Here is what mine look like:

Interface: WAN
TCP/IP Version: IPv4
Protocol: TCP
Destination: Virtual IP (you can use WAN Address or type in a host as well)
Dest Port: Port Alias (contains a group of ports such as 80, 443, etc)
Redirect target IP: 192.168.4.25/32
Redirect target port: (same alias as dest port)
NAT Reflection: enabled (I think this is what you may need, the system may default to disabled)

6

22.1 Legacy Series / Re: PPPoE/WAN Address changed after upgrade to 22.1

« on: March 22, 2022, 04:32:56 pm »

Time to roll back I guess.  NAT or PPPoE is broken, can't even overwrite with a manual rule, still uses the wrong IP.

7

22.1 Legacy Series / PPPoE/WAN Address changed after upgrade to 22.1

« on: March 21, 2022, 10:47:34 pm »

Hi

I have a /28 IP block with my ISP and am required to use PPPoE for these static addresses.  Firewall is being assigned the first IP when viewing packet capture and checking PPP IPCP frames (all other IPs are created as IP Aliases).  It seems that after upgrading to 22.1, the "WAN Address" is showing as the second usable IP now (first Alias), and this is also being used in the Automatic Outbound NAT rules.

I may have to switch to Manual outbound to fix this, but curious if anyone else has seen this?  What can I check?

Thanks!

8

22.1 Legacy Series / Re: NAT Loopback

« on: March 07, 2022, 06:16:20 pm »

Mine works and allows me to access my internal servers via their public IP.  All I did was setup a port-forward under Firewall > NAT > Port Forward.  I think the key is to enable NAT reflection in the NAT rule.

Interface:WAN
Destination: Public IP (I have a /28 block so I created aliases, but you could choose WAN Address)
Destination Port: HTTPs, etc.
Redirect target IP: Alias of server's internal IP
Redirect target port: Same as dest (change if you want port translation applied)
NAT reflection: enabled

9

General Discussion / Re: Firewall has no implicit deny all

« on: August 27, 2021, 09:07:33 pm »

In my case I have created a firewall group of all local interfaces, called ALL_LOCAL. This gives an automatic alias of ALL_LOCAL net, which contains all the IPv4 and IPv6 subnets configured on those interfaces (and so changes with changes to those networks or interfaces in the group).

Wow, been using OPNsense for a little over a year, how have I not known about Interface groups?!  Thank you for opening my eyes.  LOL.

10

General Discussion / Re: Firewall has no implicit deny all

« on: August 25, 2021, 11:03:15 pm »

I only have a couple years experience with OPNsense (and a few more with PFsense), but I don't think there is another easy way since they don't have the concept of zones that you can associate interfaces too.  I came from Sophos UTM which had a out of the box network object called "Any Internet IPv4" (or something similar) which I think is probably just doing the same thing as the invert box in OPNsense.

Would love to hear what others are doing, but this is the cleanest way I've found of preventing traffic between internal networks.

11

General Discussion / Re: Firewall has no implicit deny all

« on: August 25, 2021, 05:01:35 am »

What rules do you have in your WiFi interface/list?

I was genuinely curious, so I fired up my test instance to see.  I found the same behavior between two networks (pinging from LAN to LAN2), but as soon as I disabled all the rules for the LAN interface, I got a DENY with "Default deny rule".

Here's what I think is happening for you.  You likely have a rule in your WiFi list that is allowing destination to ANY.  So traffic is allowed in WiFi (and you likely don't have logging turned on for that rule), and then the floating rule is allowing the traffic out of the LAN interface and that is logging as "let out anything from firewall host itself".  (The floating rule is for traffic leaving an interface)

What I did for my internal network rules on DMZ, Guest, etc. is I created an Alias which has all the RFC1918 private networks (you could also be more specific and just use your actual networks).  Use this alias as the destination in all your rules that would typically be "Any", but you need to check the "Invert" checkbox.  This way my rule allows all traffic to destinations that aren't private such as all the other networks behind my OPNsense.

12

General Discussion / Re: DNS Hairpin Rule for Pi-Hole

« on: August 21, 2021, 05:44:55 am »

Thanks Greelan

I was a little lost on your outbound NAT rule for the LAN before you shared the config.  Seems this is needed, other wise the response traffic from pi-hole would leave and try to head directly back to the SRC IP of the clients, which would be an asymmetrical route, and probably dropped by them I would imagine since that's not where they sent the query to.

13

General Discussion / Re: Strange hiccup in flows

« on: August 20, 2021, 01:27:29 am »

Started digging around and found I have a GEO alias that isn't populating with entries.  I removed it and things seem to have cleared up.  When I add it back in as a test (only includes United States) and it sits and spins and then errors with: "Cannot allocate memory. [UnitedStates]"

I have another Alias which includes the United States and Ireland and it has 469829 prefixes, doesn't seem to have issues.  I set tunables net.pf.request_maxcount to 3000000 before trying to create the new Alias, but now it's back at 1000000.  ??

14

General Discussion / Re: Strange hiccup in flows

« on: August 19, 2021, 11:30:30 pm »

Looks like I've narrowed it down to at least one, if not two python processes which spike and then a hiccup.   The first one I found was flowd_aggregate.py.  I have stopped the netflow service.

Issue still happens and when it does, /usr/local/bin/python3 /usr/local/opnsense/scripts/filter/update_tables.py spikes.

Going to remove my aliases which resolve various youtube names (moved this to pi-hole anyway) and see if the issue goes away.  I did notice there was a few names that were not resolving anymore, maybe related?

15

General Discussion / Re: OPNSense and PPPoE Router questions

« on: August 19, 2021, 07:54:20 pm »

What modem model do you have?

OPNsense can do PPPoE (that's what I am using for my fiber).  If you can set your modem to full bridge mode you should be able to setup the PPPoE connection in OPNsense.  Without that, you're going to be doing double-NAT, which is exactly what you're describing being able to access the ADSL router from a machine behind OPNsense.  OPNsense is NATing the PCs traffic to it's WAN address and sending it out to the modem.  Double NAT is messy.