Networking :: Mint Current Distro - Shut Off DHCP For A Wired Ethernet INC?
Apr 16, 2011
I recently did some troubleshooting on a USB wireless dongle hooked up to my Mint distro. I need the USB wireless to access a home DSL wireless modem out to the Internet. The wireless DSL is on 192.168.0.1
I also have a 10/100 ethernet NIC in the computer, for non-wireless connections. The wired ethernet is all 192.168.1.1. I noticed in /var/log/syslog that there are numerous "DHCPDISCOVER on eth0 to 255.255.255.255 port 67" messages.
Since eth0 has a hard-coded IP, I dunno why DHCP is trying deal with it. Can I turn off DHCP activity against eth0? How to do that?
I have a Zotac Ionitx A-U. I can't get it to establish an internet connection with the wired ethernet within Ubuntu. The chip is detected, but trying to bring up the connection stalls out at trying to obtain a DHCP lease, like this:
DHCP DISCOVER ... DHCP DISCOVER ... No DHCPOFFERS received Specs: Ionitx A-U Ubuntu 10.04 x64 kernel 2.6.32-22 (also didn't work in 9.10)
I'm running an up-to-date Fedora 12 machine with the Gnome desktop (meaning with Network Manager). My network connection is a wired ethernet to a switch which then connects to a Netgear router. For some reason, this machine can't renew its leases with DHCP, so NetworkManager deactivates eth0, taking my machine off the network. I have to click Network Manager and enable eth0, which seems to work every time.
How can I fix it? Here are the relevant bits from /var/log/messages showing a failed DHCP request and then the successful renewal.
Code: Aug 1 04:00:08 ironton dhclient[12452]: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Aug 1 04:00:08 ironton dhclient[12452]: DHCPNAK from 192.168.1.1 Aug 1 04:00:08 ironton NetworkManager[1261]: <info> (eth0): DHCPv4 state changed reboot -> expire Aug 1 04:00:08 ironton NetworkManager[1261]: <info> (eth0): device state change: 8 -> 9 (reason 6) Aug 1 04:00:08 ironton NetworkManager[1261]: <info> Marking connection 'System eth0' invalid because IP configuration expired.
I want my netbook to connect automatically to both the office wired/static network and to the usual wired/DHCP networks.
wicd is wicked but netsearching hasn't revealed how to configure it for both wired/static and wired/DHCP except by manually switching profiles.
wicd's profiles can use pre/post(dis)connect scripts but I don't know how to integrate them into wicd when they are upping/downing connections on cable (un)plugging.
If it is not practical to solve this within wicd, I'll explore standalone scripts to configure eth0 on cable (un)plugging, as detected by ifplugd.
I've brought a friend over to linux from windows. He has some how deleted his "Wired Etho" connection. He said his computer would not shut down(Mint Linux 9), so he unplugged it. You guessed it right after restarting no internet. After checking under "Network Connection" his wired connection is gone. My question is? How to reconfigure a "Wired Etho" connection? He has a dsl connection running a Linksys router(sorry I don't know the model number). I have only talked with him on the phone, so I have not personally checked the system out. I just finished working on it this past sunday and everything was fine.
OS: Linux Mint 10 | Windows 7 Install Type: WUBI inside windows 7 Computer: HP Compaq Presario CQ56' Network: Realtek PCIe FE Family controller w/ Realtek 8102E chipset Problem in: Network Connection Issue: After I woke up my computer from Sleep, I lost ethernet. No connection. It told me that I had lost my connection. Why? Now, after several restarts, nothing.
A quick rundown of my equipment and plan for this particular machine.
SOYO P4I845PEISA Motherboard Intel Pentium 4 2.0GHz Processor 512MB DDR333 RAM ATI Radeon 8500 128mb AGP Video Card Using onboard AC'97 Audio and Davicom NIC Linksys BEFSR81 Wired Router
I am setting up a multiboot system with several OS's, multiple versions of Windows & several Linux distros. The main point of it all is just to have a system where I can load up a given version of Windows or Distro of Linux if I need to test something or show someone how something works.
The Problem: 5 versions of Windows installed, all hardware configured and functioning properly (including NIC) All Windows versions obtain DHCP IP addy with no problems.
Installed Red Hat Linux 9 (first of my linux distros) and it autoconfigured all of my hardware and has no problem getting an IP address.
Installed Fedora 8 and it could not obtain an IP address. I fiddled around with the network settings changing this and that, covered all of the options, and it had no effect. By this time I was irritated, so I just formatted and reinstalled the whole thing, which had no effect and resulted in the same problem. I decided to try it again, this time turning off my sound card and nic for the initial installation. After the initial install, I turned on the sound card and booted up to install it, then restarted, turning on the nic to install it. Fedora installed them both, and managed to get an IP address from my router.
I looked at the ifcfg-eth0 file and the only thing that was different from the previous installs was that a line reading "type=ethernet" (I believe thats what it said) was not there in the working install and had been before.
Puzzling and irritating, but Fedora was now working so I moved to the next distro on my list.
openSUSE 11.0 First install I tried the same thing I did with Fedora (turning off the NIC which did not work like it did in Fedora) Second install, left all of my hardware enabled, and made it to the part where it asks to verify your internet connection. I clicked Test, and got this error:
Opening of Connection eth0 device: Davicom Semiconductor, Inc. 21x4x DEC-Tulip Compatible 10/100 Ethernet (rev 40) DHCP Client is already running on eth0
I finished the install, and then got on another machine and I searched the net for this error, but could find nothing that specifically applied to my problem. I played around with the network settings, tried a couple of things that I had come across in my search (changed between tulip and dmfe, checked the box for "Request Broadcast Response", ran "service network restart" in Terminal) none of these had any effect.
The most irritating thing about this is that RHL9 had no problem with this whatsoever and it is badly dated, and the much newer distros are choking on it.
I run Ubuntu 10.04 on a PackardBell laptop, with an Orange Livebox 2 providing ADSL. I am connected to the Livebox via WiFi, but I can't connect using the ethernet cable. I think that in making changes to the system some time ago I must have ruined something, but I can't work out what.
My ISP finished some 'upgrades' on its infrastructure. The result is that I am having great difficulty in connecting to the internet.
I have 3 operating systems on my box - XP, Fedora 8 and Feota 12.
I connect using an ethernet card, using dhcp. In fedora 12, the ethernet card is controlled be networkmanager. After the ISP completed their upgrades, I was not able to connect. I tried to connect manually using
Code:
There was an error message -
Code:
I read the advice here: [url], and removed all but the important lines.
But even after that neither ifup eth0 or dhclient eth0 works.
In fedora 8, the ethernet card is activated by ifup eth0 in /etc/rc.local. I was able to connect on a couple of occasions, but that too stopped working. I tried both ifup eth0, dhclient eth0, and tried to use the gui( which fires the dhclient command), but none worked.
When I use windows, it takes about 2 minutes to get an ip (earlier it was immediate). Sometimes that doesnt work and I have to click on "repair" whereupon it starts working.
I have a HP Mini running Ubuntu Desktop 10.04, and I cannot get a wired connection to work. My network card is "Broadcom Corporation BCM4312 802.11b/g (rev 01)", and I have the restricted drivers for the card installed. Wireless works fine, though.
I've got Puppy Linux on a USB key, and yesterday, while I was on the internet with it, it hanged. I didn't know what to do, and I rebooted from the button (I now know what to do ). The problem is that, after rebooting, Puppy doesn't recognise the router. I've tried to apply the drivers that are on Puppy, but there aren't any compatible.
My router is a Xavi 7968 and my Network Card is:
NIC Fast Ethernet PCI Familia RTL 8139 from Realtek
(On Realtek's website, there isn't any driver linux-compatible)
Since that time I moved to Archlinux and I love it. I do however run lubuntu live from a USB for my work PC. I am having a problem with it. I think it's okay to post here because the core of the system is still Ubuntu. I don't think LXDE is the problem. I start up the live environment and it says 'wired connection connected' but I can not load any pages or do anything.
I thought it may be a problem with configuration so I copied down (from Windows) the IP, Subnet, Gateway and DNS. I put them in manually and it doesn't say connected any more and still no connection at all. I am unsure what to do from here. I am not really familiar with Ubuntu enough to try much. I tried to 'dhcpcd eth0' but dhcpcd isn't installed. I guess the default Ubuntu network manager has dhcp enabled automatically.
Just noticed that auto connection to my wired ethernet is not being established after restarts I'm making. Never recall this in the past. I do get an auto connect when I shutdown and restart. I'm using 10.04 LTS Lucid Lynx.
Also have noticed that nearly every upgrade over the past week or so is calling for restart to complete the upgrade. Can there be any unwanted problems in doing several upgrades over a period of several days before doing the restart? I'd like to think not.
As you can imagine these two issues together are causing some lost time.
I have installed Ubuntu 11.04 using Wubi through Windows 7. It seems to be working but it will not connect to my wired internet connection. It tells me there is no wired connection, when there is. I used sysinfo and its not showing any network adapter or controller. I have a board with nvidia nforce go 430, could it be a driver issue. It works fine in windows though. Tried using a wireless adapter and all is working. But why doesn't the wired ethernet connection work.
I have a generic P4 desktop computer with Debian Squeeze. Since instalation my wired ethernet connection will slowely slow down and then quit when surfing the web. Sometimes it seems worse than othertimes. If it fails I usualy can get it to come back back up by going to Network Connections and clicking on "wired connection"and them just closing the window. It will work for a bit but the conection will inevitably quit in a short time again. Interstingly it seems mostly a problem with web browsers as doing upgrades, package instalations, using SMXI and things of this sort do not seem to be a problem. I have tried both Epiphany and the Squeeze default Iceweasel with identical results. Also when using Google Earth a similar situation occurs in about 2 minuits of use. The same computer running Debian Lenny with Epiphany and WXP with the dreaded IE do not have this problem.
i already have an eth0 configured to automatically get its info from dhcp.
but i wanna configure eth1 to be able to serve dhcp and dns. i havent configured either dns or dhcp server on the server box since i have not configured the serving interface.
so far my interfaces file is:
Code: # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp
I acquired an older hp compaq presario computer version 6310us, and initially installed mint, followed by Ubuntu 9.04. Neither one recognized the onboard ethernet port. I checked the bios, and LAN is enabled. It is also enabled in the drop down menu from the toolbar on the desktop. The cable works fine on other computers, and the light on the ethernet port flashes like it does when the cable is connected. I'm new to linux, so not sure what to do to get the connection working.
while my brother was browsing the web on my windows partition he had a blue screen pop up, one of the soft/hardware error ones, not a true BSOD, anyways, ever since my lan port on the computer seems to not be activiating as no wired connection is recognized. The lan port/card is directly attached to the Mother Board, it's a gigabyte motherboard in a self-build computer. I'm just wondering if there's anything I can do to troubleshoot this and see if it is truly a hardware problem or if its something else.
I have just installed ubuntu 10.04 using the wubi installer to dual-boot my machine. Under ubuntu, I am not able to connect to the internet or my router. Everything works fine under windows. I have tried to find relevant information in the forums, but nothing seems to work for me. I have tried disabling ipv6, setting a static ip, but no go. ifconfig shows no IP, dhclient results in no DHCP offers and pinging my router's IP results in Network is Unreachable.
I'm having mysterious wired network problem with my Karmic/9.10 machine. It hasn't been in network a while, but now I finally got the cabling done. I can't get the IP from dhcp server (TW-EA510), and static settings doesn't work either. Fresh cabling showed OK 1Gb connection on tester, and win7 laptop works fine. I even tried with long cable though the rooms, but it doesn't help, so it definately isn't the new cabling.
Log from the router after issuing #"dhclient": Feb 16 23:01:43 DHCP SERVER: DHCPDISCOVER from 00:01:29:fb:c5:d1 via br0 Feb 16 23:01:43 DHCP SERVER: DHCP offer to 00:01:29:fb:c5:d1 Feb 16 23:01:49 DHCP SERVER: DHCP request from 00:1b:ea:c8:a0:ba Feb 16 23:01:49 DHCP SERVER: DHCP ack to 00:1b:ea:c8:a0:ba Feb 16 23:01:54 DHCP SERVER: DHCPDISCOVER from 00:01:29:fb:c5:d1 via br0 Feb 16 23:01:54 DHCP SERVER: DHCP offer to 00:01:29:fb:c5:d1 Feb 16 23:02:03 DHCP SERVER: DHCPDISCOVER from 00:01:29:fb:c5:d1 via br0 [Code]....
Motherboard is some old Lanparty with two ethernet ports, NVidia CK804 and Marvell 88E800 rev 13 Gigabit netwok adapters, neither of them works. At least another of them has been worked earlier when I last got it wired. It's been a while, so I'm not sure which one of them and with different router if that matters.
After upgrading from karmic to lucid yesterday made my RTL 8111 -network card die. It's integrated on Intel D510mo mini-itx board.
dmesg:
Code:
After some googling I found out a lot of forumposts about the same problem from year 2007, but the troubles seem to disappear on the newer versions and seem to be back now? With those posts I managed to get the link up by using ethtool by setting autoneg off and setting speed to be 10mbps and half duplex. Any other speed/duplex combination fails.
One suggestion I found was to install r8168-driver from Realtek instead of the r8169. It didn't help, result was very much the same.
I booted to 9.10 live-cd and there the network worked as intended (100Mbps, I dont have a gigabit switch)
I really wouldn't like to fall back to 9.10, but my file server is not very usable with 10mbps.
I have been using Linux Mint with great success for about 5 months. The other day when I went to turn off my computer instead of selecting shut down, I accidentally clicked on "Hibernate". Now my computer will not turn on, even after a hard shut down. Nothing comes up, not even the BIOs screen. It did this once before and my Linux-guru ex was able to fix it, but I will be dammed if I remember what he did.
Just installed Fedora 14 from the Live CD i686 on my Dell Inspiron 1521. I can't connect to the SpeedTouch 585 on either wireless broadcom card or the wired Ethernet card.
I can connect to it from the same Laptop on the Vista which is on dual boot on the same laptop.
Further confusing is that I ran Fedora 14 and connected to another SpeedTouch today.
Already checked the Channel on the wireless nic and it's on the same one as the SpeedTouch.
I've been struggling with this a bit now, and I'm not sure what the problem is. I have a laptop with a BCM4401 Ethernet card as well as a BCM4311 Wireless card. The wireless card works great out of the box, I'm able to connect with it perfectly. The problem is the ethernet card. Here is the situation: The NetworkManager menu doesn't list "Wired Networks" at all (ie. it doesn't say "not managed", it just only lists Wireless networks) Going into Network Connections, there is an "Auto eth0" entry ifconfig shows eth0 (which I assume means NetworkManager isn't managing eth0) I have edited /etc/NetworkManager/nm-system-settings.conf to say managed=true I have edited /etc/network/interfaces to remove any mention of eth0 (all that's left is the "lo" lines) So I'm not sure why eth0 is still showing up when I run ifconfig, and why Network Manager is not managing it. Any ideas?
Edit: Not sure what I did but now ifconfig spits out this:
Code: eth0 Link encap:Ethernet HWaddr 00:1c:26:2c:60:75 inet addr:10.0.1.12 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::21c:26ff:fe2c:6075/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[Code]...
The MAC address of the "Auto eth0" entry is 00:1C:23:8F:D4:39, the same as the eth1 entry that ifconfig spits out.
After so recent updates, I find the network connections has changed.
I see now that it connects to the network (dsl) by default. I unchecked the box 'connect automatically', yet it still is connected by the time the monitor turns on when awakened from sleep or hibernation.
How can I get the auto network connection turned off without physically pulling the plug?
I am pretty new to Linux, but I've been installing it on different systems for a month or so, using different distro's, and this is the first problem where I absolutely can not find a single relevant answer in Google. I recently bought an IBM Thinkcentre and set it up to dual boot Mint and windows xp, it worked great everything works except usb's.
#PROBLEM: The ports only recognize devices of any kind (controllers, mouse, flash drive, external hd) if they plugged in before booting, or if they are plugged in while the computer is sleeping.
- The usb's are recognized normally in Windows XP I tried running different live cd's (Fedora, openSUSE, ubuntu) and they all had the same problem (could this be an issue with the defualt linux 2.6 kernel not working properly with my hardware? if so I dont know what to do next) I reinstalled a newer version of Mint... same problem.
