View previous topic :: View next topic |
Author |
Message |
lo-jay l33t
Joined: 27 Feb 2005 Posts: 862
|
Posted: Tue May 10, 2005 8:37 pm Post subject: dhcp prob - not net after installation |
|
|
hi,
got my system running, but no net:cry: . hardware: adsl - router (dhcp) - switch - amd64 box.
i compiled the genkernel with genkernel --udev all
and i did emerge dhcpcd!
my /etc/con.d/net ( sorry, can't copy & past, so there might be some typos. ..)
Code: | iface_eth=="dhcp"
dhcpcd_eth0=" -H -D -N -t 30" |
ifconfig gives:
Code: | eth0 Link encap: Eternet HWaddr 00:11:09:8C:FE:EO
inet6 addr: fe80::211:9ff:fe8c:fe/64 Scope:Link
US BROADCAST NOTRAILERS MULTICAST MTU: 1500 Metric 1
RX packets:0 errors: 0 dropped:0 overruns :0 frame: 0
TX packets:8 errors: 0 dropped:0 overruns :0 carrier: 0
collisions:0 txqueuelen:100
RX bytes:0 (0:0b) TX bytes: 2148 (2.0 Kb)
Interrupt:22 Base address: 0x200
Io Link encap: Local Loopback
inet addr: 127.0.0.1 Mask 255:00.0
inet addr:: 1/128 Scope: Host
UP LOOPBACK RUNNING MTU: 16436 Metric
.
.
.
|
rc-update -s looks s.th. like this:
Code: |
coldplay | default
consolefont | boot
crypto-loop |
domainname| default
gpm |
hdparm |
hostname | boot
hotplug |
locale | default nonetwork
localmount | boot
modules | boot
net.eth0 | default
net.Io | boot
netmount | default
nscd |
numlock |
runlogin | boot
rsyncd |
serial | boot
sshd |
syslog-ng | boot
urandom | boot
vixicron | default
|
what do i miss?
thanks again:wink: !!!
hunter lives in a fortified compound in aspen _________________ lo-jay
The mechanic "One of 'em Dodge Chargers - let him go by."
The driver "Not today!"
taken from "Two Lane Blacktop" |
|
Back to top |
|
|
jdgill0 Veteran
Joined: 25 Mar 2003 Posts: 1366 Location: Lexington, Ky -- USA
|
Posted: Wed May 11, 2005 1:16 am Post subject: |
|
|
Is that a typo? It should be
_________________ Vim has excellent syntax highlighting for configuration files: emerge gentoo-syntax
Learn how to use Vim: vimtutor |
|
Back to top |
|
|
lo-jay l33t
Joined: 27 Feb 2005 Posts: 862
|
Posted: Wed May 11, 2005 5:31 am Post subject: |
|
|
yeah, it's a typo - got
_________________ lo-jay
The mechanic "One of 'em Dodge Chargers - let him go by."
The driver "Not today!"
taken from "Two Lane Blacktop" |
|
Back to top |
|
|
lo-jay l33t
Joined: 27 Feb 2005 Posts: 862
|
Posted: Wed May 11, 2005 11:27 am Post subject: |
|
|
/var/log/messages shows - among other stuff - the following:
Code: |
tux eth0: no link during initialization
tux r8169: Gigabyte Ethernet driver 2.2.2K loaded
tux eth1: Identified chip type is "RTL8169/8110s"
tux eth0=: no IPv6 router present
tux dhcpcd (7519) timed out waiting for valid DHCP server response
.
.
. |
does this tell us anything:?:
thanks one more time! _________________ lo-jay
The mechanic "One of 'em Dodge Chargers - let him go by."
The driver "Not today!"
taken from "Two Lane Blacktop" |
|
Back to top |
|
|
adaptr Watchman
Joined: 06 Oct 2002 Posts: 6730 Location: Rotterdam, Netherlands
|
Posted: Wed May 11, 2005 11:56 am Post subject: |
|
|
I can tell you one thing: you don't even have ipv4 on that interface.
If it was your intention to only use ipv6 on that interface then the preceding error says it all: your dhcp server does not properly distribute ipv6 information - or you router isn't ipv6 capable. _________________ >>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
Back to top |
|
|
lo-jay l33t
Joined: 27 Feb 2005 Posts: 862
|
Posted: Wed May 11, 2005 12:18 pm Post subject: |
|
|
somehow it worked great during install with the live-cd.
so what exactly should i do now?
thanks!!! _________________ lo-jay
The mechanic "One of 'em Dodge Chargers - let him go by."
The driver "Not today!"
taken from "Two Lane Blacktop" |
|
Back to top |
|
|
adaptr Watchman
Joined: 06 Oct 2002 Posts: 6730 Location: Rotterdam, Netherlands
|
Posted: Wed May 11, 2005 12:28 pm Post subject: |
|
|
It would help if you started by telling us what it is that you want to achieve, and then indicate what you got that did not correspond with your expectations... _________________ >>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
Back to top |
|
|
lo-jay l33t
Joined: 27 Feb 2005 Posts: 862
|
Posted: Wed May 11, 2005 12:54 pm Post subject: |
|
|
well, i do want to set up the network, so i can continue with the installation:wink: !
cheers _________________ lo-jay
The mechanic "One of 'em Dodge Chargers - let him go by."
The driver "Not today!"
taken from "Two Lane Blacktop" |
|
Back to top |
|
|
adaptr Watchman
Joined: 06 Oct 2002 Posts: 6730 Location: Rotterdam, Netherlands
|
Posted: Wed May 11, 2005 1:21 pm Post subject: |
|
|
Smartarse
Do you intend to use ipv6 or was that unintentional ?
If you don't need it, disable the ipv6 USE flag, and don't enable it in the kernel either.
It also says: no link during init.
That means you have no connection - check your cables. _________________ >>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
Back to top |
|
|
lo-jay l33t
Joined: 27 Feb 2005 Posts: 862
|
Posted: Wed May 11, 2005 1:53 pm Post subject: |
|
|
ok, pls don't underestimate my ignorance...
i can follow you so far:
my USE flags are
Code: | USE="-gtk -gnome qt kde dvd alsa cdr" |
so should i put s.th like "-IP6" there?
2nd: i used genkernel, do i have to compile again?
3rd: don't think the cables fail, ' cause it works fine with the live-cd.
cheers again! _________________ lo-jay
The mechanic "One of 'em Dodge Chargers - let him go by."
The driver "Not today!"
taken from "Two Lane Blacktop" |
|
Back to top |
|
|
Henks n00b
Joined: 10 Jan 2005 Posts: 21
|
Posted: Wed May 11, 2005 2:15 pm Post subject: |
|
|
From how I understand this:
Quote: |
tux eth0: no link during initialization
|
There is no cable plugged into eth0, thus dhcp fails
Quote: |
tux eth1: Identified chip type is "RTL8169/8110s"
|
The interface you are using is eth1
I would try the following:
cd /etc/init.d
ln -s net.eth0 net.eth1
rc-update add net.eth1 default
in /etc/conf.d/net add:
iface_eth1="dhcp"
# Some network admins require that you use the
# hostname and domainname provided by the DHCP server.
# In that case, add the following to let dhcpcd use them.
# That will override your own hostname and domainname definitions.
# dhcpcd_eth1="-HD"
# If you intend on using NTP to keep your machine clock synchronized, use
# the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file
# dhcpcd_eth1="-N"
Append:
if you are indeed using eth1 instead of eth0, you can disable eth0 completely, thus avoiding a possible timeout / error messages upon boot:
rc-update del net.eth0 |
|
Back to top |
|
|
lo-jay l33t
Joined: 27 Feb 2005 Posts: 862
|
Posted: Wed May 11, 2005 3:03 pm Post subject: |
|
|
hey henks - it works!
i'm SO THANKFULL!!! _________________ lo-jay
The mechanic "One of 'em Dodge Chargers - let him go by."
The driver "Not today!"
taken from "Two Lane Blacktop" |
|
Back to top |
|
|
|