• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

Linux Probleme (CD und NW)

OP
P

pburri

Member
ach meine güte das problem mit der karte hat sich gelöst, der treiber ist anscheinend installiert. dennoch funktioniert es nicht. ich kann mit ifconfig die ip setzen, passiert nix, im yast kann ich die netzwerkeinstellungen gar nicht machen, da aus irgendeinem grund anscheinend der dhcp client läuft. Ausschalten weiss ich aber net wie -.-
und naja wenn ich n pc rr mach, ist das eth0 device nicht mehr in der ifconfig.

darin steht nur ein lo (sehr wahrscheinlich der localhost) device und dummy0
 
A

admine

Ultimate Guru
Den störenden DHCP-Client kannst doch sicher abstellen.
Dann sollte auch YAST zum Einstellen der NW-Karte funtzen bzw. ifconfig.

Aber für weitere NW-Probs überlasse ich "das Feld" mal den Spezies ;)
 
OP
P

pburri

Member
Den störenden DHCP-Client kannst doch sicher abstellen.
Zum Vergrößern anklicken....

die frage ist wie ^^ per yast geht das ganze nicht :)

dhcpd.conf
Code: 
# dhcpd.conf
#
# Configuration file for ISC dhcpd
#

# Hosts with more than one interface MUST specify a ``server-identifier'',
# which should be the IP address of the server's primary network interface,
# or if there is no interface that can be described that way, at least an
# interface whose address isn't likely to change.

server-identifier toccata.fugue.com;

# option definitions common to all supported networks...
option domain-name "fugue.com";
option domain-name-servers toccata.fugue.com;

# Shared network declaration is used to group subnets which share the same
# physical network together.   The name is specified so that the shared
# network can be referred to in log messages - it serves no other function.

shared-network FUGUE {

# option definitions common to this shared network.
  option subnet-mask 255.255.255.224;
  default-lease-time 600;
  max-lease-time 7200;

# One of the two IP subnets that share this physical network
#
# Address ranges can be specified for each subnet attached to
# a shared network.   Since these subnets share the same physical
# network, addresses are pooled together, and assignments are made
# without regard to the actual subnet.   If the optional dynamic-bootp
# keyword is given in the address range declaration, then addresses
# in that range can be assigned either with the DHCP protocol or the
# BOOTP protocol; otherwise, only DHCP clients will have addresses
# allocated from the address range.
#
# Note that each IP subnet can have its own options specific to that subnet.
# options that aren't specified in the subnet are taken from the shared
# network (if any) and then from the global option list.

  subnet 204.254.239.0 netmask 255.255.255.224 {
    range 204.254.239.10 204.254.239.20;
    option broadcast-address 204.254.239.31;
    option routers prelude.fugue.com;
  }

# The other subnet that shares this physical network
  subnet 204.254.239.32 netmask 255.255.255.224 {
    range dynamic-bootp 204.254.239.10 204.254.239.20;
    option broadcast-address 204.254.239.31;
    option routers snarg.fugue.com;
  }
}

# IP subnets that are alone on their physical wire should be declared by
# themselves.   ISC dhcpd may still refer to them as shared networks in
# log messages, but this is simply an artifact of the underlying data
# structures.
#
# Note that options can be specified in the subnet declaration which
# supersede the global options specified earlier.

subnet 192.5.5.0 netmask 255.255.255.224 {
  range 192.5.5.26 192.5.5.30;
  option name-servers bb.home.vix.com, gw.home.vix.com;
  option domain-name "vix.com";
  option routers 192.5.5.1;
  option subnet-mask 255.255.255.224;
  option broadcast-address 192.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;
}

# If a DHCP or BOOTP client is mobile and might be connected to a variety
# of networks, more than one fixed address for that host can be specified.
# Hosts can have fixed addresses on some networks, but receive dynamically
# allocated address on other subnets; in order to support this, a host
# declaration for that client must be given which does not have a fixed
# address.   If a client should get different parameters depending on
# what subnet it boots on, host declarations for each such network should
# be given.   Finally, if a domain name is given for a host's fixed address
# and that domain name evaluates to more than one address, the address
# corresponding to the network to which the client is attached, if any,
# will be assigned.
host confusia {
  hardware ethernet 02:03:04:05:06:07;
  fixed-address confusia-1.fugue.com, confusia-2.fugue.com;
  filename "vmunix.confusia";
  server-name "toccata.fugue.com";
}

host confusia {
  hardware ethernet 02:03:04:05:06:07;
  fixed-address confusia-3.fugue.com;
  filename "vmunix.confusia";
  server-name "snarg.fugue.com";
}

host confusia {
  hardware ethernet 02:03:04:05:06:07;
  filename "vmunix.confusia";
  server-name "bb.home.vix.com";
}

route
Code: 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
atglinux.microc *               255.255.255.255 UH    0      0        0 dummy0
loopback        *               255.0.0.0       U     0      0        1 lo

ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:50 errors:0 dropped:0 overruns:0 frame:0
TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
collisions:0

eth0 Link encap:Ethernet HWaddr 00:50:FC:C1:6D:24
inet addr:192.168.100.204 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
Interrupt:10 Base address:0xcc00

dummy0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.100.204 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING NOARP 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
Zum Vergrößern anklicken....
 
OP
P

pburri

Member
ok hat sich erledigt ^^ Konfigurationsdatei nochmal überflogen und angepasst und jetzt funtzt auch alles wie es soll ^^
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Oben