NAT Server in conduit

[Guillermo Martinez]

Hi, I am working with the Conduit model “MTCDT-247A” with WiFi incorporated.

I am trying to figure out how to access another conduit’s “Application Enablement Platform (AEP)”, model “MTCDT-246A” with no WiFi nor Cell connection through the first one, connecting the two of them via Ethernet.

Both the conduits are on the Firmware Version 5.1.6

The “Just Ethernet” model is configured as follows:
-Ethernet LAN IP: 192.168.2.2
-Ethernet Gateway: 192.168.2.1
-Ethernet Mask: 255.255.255.0

The “also WiFi” model is configured as follows:
-WiFi WAN IP: 192.168.1.56
-WiFi Gateway: 192.168.1.1
-Wifi Mask: 255.255.255.0
-Ethernet LAN IP: 192.168.2.1
-Ethernet Gateway: 192.168.2.2
-Ethernet Mask: 255.255.255.0

Then what I tried was to configure a DNAT rule:
-Destination Settings:
–Destination IP: 192.168.1.56
–Destination Port: 9999
–Destination Mask: 255.255.255.0
–Destination Interface: ANY
-Source Settings:
–Source IP: ANY
–Source Port: ANY
–Source Mask: //Blank
–Source Interface: ANY
-General Configuration:
–Protocol: TCP/UDP
–NAT IP: 192.168.2.2
–NAT Port: 443

Could anybody help me out with this issue? Thanks in advance

• This topic was modified 3 years, 9 months ago by Guillermo Martinez.
• This topic was modified 3 years, 9 months ago by Guillermo Martinez.

[Jeff Hatch]

Hello Guillermo,

Hooking the two Conduits together like that with their Gateway settings pointing at each other will probably cause a routing loop. Maybe since they are configured as LAN the gateway settings for those interfaces won’t get set in the routing configuration. Can you ping from one Conduit to the other?

Jeff

[Guillermo Martinez]

Hi Jeff,

Yes, I can ping from one to another with no problem, if I connect to each of them through serial port with my computer

Guillermo

[Jeff Hatch]

Hello Guillermo,

The SNAT rule will NAT the source address of the device that the connection is coming from. Is that what you want it to do?

Jeff

[Guillermo Martinez]

Hi Jeff, I am sorry, I confused SNAT and DNAT, what I was trying to configure is a DNAT rule.

Basically, what I want it to do, is to configure the WiFi conduit to NAT so that I could access the second gateway from it.

How I think it should work is to type 192.168.1.56:9696 in my browser, so that the WiFi conduit would understand that it should translate it into 192.168.2.2:443 and therefore accessing the AEP of the “Only Ethernet” Gateway

[Author]

Posts