Guest User!

You are not Sophos Staff.

Thread Info
  • Locked Locked
  • Replies 1 reply
  • Subscribers 4 subscribers
  • Views 611 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NAT: New Device behind RED

Mario Noklies

Hi There,

we are using an UTM FIrewall in our HQ and RED-Devices on our branch-offices.

Now a new System with no DHCP-Support was plugged in to the RED.
It has a static IP 192.168.0.1.

As the network at the branch office is different (172.24.1.0/24) i would like to ask, if you have an idea maybe using NAT to connect from my computer in the HQ (behind the UTM) to this new device.

Is there another way to "mask" my computer or do i need to go to the branch office and connect local to the new device.

As i am not very good in NAT, i would be happy if you could explain it the easy way :-)

Thanky for your help

Regards



This thread was automatically locked due to age.
Parents

  • Hallo Mario,

    du benötigst das passende Subnetz hinter dem RED um die 192.168.0.1 ansprechen zu können.

    Zur Not muss dieses parallel (als Alias/zusätzliche IP) zum bestehenden 172.24.1.0/24 betrieben werden.

    2 Subnetze an einem Interface ist zwar nicht schön, geht aber.

    Wenn das Gerät mit der 192.168.0.1 nur im eigenen Subnetz kommunizieren kann (kei Gateway hat) musst du die Traffic am Interface maskieren.

    Dann kann dein PC auf die 192.168.0.1 zugreifen.

    Ist hier alles nicht ganz einfach zu erklären. Details gerne später

    ##########################

    Hello Mario,

    you need the appropriate subnet behind the RED to be able to address 192.168.0.1.

    If necessary, this must be operated in parallel (as an alias / additional IP) to the existing 172.24.1.0/24.
    2 subnets on one interface is not nice, but it works.

    If the device can only communicate with 192.168.0.1 in its own subnet (has no gateway), you have to mask the traffic on the interface.

    Then your PC can access the 192.168.0.1.

    Everything is not easy to explain here. Details later


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Reply

  • Hallo Mario,

    du benötigst das passende Subnetz hinter dem RED um die 192.168.0.1 ansprechen zu können.

    Zur Not muss dieses parallel (als Alias/zusätzliche IP) zum bestehenden 172.24.1.0/24 betrieben werden.

    2 Subnetze an einem Interface ist zwar nicht schön, geht aber.

    Wenn das Gerät mit der 192.168.0.1 nur im eigenen Subnetz kommunizieren kann (kei Gateway hat) musst du die Traffic am Interface maskieren.

    Dann kann dein PC auf die 192.168.0.1 zugreifen.

    Ist hier alles nicht ganz einfach zu erklären. Details gerne später

    ##########################

    Hello Mario,

    you need the appropriate subnet behind the RED to be able to address 192.168.0.1.

    If necessary, this must be operated in parallel (as an alias / additional IP) to the existing 172.24.1.0/24.
    2 subnets on one interface is not nice, but it works.

    If the device can only communicate with 192.168.0.1 in its own subnet (has no gateway), you have to mask the traffic on the interface.

    Then your PC can access the 192.168.0.1.

    Everything is not easy to explain here. Details later


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Children
No Data
Unfiltered HTML