| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="nat-bind-sockets">
|
|---|
| 4 | <title>Binding NAT Sockets to a Specific Interface</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s NAT engine will route TCP/IP
|
|---|
| 9 | packets through the default interface assigned by the host's
|
|---|
| 10 | TCP/IP stack. The technical reason for this is that the NAT
|
|---|
| 11 | engine uses sockets for communication. If you want to change
|
|---|
| 12 | this behavior, you can tell the NAT engine to bind to a
|
|---|
| 13 | particular IP address instead. For example, use the following
|
|---|
| 14 | command:
|
|---|
| 15 | </p>
|
|---|
| 16 | <pre xml:space="preserve">$ VBoxManage modifyvm <varname>VM-name</varname> \
|
|---|
| 17 | --natbindip1 "10.45.0.2"</pre>
|
|---|
| 18 | <p>
|
|---|
| 19 | After this, all outgoing traffic will be sent through the
|
|---|
| 20 | interface with the IP address 10.45.0.2. Ensure that this
|
|---|
| 21 | interface is up and running before changing the NAT bind
|
|---|
| 22 | address.
|
|---|
| 23 | </p>
|
|---|
| 24 | </body>
|
|---|
| 25 |
|
|---|
| 26 | </topic>
|
|---|
