[SOLVED] Firewall: NAT: Outbound : Mapping only for network, not single address

[weust]

I use a outbound static mapping for my PlayStation 3 and 4. They need it to get a Type 2 connection.
Without it, voice communication doesn't work and multiplayer games barely work.

But for the Source I can only set a Network (ie. 192.168.1.0/24), "any" or "This Firewall (self)".
I don't need my entire LAN to use static mapping towards the internet, just the IP address of the PlayStation console.

Is it possible to get a "Single IP address" type option?

[AdSchellevis]

Hi Tom,

If you have the time, can you try the development version. I've refactored the page last week and you should be able to fill it in now, although I'm not absolutely sure the backend code handles it correctly.

Cheers,

Ad

[weust]

Hi Ad,

No problem. Will give that a go later today.
If the backend code doesn't handle it properly, the PlayStation network test will show that.
It shows a Type 3 meaning the traffic is being NAT'ed, and I will have voice comm and multi player issues.

Will update the topic on my findings.

[weust]

Already giving it a go...

Nice thing is I can select the Alias for my PlayStation, instead of typing it's address.
But when I only change that, and press save I get an error message:

The following input errors were detected:
•A valid target IP address must be specified.

Bit weird, since Destination is "any".
Also tried this with entering the source IP address just in case something got mixed up there.

Also, since there is no input for "target IP address" on the page, what does it relate too?

Last, pressing the Cancel button doesn't return you to the overview page with all rules, but clears any changes on the page you were editing. That doesn't sound very consistent to other pages?
Meaning I have to select NAT in the menu again, and go to the Outbound tab manually.

Hope this helps in making it better. If you want me to test something again, let me know.

[AdSchellevis]

The error message / input is a bit confusing, I have copied the old ones in and with "target" it should mean "Translation"..
I think we should rename translation to something less confusing....

The problem with the cancel button is odd, it's doing the same as all the other pages for as far as I can see (return to caller). But is probably related to the error message, when you do an apply, the caller will be the same page you where on. (other pages have this flaw as well)

[weust]

Confusion aside, why would it give me that error when it worked fine before?
It's a static mapping, so what is there to translate?

Sound like that is the case with the return to caller.

[AdSchellevis]

My mistake, I responded a bit too quick...
The Translation/target was supposed to be optional and by mistake I made it required ;(

This commit should fix the issue:
https://github.com/opnsense/core/commit/8addbbee668a9b5fd1179eacf5ea343a69ebe5c2

If you have time to test again, just overwrite that file or try the current version in git using the core checkout in the /root directory.

[weust]

I'll just manually edit the file and replace what's needed :-)
I don't use GitHub for checkouts etc.

[franco]

Sooo... all good?

[weust]

Yes, Ad (or Jos?) did a TeamViewer session to my machine and fixed it and put it on GitHub as well.
We discussed it more on IRC, so this topic is done.

I will update with [Solved]

[franco]

brilliant,cheers!