View previous topic :: View next topic |
Author |
Message |
BrentNorin n00b
Joined: 31 Jan 2007 Posts: 60 Location: Akron, Ohio
|
Posted: Sat Feb 03, 2007 7:40 pm Post subject: My Internet Died |
|
|
Well, it was working. Then I removed devfsd and added udev. The network continued to work fine. After a reboot, it doesn't work.
Before, when starting up it would show starting eth0 then move on to eth1 and get an address and everything would be ok. Now, it only shows that it starts up lo. When I do an ifconfig I have an ipaddress on eth1. I'm using DHCP to retreive all the information, and I think my DNS is not getting retrieved. So heres a couple things.
When I rc-update -s default, net.eth1 is in the list.
my /etc/resolv.conf is as follows:
my /etc/conf.d/net is as follows:
Code: | dns_domain_lo="brentrealm"
config_eth1=( "dhcp" )
dhcp_eht1="" |
I don't know much, but thanks in advance! |
|
Back to top |
|
|
thecooptoo Veteran
Joined: 27 Apr 2003 Posts: 1353 Location: UK
|
Posted: Sat Feb 03, 2007 8:04 pm Post subject: |
|
|
ifconfig -a
will show ALL network cards ,whether up or not .
can you manually start the ones that arent up ?
I assume one eth0 is wired and eth1 wireless ? _________________ join the optout - http://nhsconfidentiality.org |
|
Back to top |
|
|
Dan Veteran
Joined: 25 Oct 2005 Posts: 1302
|
Posted: Sat Feb 03, 2007 8:07 pm Post subject: |
|
|
you could always add to resolv.conf
Quote: | nameserver x.x.x.x |
using the ip of your gateway as the dns server or if you know the ip's of your isp's dns servers you could add them also.
Quote: | nameserver x.x.x.x
nameserver x.x.x.x
nameserver x.x.x.x
|
_________________ - Failure is not an option. It's bundled with your software. |
|
Back to top |
|
|
BrentNorin n00b
Joined: 31 Jan 2007 Posts: 60 Location: Akron, Ohio
|
Posted: Sat Feb 03, 2007 8:52 pm Post subject: |
|
|
thecooptoo wrote: | ifconfig -a
will show ALL network cards ,whether up or not .
can you manually start the ones that arent up ?
I assume one eth0 is wired and eth1 wireless ? |
ok I did that. eth0 is wireless (which I dont use) and eth1 is wired. manually start? u mean #dhcpcd eth1? |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54831 Location: 56N 3W
|
Posted: Sat Feb 03, 2007 8:59 pm Post subject: |
|
|
BrentNorin,
You hardware devices may not always be assigned the same logical interface names any more.
They can swap every boot if you are really unlucky.
Providing you can show that everything else is ok, you need some udev rules to fix the device names to the MAC Addresses. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
BrentNorin n00b
Joined: 31 Jan 2007 Posts: 60 Location: Akron, Ohio
|
Posted: Sat Feb 03, 2007 9:05 pm Post subject: |
|
|
ok, I've rebooted twice and the mac addresses have not changed. from my xp environment I can confirm that the mac address being reported from eth0 and eth1 are from my wireless and wired, respectively. dcoats, I have tried forcing a DNS and with no results.
neddyseagoon, can you please go into detail on ur last statement. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54831 Location: 56N 3W
|
Posted: Sat Feb 03, 2007 9:20 pm Post subject: |
|
|
BrentNorin,
You will only get a dhcp response to the interface that is connected to the dhcp server.
The MAC addesses are fied to the hardware of the interface but the names eth0 and eth1 are not, they are allocated in the order in which the interfaces are 'discovered' or started, which is not deterministic.
On some boots, eth1 will be wired, on others, wireless. will let you sort out whats what, provided you know the MAC addresses (HWAddr in ifconfig)
Providing you can get the wired interface up and working manually, you can write udev rules to fix names to the MAC Addresses. My /etc/udev/rules.d/03-local-net.rules file contains Code: | # Name the eth interfaces correctly
KERNEL=="eth*", SYSFS{address}=="00:26:54:0b:c6:c6", NAME="eth_lan"
KERNEL=="eth*", SYSFS{address}=="00:0c:6e:14:c8:e7", NAME="eth_spare" | which works only for my MAC addresses. You cannot use the kernel names eth0 and eth1, since when the rule runs, the name may be in use.
Make up some new names and propogate them in /etc/init.d/ /etc/conf.d/net and rc-update.
Gotcha for the unwary - hex digits must be lowercase in the rules. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
BrentNorin n00b
Joined: 31 Jan 2007 Posts: 60 Location: Akron, Ohio
|
Posted: Sat Feb 03, 2007 11:42 pm Post subject: |
|
|
Neddy, I did as you said.
My interfaces are now named. Problem is not solved. Yes, I propagated them in /etc/init.d with ln -s net.lo net.eth_wired and added them to rc-update while removing the old. Still the same problem. One thing I have noticed is that if I set a nameserver in /etc/resolv.conf, upon the next reboot the changes are not there! |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54831 Location: 56N 3W
|
Posted: Sat Feb 03, 2007 11:46 pm Post subject: |
|
|
BrentNorin,
dhcp provides a nameserver, or at least, its supposed to, so it would delete any entry you made manually.
However, look in /etc/conf.d/net.example to see how to pass options to dhcpcd to stop it doing that.
You will then need a working nameserver in /etc/resolv.conf _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
BrentNorin n00b
Joined: 31 Jan 2007 Posts: 60 Location: Akron, Ohio
|
Posted: Sat Feb 03, 2007 11:49 pm Post subject: |
|
|
I know. Even with nodns in the conf.d/net the resolv.conf still gets wiped. |
|
Back to top |
|
|
BrentNorin n00b
Joined: 31 Jan 2007 Posts: 60 Location: Akron, Ohio
|
Posted: Sun Feb 04, 2007 12:29 am Post subject: |
|
|
Ok, so heres an update. When I boot, my internet doesn't work. If I do Code: | /etc/init.d/net.eth_wired start | it tells me that it is already started. My internet still won't work. If I do Code: | /etc/init.d/net.eth_wired restart | it restarts and then my internet works. I'm finding that I have to do this each time I reboot my machine. How can I get it to start the first time and work? |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54831 Location: 56N 3W
|
Posted: Sun Feb 04, 2007 1:11 pm Post subject: |
|
|
BrentNorin,
Starting a service thats already running does nothing. Restarting it stops it then goes throght the startup again.
What runlevel is eth_wired in ?
It should be default, not boot. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
BrentNorin n00b
Joined: 31 Jan 2007 Posts: 60 Location: Akron, Ohio
|
Posted: Sun Feb 04, 2007 7:32 pm Post subject: |
|
|
It is in default. It loads up with my system, as it always did. However it is non-functional until I restart it. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54831 Location: 56N 3W
|
Posted: Sun Feb 04, 2007 9:12 pm Post subject: |
|
|
BrentNorin,
Do you have the -t option in /etc/conf.d/net for dhcp ?
Setting that aggressively (low numbers) can cause the timeout before the dhcp server has responded. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
BrentNorin n00b
Joined: 31 Jan 2007 Posts: 60 Location: Akron, Ohio
|
Posted: Sun Feb 04, 2007 11:21 pm Post subject: |
|
|
-t is not set. |
|
Back to top |
|
|
|