Re: resolv.conf getting erased

2009-01-30 Thread tyler
tyler tyler.sm...@mail.mcgill.ca writes:

 Thanks for all the tips, on and off-list. I noticed that at the same
 time as my resolv.conf was getting cleared, something was bringing up
 the eth0 interface. After much poking and prodding, I found that
 commenting out the allow-hotplug lines associated with eth0 in my
 /etc/network/interfaces, ie:

   # The primary network interface
   # allow-hotplug eth0
   # iface eth0 inet dhcp

 seems to have solved the problem. This is something I was messing with
 months ago, and I have no idea why (or if!) the associated behaviour
 changed now. Anyways, things seem to be working fine now. We'll see what
 happens when I plug into eth0 at work tomorrow.


I've been working at home all week, just plugged into my work eth0. On
resuming from hibernate to disk, only the lo interface was up. I plugged
in the ethernet cable and called ifconfig eth0 up. The eth0 network was
up, without an IP, and I also had an entry for eth0:avahi:

eth0:avahi Link encap:Ethernet  HWaddr 00:16:d3:29:0d:aa  
  inet addr:169.254.5.190  Bcast:169.254.255.255  Mask:255.255.0.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  Interrupt:16 

I then called dhclient eth0, and got an IP on eth0. Everything then
seemed to be working, but dns lookups were slow. So I checked
resolv.conf, and this time, instead of being cleared of all useful info,
it had the dns servers for my work network *and* my home router:

tyler:~- cat /etc/resolvconf/run/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.2.1
nameserver 140.184.1.21
nameserver 140.184.1.22
search no-domain-set.aliant SMUNET.SMU.CA

So now I've got the opposite problem as before - instead of having
resolv.conf properly updated, I'm getting the new info appended. Which
means I still have to edit the file by hand. Any ideas what's wrong
would be most helpful!

I will eventually look into automating more of this, but I would like to
understand what's going on at a lower level, hence my current efforts to
sort this out at with dhclient and ifconfig.

Cheers,

Tyler

-- 
I never loan my books, for people never return them. The only books
remaining in my library are those I’ve borrowed from others.
   --unknown


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: resolv.conf getting erased

2009-01-30 Thread John Hasler
Tyler writes:
 So now I've got the opposite problem as before - instead of having
 resolv.conf properly updated, I'm getting the new info appended. Which
 means I still have to edit the file by hand. Any ideas what's wrong would
 be most helpful!

I'd start by removing resolvconf as well as network-manager and avahi if
they are installed.
-- 
John Hasler


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: resolv.conf getting erased

2009-01-26 Thread Osamu Aoki
On Sun, Jan 25, 2009 at 03:13:53PM -0400, tyler wrote:
 Celejar cele...@gmail.com writes:
 
  annoying. Any idea how I find out what is messing up my resolv.conf
  files?
 
  I'm no guru, but perhaps the audit package can help?
 
 Thanks for all the tips, on and off-list. I noticed that at the same
 time as my resolv.conf was getting cleared, something was bringing up
 the eth0 interface. After much poking and prodding, I found that
 commenting out the allow-hotplug lines associated with eth0 in my
 /etc/network/interfaces, ie:
 
   # The primary network interface
   # allow-hotplug eth0
   # iface eth0 inet dhcp
 
 seems to have solved the problem. This is something I was messing with
 months ago, and I have no idea why (or if!) the associated behaviour
 changed now. Anyways, things seem to be working fine now. We'll see what
 happens when I plug into eth0 at work tomorrow.

Are you rebooting system or restarting by hand.

You may want to automate this ...
 
http://people.debian.org/~osamu/pub/getwiki/html/ch06.en.html#automaticnetworkconfiguration


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: resolv.conf getting erased

2009-01-25 Thread tyler
Celejar cele...@gmail.com writes:

 annoying. Any idea how I find out what is messing up my resolv.conf
 files?

 I'm no guru, but perhaps the audit package can help?

Thanks for all the tips, on and off-list. I noticed that at the same
time as my resolv.conf was getting cleared, something was bringing up
the eth0 interface. After much poking and prodding, I found that
commenting out the allow-hotplug lines associated with eth0 in my
/etc/network/interfaces, ie:

  # The primary network interface
  # allow-hotplug eth0
  # iface eth0 inet dhcp

seems to have solved the problem. This is something I was messing with
months ago, and I have no idea why (or if!) the associated behaviour
changed now. Anyways, things seem to be working fine now. We'll see what
happens when I plug into eth0 at work tomorrow.

Cheers,

Tyler

-- 
The contents of this message have been carefully examined by skilled
artisans to ensure that only the purest, archival-quality, virus-free
bits have been used in its construction.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: resolv.conf getting erased - every 5 minutes

2009-01-24 Thread tyler
tyler tyler.sm...@mail.mcgill.ca writes:

 An update to the problem discussed below: on connecting to my wireless
 with dhclient ath0, I saw a warning that /etc/resolv.conf was not a
 symlink to /etc/resolvconf/run/resolv.conf. This was a consequence of
 having to manually correct /etc/resolv.conf to point at my wireless
 router for dns. 

 So I deleted /etc/resolv.conf, and replaced it with a symlink to
 /etc/resolvconf/run/resolv.conf, after confirming that this target did
 contain correct dns info. Twice in the last half hour since doing this,
 this file has been cleared - only the comment lines at the top remain,
 all the dns info is gone. This breaks my internet connection, or at
 least my ability to resolve addresses.

 Calling dhclient ath0 restores the file, but this is getting really
 annoying. Any idea how I find out what is messing up my resolv.conf
 files?


Sorry to be a pest, but I've now determined that
/etc/resolvconf/run/resolv.conf is being cleared every five minutes.
There is nothing in my leases files, or in dhcp.conf, or in the message
I get from dhclient that indicates that the wireless lease should last
less than hours/days. This is beyond me, but it's making my computer
unusable for anything that requires internet connections. Which is just
about everything...

Thanks for any suggestions,

Tyler

-- 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: resolv.conf getting erased [WAS: dhclient not updating]

2009-01-24 Thread Celejar
On Sat, 24 Jan 2009 14:02:00 -0400
tyler tyler.sm...@mail.mcgill.ca wrote:

...

 annoying. Any idea how I find out what is messing up my resolv.conf
 files?

I'm no guru, but perhaps the audit package can help?

http://www.cyberciti.biz/tips/linux-audit-files-to-see-who-made-changes-to-a-file.html

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org