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)
[Code]...
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.
[Code]...
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 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?
laptop: averatec 6200 series
ethernet driver: SiS 900
wirless lan driver: rt2500
I got 10.04 installed and running pretty well.I cant get the wired ethernet to work but the wireless works. i did the the command line
[Code]...
also, dont know if i matters but ive got 8mbps/1.5mbps cable (motorala surfboard cable modem) and a linksys wrt54g wireless router.
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.
My /etc/network/interfaces:
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.
View 9 Replies View RelatedI have a home WiFi network that has been working fine for ages, which currently supports two Windows-based laptops and a WM5 smartphone. They all connect to the WiFi router (Linksys WRT54G) which in turn connects to the ADSL modem (Huawei MT882). The router is configured with a WEP key, the SSID is not being broadcast, and all MAC addresses must be whitelisted. I try to follow good wireless network security practice. I also have NAT running between the router and the modem.
Everything is working fine for the Windows clients, and now I am trying to add my Linux box to the mix. I am setting up an older HP Pavilion 510a desktop with Ubuntu v8.04LTS, using a Realtek RTL8185 WLAN card. The machine has an onboard RTL8139 LAN adaptor also, which works fine when I plug it in directly to an ethernet port on the wireless router. The WLAN, however, does not seem to be getting a DHCP packet, and keeps on autoconfiguring with a 169.254.x.x address. When I try giving it a static IP address it doesn't connect either.
As you can see from the screenshots below, the WLAN is working fine. I have it installed using the ndiswrapper and Windows drivers. I've been through the Comprehensive ndiswrapper troubleshooting guide but that did not resolve my problem.
I configured the network myself, and it works perfectly for my Windows machines. It is just my lack of experience with Linux which is preventing me from getting the wireless to work under Linux. I can get a HDCP packet in Linux when I am connected to the LAN using the RTL8139 adaptor, but not on the WLAN using the RTL8185 adaptor.
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.
Is there any way to get an async notification (perhaps through something like a Linux message queue or Unix socket) when a DHCP client is either unable to renew its lease, or the address obtained changes from the previous value? I've got the ISC client and will dig into it to determine if it supports such a feature, but thought I'd ask here in parallel. (I'm trying to find out if there are any DHCP clients out there which already support this capability.)
If you're curious: We have an application where we're doing auto-registration of an IP camera to an external server. If the camera's dynamically assigned address changes, we need to restart the auto-reg state machine. I've seen implementations where a socket is opened and a SIOCGIFADDR ioctl used to fetch the IP addr, but I'd sure like to avoid polling like this if possible.
We have 20+ Redhat servers on our network and every so often our DHCP server goes down. When it comes back up we have to go around to all of our RedHat servers and restart networking manually. Other OS's (Ubuntu, Windows, etc..) will continually try to get a DHCP lease so that when our DHCP does come back up it requires no work from us for them to get back on the network. But it seems that Redhat only tries once and if it fails it never tries again. Have to go around to 20 different servers (some of them are at remote locations) is less then ideal when this happens. how we can get Redhat to continually try to get a DHCP lease like other OS's?
View 1 Replies View RelatedThe system I am working on is a xdsl board running Linux kernel 2.6 and receiving dhcp address from a Microsoft XP PC. when looking through the dhclient.leases file I can see there's something wrong with renew time and stuff.strange calculation. as far as you know is this normal? You may find below the dhclient.lease file.
lease {
interface "tap0";
fixed-address 10.0.1.16;
filename "***";
medium "-link0 -link1 -link2";
[code]....
I got a strange issue here: We are using ISC DHCP v4 which is default in Open SuSE 11.4. These two options 'default-lease-time' and 'max-lease-time' are set in all subnets, with values between 43200 (12 hours) to 518400 (144 hours). See partial dhcpd.conf below please.Now the lease time from Windows client's ipconfig output is only 10 minutes. Why? (dhcpd on servers restarted many times. ipconfig /release, ipconfig /renew on client run many times)
Code:
lease-file-name "/etc/dhcpd.leases";
default-lease-time 43200; # 12 hours
[code]....
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?
View 1 Replies View RelatedI've set up a permanent DHCP lease for my MAC address. I did this hoping to resolve the fact that I share my Internet ADSL connection with my wife and my daughter (the latter a great bandwidth hog)!
View 5 Replies View RelatedI 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.
It was working just fine, until the other day I yanked it out. The wireless works just fine on the same router. If I login to a windows 7 instance on this dual boot laptop then the ehternet works just fine. So it's not a hardware, cable or router issue. The card even gets an ip, but I can't connect to the internet.
View 2 Replies View RelatedI would like to be able to schedule a limit for an IP connection for my kid's computers/iPods. Since I know the MAC addresses of their various hardware items, is there a way to shut down their connectivity at a particular time via the DHCP server or perhaps a firewall rule?
Running Ubuntu 10.04 and Shorewall is being used for the firewall.
Looking at var/log/messages below, it looks like I'm not being offered a lease on this particular network. I can successfully connect to the network because iwconfig wlan0 reveals my network ssid and the access point I'm connected to. But pinging google.com gives me nothing..
Code:
root@darkstar:/# tail -f var/log/messages | grep dhcpcd
Mar 28 15:45:42 darkstar dhcpcd[5329]: wlan0: adding IP address 169.254.76.182/16
Mar 28 15:46:13 darkstar dhcpcd[5329]: wlan0: adding IP address 169.254.76.182/16
Mar 28 15:46:44 darkstar dhcpcd[5329]: wlan0: adding IP address 169.254.76.182/16
[code]...
I'm having some problems bringing up my wireless card at boot time on my Red Hat Linux 9.0 box. After some investigation with the boot scripts, I noticed that it was having problems with the DHCP negotiations when the ifup wlan0 command is issued.I then tested the command outside of the booting process and everytime the command is issued the first time, the dhclient fails to get any DHCP offers and returns with the message Unable to obtain a lease on first try. Exiting. and then exits.
If I then issue the same ifup command again a second time, it successfully receives a DHCP offer from the router and receives the needed IP address, and after this, the Internet connection on the box works fine. It is consistently doing this everytime. Why is it failing to obtain a lease the first time?
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 installed Scientific Linux 6. Does anyone know how to get it to connect to wired ethernet network?
View 3 Replies View RelatedI 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.
View 8 Replies View RelatedJust 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 two laptops (Dell & Lenovo), both have wifi.
I am having one wired Ethernet connection.
I want to share this Internet connection among two system , to access Internet from both the system.
I had tried by creating a wireless network, but was not able to do so.
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'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)
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
[Code]....
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.
View 2 Replies View RelatedI 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.
View 5 Replies View Related