Network Management - probably pebcak needs sorting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 08 March 2010 17:53:44 Anne Wilson wrote:
> On Monday 08 March 2010 16:36:25 Martin Kho wrote:
> > On Monday 08 March 2010 17:17:51 Anne Wilson wrote:
> > > On Monday 08 March 2010 16:09:44 Patrick Boutilier wrote:
> > > > On 03/08/2010 12:06 PM, Anne Wilson wrote:
> > > > > On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
> > > > >> On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
> > > > >>> Do try the NetoworkManager-gnome (nm-applet). I had a different
> > > > >>> problem, not solvable with knetworkmanager, but with nm-applet.
> > > > >> 
> > > > >> I could try it again, but of course the reason I was trying
> > > > >> knetwork manager was because NetworkManager-gnome wasn't working.
> > > > >>  Still, it's worth a try, since I tried to change over before the
> > > > >> 4.4.1 update. I'll report back.
> > > > > 
> > > > > Is there no way of restarting things like this, without rebooting?
> > > > > It's beginning to feel like windows!  AIUI the command 'service
> > > > > network restart' can't be used if NetworkManager-gnome is to
> > > > > control it.  Is that right?
> > > > 
> > > > service NetworkManager restart
> > > 
> > > service NetworkManager restart
> > > Stopping NetworkManager daemon:                            [  OK  ]
> > > Setting network parameters...                              [  OK  ]
> > > Starting NetworkManager daemon:                            [  OK  ]
> > > [root at anne-laptop ~]# ifup eth0
> > > 
> > > Determining IP information for eth0...dhclient(6296) is already running
> > > - exiting.
> > > 
> > > This version of ISC DHCP is based on the release available
> > > on ftp.isc.org.  Features have been added and other changes
> > > have been made to the base software release in order to make
> > > it work better with this distribution.
> > > 
> > > Please report for this software via the Red Hat Bugzilla site:
> > >     http://bugzilla.redhat.com
> > > 
> > > exiting.
> > > 
> > >  failed.
> > > 
> > > I think I'm beaten.
> > > 
> > > Just one thought - I have no idea why, but on this laptop eth0 is
> > > defined as the wireless interface and eth1 is the cabled one.  I
> > > didn't do this - the setup did - but I'm beginning to wonder whether
> > > it's relevant.
> > 
> > What have in /etc/sysconfig/network-scripts/ifcfg-eth[0,1]? Do they
> > exist?
> 
> Experimenting in system-config-network I changed eth0 to wlan0, but ifup
> wlan0 gives the same errors.

Running system-config-network sets up network not NetworkManager. In my config 
for eth0 I only have:

"# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet 
controller
DEVICE=eth0
HWADDR=00:18:F3:8A:F3:D6"

The rest is set up by NetworkManager. In
/var/lib/dhclient/dhclient-<big number>-eth[0,1].lease you'll find the find the 
set up info.

> 
> ifcfg-wlan0
> # Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection
> DEVICE=eth0
> BOOTPROTO=dhcp
> HWADDR=xx:xx:xx:xx:xx:xx
> ONBOOT=yes
> DNS2=212.23.3.100
> TYPE=Wireless
> DNS1=192.168.0.1
> NM_CONTROLLED=yes
> USERCTL=yes
> PEERDNS=yes
> IPV6INIT=yes
> MODE=Managed
> RATE=auto
> ESSID=
> CHANNEL=
> 
> (the firmware is installed)
> 
> ifcfg-eth1
> # Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet
> DEVICE=eth1
> BOOTPROTO=dhcp
> HWADDR=xx:xx:xx:xx:xx:xx
> ONBOOT=yes
> TYPE=Ethernet
> IPV6INIT=no
> USERCTL=no
> 
> Anne


[Index of Archives]     [KDE Users]     [Fedora General Discussion]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Coolkey]     [Yum Users]     [Yosemite Forum]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux