[sкavєи]

Hi,

ich hab' da ein kleines Problem mit meinem LAN. Ich habe 3 Rechner:

Rechner 1 (Win XP Home) hängt per WLAN direkt am Router kommt in's LAN und auch in's Internet.
Rechner 2 (Debian 3.1 SARGE) hängt per Patch-Kabel am Router.
Rechner 3 (Win XP Pro) hängt per Crossover-Kabel an Rechner 2.

Das Problem ist folgendes:
Wenn ich einer Ethernet-Bridge zwischen eth0 und eth1 an Rechner 2 einrichte und die IP-Adressen statisch vergebe kommt dieser zwar noch in's LAN aber nicht mehr in's Internet. Rechner 3 welcher ja an Rechner 2 hängt kommt dann aber noch sowohl in's LAN als auch in's Internet.
Wenn ich die IP-Adressen vom Router per DHCP vergeben lasse und keine Bridge verwende, kann ich ja nur eine für eth0 anfordern lassen, weil eth1 ja gar keine Verbindung zum Router hat. D.h. ich kann auch DHCP-Relay vergessen, da eth1 gar nicht initialisiert wird, da es keine IP hat. eth1 eine statische IP geben funktioniert zwarallerdings funktioniert der DHCP-Relay dann nicht. Jedenfalls bekommt der Rechner 3 keine IP zugewiesen.

Konfiguration ist derzeit folgende:
Rechner 1: läuft wunderbar also egal.
Rechner 2:
/etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto lo eth1 eth2
allow-hotplug eth1 eth2

# The loopback network interface

iface lo inet loopback

# The primary network interface

iface eth0 inet dhcp
name Ethernet LAN-Karte

auto eth0

iface eth1 inet dhcp
name Ethernet LAN-Karte

/etc/default/dhcp3-relay

# Defaults for dhcp3-relay initscript
# sourced by /etc/init.d/dhcp3-relay
# installed at /etc/default/dhcp3-relay by the maintainer scripts

#
# This is a POSIX shell fragment
#

# What servers should the DHCP relay forward requests to?
SERVERS="192.168.2.1"

# On what interfaces should the DHCP relay (dhrelay) serve DHCP requests?
INTERFACES="eth1"

# Additional options that are passed to the DHCP relay daemon?
OPTIONS=""

/etc/dhcp3/dhcpd.conf

#
# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the 
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

#subnet 10.254.239.0 netmask 255.255.255.224 {
#  range 10.254.239.10 10.254.239.20;
#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 10.254.239.40 10.254.239.60;
#  option broadcast-address 10.254.239.31;
#  option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
#  range 10.5.5.26 10.5.5.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 10.5.5.1;
#  option broadcast-address 10.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
#  hardware ethernet 0:0:c0:5d:bd:95;
#  filename "vmunix.passacaglia";
#  server-name "toccata.fugue.com";
#}

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
#  hardware ethernet 08:00:07:26:c0:a5;
#  fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that.   The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {
#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}

#shared-network 224-29 {
#  subnet 10.17.224.0 netmask 255.255.255.0 {
#	option routers rtr-224.example.org;
#  }
#  subnet 10.0.29.0 netmask 255.255.255.0 {
#	option routers rtr-29.example.org;
#  }
#  pool {
#	allow members of "foo";
#	range 10.17.224.10 10.17.224.250;
#  }
#  pool {
#	deny members of "foo";
#	range 10.0.29.10 10.0.29.230;
#  }
#}

debian:/etc/dhcp3# ifconfig && netstat -rn
eth0	  Protokoll:Ethernet  Hardware Adresse 00:A0:CC:66:78:A9
		  inet Adresse:192.168.2.101  Bcast:192.168.2.255  Maske:255.255.255.0
		  inet6 Adresse: fe80::2a0:ccff:fe66:78a9/64 Gültigkeitsbereich:Verbindung
		  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
		  RX packets:14551 errors:1 dropped:0 overruns:0 frame:0
		  TX packets:12518 errors:1 dropped:0 overruns:0 carrier:1
		  Kollisionen:0 Sendewarteschlangenlänge:1000
		  RX bytes:12114468 (11.5 MiB)  TX bytes:1377154 (1.3 MiB)
		  Interrupt:16 Basisadresse:0xcf00

eth1	  Protokoll:Ethernet  Hardware Adresse 00:0C:6E:0C:C3:E8
		  inet6 Adresse: fe80::20c:6eff:fe0c:c3e8/64 Gültigkeitsbereich:Verbindung
		  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
		  RX packets:1026 errors:0 dropped:0 overruns:0 frame:0
		  TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
		  Kollisionen:0 Sendewarteschlangenlänge:1000
		  RX bytes:110633 (108.0 KiB)  TX bytes:2430 (2.3 KiB)
		  Interrupt:17 Basisadresse:0xd800

lo		Protokoll:Lokale Schleife
		  inet Adresse:127.0.0.1  Maske:255.0.0.0
		  inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
		  UP LOOPBACK RUNNING  MTU:16436  Metric:1
		  RX packets:330 errors:0 dropped:0 overruns:0 frame:0
		  TX packets:330 errors:0 dropped:0 overruns:0 carrier:0
		  Kollisionen:0 Sendewarteschlangenlänge:0
		  RX bytes:20016 (19.5 KiB)  TX bytes:20016 (19.5 KiB)

Kernel IP Routentabelle
Ziel			Router		  Genmask		 Flags   MSS Fenster irtt Iface
192.168.2.0	 0.0.0.0		 255.255.255.0   U		 0 0		  0 eth0
0.0.0.0		 192.168.2.1	 0.0.0.0		 UG		0 0		  0 eth0

Rechner 3: DHCP (geht nicht / DNS-Server: 192.168.2.103 (Rechner 2 eth1) / Gateway: 192.168.2.1)

Z.Zt kommt nur der Deabian Rechner in's Internet und LAN und der andere gar nicht (logisch ohne IP-Zuweisung ).
Kannmir einer sagenwo der Fehler is' bzw. wie ich es realisieren kann, dass beide Rechner sowohl in's LAN als auch in's Internet kommen?

Grüße
TheSuicider

P.S.: Kommt mir nicht mit Vorschläagen wie,kauf dir'n Switch!