VirtualBox

Changeset 47901 in vbox


Ignore:
Timestamp:
Aug 20, 2013 12:27:43 PM (12 years ago)
Author:
vboxsync
svn:sync-xref-src-repo-rev:
88206
Message:

doc: NAT network (section), with examples.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/user_Networking.xml

    r46821 r47901  
    404404      ports (i.e. ports not below 1024).</para>
    405405    </sect2>
     406  </sect1>
     407
     408  <sect1 id="network_nat_service">
     409    <title>Network Address Translation (NAT) Service (experimental)</title>
     410   
     411    <para>NAT service provides router functionality similar to home network
     412    configuration, hiding each member from direct outer access, but let establish
     413    communication to from internal network to LAN and WAN resources over TCP and UDP
     414    (IPv4 and IPv6).</para>
     415
     416    <para>NAT service attached to internal network and guests supposed to get natted
     417    connection should be attached to the same internal network. Name of internal network
     418    selected during creation (it doesn't metter whether network exists or not).
     419    </para>
     420    <para><screen>VBoxManage natnetwork add -t nat-int-network -n "192.168.15.0/24" -e
     421    </screen>
     422    "-t nat-int-network" points to name of internal network, that should be pointed while VM
     423    network attachment configuration, -n "192.168.15.0/24" - sets network id and mask, of NAT
     424    service interface, by default in static configuration gateway should assigned to 192.168.15.1
     425    (networkid +1, note after release it could be changed). It's possible to attach DHCP server,
     426    to the internal network, it could be done while creation:
     427    <screen>VBoxManage natnetwork add -t nat-int-network -n "192.168.15.0/24" -e -h on</screen> or
     428    in modification:
     429    <screen>VBoxManage natnetwork modify -t nat-int-network -h on</screen> -h on|off, enable or
     430    disable DHCP server.
     431    </para>
     432    <para>Note: current limitation of DHCP server it doesn't provide nameserver information, so
     433    guest should be explicitly configured to use right DNS servers.</para>
     434    <para>To start NAT service, following command should be executed:<screen>
     435    VBoxManage natnetwork start -t nat-int-network</screen> note if network configured with DHCP server
     436    it will start together with NAT network service.</para>
     437    <para><screen>VBoxManage natnetwork start -t nat-int-network</screen> Stops, NAT network service,
     438    together with DHCP server, if one's enabled.
     439    </para>
     440    <para>To delete NAT network service:<screen>VBoxManage natnetwork remove -t nat-int-network</screen>
     441    Note: this command doesn't remove DHCP server, if one is enabled on the network.</para>
     442    <para>Port-forwarding, is supported (controlled via -p for IPv4 and -P for IPv6):<screen>
     443VBoxManage natnetwork modify -t nat-int-network -p "ssh:tcp:[]:10022:[192.168.15.15]:22"
     444  </screen> this adds port-forwarding rule from host's TCP 10022 port to guest with IP
     445  192.168.15.15 on port 22, and to delete rule <screen>
     446VBoxManage natnetwork modify -t nat-int-network -p delete ssh</screen></para>
     447    <para>To get the list of registered natnetworks:
     448    <screen>VBoxManage list natnetworks</screen></para>
    406449  </sect1>
    407450
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette