Backtrack IP resets every few minutes
Guus
gbonnema at xs4all.nl
Fri Jun 29 17:19:43 UTC 2012
On 06/29/2012 07:05 PM, TopBot . wrote:
>
>
> On Fri, Jun 29, 2012 at 3:22 AM, Guus <gbonnema at xs4all.nl
> <mailto:gbonnema at xs4all.nl>> wrote:
>
> On 06/28/2012 06:54 PM, TopBot . wrote:
>>
>>
>> On Thu, Jun 28, 2012 at 8:56 PM, Guus <gbonnema at xs4all.nl
>> <mailto:gbonnema at xs4all.nl>> wrote:
>>
>> On 06/28/2012 04:54 PM, TopBot . wrote:
>>>
>>>
>>> On Thu, Jun 28, 2012 at 7:28 PM, Guus <gbonnema at xs4all.nl
>>> <mailto:gbonnema at xs4all.nl>> wrote:
>>>
>>> On 06/28/2012 04:06 PM, TopBot . wrote:
>>>> Hi, I've been using backtrack 5 since a year on the
>>>> same system and the same lan card. Since yesterday, my
>>>> IP resets every 2-3 minutes and I have to repeatedly
>>>> add "ifconfig eth0 192.168.xx.xx" and "route add
>>>> default gw 192.168.xx.xx" to it to keep it running.
>>>> Can't seem to find the solution after a few google
>>>> searches. Any one has any idea what's wrong? I have
>>>> dual boot and windows xp is working just fine on the
>>>> same lan.
>>>>
>>>> --
>>>> TopBot.
>>>>
>>>>
>>>
>>> Here's what the IP resets to (settings before and after the
>>> reset respectively):
>>>
>>> root at bt:~# ifconfig -a
>>> eth0 Link encap:Ethernet HWaddr 00:1a:92:95:81:ca
>>> inet addr:192.168.93.92 Bcast:192.168.93.255 Mask:255.255.255.0
>>> inet6 addr: fe80::21a:92ff:fe95:81ca/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:34391 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:18367 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:15099569 (15.0 MB) TX bytes:4144722 (4.1 MB)
>>> Interrupt:20
>>>
>>> <snip>
>>> ...settings are lost/initialized after the reset I think. My
>>> lan uses switches and a server which is connected to the
>>> main server; our IPs are static on the lan with no
>>> restrictions. All my auto updates are off and I did not
>>> change any settings. It just started to happen since a day ago.
>>>
>>> Yes, I posted to both lists (I'm subscribed to both), my bad
>>> if that's not the norm here.
>>>
>>> --
>>> TopBot.
>> Hmmm, could you check your logs for messages? Start looking
>> at /var/log/syslog. I found lots of IP related messages in
>> my syslog. Also dmesg might contain a hint. Try to find out
>> why it resets. Then you have more to go on.
>>
>> --
>> Kind regards, Guus Bonnema.
>>
>>
>> Couldn't find any reset related messages at the log.
> <snip>
> As far as the logs, if you lose your IP address, there must be
> something in the logs that indicates what is going on.
>
> --
> Kind regards, Guus Bonnema.
>
>
> Yes, windows is not facing the problem.. I'm attaching my log incase I
> didn't get something. I tried running it on dhcp but that didn't work
> too. I've to reset my IP every other minute still but I don't
> understand why this does not happen when the lan cable is not plugged
> in.. makes me thing this has something to do with my networl
Looked at your syslog. These lines stand out:
Jun 29 06:30:41 bt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 5
Jun 29 06:30:46 bt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 12
Jun 29 06:30:58 bt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 19
Jun 29 06:31:17 bt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 20
Jun 29 06:31:37 bt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 5
Jun 29 06:31:42 bt dhclient: No DHCPOFFERS received.
Jun 29 06:31:42 bt dhclient: Trying recorded lease 192.168.137.206
Jun 29 06:31:45 bt dhclient: No working leases in persistent database -
sleeping.
Jun 29 06:34:44 bt dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 8
I looked the message "No working leases in persistent database" up and
it points to Network Manager.
Did you know you have Network Manager running? If you have a fixed IP
address, why do you have Network manager running? As I recall, one of
the first responses on this thread was whether you had Network manager
installed.
Probably Network manager and manual setting of IP interface don't work
well together. You could try disabling or uninstalling Network Manager.
But check the docs first though.
Anyone on this thread who understands Network Manager stuff? Maybe can help?
--
Kind regards, Guus Bonnema.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kubuntu-users/attachments/20120629/84211a23/attachment.html>
More information about the kubuntu-users
mailing list