ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    AWS routing question

    Scheduled Pinned Locked Moved Unsolved IT Discussion
    24 Posts 4 Posters 1.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • IRJI
      IRJ @JaredBusch
      last edited by

      @JaredBusch said in AWS routing question:

      @IRJ said in AWS routing question:

      @JaredBusch said in AWS routing question:

      @IRJ said in AWS routing question:

      @JaredBusch said in AWS routing question:

      @IRJ said in AWS routing question:

      @JaredBusch said in AWS routing question:

      @IRJ is the server with a public IP running a router?

      Nope

      Then that is your problem. It has no idea what to do with these requests coming in from the other machine.

      Yeah so I am guessing I am better off just putting this box on a new subnet all together.

      What you want to do is entirely possible. Just the device with the public IP needs to be setup to route traffic.

      What I really want to do which I dont know if this is possible is route any requests from it's IP to the NAT instead of internet gateway.

      You want Server A (with public & private) to talk only to Server B (private only)?

      Yes and then I went server B to go out to the internet through the NAT device. I dont want it dependent on Server A in anyway.

      JaredBuschJ DashrenderD 2 Replies Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch @IRJ
        last edited by

        @IRJ said in AWS routing question:

        @JaredBusch said in AWS routing question:

        @IRJ said in AWS routing question:

        @JaredBusch said in AWS routing question:

        @IRJ said in AWS routing question:

        @JaredBusch said in AWS routing question:

        @IRJ said in AWS routing question:

        @JaredBusch said in AWS routing question:

        @IRJ is the server with a public IP running a router?

        Nope

        Then that is your problem. It has no idea what to do with these requests coming in from the other machine.

        Yeah so I am guessing I am better off just putting this box on a new subnet all together.

        What you want to do is entirely possible. Just the device with the public IP needs to be setup to route traffic.

        What I really want to do which I dont know if this is possible is route any requests from it's IP to the NAT instead of internet gateway.

        You want Server A (with public & private) to talk only to Server B (private only)?

        Yes and then I went server B to go out to the internet through the NAT device. I dont want it dependent on Server A in anyway.

        If Server A has no public NIC, then it has to talk to a NAT router someplace. You only have Server A and Server B. So where is the NAT happening?

        DashrenderD 1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender @IRJ
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender @JaredBusch
            last edited by Dashrender

            @JaredBusch said in AWS routing question:

            @IRJ said in AWS routing question:

            @JaredBusch said in AWS routing question:

            @IRJ said in AWS routing question:

            @JaredBusch said in AWS routing question:

            @IRJ said in AWS routing question:

            @JaredBusch said in AWS routing question:

            @IRJ said in AWS routing question:

            @JaredBusch said in AWS routing question:

            @IRJ is the server with a public IP running a router?

            Nope

            Then that is your problem. It has no idea what to do with these requests coming in from the other machine.

            Yeah so I am guessing I am better off just putting this box on a new subnet all together.

            What you want to do is entirely possible. Just the device with the public IP needs to be setup to route traffic.

            What I really want to do which I dont know if this is possible is route any requests from it's IP to the NAT instead of internet gateway.

            You want Server A (with public & private) to talk only to Server B (private only)?

            Yes and then I went server B to go out to the internet through the NAT device. I dont want it dependent on Server A in anyway.

            If Server A has no public NIC, then it has to talk to a NAT router someplace. You only have Server A and Server B. So where is the NAT happening?

            Right - I'm trying to see if you have a multi-homed machine (i.e. two NICs - one plugged into internet, and one plugged into internal subnet)? or do you have two IPs assigned to the same NIC in Server A?

            IRJI 1 Reply Last reply Reply Quote 0
            • IRJI
              IRJ @Dashrender
              last edited by

              @Dashrender said in AWS routing question:

              @JaredBusch said in AWS routing question:

              @IRJ said in AWS routing question:

              @JaredBusch said in AWS routing question:

              @IRJ said in AWS routing question:

              @JaredBusch said in AWS routing question:

              @IRJ said in AWS routing question:

              @JaredBusch said in AWS routing question:

              @IRJ said in AWS routing question:

              @JaredBusch said in AWS routing question:

              @IRJ is the server with a public IP running a router?

              Nope

              Then that is your problem. It has no idea what to do with these requests coming in from the other machine.

              Yeah so I am guessing I am better off just putting this box on a new subnet all together.

              What you want to do is entirely possible. Just the device with the public IP needs to be setup to route traffic.

              What I really want to do which I dont know if this is possible is route any requests from it's IP to the NAT instead of internet gateway.

              You want Server A (with public & private) to talk only to Server B (private only)?

              Yes and then I went server B to go out to the internet through the NAT device. I dont want it dependent on Server A in anyway.

              If Server A has no public NIC, then it has to talk to a NAT router someplace. You only have Server A and Server B. So where is the NAT happening?

              Right - I'm trying to see if you have a multi-homed machine (i.e. two NICs - one plugged into internet, and one plugged into internal subnet)? or do you have two IPs assigned to the same NIC in Server A?

              One NIC with two assigned IPs

              DashrenderD 1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender @IRJ
                last edited by

                @IRJ said in AWS routing question:

                @Dashrender said in AWS routing question:

                @JaredBusch said in AWS routing question:

                @IRJ said in AWS routing question:

                @JaredBusch said in AWS routing question:

                @IRJ said in AWS routing question:

                @JaredBusch said in AWS routing question:

                @IRJ said in AWS routing question:

                @JaredBusch said in AWS routing question:

                @IRJ said in AWS routing question:

                @JaredBusch said in AWS routing question:

                @IRJ is the server with a public IP running a router?

                Nope

                Then that is your problem. It has no idea what to do with these requests coming in from the other machine.

                Yeah so I am guessing I am better off just putting this box on a new subnet all together.

                What you want to do is entirely possible. Just the device with the public IP needs to be setup to route traffic.

                What I really want to do which I dont know if this is possible is route any requests from it's IP to the NAT instead of internet gateway.

                You want Server A (with public & private) to talk only to Server B (private only)?

                Yes and then I went server B to go out to the internet through the NAT device. I dont want it dependent on Server A in anyway.

                If Server A has no public NIC, then it has to talk to a NAT router someplace. You only have Server A and Server B. So where is the NAT happening?

                Right - I'm trying to see if you have a multi-homed machine (i.e. two NICs - one plugged into internet, and one plugged into internal subnet)? or do you have two IPs assigned to the same NIC in Server A?

                One NIC with two assigned IPs

                So the router that's on that 'subnet' is only aware of the Public IP range info, I'm guessing - right? The router doesn't know about 10.x.x.x, even though that data is on the wire. You'd need to make the router also One NIC with two IPs.. then setup NAT routing out.

                1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender
                  last edited by Dashrender

                  Thanks @JaredBusch for reminding me to look at the OP - this is AWS.... so ...

                  1 Reply Last reply Reply Quote 0
                  • IRJI
                    IRJ
                    last edited by

                    Subnet 1 - Routes out to the Internet though Internet Gateway
                    Subnet 2 - Rotues to the internet through NAT on subnet1
                    Subnet 3 - Rotues to the internet through NAT on subnet1
                    Subnet 4 - Rotues to the internet through NAT on subnet1
                    Subnet 5 - Rotues to the internet through NAT on subnet1
                    Subnet 6 - Rotues to the internet through NAT on subnet1
                    Subnet 7 - Rotues to the internet through NAT on subnet1

                    What I am trying to do is route a single server on Subnet 1 through the NAT as well. The route table is controlled at Subnet level. So If I change the subnet routeing rules to go through NAT it breaks.

                    1 Reply Last reply Reply Quote 0
                    • DashrenderD
                      Dashrender
                      last edited by

                      I know nothing about AWS routing - can you setup two IPs on the Subnet 1 "router" interface. I know it's not a real router - it's all in software, but I don't know what else to call it.

                      IRJI 1 Reply Last reply Reply Quote 0
                      • IRJI
                        IRJ @Dashrender
                        last edited by

                        @Dashrender said in AWS routing question:

                        I know nothing about AWS routing - can you setup two IPs on the Subnet 1 "router" interface. I know it's not a real router - it's all in software, but I don't know what else to call it.

                        Devices are not configurable. Both NAT and IGW have zero configurable options. You just create them in AWS

                        1 Reply Last reply Reply Quote 0
                        • dbeatoD
                          dbeato
                          last edited by dbeato

                          You need to setup the EC2 instance with a WAN Dynamic IP (Elastic IP address). Then just go through the Internet gateway and have the security group blocking incoming traffic over the Dynamic IP provided to the EC2 instance.

                          1 Reply Last reply Reply Quote 1
                          • 1
                          • 2
                          • 1 / 2
                          • First post
                            Last post