| View previous topic :: View next topic |
| Author |
Message |
danne123
n00b
Joined: 31 Mar 2007
Posts: 8
|
 Posted: Wed Apr 04, 2007 5:01 pm Post subject: Ohhh no!!! |
 |
|
I lost my internet connection when I emerge updates to the etc directory.
Before the update everything was working fine.
I tried to modprobe my network card. Nothing special happend no errors, no internet.
The command ifconfig only show l0 and NOT eth0.
Can anyone help me get back my internet connection?
(I am sitting on a windows computer right now. So I can´t copy the information that is written in the terminal.) |
|
| Back to top |
|
 |
thorpe
l33t
Joined: 09 May 2005
Posts: 618
Location: Sydney, Australia.
|
| Posted: Wed Apr 04, 2007 5:11 pm Post subject: |
|
|
Check you didn't overight /etc/conf.d/net with a new file. If so, you will need to reconfigure it.
_________________
Research before taking any advice from me. I'm still coming to grips with this myself. |
|
| Back to top |
|
|
danne123
n00b
Joined: 31 Mar 2007
Posts: 8
|
| Posted: Wed Apr 04, 2007 5:24 pm Post subject: |
|
|
| thorpe wrote: | | Check you didn't overight /etc/conf.d/net with a new file. If so, you will need to reconfigure it. |
There where only two lines of code there...
Eth0_dhcpcd something
Ohhh no...
I have a laptop computer that is connected to the same network as my desktop computer is connect to. Can that come in handy? |
|
| Back to top |
|
|
mark_alec
Bodhisattva
Joined: 11 Sep 2004
Posts: 6066
Location: Melbourne, Australia
|
| Posted: Thu Apr 05, 2007 7:57 am Post subject: |
|
|
Moved from Portage & Programming to Networking & Security.
_________________
www.gentoo.org.au || #gentoo-au |
|
| Back to top |
|
|
danne123
n00b
Joined: 31 Mar 2007
Posts: 8
|
| Posted: Fri Apr 06, 2007 5:06 pm Post subject: |
|
|
The problem that the internet doesn´t work after modprobe is maby because I have tried to install IP-tables.
I was useing this guide, http://gentoo-wiki.com/HOWTO_Iptables_for_newbies. But I never did forfill it. Do you think it helps if I unemerge iptables? Or shall I forfill the guide? |
|
| Back to top |
|
|
dark-lord
n00b
Joined: 06 Apr 2007
Posts: 10
Location: Israel
|
| Posted: Fri Apr 06, 2007 5:53 pm Post subject: |
|
|
Hi!
Try this out:
| Code: |
/etc/init.d/net.eth0 start
|
Then:
&&It should include eth0  |
|
| Back to top |
|
|
danne123
n00b
Joined: 31 Mar 2007
Posts: 8
|
| Posted: Fri Apr 06, 2007 7:49 pm Post subject: |
|
|
| dark-lord wrote: | Hi!
Try this out:
| Code: |
/etc/init.d/net.eth0 start
|
Then:
&&It should include eth0 |
No it didn´t work... 
| Code: | | Error dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring |
|
|
| Back to top |
|
|
Bobnoxous
Apprentice
Joined: 03 May 2005
Posts: 240
|
| Posted: Fri Apr 06, 2007 8:31 pm Post subject: |
|
|
Even if iptables is installed, you should still get a network connection. What does:
> /sbin/ifconfig -a
tell you?
_________________
"The problem with the world is that fools and fanatics are always so sure of themselves while wiser people are so full of doubt."
- Bertrand Russell |
|
| Back to top |
|
|
danne123
n00b
Joined: 31 Mar 2007
Posts: 8
|
| Posted: Fri Apr 06, 2007 10:17 pm Post subject: |
|
|
| Bobnoxous wrote: | Even if iptables is installed, you should still get a network connection. What does:
> /sbin/ifconfig -a
tell you? |
| Code: | /sbin/ifconfig -a
eth0 Link encap:UNSPEC HWaddr 00-30-05-31-00-03-11-39-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth1 Link encap:UNSPEC HWaddr 00-02-3C-00-91-06-16-6D-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth2 Link encap:Ethernet HWaddr 00:30:05:44:39:5D
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
|
|
| Back to top |
|
|
Bobnoxous
Apprentice
Joined: 03 May 2005
Posts: 240
|
| Posted: Fri Apr 06, 2007 10:49 pm Post subject: |
|
|
I don't think it's iptables. You're not getting an IP address. What's in /etc/conf.d/net? If you rename it so it's not used, dhcp should be the default?
Also, try:
> more /var/log/messages | grep dhcpcd
to see if dhcp is throwing any warnings.
_________________
"The problem with the world is that fools and fanatics are always so sure of themselves while wiser people are so full of doubt."
- Bertrand Russell |
|
| Back to top |
|
|
fvila
n00b
Joined: 09 Sep 2004
Posts: 19
|
| Posted: Sat Apr 07, 2007 6:10 pm Post subject: |
|
|
How many interfaces do you have? From the ifconfig -a output it seems that the only Ethernet interface is eth2. Have you tried dhcpcd eth2?
Maybe something has messed up /etc/modules.d/aliases
Francesc |
|
| Back to top |
|
|
danne123
n00b
Joined: 31 Mar 2007
Posts: 8
|
| Posted: Sat Apr 07, 2007 7:57 pm Post subject: |
|
|
| Code: | /etc/conf.d/net
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
iface_eth0="dhcp"
dhcpcd_eth0=""
net lines 1-6/6 (END)
more /var/log/messages | grep dhcpcd
Mar 25 00:03:15 fenix dhcpcd[8241]: terminating on signal 15
Mar 25 00:24:14 fenix dhcpcd[8171]: terminating on signal 15
Mar 25 00:31:39 fenix dhcpcd[8150]: terminating on signal 15
Mar 25 00:59:55 fenix dhcpcd[8142]: terminating on signal 15
Mar 25 01:57:30 fenix dhcpcd[8176]: terminating on signal 15
Mar 25 12:44:43 fenix dhcpcd[9844]: terminating on signal 15
Mar 26 00:35:05 fenix dhcpcd[8246]: terminating on signal 15
Mar 26 11:52:54 fenix dhcpcd[9905]: terminating on signal 15
Mar 27 00:08:15 fenix dhcpcd[9843]: terminating on signal 15
Mar 27 14:02:38 fenix dhcpcd[8215]: terminating on signal 15
Mar 28 17:48:35 fenix dhcpcd[9843]: terminating on signal 15
Mar 28 22:18:43 fenix dhcpcd[8184]: terminating on signal 15
Mar 28 23:22:27 fenix dhcpcd[8275]: terminating on signal 15
Mar 29 23:00:58 fenix dhcpcd[10086]: terminating on signal 15
Mar 31 01:38:57 fenix dhcpcd[9940]: terminating on signal 15
Mar 31 21:20:58 fenix dhcpcd[8377]: terminating on signal 15
Apr 1 01:28:12 fenix dhcpcd[8210]: terminating on signal 15
Apr 1 11:33:43 fenix dhcpcd[10052]: terminating on signal 15
Apr 1 11:40:19 fenix dhcpcd[8146]: terminating on signal 15
Apr 2 08:43:25 fenix dhcpcd[9565]: MAC address = 00:30:05:44:39:5d
Apr 2 08:43:29 fenix dhcpcd[9565]: verified 85.226.208.60 address is not in use
Apr 2 08:43:29 fenix dhcpcd[9565]: your IP address = 85.226.208.60
Apr 2 12:07:35 fenix dhcpcd[9567]: terminating on signal 15
Apr 2 12:05:59 localhost dhcpcd[12082]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 2 12:15:02 localhost dhcpcd[8480]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 4 20:03:18 localhost dhcpcd[8481]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 4 20:04:32 localhost dhcpcd[8483]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 4 20:28:06 localhost dhcpcd[8480]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 6 23:06:45 localhost dhcpcd[8479]: dhcpStart: ioctl SIOCGIFHWADDR: No such device
Apr 6 23:07:57 localhost dhcpcd[9367]: dhcpStart: ioctl SIOCGIFHWADDR: No such device
Apr 6 23:08:49 localhost dhcpcd[9814]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 6 23:11:38 localhost dhcpcd[10276]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 7 00:31:25 localhost dhcpcd[8479]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 7 13:55:35 localhost dhcpcd[8480]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 7 14:09:29 localhost dhcpcd[8480]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Apr 7 22:47:03 localhost dhcpcd[8480]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring |
|
|
| Back to top |
|
|
Hamlet
Apprentice
Joined: 15 Apr 2005
Posts: 151
Location: Turin (Italy)
|
| Posted: Sun Apr 08, 2007 12:05 am Post subject: |
|
|
Try to change every eth0 into eth2 in your /etc/conf.d/net, and then to restart network.
| Code: |
cp /etc/conf.d/net /etc/conf.d/net.when-it-was-eth0
sed -i -e 's/eth0/eth2/g' /etc/conf.d/net
[[ -r /etc/init.d/net.eth2 ]] || ln -s net.lo /etc/init.d/net.eth2
/etc/init.d/net.eth0 stop
/etc/init.d/net.eth2 start
|
Translation bash -> English:
Make a backup copy of old configuration file
Then change all "eth0" text in /etc/conf.d/net into "eth2".
Then, if /etc/init.d/net.eth2 is not a readable file (e.g. it doesn't exist), create it as a link to /etc/init.d/net.lo .
Then stop net service on eth0 (this will probably fail since dhcp failed...)
Finally start network service on eth2, which seems to be your real network card now.
Disclaimer: try to understand the meaning of those commands, since they could contain typos (of course I don't see any, but I didn't test them).
If this works, you will connect to the net; still, you should understand why your eth0 became eth2 and maybe make it go back to eth0. |
|
| Back to top |
|
|
dark-lord
n00b
Joined: 06 Apr 2007
Posts: 10
Location: Israel
|
| Posted: Sun Apr 08, 2007 7:40 am Post subject: |
|
|
So try this:
| Code: |
/etc/init.d/eth2 start
|
then:
|
|
| Back to top |
|
|
|
Networking & Security
