LinuxMCE Forums
May 20, 2013, 10:27:20 pm GMT-1 *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
 
   Home   Help Search Chat Login Register  
Pages: [1]
  Print  
Author Topic: dhcp-server failed to start after replacing internal nic  (Read 768 times)
deffcon
Veteran
***
Posts: 94


View Profile
« on: November 10, 2008, 09:08:16 am »

Hi,

After some reading on the net and following syslog, i decided to replace my internal network card, my old one was an attansic ( atl1 ) and the new one is an tg3
My problem is now that my dhcp-server won't start anymore, the only logging i could find is this :

Nov 10 08:56:41 dcerouter dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 10 08:56:41 dcerouter dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 10 08:56:41 dcerouter dhcpd: All rights reserved.
Nov 10 08:56:41 dcerouter dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 10 08:56:41 dcerouter dhcpd: Wrote 0 deleted host decls to leases file.
Nov 10 08:56:41 dcerouter dhcpd: Wrote 0 new dynamic host decls to leases file.
Nov 10 08:56:41 dcerouter dhcpd: Wrote 0 leases to leases file.
Nov 10 08:56:41 dcerouter dhcpd: socket: Address family not supported by protocol - make sure
Nov 10 08:56:41 dcerouter dhcpd: CONFIG_PACKET (Packet socket) and CONFIG_FILTER
Nov 10 08:56:41 dcerouter dhcpd: (Socket Filtering) are enabled in your kernel
Nov 10 08:56:41 dcerouter dhcpd: configuration!
Can someone help please,


Thanx a lot,

Dave
Logged
superfro
Regular Poster
**
Posts: 24


View Profile
« Reply #1 on: November 10, 2008, 05:43:08 pm »

try searching for tg3 in the logs or 'dmesg | grep -i tg3' or 'eth0' 'eth1' ... basically make sure the nic is being recognized....

Its possible that the driver is outdated for your card thus giving the error because no nic was loaded...

Another problem could be since you swapped nic's it changed the eth0/eth1/eth2 numbering and dhcp-server is set to listen on eth0 (or 1) and the new nic you added enumerated as eth2 or something...

check the 'ifconfig' command ... and see what nic the dhcp-server is listening on
Logged
Zaerc
Alumni
LinuxMCE God
*
Posts: 2256


Department of Redundancy Department.


View Profile
« Reply #2 on: November 10, 2008, 06:48:19 pm »

I'm betting you'll want to edit your /etc/udev/rules.d/70-persistent-net.rules file, and update it to your current situation. 
Logged

"Change is inevitable. Progress is optional."
-- Anonymous

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!