12 thoughts on “Running a Virtual Router & Firewall inside VMware ESX with Vyatta

  1. c4tchmeIFy0ucAn

    nice tutorial, at least it can give me an extra idea to finish my class project about using vyatta feature in my university

  2. George Ou

    http://happyrouter.com/running-a-virtual-router-firewall-inside-vmware-esx-with-vyatta

    I’m actually setting up a new 1U server for a colocation. I’ll be putting ESXi 4.x on it and I’ll be running a virtual Vyatta machine for sure just to be able to make better use of my public IP addresses (which cost money per month).

    My only question is whether Vyatta works like the dirt cheap consumer routers which allow you to take a single public IP address and forward different TCP/UDP ports to different internal IP addresses. For the life of me, I don’t think I ever figured out how to do that on a Cisco router since they require mapping 1 public IP to 1 private IP.

  3. Jk

    “””…they require mapping 1 public IP to 1 private IP.”””

    What are you talking about. Cisco routers (or any NAT router) permit 65535 private IP’s mapped to just 1 public IP, since the private IP’s have just 1 open connection to the internet. You have to configure a NAT , and at the end of the command, you add “OVERLOAD” (this is called PAT – Port Address Translation).

    Example:
    Public IP = 200.0.0.1 255.255.255.252
    Private IP = 192.168.1.1 255.255.255.0
    NAT pool name (your choice) = EXAMPLE

    Router#ip nat pool EXAMPLE 200.0.0.1 200.0.0.1 netmask 255.255.255.252
    Router#ip nat inside source-list 1 pool EXAMPLE overload
    Router#access-list 1 permit 192.168.1.0 0.0.0.255

    I hope that you understand that, because my english sucks

  4. Pingback: Virtual Networking with BT4 on Virtual Box

  5. David Bonne

    I think George was talking about INCOMING network connections. PAT on a cisco is no good for this – you need “port forwarding” as per most DSL routers (eg Linksys). I believe it’s possible however – just need to dig around a bit more!

  6. Tom

    This is what you need JK if you’re on an ADSL cisco like an 877:

    ip nat inside source static tcp [internal ip] [internal port] interface Dialer0 [external port]

    ie to forward external 57812 to internal 3389 on 10.0.0.88 you’d do:

    ip nat inside source static tcp 10.0.0.88 3389 interface Dialer0 57812

  7. Pingback: | Sys Admin Extraordinaire | » Blog Archive » VMware vSphere Hypervisor (ESXi) Test Lab Configuration Notes

  8. david

    Ohh! really nice that when you go to downloads on vyatta the community edition is missing! ups! nice this community concept: let the idiots program for u and then use the improvements on pay version.

Leave a Reply

Your email address will not be published. Required fields are marked *