4

My gateway/router interface requesting an IP for itself

view full story
linux-howto

http://forums.fedoraforum.org – Greetings. This is kind of a funny setup but I have a laptop running Windows and I have Fedora 11 installed via VirtualBox. I have a USB-to-Ethernet device which then gets owned by the VM. So, the plan is to configure my virtual machine as a gateway, router and DNS server. eth0 is the interface provided by VirtualBox and eth1 is the USB/Ethernet interface I would then plug into another device (via crossover cable) or to a hub/switch. In my case I have a crossover cable plugged into another machine. I followed the instructions at http://www.stanford.edu/~fenn/linux/ for my home server (also FC 11) and it works fine. I used the same instructions for my VM setup and it appears to work, with the exception of my problem. After restarting the network, dhcpd, and named, ifconfig shows eth0 has an IP from the laptop's network and eth1 uses 192.168.100.1. My DHCP settings assign IP's from 192.168.100.10 to 192.168.100.100. When I plug in my crossover cable to the other PC, my eth1 interface gets assigned the IP 192.168.100.10. So it appears it assigns itself an address. My server at home does not do this. '/var/log/messages' shows: Code: Oct  5 12:22:16 vedora kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Oct  5 12:22:16 vedora NetworkManager: <info>  (eth1): carrier now ON (device state 2) Oct  5 12:22:16 vedora NetworkManager: <info>  (eth1): device state change: 2 -> 3 (reason 40) Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) starting connection 'Auto eth1' Oct  5 12:22:16 vedora NetworkManager: <info>  (eth1): device state change: 3 -> 4 (reason 0) Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) started... Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting... Oct  5 12:22:16 vedora NetworkManager: <info>  (eth1): device state change: 4 -> 5 (reason 0) Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) successful. Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled. Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete. Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) started... Oct  5 12:22:16 vedora NetworkManager: <info>  (eth1): device state change: 5 -> 7 (reason 0) Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Beginning DHCP transaction. Oct  5 12:22:16 vedora kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000 Oct  5 12:22:16 vedora NetworkManager: <info>  dhclient started with pid 4851 Oct  5 12:22:16 vedora NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) complete. Oct  5 12:22:16 vedora dhclient: Internet Systems Consortium DHCP Client 4.1.0p1 Oct  5 12:22:16 vedora dhclient: Copyright 2004-2009 Internet Systems Consortium. Oct  5 12:22:16 vedora dhclient: All rights reserved. Oct  5 12:22:16 vedora dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Oct  5 12:22:16 vedora dhclient: Oct  5 12:22:16 vedora NetworkManager: <info>  DHCP: device eth1 state changed normal exit -> preinit Oct  5 12:22:16 vedora dhclient: Listening on LPF/eth1/00:25:9c:2f:c6:b0 Oct  5 12:22:16 vedora dhclient: Sending on  LPF/eth1/00:25:9c:2f:c6:b0 Oct  5 12:22:16 vedora dhclient: Sending on  Socket/fallback Oct  5 12:22:18 vedora dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Oct  5 12:22:18 vedora dhcpd: DHCPREQUEST for 192.168.100.10 from 00:25:9c:2f:c6:b0 via eth1 Oct  5 12:22:18 vedora dhcpd: DHCPACK on 192.168.100.10 to 00:25:9c:2f:c6:b0 via eth1 Oct  5 12:22:18 vedora dhclient: DHCPACK from 192.168.100.1 Oct  5 12:22:18 vedora NetworkManager: <info>  DHCP: device eth1 state changed preinit -> reboot Oct  5 12:22:18 vedora NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled... Oct  5 12:22:18 vedora NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) started... Oct  5 12:22:18 vedora NetworkManager: <info>    address 192.168.100.10 Oct  5 12:22:18 vedora NetworkManager: <info>    prefix 24 (255.255.255.0) Oct  5 12:22:18 vedora NetworkManager: <info>    gateway 192.168.100.1 Oct  5 12:22:18 vedora NetworkManager: <info>    hostname 'dhcp-192-168-100-10' Oct  5 12:22:18 vedora NetworkManager: <info>    nameserver '192.168.100.1' Oct  5 12:22:18 vedora NetworkManager: <info>    nameserver '10.20.14.205' Oct  5 12:22:18 vedora NetworkManager: <info>    nameserver '10.20.14.206' Oct  5 12:22:18 vedora NetworkManager: <info>    domain name 'vedora' Oct  5 12:22:18 vedora NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled... Oct  5 12:22:18 vedora NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) complete. Oct  5 12:22:18 vedora NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Oct  5 12:22:18 vedora dhclient: bound to 192.168.100.10 -- renewal in 152938 seconds. Oct  5 12:22:19 vedora NetworkManager: <info>  (eth1): device state change: 7 -> 8 (reason 0) Oct  5 12:22:19 vedora NetworkManager: <info>  Policy set 'Auto eth1' (eth1) as default for routing and DNS. Oct  5 12:22:19 vedora NetworkManager: <info>  Activation (eth1) successful, device activated. Oct  5 12:22:19 vedora NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete. Oct  5 12:22:20 vedora named[2972]: received control channel command 'reload' Oct  5 12:22:20 vedora named[2972]: loading configuration from '/etc/named.conf' Oct  5 12:22:20 vedora named[2972]: using default UDP/IPv4 port range: [1024, 65535] Oct  5 12:22:20 vedora named[2972]: using default UDP/IPv6 port range: [1024, 65535] Oct  5 12:22:20 vedora named[2972]: no longer listening on 192.168.100.1#53 Oct  5 12:22:20 vedora named[2972]: the working directory is not writable Oct  5 12:22:20 vedora named[2972]: reloading configuration succeeded Oct  5 12:22:20 vedora named[2972]: reloading zones succeeded Can anyone add some insight to this issue? Any help is appreciated. (HowTos)