OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 16.7 Legacy Series »
  • NAT problem
« previous next »
  • Print
Pages: [1]

Author Topic: NAT problem  (Read 7455 times)

tsystem

  • Newbie
  • *
  • Posts: 47
  • Karma: 0
    • View Profile
NAT problem
« on: December 14, 2016, 05:59:58 pm »
Hi,

I think its simple, but i can get it to work, i on ly want to root a port through my modem and through my firewall to an internal ip with a really simple way, but i can get it to work.

goal : routing external port 3375 to internal computer on port 7533
external ip:3375 -> modem (nat to firewall ip:3375) -> firewall ( nat to internal ip: 7533) -> internal ip server


I try to do it in firewall / NAT / port forward, add :
Disabled:uncheck
No RDR : uncheck
interface : Opt1 (modem)
tcp/ip : ipv4
protocol tcp/udp
source : (simple)
destination : any
destination range from/to : 3375/3375
redir target ip : single host / 192.168.201.xxx
redir target port : other / 7533
XMLRPC : unchecked
nat reflection : disable
filter rule : add associated filter rule


what's my mistake ??  :-[

Thanks for your help



Logged

tsystem

  • Newbie
  • *
  • Posts: 47
  • Karma: 0
    • View Profile
Re: NAT problem
« Reply #1 on: December 14, 2016, 06:53:17 pm »
Hi,

i've look in the log of the firewall and i get this message on the blocked connection : @0 block drop in log inet all label "Default deny rule IPv4"

What's this default deny rule, where can i change it  ?

Thanks
Logged

weust

  • Hero Member
  • *****
  • Posts: 648
  • Karma: 57
    • View Profile
Re: NAT problem
« Reply #2 on: December 14, 2016, 07:20:44 pm »
Looks like you added the rule below the "Default deny rule IPv4".
Try placing it above that line.
Logged
Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.

tsystem

  • Newbie
  • *
  • Posts: 47
  • Karma: 0
    • View Profile
Re: NAT problem
« Reply #3 on: December 15, 2016, 10:15:16 am »
Hi,

Tks  ;)
That was exaclty what i try to do, but the "Default deny rule IPv4" rule is not visible in the firewall rule, and i don't create this rule previously.... ???
Logged

weust

  • Hero Member
  • *****
  • Posts: 648
  • Karma: 57
    • View Profile
Re: NAT problem
« Reply #4 on: December 15, 2016, 11:12:04 am »
That rule should be there by default. Otherwise you have an open gate...
Logged
Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13906
  • Karma: 1206
    • View Profile
Re: NAT problem
« Reply #5 on: December 15, 2016, 12:06:03 pm »
The default deny doesn't show in the GUI rules, it's an implicit default.

Since it's not hitting the NAT/pass rule it may

(A) be coming from a different interface
(B) does not match the rule parameters (port, protocol)


Cheers,
Franco
Logged

tsystem

  • Newbie
  • *
  • Posts: 47
  • Karma: 0
    • View Profile
Re: NAT problem
« Reply #6 on: December 15, 2016, 03:02:24 pm »
Hi Franco, and thanks too for your feedback,

I think (A) is not the problem because i got an inbound connection, i think it's come from B, but i can't see / find my error.

What i try to Do :
internet----------Modem------------firewall OPT1 > LAN-------------internal Server


internet:
request comme from any external ip:3375

Modem (gateway internal ip = 192.168.1.254/24)
it send icoming port (anyIp:3375) to OPT1 (192.168.1.222:3375) 

firewall (OPT1 ip is 192.168.1.222/24 and LAN ip is 192.168.200/20)
it send incoming port from 192.168.254:3375 to internal serveur listing on 192.168.201.18:7533

just for information, at the origin, OPT1 was not my default gateway

My rule is very simple, but some thing is wrong .... below the extration of the configuration showing my firewall config. (No additionnal change from stock nano install)

And i got this error when logking in the monitor (Log file) :

