Re: from 13 to 14

ifconfig -a will see the eth0

so i ifup eth0
then ifconfig show :


eth0 Link encap:Ethernet HWaddr 00:EA:01:21:8E:87
inet6 addr: fe80::2ea:1ff:fe21:8e87/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1148 (1.1 KiB) TX bytes:468 (468.0 b)
Interrupt:41

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1440 (1.4 KiB) TX bytes:1440 (1.4 KiB



it did't show my ip4 address . So still can't connect



I may show something in /var/log/message:





Dec 12 20:36:30 localhost avahi-daemon[1146]: Successfully called chroot().
Dec 12 20:36:30 localhost avahi-daemon[1146]: Successfully dropped
remaining capabilities.
Dec 12 20:36:30 localhost avahi-daemon[1146]: Loading service file
/services/ssh.service.
Dec 12 20:36:30 localhost avahi-daemon[1146]: Loading service file
/services/udisks.service.
Dec 12 20:36:30 localhost avahi-daemon[1146]: System host name is set
to 'localhost'. This is not a suitable mDNS host name, looking for
alternatives.
Dec 12 20:36:30 localhost avahi-daemon[1146]: Network interface
enumeration completed.
Dec 12 20:36:30 localhost avahi-daemon[1146]: Registering HINFO record
with values 'I686'/'LINUX'.
Dec 12 20:36:30 localhost avahi-daemon[1146]: Server startup complete.
Host name is linux.local. Local service cookie is 3931582572.
Dec 12 20:36:30 localhost avahi-daemon[1146]: Service "linux"
(/services/udisks.service) successfully established.
Dec 12 20:36:30 localhost avahi-daemon[1146]: Service "linux"
(/services/ssh.service) successfully established.
Dec 12 20:36:30 localhost NetworkManager[1137]: <info> VPN: loaded
org.freedesktop.NetworkManager.pptp
Dec 12 20:36:30 localhost NetworkManager[1137]: <info> VPN: loaded
org.freedesktop.NetworkManager.openvpn
Dec 12 20:36:30 localhost NetworkManager[1137]: <info> VPN: loaded
org.freedesktop.NetworkManager.vpnc
Dec 12 20:36:30 localhost NetworkManager[1137]: <info> VPN: loaded
org.freedesktop.NetworkManager.openconnect
Dec 12 20:36:30 localhost NetworkManager[1137]: <info> trying to start
the modem manager...
Dec 12 20:36:30 localhost NetworkManager[1137]: <info> monitoring
kernel firmware directory '/lib/firmware'.
Dec 12 20:36:30 localhost modem-manager: ModemManager (version
0.4-4.git20100720.fc13) starting...
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Option High-Speed
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Ericsson MBM
Dec 12 20:36:30 localhost modem-manager: Loaded plugin ZTE
Dec 12 20:36:30 localhost modem-manager: Loaded plugin SimTech
Dec 12 20:36:30 localhost NetworkManager[1137]: ifcfg-rh: Acquired
D-Bus service com.redhat.ifcfgrh1
Dec 12 20:36:30 localhost NetworkManager[1137]: <info> Loaded plugin
ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the
NetworkManager mailing list.
Dec 12 20:36:30 localhost NetworkManager[1137]: ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-eth0 ...
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Gobi
Dec 12 20:36:30 localhost modem-manager: Loaded plugin AnyData
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Generic
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Option
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Longcheer
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Novatel
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Nokia
Dec 12 20:36:30 localhost modem-manager: Loaded plugin MotoC
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Huawei
Dec 12 20:36:30 localhost modem-manager: Loaded plugin Sierra
Dec 12 20:36:31 localhost NetworkManager[1137]: ifcfg-rh: read
connection 'System eth0'
Dec 12 20:36:31 localhost NetworkManager[1137]: ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-lo ...
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> Activation
(eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> Activation
(eth0) Stage 4 of 5 (IP4 Configure Get) started...
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> address 192.168.1.102
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> prefix 24
(255.255.255.0)
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> gateway 192.168.1.1
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> nameserver
'202.103.44.150'
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> nameserver
'202.103.24.68'
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> domain name 'domain'
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> Activation
(eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> Activation
(eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Dec 12 20:36:32 localhost NetworkManager[1137]: <info> Activation
(eth0) Stage 5 of 5 (IP Configure Commit) started...
Dec 12 20:36:32 localhost avahi-daemon[1146]: Joining mDNS multicast
group on interface eth0.IPv4 with address 192.168.1.102.
Dec 12 20:36:32 localhost avahi-daemon[1146]: New relevant interface
eth0.IPv4 for mDNS.
Dec 12 20:36:32 localhost avahi-daemon[1146]: Registering new address
record for 192.168.1.102 on eth0.IPv4.
Dec 12 20:36:32 localhost avahi-daemon[1146]: Registering new address
record for fe80::2ea:1ff:fe21:8e87 on eth0.*.
Dec 12 20:36:33 localhost NetworkManager[1137]: <info> (eth0): device
state change: 7 -> 8 (reason 0)
Dec 12 20:36:33 localhost NetworkManager[1137]: <info> Policy set
'System eth0' (eth0) as default for IPv4 routing and DNS.
Dec 12 20:36:33 localhost NetworkManager[1137]: <info> Updating
/etc/hosts with new system hostname
Dec 12 20:36:33 localhost NetworkManager[1137]: <info> Activation
(eth0) successful, device activated.
Dec 12 20:36:33 localhost NetworkManager[1137]: <info> Activation
(eth0) Stage 5 of 5 (IP Configure Commit) complete.
Dec 12 20:36:33 localhost nm-dispatcher.action: nm_dispatcher_action:
Invalid connection: '(null)' / 'connection setting not found' invalid:
1


Beacuse i never meet the problem before . So i have no idea about the message


thankyou


2010/12/12 stan <gryt2@xxxxx>:
On Sun, 12 Dec 2010 22:49:14 +0800
xinyou yan <yxy.716@xxxxxxxxx> wrote:

I just choose  13 upgrade to 14  when i use the dvd

However , when i login I can't connect to the Internet

the    ifconfig          just show the  message of     " l0 "

Does  fedora 14 can't  know my decives  of  NIC ?

I use the network service instead of the default Network Manager, so I
might not be the best person to answer this.  In network, you could try
from the command line as root the command   ifup eth0   .  For
network manager, bring up the network application that your gui
uses.  Tell it to restart the network.

If you are using wireless, it is possible that you need some firmware
that has been updated for f14.

In general, F14 should take care of this automatically.  If you look
in /var/log/messages after the boot, do you see any error messages
generated  while booting up?

--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Relevant Pages

  • Networking - multiple nics not setting up
    ... There seems to be some sort of auto ... want the eth3:avah interface or the 169.x.x.x network. ... iface eth0 inet static ... UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ...
    (Ubuntu)
  • Networking - multiple nics not setting up
    ... There seems to be some sort of auto ... want the eth3:avah interface or the 169.x.x.x network. ... iface eth0 inet static ... UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ...
    (Ubuntu)
  • Re: set maximum ip-packet-size ?
    ... If it is an ethernet interface (like eth0, connected to a router or gateway), ... the default MTU will most likely have the default ... You can use the ifconfig command to alter this setting ... (for any network interface). ...
    (comp.os.linux.networking)
  • Re: Multiple IP addresses on eth0 - which is "canonical"?
    ... mail mail came from the IP address associated with eth0:1 not eth0. ... # This file describes the network interfaces available on your system ... iface eth0 inet static ... UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ...
    (Debian-User)
  • Re: ifconfig command shows only loopback device.
    ... after running modprobe e1000 ifconfig returns eth0. ... ifconfig -a does not show eth0. ... configure for e1000 network module to be loaded at every boot?. ...
    (RedHat)