[xubuntu-users] Wireless + wired connection

[Nicolas Ferré]

The problem is solved, at least partially. Actually, I manually set up 
the wireless connection, instead of using the so-called "roaming mode". 
Now it seems that the connection is recognized at some point during the 
boot. Tomorrow, I'll see at work if the wired connection (eth0, not 
eth1) works well.

Thanks for you help.

Charlie Kravetz a écrit :
> On Sat, 2008-01-26 at 10:57 +0100, Nicolas Ferré wrote:
>> Charlie Kravetz a écrit :
>>> On Wed, 2008-01-23 at 10:41 +0100, Nicolas Ferré wrote:
>>>> Hi,
>>>>
>>>> I installed Xubuntu on my laptop a month ago and there is something
>>>> bothering me. At work, I have a wired internet connection I set up
>>>> manually. At home, I have a wireless connection in roaming mode. Every
>>>> time I change my place, at start, Xubuntu complains about my hostname
>>>> not defined explicitly in /etc/hosts. Each time, I add it to /etc/hosts
>>>> but it get lost when I change my place !
> 
> < snip >
> 
>> Hi,
>>
>> I just connected at home (in wireless/roaming mode), and here is my 
>> /etc/hosts file:
>>
>> 127.0.0.1 localhost
>   This address and hostname is used by Ubuntu 7.10 and thus can not be
> changed by the user
> 
>> 127.0.1.1 zeeman.up.univ-mrs.fr
>             ^^^^^^
>   This should be the hostname of this computer
> 
>> # The following lines are desirable for IPv6 capable hosts
>> ::1 ip6-localhost ip6-loopback
>> fe00::0 ip6-localnet
>> ff00::0 ip6-mcastprefix
>> ff02::1 ip6-allnodes
>> ff02::2 ip6-allrouters
>> ff02::3 ip6-allhosts
>>
>> Actually, last time I boot, I manually added zeeman as an alias to 
>> 127.0.0.1 and 127.0.1.1, but something (network manager ?) overwrote my 
>> /etc/hosts at start ! It seems xubuntu complains when the "zeeman" alias 
>> is not set.
>>
>> By the way, I looked at the /var/log/messages file and found the following:
>> Jan 26 10:40:59 zeeman kernel: [   27.656000] ADDRCONF(NETDEV_UP): eth1: 
>> link is not ready
>> Jan 26 10:41:09 zeeman kernel: [   37.736000] audit(1201340469.294:3): 
>> type=1503 operation="inode_permission" requested_mask="a" 
>> denied_mask="a" name="/dev/tty" pid=5232 profile="/usr/sbin/cupsd"
>> Jan 26 10:41:19 zeeman kernel: [   47.860000] apm: BIOS not found.
>> Jan 26 10:41:20 zeeman kernel: [   48.936000] Failure registering 
>> capabilities with primary security module.
>> Jan 26 10:41:20 zeeman dhcdbd: Started up.
>> Jan 26 10:42:01 zeeman dhcdbd: message_handler: message handler not 
>> found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
>> Jan 26 10:42:13 zeeman kernel: [  102.032000] NET: Registered protocol 
>> family 17
>> Jan 26 10:42:17 zeeman kernel: [  105.424000] ADDRCONF(NETDEV_CHANGE): 
>> eth1: link becomes ready
>> Jan 26 10:42:19 zeeman dhcdbd: message_handler: message handler not 
>> found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.host_name
>> Jan 26 10:42:19 zeeman dhcdbd: message_handler: message handler not 
>> found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.domain_name
>> Jan 26 10:42:19 zeeman dhcdbd: message_handler: message handler not 
>> found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_domain
>> Jan 26 10:42:19 zeeman dhcdbd: message_handler: message handler not 
>> found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_servers
>>
>> Has someone some ideas about what it means ?
>>
>> -- 
>> Nicolas Ferré
>> Laboratoire Chimie Provence
>> Université de Provence - France
>> Tel: +33 391282733
>>
> The messages are referring to _eth1_, which should be your _wired
> connection_. If you are connecting in wireless mode with the wired
> connection disconnected, those are to be expected. I think (someone
> correct me if I am wrong) we can disregard those messages unless the
> wired connection is active.
> 
> Are all your home systems using the same setup (dhcp) to connect to each
> other? 
> 
> This is the full /etc/hosts file from my own setup:
> 
> 127.0.0.1 localhost
> 127.0.1.1 number3
> 192.168.51.1	whynot.keepingdreams.org	whynot
> 192.168.51.2	justhaveto	justhaveto
> 192.168.51.3	ucandoit	ucandoit
> 192.168.51.4	wecan	wecan
> 192.168.51.5	number3	number3
> 
> 
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
> 
> As you can see, I have used static addresses for my home systems. I use
> a second network card in the server to connect to my router using dhcp,
> so it does not need to have the address and hostname in /etc/hosts.
> 
> good luck,
> 


-- 
Nicolas Ferré
Laboratoire Chimie Provence
Université de Provence - France
Tel: +33 391282733