Act : block (cross)
If: OPT1 ( but without the little icon with cloud)
Source: xxx.xxx.xxx.xxx:48043
desti : 192.168.1.222:3375
Proto : TCP:S
and in the detail : @0 block drop in log inet all label "Default deny rule IPv4"



Code: [Select]
  <nat>
    <outbound>
      <mode>automatic</mode>
    </outbound>   
    <rule>
      <protocol>tcp/udp</protocol>
      <interface>opt1</interface>
      <ipprotocol>inet</ipprotocol>
      <descr>nt83</descr>
      <associated-rule-id>nat_585184f53aed85.09056949</associated-rule-id>
      <target>192.168.201.18</target>
      <local-port>7533</local-port>
      <source>
        <any>1</any>
        <port>3375</port>
      </source>
      <destination>
        <any>1</any>
        <port>3375</port>
      </destination>     
    </rule>
  </nat>
  <filter>
    <rule>
      <type>pass</type>
      <ipprotocol>inet</ipprotocol>
      <descr>Default allow LAN to any rule</descr>
      <interface>lan</interface>
      <source>
        <network>lan</network>
      </source>
      <destination>
        <any/>
      </destination>
    </rule>
    <rule>
      <type>pass</type>
      <ipprotocol>inet6</ipprotocol>
      <descr>Default allow LAN IPv6 to any rule</descr>
      <interface>lan</interface>
      <source>
        <network>lan</network>
      </source>
      <destination>
        <any/>
      </destination>
    </rule>
    <rule>
      <source>
        <any>1</any>
        <port>3375</port>
      </source>
      <interface>opt1</interface>
      <protocol>tcp/udp</protocol>
      <ipprotocol>inet</ipprotocol>
      <destination>
        <address>192.168.201.18</address>
        <port>7533</port>
      </destination>
      <descr>NAT nt83</descr>
      <associated-rule-id>nat_585184f53aed85.09056949</associated-rule-id>     
    </rule>
  </filter>

Is my mistake visible ?
Thanks for your help
« Last Edit: December 15, 2016, 03:13:44 pm by tsystem »
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13906
  • Karma: 1206
    • View Profile
Re: NAT problem
« Reply #7 on: December 18, 2016, 10:23:01 am »
I don't fully understand this:

=========
firewall (OPT1 ip is 192.168.1.222/24 and LAN ip is 192.168.200/20)

it send incoming port from 192.168.1.254:3375
=========

Is this a typo? If not, what is the difference of 222 and 254?


Cheers,
Franco
Logged

tsystem

  • Newbie
  • *
  • Posts: 47
  • Karma: 0
    • View Profile
Re: NAT problem
« Reply #8 on: December 19, 2016, 11:25:22 am »
Hi Franco,

Thanks for your feedback and no, it's not a typo  ;) between 222 and 254 but i make a mistake in the lan ip because i forgot last octet  :-[ LAN is 192.168.200.166/20

But you're right my config is not so clear.

network between modem and firewall is a 255.255.255.0 subnet, modem ip is 192.168.1.254 and firewall ip (on 3td  NIC with name OPT1) is 192.168.1.222. so modem and firewall can exchange without trouble.

On the other side ( internal network ) we have a 255.255.240.0 subnet, the firewall have the ip 192.168.200.166 and i try to send port to the internal serveur 192.168.201.18.

In the error returned by firewall, it's look than the inbound connection arrived from external modem to the OPT1 NIC (192.168.1.222) of the firewall, But dont pass trought the firewall to come to the internal server...

Thanks
Mr

Logged

tsystem

  • Newbie
  • *
  • Posts: 47
  • Karma: 0
    • View Profile
Re: NAT problem
« Reply #9 on: December 20, 2016, 10:10:40 am »
Hi,

Just an idea ...
is it possible the problem come from the default configuration of the OPT1 interface configuration that is not by default a gateway ? do i need to make something special on this interface ?

Thanks

Mr
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 16.7 Legacy Series »
  • NAT problem
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2