Messages

holy shit it's fucking working.

but why? It's just the same config as before.

UUUUHG this is almost worse than it not working at all what the hell.

I deleted and recreated the rule and no error this time, but it still doesn't work. Must be a firewall problem though, uhg.

I just noticed this error pops up when I save the firewall rule but clicking on it doesn't go into detail. hmm

slightly more info

2021-05-28T18:55:39   opnsense[20610]   /usr/local/etc/rc.filter_configure: There were error(s) loading the rules: /tmp/rules.debug:128: syntax error - The line in question reads [128]: rdr log on em1_vlan3000 inet proto {tcp udp} from {any} to {(em1_vlan3000)} port $DayzEpoch tag Dayz Server -> $DL380_G6 # Dayz Server

Ok, no, that's not it, it is binding to the right IP on my server but it still won't pass through the firewall. uhg.

Ok, well it seems like you can't bind a specific IP address in the startup batch file for the server so I bet the damn thing is binding to the wrong IP address. I tried adding the second IP for my server into it's alias but that brought it all down so now to try and figure this out.

I have my mellanox card set to be the first one in that windows (metric?) setting, and have my other four nics in an LAG group that should be second billing. apparently that's not enough though.

I have the same NAT settings, also tried manually switching from default and no luck again, uhg.

2302 is the game server, 2303 is the steam discovery port and the others are some misc ones that may or may not be used by it, so I opened those up as well just in case.

Definitely the right IP and I have 2302 and 2303 opened up in the firewall, but I also have the program itself allowed to go through completely since it didn't work with only the ports.

Works fine on LAN

I've been using port checkers on the game server and changing my ftp servers port, and also tethering my phone to my laptop to try from the external network. No luck on all fronts.

I'll take a look at those settings when I'm done work in an hour and a half ish and report back

Well, if that's the majority of my issues I'll smack my head in a wall. Tried it and still no joy but maybe I still made a mistake somehow? Have to run back to work since my lunch is over so can't test more.

https://imgur.com/a/HHipS56

Hi all, so I've been trying to port forward a dayz server for a while now and I've had no luck. I cloned existing, working firewall rules without any luck, and I also manually added a firewall rule allowing traffic from my internal machine (dl380-g6) to any wan address, as I saw mentioned elsewhere. (I also deleted the floating rule as a test, no change still)

The ports refuse to open though. I've struggled with port forwarding almost every time I try to do it, and I'm not sure why cloning existing rules doesn't work.

https://imgur.com/a/OMvokHF

I've looked at a dozen or so different guides on port forwarding and made rules completely from scratch following them and the ports refuse to open, and I can't see them on the live firewall feed. That's why this is so frustrating, I made this rule following that link, as well as taking other rules for this exact same machine (dl380-g6) and simply changing the port and they don't work. It makes zero sense. I've even also set manual floating rules for these same ranges and they work for some that have been active for ages but new ones won't work. Rebooting doesn't help either.

Also I I noticed after posting that virtual ip was set to /32, and when I change it over to /24 it kills my internet connection.

I tried setting a one to one NAT rule to push everything through the .190 address but that didn't seem to help. I'm basically wanting everything to default to that, but for a couple select machines to be manually set to use .189 instead.

It was working at some point and then I'm not sure what happened but it stopped so I set everything back.

Honestly right now the port forwarding is the main thing. I know my firewalls are all set properly and these things work on the internal network but the ports just never open up to be visible from test pages or to other people.

Also I like open source stuff and I'm aware that the pfsense guys pulled some shady shit against opnsense so that's why I chose opnsense in the first place, and I like it, it's just that it's so frustrating right now.

Hi all, so this is something I was struggling with on the previous production series (19.7) and it's still an issue, after upgrading and after doing a complete fresh install of opnsense 20.1, restoring my config, and updating.

Essentially I'm trying to open up a port for TCP/UDP, and no matter what I try it doesn't open, sites like canyouseeme can't see the port open and trying to connect to something like a game through that port also doesn't work.

In this instance it's 25445 for one of my servers, DL380-G6 that's refusing to work.

I've cloned existing rules that do work, and show an open port on test sites, and allow connections, such as teamspeak, but when I try to add anything new it doesn't work and it's driving me absolutely insane.


On top of that I have a second public static IP which I want to use, however if I add that as a virtual IP it kills my network.

I had that working at one point too and then one day it shat the bed, and no longer worked so I had to move all my hosting back onto the first static IP.

I'm at my wits end with this and have made a couple other topics about this with loads of screenshots and no solutions have been found so I'm hoping posting my whole damn config will maybe get someone who knows more about this to spot why the hell it isn't working.

Frankly I would  switch over to pfsense since every google search is overloaded with results for that instead of opnsense but my hardware is too old for the newest versions.

Still trying to get this to work with this port, and now another port. I have NAT rules set up, I have floating rules set up and the ports won't open. This is insanely frustrating.

Hi all, so I'm running into an issue trying to open port 25001 for TCP and UDP. I don't know why but no matter how I configure the rules, including cloning an already existing, and working rule, but this port won't open.

I'm wondering if maybe it's because it's an oddly high port that it's causing issues? I have noticed some other weird behaviour with my router, like it not actually rebooting when I send it a command but firewall rules seem to apply, and I've tried shutting down and giving it a hard reboot, and the rules stuck but the port won't open. I also don't have the option to update to the new production series for some reason in the update section either.

edit: Well shit it just showed up now so I'll update I guess and see if that fixes this too.

It's just really puzzling that cloning a rule and changing the port and target aren't working.

https://i.imgur.com/Bhl0ASY.jpg
https://i.imgur.com/MZYjyp.jpg

edit: well the update had no effect on this.

edit 2: Looks like those open port checker sites don't work with all ports for some reason because I know my teamspeak server works, but the ports don't register as open on multiple sites that check them, I wonder why. Maybe whatever is blocking those sites from working is stopping this game from being able to connect as well.