1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Two NAT routers on the same subnet?

Discussion in 'Networking' started by mlager, Feb 18, 2012.

  1. mlager

    mlager New Member

    Messages:
    54
    Likes Received:
    0
    I have a network, 172.16.3.0/24, that has a NAT router (PF)

    Ext: A.A.A.A
    Internal: 172.16.3.1

    Currently, clients use 172.16.3.1 as their default gateway for the Internet. I want to bring in a second Internet connection and have certain devices obtain the Internet through it. Is it possible to add a second NAT router, such as:

    Ext: B.B.B.B
    Internal: 172.16.3.2

    And then have certain devices on the network use a default gateway of 172.16.3.1 to push trafic through A.A.A.A and other devices on the network use a default gateway of 172.16.3.2 to push traffic through B.B.B.B? Both internal interfaces would be on the same switch.

    It seems logical and I can't figure out why that wouldn't work, but I thought I'd check with some experts first.

    Thanks for any advice!
     
  2. bbzz

    bbzz New Member

    Messages:
    867
    Likes Received:
    0
    Yes, that's possible, the fact that both gateways are one same LAN doesn't matter.

    You could also have one gateway which load balances over two Internet connections.
    If you have multiple exit points, look into CARP.
     
  3. mlager

    mlager New Member

    Messages:
    54
    Likes Received:
    0
    Great thanks for the response... Now I've run into something that is pretty annoying. I brought in a U-Verse connection from AT&T (B.B.B.B) and the useless modem / router they included has not ability to disable its DHCP functionality. And I don't want anything grabbing addresses from it because the only point of the AT&T connection is to power the VOIP system. But it hands out addresses and forces itself to be the default gateway.

    I'm not on-site, but it seems my only option, at least with this hardware, is to install another network card in the VOIP system, and plug directly into that. The other network card would plug into the existing network. That way the existing network would never query the new AT&T router for addresses and would just get them from the FreeBSD system like they always did.

    I guess I could go static IP addresses on clients in the meantime.