i used networkmanager and gnome-nettool in kde4 to connect the internet.
At first, the network wors fine , but when kde is blocked ,i used reboot , and when i want to connect the internet, there's a problem

Whatever, you still have a current lease on 211.87.223.108.
Thats odd for several reasons. First, it means it has worked in the past.
It looks like you have a vaid lease, the dhcp server is refusing to renew it then it breaks instead of offering you a new IP address.

211.87.223.108 is a public IP. Its not wrong for you to connect you system directly to the big bad internet but its very rare.

Your /etc/conf.d/net file contains the old depreciated syntax but as the warning says

Code:

This feature will be removed in the future.

Code:

config_eth0=( "dhcp" )

should be

Code:

config_eth0="dhcp"

Why do you need to set the mac address on eth0?

Something to try ... read man dhcpcd and work out how to dell dhcpcd to drop your lease.
Of course, the lease may have expired by the time you read this, so it may all justwork._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

"rebinding" means your system has found a dhcp lease that is still current accoring to your system clock and has asked the dhcp server to reuse the lease.
Both your system and the server are supposed to do that. The dhcp server should just say 'yes'.

A few thinks can go wrong here. If the server needed to reallocate the IP you hold a lease on, it should say you can't have that IP address, ask for a new one.
That should work too.

If you have a problem with your clock, your system may think you have a valid lease but if your clock is slow, the dhcp server may not agree.
Does the date command return the correct time and date?
As you won't have ntp running yet (your network is not up) your clock needs to be close enough to the ouside world for lease expiry to work.
Run dhcpcd by hand and tell it to drop any leases it may hold._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

"rebinding" means your system has found a dhcp lease that is still current accoring to your system clock and has asked the dhcp server to reuse the lease.
Both your system and the server are supposed to do that. The dhcp server should just say 'yes'.

A few thinks can go wrong here. If the server needed to reallocate the IP you hold a lease on, it should say you can't have that IP address, ask for a new one.
That should work too.

If you have a problem with your clock, your system may think you have a valid lease but if your clock is slow, the dhcp server may not agree.
Does the date command return the correct time and date?
As you won't have ntp running yet (your network is not up) your clock needs to be close enough to the ouside world for lease expiry to work.
Run dhcpcd by hand and tell it to drop any leases it may hold.

Thanks a lot.

But I cann't understand your words about the date becaue of my poor Eniglish . And indeed, my date time is not correct. I'm trying to make it correct.

Windows and *NIX disagree on how real time clocks should be set. Windows is wrong but you can set *NIX to be equally wrong so the two live together - almost.
You do loose a little bit of *NIX functionality that Windows doesn't have but thats the price for booting both systems on the same hardware.

For easy living with windows, set the BIOS time to your local time from your wristwatch. Windows demands this.
Boot Windows and fix the time in Windows if its wrong.

Boot Gentoo (arch will do something similar)
In /etc/timezone put localtime
cp /usr/share/zoneinfo/localtime to /etc/localtime
edit /etc/conf.d/hwclock
Follow the comments at the top of the file - your hardware clock is not set to UTC.
and fix

Code:

# If you do not want to set the hardware clock to the current system
# time (software clock) during shutdown, set this to NO
#clock_systohc="YES"

Only Windows must reset the BIOS clock. (uncomment it too).
further down the same file.
This should make your time correct in both Gentoo and Windows.
Reboot Gentoo to make sure it stays right.

Fixing arch is left as an exercise to the reader.

I mentioned a slight loss of functionality ... you need to boot Windows to update your BIOS time when daylight saving time begins/ends.

Having monotonic time in *NIX is essentail for normal operation. A lot of things depend on time always increasing.
Having (reasonably) correct time is essential for initial interaction with the outside world._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.