David Liontooth wrote:
Sebastian Haase wrote:
Thanks for the replies.
sarge-amd64-2.6.12-netinst.iso did not auto-detect the NICs but after
manually choosing forcedeth it actually worked.
ONLY: that I did get some "timeout" kernel error messages (sorry,
forgot the exact text) and it only really worked after I switched the
network cable between the two ports back and forth many times !!
Good to hear you got it going, but do upgrade your kernel -- the driver
should work without problems.
How can I know which port is eth0 and which eth1 ?
And - if not - can I at least rely on the order staying the same
between reboots ?? (I want to connect one port to the internet the
other to a local (unroutable) private sub-net...
Yes, you can -- as usual in Linux, there are several ways. Check out
http://www.science.uva.nl/research/air/wiki/LogicalInterfaceNames -- the
script /share/usr/share/doc/ifupdown/examples/get-mac-address.sh comes
with the ifupdown package.
Does that mean that the port assignment COULD potentially change after
each reboot !? And I need a special script to adjust
/etc/network/interfaces !? Hard to believe...
[[ OK - I just started reading the mentioned wiki web page and here is a
quote just for documentation purposes:
"""
One of the problems of Linux is that the order of the network interfaces
is unpredictable. Between reboots it does stay the same, but it is very
well possible that after an upgrade to a new kernel or the addition or
replacement of a network card (NIC) that the other of all network
interface changes. For example, what used to be eth0 now becomes eth1 or
eth2 or visa versa.
"""
]]
Is "forcedeth" the only possible driver ? Just curious ...
Yes -- and it works great!
Thanks, good to know.
Sebastian Haase
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
