This may be a very basic question but I was wondering if there is a way through the command line to find out which interfaces are using dhcp. I'm using Ubuntu 9.10 in case that makes a difference.
I am running Fedora 13 and after my machine is booted my ethernet interface eth0 does not have an IP address. Running
Code:
At the terminal does not work, and I can see that in /var/log/messages I have the following error:
Code:
I assume that the same command was attempted during the boot process (please correct me if I am wrong) to use DHCP to get an address for eth0, but failed for the same reason it is failing after boot when I run it manually, whatever that reason may be.
I noted, however, that eth0 IS in broadcast mode:
Code:
I also noted that running
Code:
Does in fact work and will run DHCP and configure eth0 with an ip address.
It is quite mysterious to me why running 'dhclient eth0' will work, but manually running 'dhclient' does not.
I work for a SUN resller in South Africa, I have recieved a request from a customer for a autoloader with LTO3 or 4 drives. Where can I find out what auto loaders and interfaces (SCSI or SAS) are supported.
I have a weird issue that I have not seen on any forum. My jaunty on DELL studio laptop seems connected to net, but I can not access any network service (ssh, firefox etc.). But when I connect a cable the cable lights blink as it should be and in wireless connection my wifi light blinks.
It was working 2 days ago without problem, and I have not done big changes recently.I removed and reinstalled network-manager and network-manager-gnome. Nothing changed. I see a message in each restart as follows (when Openafs is starting). I can reproduce it with "/etc/init.d/openafs-client restart"
Code:
ADVISEADDR:error in specifying interfaces: no existing ip interfaces found
I have 3 Interfaces for a different LAN's and when I start one interface the another interfaces goes down.How can it's possible?I configure my ethernets as:
If I try to add a new interface (eth1) to /etc/network/interfaces, I get
Code: * Reconfiguring network interfaces... SIOCSIFADDR: No such device eth1: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device
[Code]...
How do I add 2 interfaces and get anyone of them to work, as available ?
I don't really have a reason for this currently. I recognize all the MAC address on my DHCP client list and keep it rather well locked down. I was just wondering if there was something I could run on the terminal to get more information on a given MAC address on my network. Something kind of like whois for websites.
For some reason I am unable to find a DHCP Server package for Fedora 14 using yum. Does anyone know what I should be searching for or even a .rpm that can be used?
I would like to make my Fedora 13 box a DHCP server for my network. I can not find dhcpd in YUM. Is there a way to make my Fedora box a dhcp server? This was relay easy with Suse, but my Opensuse box just suffered a hard drive failure.
first: PXE flawless bind to dhcp address but put next binding state to free second: when installer calls init script to reinit ethernet driver (e1000 (vmware)) binding fails 11.2 opensuse fail to reinit dhcp with log entry "no free leases" third: when manual set network install works how to preserve dhcp lease on reinit of driver?
Back in April I set up a Ubuntu DHCP server and a multiple VLAN network [URL] to migrate our various servers, workstations, etc off the 192.168.1.1 /24 network that everything was on because we where running out of address space. I built out the new network and everything worked great except our AD server would never get an IP address from the DHCP server (static reservation) and even if I set the IP statically on the AD server it couldn't ping the gateway and noone could log in. After several attempts to resolve this, including bringing in outside help, we where never able to figure out what the problem was.
Now 6 months later I have time to revisit the issue without effecting the live network. I used Acronis and imaged the AD server last Friday, cloned it on to another box with the same hardware, and put it up on the new network that's been sitting unused for the last 6 months. Today when I statically set the IP on the AD server (which is what I want) it connects and I can ping it's gateway 192.168.1.1 and all the way across vlans to a test sales agent workstation at 192.168.8.xxx on vlan 800 but only if I statically assign the agents station an IP address. When I try to get an IP address via DHCP it fails as destination unreachable. Nothing has changed in the last 6 months on the DHCP server but now it for some reason can't ping its default gateway 192.168.1.1. All of the config files are the same as they where left from the post linked above aside from the vlan id's used where changed from 1's to 100's (i.e. vlan 3 is now vlan 300) /etc/network/interfaces
Code:
auto lo iface lo inet loopback auto vlan100 iface vlan100 inet static
[code]....
why it can't reach the gateway, when I do a tcpdump I can see the DHCP requests come in on eth0 but the server never responds and I'm pretty sure its because it isn't "seeing" them since it thinks there isn't a network connection but I don't know how to trouble shoot to find out where the problem lies.
Back in April I set up a Ubuntu DHCP server and a multiple VLAN network [URL] to migrate our various servers, workstations, etc off the 192.168.1.1 /24 network that everything was on because we where running out of address space. I built out the new network and everything worked great except our AD server would never get an IP address from the DHCP server (static reservation) and even if I set the IP statically on the AD server it couldn't ping the gateway and noone could log in. After several attempts to resolve this, including bringing in outside help, we where never able to figure out what the problem was.
Now 6 months later I have time to revisit the issue without effecting the live network. I used Acronis and imaged the AD server last Friday, cloned it on to another box with the same hardware, and put it up on the new network that's been sitting unused for the last 6 months. Today when I statically set the IP on the AD server (which is what I want) it connects and I can ping it's gateway 192.168.1.1 and all the way across vlans to a test sales agent workstation at 192.168.8.xxx on vlan 800 but only if I statically assign the agents station an IP address.
When I try to get an IP address via DHCP it fails as destination unreachable. Nothing has changed in the last 6 months on the DHCP server but now it for some reason can't ping its default gateway 192.168.1.1. All of the config files are the same as they where left from the post linked above aside from the vlan id's used where changed from 1's to 100's (i.e. vlan 3 is now vlan 300) /etc/network/interfaces
Code:
auto lo iface lo inet loopback auto vlan100
[code]....
why it can't reach the gateway, when I do a tcpdump I can see the DHCP requests come in on eth0 but the server never responds and I'm pretty sure its because it isn't "seeing" them since it thinks there isn't a network connection but I don't know how to trouble shoot to find out where the problem lies.
I am puzzled with trying to configure a linux (openSUSE) client to dhcp to eBox DHCP server. I am using dhclient to lease an IP address with dhclient eth0 -s 10.45.48.108 and get a response
openSUSE11232CL1 dhclient: DHCPDISCOVER on eth0 to 10.45.48.108 port 67 interval 4 openSUSE11232CL1 dhclient: DHCPOFFER from 10.45.48.108 openSUSE11232CL1 dhclient: DHCPREQUEST on eth0 to 10.45.48.108 port 67 openSUSE11232CL1 dhclient: send_packet: Network is unreachable openSUSE11232CL1 dhclient: send_packet: please consult README file regarding broadcast address.
The server reports eBox141 dhcpd: DHCPDISCOVER from 00:0c:29:3e:57:a3 (openSUSE11232CL1.domain.net) via eth0 eBox141 dhcpd: DHCPOFFER on 10.45.200.2 to 00:0c:29:3e:57:a3 (openSUSE11232CL1.domain.net) via eth0
I interpret this as the server receives the request and the client accepting it but the lease does not last long and the connection breaks. what this could be and why the connection breaks? Or my undestanding is totally wrong on how it works and should work? And BTW, where is that README file that's referenced in the message I receive on the client?
Currently I have my eth0 interface getting a DHCP address but at times the DHCP server will not be reachable. Sooo what I would like my server to do is if it cannot find a DHCP server assign a static address to eth0. Then start the DHCP service so it can then dish out some addresses.How can I do this? Surely it is possible
I have an embedded device for which I've created an html configuration page. This page allows you to set static IPs, dhcp, and can scan for wireless devices.My problem is that in order to access the device it requires that it runs as a dhcp server otherwise people are not assigned an IP and so can not access the embedded devices static IP. (This config page is for the laymen and so they are not the type who are able to set up their own static IPs). One of the potential options is to have the device connect to the network on eth0 acting as a dhcp client. However this prevents me from running a dhcp server.One solution I can think of is running a dhcp server only if it doesn't detect another dhcp server running on the network.
a Netgear router with DHCP off at 192.168.0.1 my computer
eth0 at 192.168.0.2 wlan0 at 192.168.0.2
The wlan0 interface always connects to the router, while the eth0 interface connects to other computers with crossover and acts as a dnsmasq DHCP server for network boot and installation.
If I use the Gnome NetworkManager to enable both connections, that is, with wlan0 connected to the router/internet and eth0 to another computer, both as 192.168.0.2, I cannot access the internet while eth0 is connected.
Why is this? How can I configure my computer to follow wlan0 for Internet usage, but use eth0 for itself (the latter is working but blocking wlan0).
I am using wvdial to connect to a mobile network (I have a usb modem) and it works fine. However, I wanted to automate the connection a bit (currently I am running wvdial every time I want to connect). I was wandering if there is a way to add this network to /etc/network/interfaces (in a truly Debian way) to have it connect on startup and/or whenever I connect my modem.
I'm often on my corporate network but also need to be on another network simultaneously. At the moment I have to manually switch back and forth between the two. I'm using ubuntu 10.04. I've come across an excellent document that explains how to do this: "Linux Advanced Routing & Traffic Control HOWTO" by Bart Hubert. He mentions:
make sure that your kernel is compiled with the "IP: advanced router" and "IP: policy routing" features
I've downloaded the kernel sources, but I don't find any config options with names like these in them.
So my question is...how can I tell if the kernel I have has these config options. Failing that, how do I build a kernel that does support these things?
Additional use cases for this knowledge. (1) At work with desktop computer plugged into corporate network. Plug 3g phone into USB port. My corporate network wont allow me to access my external servers over ssh, but the 3g phone will. (2) At home on the corporate VPN, but would like to access my other local network computers.
When I run cat /etc/network/interfaces in Ubuntu 11.04 I get the below output. auto lo iface lo inet loopback I don't see the eth0 or eth1 interfaces, but I am able to see them in the Network Tools application. How do I configure the eth0 and eth1 from command line?
I have an embedded device for which I've created an html configuration page. This page allows you to set static IPs, dhcp, and can scan for wireless devices. My problem is that in order to access the device it requires that it runs as a dhcp server otherwise people are not assigned an IP and so can not access the embedded devices static IP. (This config page is for the laymen and so they are not the type who are able to set up their own static IPs). One of the potential options is to have the device connect to the network on eth0 acting as a dhcp client. However this prevents me from running a dhcp server. One solution I can think of is running a dhcp server only if it doesn't detect another dhcp server running on the network. However I have no idea how this could be setup.
I have two physical NICs (eth2 & eth3) with eth2 connecting to the home router/dhcp server and eth3 connecting to another machine which needs access to the internet. I'm trying to create a bridge so that the second machine on eth3 can be connected on the lan. I've tried the following, however it hangs when attempting to get an IP address from the router. Likewise, attempting to give it a static route doesn't seem to work either.
$ sudo aptitude install bridge-utils $ sudo ifconfig eth2 down $ sudo ifconfig eth3 down $ sudo brctl addbr br0 $ sudo brctl addif br0 eth2 eth3 $ sudo dhclient br0 # this hangs and fails to get a dhcp address
I've tried to ensure my routing table mimics what it looks like when using eth2 normally, I cannot hit the gateway at all.
$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 2 0 0 br0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 br0
I attempted an 'arping' to the MAC address of the router while I had eth2/3 bridged, but it failed to obtain it's IP address as well. One interesting thing I noticed was that attempting to bring down the bridge & reactivate my internet on eth2, I was having trouble pinging the gateway. It turned out 'ipmasq' had been installed and was running causing odd problems. When I stopped the ipmasq service, my internet started working properly again. I removed the 'ipmasq' package entirely and tried bridging the NICs again thinking it may have been causing problems, but it still failed.
I have two HP servers which have a total of 10 Ethernet ports each, both running RHEL 5.7. I need to make sure that Ethernet ports are mapped to the same devices in Linux on both systems (see below) because these servers must be identical (the second box is a drop-in replacement in case the first system fails).The ethernet ports on the first system are mapped as follows:
Device Port eth0 Intel Dual Port Card, Port 1 (Rightmost Port) eth1 Dual, Port 2
We have a server and a target board. Most of the times I am able to mount the server through network file system. But sometimes it is observed that mounting hangs. When this happens, it was noted that both ethernet interfaces are up. Now when I make one down,mount works properly. The interface which I made down was having dummy(default) IP address, gateway etc.
Does this mean that all of my network interfaces are listening as opposed to just one specific network interface? Would 0.0.0.0 include 127.0.0.1?
Also, this computer(A) is on a LAN at my house. It has two network interfaces(eth0 & eth1), both on different subnets. I can connect from another computer(B) on my LAN to this one on one interface(eth0) via SSH just fine. The other interface(eth1) on this computer is hooked up to it's own gateway to the internet using DSL. I'm using this interface(eth1) for running bind.
Anyhow, here's my issue. When using a computer(C), which is a hosted VM , from outside my LAN, to connect to computer(A) via SSH, I get connection refused. So I checked my hosts.deny & hosts.allow files, both empty. I run nmap from computer C and SSH comes up as closed. So I'm thinking it's a firewall issue.
Here's what my iptables -L looks like:
Code:
I've been meaning to learn more about iptables, but which chain is for which network interface? I have also tried running nmap from computer(C) to test bind out on tcp 53 that comes up closed. I run udp 53 and that comes up as closed but then again udp is funny because it's stateless. If I run netcat on udp port 53 from computer C I get a blank line as if it's still running. However, I get that for all other ports anyways so that's of no use.
Unless my AT&T DSL is blocking those ports. But if that were the case would the error 'Connection refused' come up when I try to connect via SSH?
I had been using Guarddog for iptables but I updated to KDE4 and guarddog does not work with KDE4, neither does Firestarter. Is there a Graphical interface for iptables available that works with KDE4?