[TriLUG] DHCP renewal problems

[Matt Pusateri]

I think this is probably script/hardware related.  Your script doesn't 
set the MAC does it?  Does it load or unload modules?  Do you need to do 
a whole network restart or just down the interface and bring it back 
up.  I assume your using the internal onboard NIC's in the SC1435's ?  
Can you put a network card that is known to work(in another machine) in 
the SC1435's and test that?


Matt P.

Tim Jowers wrote:
> Stab in the dark but maybe the MAC addresses are the same and causing a
> problem with DHCP? I'm not sure what cards do when none is entered as some
> allow you to enter a MAC address. I'm seeing something related but different
> on my home network. I had one machine with a fixed IP: 192.168.1.6 and then
> I added a 4th machine and the router gave it 192.168.1.6. Conflict. Well, I
> shut down the second 192.168.1.6  machine but now when I ssh to the original
> 192.168.1.6 machine then it takes like 2 minutes for the password prompt to
> come up. I'll try to reboot all router and machines once I get a chance to
> mess with it.
>
> Tim
>
>
> On Jan 21, 2008 10:35 PM, Christopher L Merrill <chris at webperformance.com>
> wrote:
>
>   
>> Alan Porter wrote:
>>     
>>>> Any ideas?  I don't even know where to start googling...
>>>>         
>>> Try setting the address manually:
>>>
>>>    ifconfig eth0 192.168.1.103 netmask 255.255.255.0 up
>>>       
>> Any invocation of "ifconfig" results in a non-responsive terminal (i.e. it
>> hangs).
>>
>>     
>>> And then see if you can see the DHCP server:
>>>
>>>    ping 192.168.1.1
>>>
>>> You may need to set a route:
>>>
>>>    route add default dev eth0
>>>
>>> See if there are any firewall rules:
>>>
>>>    iptables -L -n -v
>>>       
>> iptables is not installed
>>
>>     
>>> Post your DHCP client's config file here.  Some might have clauses
>>> about "request" and "require" that can cause the client to refuse
>>> an offered address.
>>>       
>> Would that be /etc/dhcpclient.conf or something similar?  There is
>> no /etc/dhcp* on the machines in question.  I assume that means
>> it is using all default settings.
>>
>>     
>>> Post your DHCP server's config file here.  There might be some
>>> special entry for the server that works, and might be missing for
>>> the one that doesn't.
>>>       
>> Here it is.
>>
>> #       $OpenBSD: dhcpd.conf,v 1.1 1998/08/19 04:25:45 form Exp $
>> #
>> # DHCP server options.
>> # See dhcpd.conf(5) and dhcpd(8) for more information.
>> #
>>
>> # Network:              192.168.1.0/255.255.255.0
>> # Domain name:          my.domain
>> # Name servers:         192.168.1.3 and 192.168.1.5
>> # Default router:       192.168.1.1
>> # Addresses:            192.168.1.32 - 192.168.1.127
>> #
>> shared-network LOCAL-NET {
>> #       option  domain-name "my.domain";
>> #       option  domain-name-servers 24.25.5.60, 24.25.5.61;
>>        option  domain-name-servers 24.25.4.108, 24.25.4.109;
>>
>>        subnet 192.168.1.0 netmask 255.255.255.0 {
>>                option routers 192.168.1.1;
>> #               option static-routes 192.168.2.0 255.255.255.0
>> 192.168.1.101;
>>                range 192.168.1.200 192.168.1.249;
>>        }
>>        subnet 24.172.127.52 netmask 255.255.255.252 {
>>        }
>> }
>>
>>
>> TIA,
>> Chris
>>
>> --
>> ------------------------------------------------------------------------ -
>> Chris Merrill                           |  Web Performance, Inc.
>> chris at webperformance.com                |  http://webperformance.com
>> 919-433-1762                            |  919-845-7601
>>
>> Website Load Testing and Stress Testing Software & Services
>> ------------------------------------------------------------------------ -
>> --
>> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
>> TriLUG Organizational FAQ  : http://trilug.org/faq/
>> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
>>
>>