* [gentoo-user] Network problem
@ 2007-02-12 8:54 Roman Naumann
2007-02-12 10:15 ` Hans-Werner Hilse
0 siblings, 1 reply; 4+ messages in thread
From: Roman Naumann @ 2007-02-12 8:54 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Hi,
I have a problem with my ehternet connection and would be pleased if someone
could help me:
I emerged some things (don't ask me what exactly...) and am unable to ping
anything now.
The ip-address and co. are alright, I can just boot another operating system
on my pc (sabayon or windows) and eth0 is working fine using the same
configuration.
Ifconfig eth0 gives me this:
Link encap:
UNSPEC HWaddr 44-4F-C0-00-14-31-AC-10-00-00-00-00-00-00-00-00
inet addr:192.168.0.45 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:72 (72.0 b)
I'm pretty sure the Mac-Addr is too long.. that's weird,
Also, when using Sabayon, the first line differs: "Link encap:ether" and the
mac is correct
I tried to change the mac with:
ifconfig eth0 hw ether 10:20:30:40:50:60
but then, I get th following:
SIOCSIFHWADDR: Invalid argument
Very strange: I have two independend pcs and BOTH of them have the same
problem meanwhile!
Any ideas?
[-- Attachment #2: Type: text/html, Size: 1375 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Network problem
2007-02-12 8:54 [gentoo-user] Network problem Roman Naumann
@ 2007-02-12 10:15 ` Hans-Werner Hilse
2007-02-12 12:14 ` Roman Naumann
0 siblings, 1 reply; 4+ messages in thread
From: Hans-Werner Hilse @ 2007-02-12 10:15 UTC (permalink / raw
To: gentoo-user
Hi,
On Mon, 12 Feb 2007 09:54:42 +0100 "Roman Naumann"
<sapiens.dyslexia@googlemail.com> wrote:
> Ifconfig eth0 gives me this:
>
> Link encap:
>
> UNSPEC HWaddr 44-4F-C0-00-14-31-AC-10-00-00-00-00-00-00-00-00
> [...]
> I'm pretty sure the Mac-Addr is too long.. that's weird,
> Also, when using Sabayon, the first line differs: "Link encap:ether"
> and the mac is correct
>
> I tried to change the mac with:
> ifconfig eth0 hw ether 10:20:30:40:50:60
> but then, I get th following:
> SIOCSIFHWADDR: Invalid argument
eth0 doesn't seem to be what it has been anymore. You probably compiled
a new kernel with some extra network drivers (USB devices? Firewire?).
Looking at the "MAC" address above, I'd say it's something designated
for a peer-to-peer connection.
use "ifconfig -a" to find your real network interface. If it's not
shown there (under different name, of course), you're probably missing
the right modules. You might want to use udev to give your interfaces a
persistent naming in the future, that will save you these troubles.
-hwh
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Network problem
2007-02-12 10:15 ` Hans-Werner Hilse
@ 2007-02-12 12:14 ` Roman Naumann
2007-02-13 17:43 ` Daniel da Veiga
0 siblings, 1 reply; 4+ messages in thread
From: Roman Naumann @ 2007-02-12 12:14 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
On 2/12/07, Hans-Werner Hilse <hilse@web.de> wrote:
>
> Hi,
>
> On Mon, 12 Feb 2007 09:54:42 +0100 "Roman Naumann"
> <sapiens.dyslexia@googlemail.com> wrote:
>
> > Ifconfig eth0 gives me this:
> >
> > Link encap:
> >
> > UNSPEC HWaddr 44-4F-C0-00-14-31-AC-10-00-00-00-00-00-00-00-00
> > [...]
> > I'm pretty sure the Mac-Addr is too long.. that's weird,
> > Also, when using Sabayon, the first line differs: "Link encap:ether"
> > and the mac is correct
> >
> > I tried to change the mac with:
> > ifconfig eth0 hw ether 10:20:30:40:50:60
> > but then, I get th following:
> > SIOCSIFHWADDR: Invalid argument
>
> eth0 doesn't seem to be what it has been anymore. You probably compiled
> a new kernel with some extra network drivers (USB devices? Firewire?).
> Looking at the "MAC" address above, I'd say it's something designated
> for a peer-to-peer connection.
>
> use "ifconfig -a" to find your real network interface. If it's not
> shown there (under different name, of course), you're probably missing
> the right modules. You might want to use udev to give your interfaces a
> persistent naming in the future, that will save you these troubles.
>
> -hwh
>
>
> --
> gentoo-user@gentoo.org mailing list
>
> thanks for your quick answer.
yes, there is a new interface named eth1 and it works.
(so it seems that this problem was caused by replacing coldplug with udev)
[-- Attachment #2: Type: text/html, Size: 1898 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Network problem
2007-02-12 12:14 ` Roman Naumann
@ 2007-02-13 17:43 ` Daniel da Veiga
0 siblings, 0 replies; 4+ messages in thread
From: Daniel da Veiga @ 2007-02-13 17:43 UTC (permalink / raw
To: gentoo-user
On 2/12/07, Roman Naumann <sapiens.dyslexia@googlemail.com> wrote:
> On 2/12/07, Hans-Werner Hilse <hilse@web.de> wrote:
> > Hi,
> >
> > On Mon, 12 Feb 2007 09:54:42 +0100 "Roman Naumann"
> > <sapiens.dyslexia@googlemail.com> wrote:
> >
> > > Ifconfig eth0 gives me this:
> > >
> > > Link encap:
> > >
> > > UNSPEC HWaddr
> 44-4F-C0-00-14-31-AC-10-00-00-00-00-00-00-00-00
> > > [...]
> > > I'm pretty sure the Mac-Addr is too long.. that's weird,
> > > Also, when using Sabayon, the first line differs: "Link encap:ether"
> > > and the mac is correct
> > >
> > > I tried to change the mac with:
> > > ifconfig eth0 hw ether 10:20:30:40:50:60
> > > but then, I get th following:
> > > SIOCSIFHWADDR: Invalid argument
> >
> > eth0 doesn't seem to be what it has been anymore. You probably compiled
> > a new kernel with some extra network drivers (USB devices? Firewire?).
> > Looking at the "MAC" address above, I'd say it's something designated
> > for a peer-to-peer connection.
> >
> > use "ifconfig -a" to find your real network interface. If it's not
> > shown there (under different name, of course), you're probably missing
> > the right modules. You might want to use udev to give your interfaces a
> > persistent naming in the future, that will save you these troubles.
> >
> > -hwh
> >
> >
> > --
> > gentoo-user@gentoo.org mailing list
> >
> >
> thanks for your quick answer.
> yes, there is a new interface named eth1 and it works.
> (so it seems that this problem was caused by replacing coldplug with udev)
>
In fact, you may have a firewire connection, and that is being
recognized as eth0, try adding "nofirewire" to your kernel boot line,
and check if eth0 will be your network card again. Also, there was a
similar problem on the list a few days ago and the OP of that thread
asked for UDEV rules to set names to its interfaces, check the
archives.
--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-02-13 17:48 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-12 8:54 [gentoo-user] Network problem Roman Naumann
2007-02-12 10:15 ` Hans-Werner Hilse
2007-02-12 12:14 ` Roman Naumann
2007-02-13 17:43 ` Daniel da Veiga
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox