Changes between Version 33 and Version 34 of VmServer
- Timestamp:
- Jun 4, 2008, 3:25:59 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
VmServer
v33 v34 35 35 === Network Access === #server-network 36 36 37 37 38 VMWare provides two ways to access the network from the VM: 38 39 Bridged Ethernet and NAT (Network Address Translation). … … 40 41 We recommend that you start with Bridged Ethernet. 41 42 43 The first time you boot the VM, log on as root and delete the file 44 {{{ 45 /etc/udev/rules.d/rules.d/z25_persistent-net.rules 46 }}} 47 42 48 === Bridged Ethernet === 43 The VM will act like a real machine on your network. 49 50 In this mode, the VM will act like a separate machine on your network. 44 51 Scanning the network will reveal two machines, your host and the VM. 45 52 Outgoing and incoming connections are possible. 46 53 47 By default, the VM will get an IP address via DHCP. 48 This will work if your network has a DHCP server configured to 49 issue IP address to new hosts. 50 51 52 Alternatively, you can give the VM a static IP address. 54 We recommend that you give the VM a static IP address. 53 55 To do this, edit /etc/network/interfaces. 54 56 For example: … … 56 58 # The primary network interface 57 59 auto eth0 58 #iface eth0 inet dhcp 59 # pre-up iptables-restore < /etc/iptables.up.rules 60 60 61 iface eth0 inet static 61 62 address 141.142.234.9 … … 82 83 If you're using a proxy to access the internet you should add 'debian.localdomain' to your list of exceptions in your browser. 83 84 You won't need a proxy to resolve a local address. 85 86 Alternatively, you can get an IP address via DHCP. 87 '''We don't recommend this because clients will get confused if the IP address changes.''' 88 To do this, edit /etc/network/interfaces to include: 89 {{{ 90 iface eth0 inet dhcp 91 }}} 92 This will work if your network has a DHCP server configured to 93 issue IP address to new hosts. 84 94 85 95 === NAT ===