Skocz do zawartości
Storm25

Dlaczego Nie Startuje Dhcp Serwer

Rekomendowane odpowiedzi

# dhcpd.conf

ddns-update-style ad-hoc;

option domain-name-servers 194.146.216.16;

option netbios-name-servers 192.168.1.1;

option broadcast-address 192.168.1.255;

default-lease-time 86400;

max-lease-time 12400;

subnet 192.168.1.0 netmask 255.255.255.0 {

range 192.168.1.35 192.168.1.10;

option broadcast-address 192.168.1.255;

option routers 192.168.1.1;

 

}

 

dalej chce zeby serwer dhcp dziala na interfejsie eth1 po starcie systemu wiec zrobilem plik startowy:

pico /etc/rc.d/rc/dhcpd

#!/bin/sh

# Skrypt start/stop dhcpd

case "$1" in

start)

dhcpd eth1

;;

stop)

killall dhcpd

;;

*)

echo ""

echo "Użycie: $0 { start | stop }"

echo ""

exit

;;

esac

 

i dopisuje rc.local:

pico /etc/rc.d/rc.local

if [ -x /etc/rc.d/rc.dhcpd ]; then

/etc/rc.d/rc.dhcpd start

fi

 

POWINNO DZIALAC PO STARCIE PRAWDA, A NIE DZIAŁA :/

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Witam,

pozwolę sobię podłączyć się pod ten temat, ponieważ też mam problem ze startem serwera Dhcp. Moja sytuacja wygląda następująco: komputer z Linuksem Gentoo ma udostępniać internet z neostrady (z modemu sagem) dla innych komputerów w lokalnej sieci. Połączenie z neo skonfigurowałem, ale jest problem z udostępnieniem. Robiłem z grubsza tak jak piszą w podręczniu na stronach gentoo, ale po pewnym czasie zniknęła mi karta eth1. Mam tylko eth0 eth2 lo ppp. W komputerze mam fizycznie jedną kratę sieciową (zintegrowaną), oraz podłączony sagem. Przy ładowaniu się systemu cały czas dostaję [ok] aż do momentu:

 

Starting eth1

Bringing up eth1

dhcp

Running dhcpcd... [!!]

 

Pomocy, ja już nie chcę włączać Windows!!!

 

Może powrzucam trochę moich plików i odpowiedzi:

 

ifconfig -la:

eth0	  Link encap:Ethernet  HWaddr 00:0E:A6:AC:40:D3  		  inet addr:192.168.0.1  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: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)		  Interrupt:23 Base address:0x6000 eth1	  Link encap:UNSPEC  HWaddr 00-00-4C-01-00-00-00-36-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:60:4C:6E:6E:53  		  UP BROADCAST RUNNING MULTICAST  MTU:65535  Metric:1		  RX packets:18074 errors:0 dropped:0 overruns:0 frame:0		  TX packets:13633 errors:0 dropped:0 overruns:0 carrier:0		  collisions:0 txqueuelen:1000 		  RX bytes:11448508 (10.9 Mb)  TX bytes:1968994 (1.8 Mb)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:12 errors:0 dropped:0 overruns:0 frame:0		  TX packets:12 errors:0 dropped:0 overruns:0 carrier:0		  collisions:0 txqueuelen:0 		  RX bytes:600 (600.0 b)  TX bytes:600 (600.0 b)ppp0	  Link encap:Point-to-Point Protocol  		  inet addr: tu jest adres ip  P-t-P:213.25.2.5  Mask:255.255.255.255		  UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1		  RX packets:17982 errors:0 dropped:0 overruns:0 frame:0		  TX packets:13530 errors:0 dropped:0 overruns:0 carrier:0		  collisions:0 txqueuelen:3 		  RX bytes:11411591 (10.8 Mb)  TX bytes:1695392 (1.6 Mb)

/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 :]!).ifconfig_eth1=( "adsl" )user_eth1=( "tu jest prawidlowa nazwa uzytkownika" )ifconfig_eth1=( "dhcp" )ifconfig_eth0=( "192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" )

dnsmasq.conf:

# Configuration file for dnsmasq.## Format is one option per line, legal options are the same# as the long options legal on the command line. See# "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.# The following two options make you a better netizen, since they # tell dnsmasq to filter out queries which the public DNS cannot# answer, and which load the servers (especially the root servers) # uneccessarily. If you have a dial-on-demand link they also stop# these requests from bringing up the link uneccessarily.# Never forward plain names (with a dot or domain part)domain-needed# Never forward addresses in the non-routed address spaces.bogus-priv# Uncomment this to filter useless windows-originated DNS requests# which can trigger dial-on-demand links needlessly.# Note that (amongst other things) this blocks all SRV requests, # so don't use it if you use eg Kerberos.# This option only affects forwarding, SRV records originating for# dnsmasq (via srv-host= lines) are not suppressed by it.#filterwin2k# Change this line if you want dns to get its upstream servers from# somewhere other that /etc/resolv.conf #resolv-file=# By  default,  dnsmasq  will  send queries to any of the upstream# servers it knows about and tries to favour servers to are  known# to  be  up.  Uncommenting this forces dnsmasq to try each query# with  each  server  strictly  in  the  order  they   appear   in# /etc/resolv.conf#strict-order# If you don't want dnsmasq to read /etc/resolv.conf or any other# file, getting its servers for this file instead (see below), then# uncomment this#no-resolv# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv# files for changes and re-read them then uncomment this.#no-poll# Add other name servers here, with domain specs if they are for # non-public domains.#server=/localnet/192.168.0.1# Add local-only domains here, queries in these domains are answered# from /etc/hosts or DHCP only.#local=/localnet/# Add domains which you want to force to an IP address here.# The example below send any host in doubleclick.net to a local# webserver.#address=/doubleclick.net/127.0.0.1# If you want dnsmasq to change uid and gid to something other# than the default, edit the following lines.#user=#group=# If you want dnsmasq to listen for requests only on specified interfaces# (and the loopback) give the name of the interface (eg eth0) here. # Repeat the line for more than one interface.#interface=eth0# Or you can specify which interface _not_ to listen on#except-interface=# Or which to listen on by address (remember to include 127.0.0.1 if# you use this.)#listen-address=# On systems which support it, dnsmasq binds the wildcard address,# even when it is listening on only some interfaces. It then discards# requests that it shouldn't reply to. This has the advantage of # working even when interfaces come and go and change address. If you# want dnsmasq to really bind only the interfaces it is listening on,# uncomment this option. About the only time you may need this is when # running another nameserver on the same machine.#bind-interfaces # If you don't want dnsmasq to read /etc/hosts, uncomment the# following line.#no-hosts# or if you want it to read another file, as well as /etc/hosts, use# this.#addn-hosts=/etc/banner_add_hosts# Set this (and domain: see below) if you want to have a domain# automatically added to simple names in a hosts-file.#expand-hosts# Set the domain for dnsmasq. this is optional, but if it is set, it# does the following things.# 1) Allows DHCP hosts to have fully qualified domain names, as long#	 as the domain part matches this setting.# 2) Sets the "domain" DHCP option thereby potentially setting the#	domain of all systems configured by DHCP# 3) Provides the domain part for "expand-hosts"#domain=thekelleys.org.uk  # Uncomment this to enable the integrated DHCP server, you need# to supply the range of addresses available for lease and optionally # a lease time. If you have more than one network, you will need to# repeat this for each network on which you want to supply DHCP# service.#dhcp-range=192.168.0.50,192.168.0.150,12h# This is an example of a DHCP range where the netmask is given. This# is needed for networks we reach the dnsmasq DHCP server via a relay # agent. If you don't know what a DHCP relay agent is, you probably# don't need to worry about this.#dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h# This is an example of a DHCP range with a network-id, so that# some DHCP options may be set only for this network.#dhcp-range=red,192.168.0.50,192.168.0.150# Supply parameters for specified hosts using DHCP. There are lots# of valid alternatives, so we will give examples of each. Note that# IP addresses DO NOT have to be in the range given above, they just# need to be on the same network. The order of the parameters in these# do not matter, it's permissble to give name,adddress and MAC in any order# Always allocate the host with ethernet address 11:22:33:44:55:66 # The IP address 192.168.0.60#dhcp-host=11:22:33:44:55:66,192.168.0.60# Always set the name of the host with hardware address# 11:22:33:44:55:66 to be "fred"#dhcp-host=11:22:33:44:55:66,fred# Always give the host with ethernet address 11:22:33:44:55:66# the name fred and IP address 192.168.0.60 and lease time 45 minutes#dhcp-host=11:22:33:44:55:66,fred,192.168.0.60,45m# Give the machine which says it's name is "bert" IP address# 192.168.0.70 and an infinite lease#dhcp-host=bert,192.168.0.70,infinite# Always give the host with client identifier 01:02:02:04 # the IP address 192.168.0.60#dhcp-host=id:01:02:02:04,192.168.0.60# Always give the host with client identifier "marjorie"# the IP address 192.168.0.60#dhcp-host=id:marjorie,192.168.0.60# Enable the address given for "judge" in /etc/hosts# to be given to a machine presenting the name "judge" when# it asks for a DHCP lease.#dhcp-host=judge# Never offer DHCP service to a machine whose ethernet # address is 11:22:33:44:55:66#dhcp-host=11:22:33:44:55:66,ignore# Ignore any client-id presented by the machine with ethernet# address 11:22:33:44:55:66. This is useful to prevent a machine # being treated differently when running under different OS's or# between PXE boot and OS boot.#dhcp-host=11:22:33:44:55:66,id:*# Send extra options which are tagged as "red" to # the machine with ethernet address 11:22:33:44:55:66#dhcp-host=11:22:33:44:55:66,net:red# Send extra options which are tagged as "red" to # any machine with ethernet address starting 11:22:33:#dhcp-host=11:22:33:*:*:*,net:red# Send extra options which are tagged as "red" to any machine whose# DHCP vendorclass string includes the substring "Linux"#dhcp-vendorclass=red,Linux# Send extra options which are tagged as "red" to any machine one # of whose DHCP userclass strings includes the substring "accounts"#dhcp-userclass=red,accounts# If this line is uncommented, dnsmasq will read /etc/ethers and act# on the ethernet-address/IP pairs found there just as if they had# been given as --dhcp-host options. Useful if you keep# MAC-address/host mappings there for other purposes.#read-ethers# Send options to hosts which ask for a DHCP lease.# See RFC 2132 for details of available options.# Note that all the common settings, such as netmask and# broadcast address, DNS server and default route, are given# sane defaults by dnsmasq. You very likely will not need any# any dhcp-options. If you use Windows clients and Samba, there# are some options which are recommended, they are detailed at the# end of this section.# For reference, the common options are:# subnet mask - 1# default router - 3# DNS server - 6# broadcast address - 28# Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5#dhcp-option=42,192.168.0.4,10.10.0.5# Set the NTP time server address to be the same machine as # is running dnsmasq#dhcp-option=42,0.0.0.0# Set the NIS domain name to "welly"#dhcp-option=40,welly# Set the default time-to-live to 50#dhcp-option=23,50# Set the "all subnets are local" flag#dhcp-option=27,1# Send the etherboot magic flag and then etherboot options (a string).#dhcp-option=128,e4:45:74:68:00:00#dhcp-option=129,NIC=eepro100# Specify an option which will only be sent to the "red" network # (see dhcp-range for the declaration of the "red" network)#dhcp-option=red,42,192.168.1.1# The following DHCP options set up dnsmasq in the same way as is specified# for the ISC dhcpcd in # http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt# adapted for a typical dnsmasq installation where the host running# dnsmasq is also the host running samba.# you may want to uncomment them if you use Windows clients and Samba.#dhcp-option=19,0		   # option ip-forwarding off #dhcp-option=44,0.0.0.0	 # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)#dhcp-option=45,0.0.0.0	 # netbios datagram distribution server#dhcp-option=46,8		   # netbios node type#dhcp-option=47			 # empty netbios scope.# Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client# probably doesn't support this......#dhcp-option=119,eng.apple.com,marketing.apple.com # Send encapsulated vendor-class specific options. The vendor-class# is sent as DHCP option 60, and all the options marked with the# vendor class are send encapsulated in DHCP option 43. The meaning of# the options is defined by the vendor-class. This example sets the # mtftp address to 0.0.0.0 for PXEClients#dhcp-option=vendor:PXEClient,1,0.0.0.0# Set the boot filename and tftpd server name and address# for BOOTP. You will only need this is you want to# boot machines over the network.#dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3# Set the limit on DHCP leases, the default is 150#dhcp-lease-max=150# The DHCP server needs somewhere on disk to keep its lease database.# This defaults to a sane location, but if you want to change it, use# the line below.#dhcp-leasefile=/var/lib/misc/dnsmasq.leases# Set the DHCP server to authoritative mode. In this mode it will barge in # and take over the lease for any client which broadcasts on the network, # whether it has a record of the lease or not. This avoids long timeouts# when a machine wakes up on a new network. DO NOT enable this if there's # the slighest chance that you might end up accidentally configuring a DHCP# server for your campus/company accidentally. The ISC server uses the same# the same option, and this URL provides more information:# http://www.isc.org/index.pl?/sw/dhcp/authoritative.php#dhcp-authoritative# Set the cachesize here.#cache-size=150# If you want to disable negative caching, uncomment this.#no-negcache# Normally responses which come form /etc/hosts and the DHCP lease# file have Time-To-Live set as zero, which conventionally means# do not cache further. If you are happy to trade lower load on the # server for potentially stale date, you can set a time-to-live (in # seconds) here.#local-ttl=# If you want dnsmasq to detect attempts by Verisign to send queries# to unregistered .com and .net hosts to its sitefinder service and# have dnsmasq instead return the correct NXDOMAIN response, uncomment# this line. You can add similar lines to do the same for other# registries which have implemented wildcard A records.#bogus-nxdomain=64.94.110.11# If you want to fix up DNS results from upstream servers, use the# alias option. This only works for IPv4.# This alias makes a result of 1.2.3.4 appear as 5.6.7.8#alias=1.2.3.4,5.6.7.8# and this maps 1.2.3.x to 5.6.7.x#alias=1.2.3.0,5.6.7.0,255.255.255.0# Change these lines if you want dnsmasq to serve MX records.# Return an MX record named "maildomain.com" with target# servermachine.com and preference 50#mx-host=maildomain.com,servermachine.com,50# Set the default target for MX records created using the localmx option.#mx-target=servermachine.com# Return an MX record pointing to the mx-target for all local# machines.#localmx# Return an MX record pointing to itself for all local machines.#selfmx# Change the following lines if you want dnsmasq to serve SRV # records.  These are useful if you want to serve ldap requests for# Active Directory and other windows-originated DNS requests.# See RFC 2782.# You may add multiple srv-host lines. # The fields are <name>,<target>,<port>,<priority>,<weight># If the domain part if missing from the name (so that is just has the# service and protocol sections) then the domain given by the domain=# config option is used. (Note that expand-hosts does not need to be# set for this to work.)# A SRV record sending LDAP for the example.com domain to# ldapserver.example.com port 289#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389# A SRV record sending LDAP for the example.com domain to# ldapserver.example.com port 289 (using domain=)#domain=example.com#srv-host=_ldap._tcp,ldapserver.example.com,389# Two SRV records for LDAP, each with different priorities#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2# A SRV record indicating that there is no LDAP server for the domain# example.com #srv-host=_ldap._tcp.example.com# Change the following lines to enable dnsmasq to serve TXT records.# These are used for things like SPF and zeroconf. (Note that the# domain-name expansion done for SRV records _does_not # occur for TXT records.)#Example SPF.#txt-record=example.com,v=spf1 a -all#Example zeroconf#txt-record=_http._tcp.example.com,name=value,paper=A4# For debugging purposes, log each DNS query as it passes through# dnsmasq.#log-queries# Include a another lot of configuration options.#conf-file=/etc/dnsmasq.more.conf dhcp-range=192.168.0.100,192.168.0.250,72h

regułki iptables:

# Generated by iptables-save v1.3.4 on Mon Mar 13 19:19:52 2006*nat:PREROUTING ACCEPT [351:21476]:POSTROUTING ACCEPT [94:6322]:OUTPUT ACCEPT [73:5078]-A POSTROUTING -o eth1 -j MASQUERADE COMMIT# Completed on Mon Mar 13 19:19:52 2006# Generated by iptables-save v1.3.4 on Mon Mar 13 19:19:52 2006*mangle:PREROUTING ACCEPT [937:329668]:INPUT ACCEPT [841:323811]:FORWARD ACCEPT [96:5857]:OUTPUT ACCEPT [805:67500]:POSTROUTING ACCEPT [901:73357]COMMIT# Completed on Mon Mar 13 19:19:52 2006# Generated by iptables-save v1.3.4 on Mon Mar 13 19:19:52 2006*filter:INPUT ACCEPT [748:311159]:FORWARD DROP [0:0]:OUTPUT ACCEPT [805:67500]-A INPUT -i lo -j ACCEPT -A INPUT -i eth0 -j ACCEPT -A INPUT -i ! eth0 -p udp -m udp --dport 67 -j REJECT --reject-with icmp-port-unreachable -A INPUT -i ! eth0 -p udp -m udp --dport 53 -j REJECT --reject-with icmp-port-unreachable -A INPUT -i eth0 -p tcp -m tcp --dport 0:1023 -j DROP -A INPUT -i eth0 -p udp -m udp --dport 0:1023 -j DROP -A FORWARD -d 192.168.0.0/255.255.0.0 -i eth0 -j DROP -A FORWARD -s 192.168.0.0/255.255.0.0 -i eth0 -j ACCEPT -A FORWARD -d 192.168.0.0/255.255.0.0 -i eth0 -j ACCEPT COMMIT# Completed on Mon Mar 13 19:19:52 2006

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

dla Pana z gentoo - skoro podsieć Twoja jest na eth0 to dlaczego chcesz uruchomic ją z eth1 ?

OK racja poprawiłem w /etc/conf.d/net, teraz jest tam:

 

zamiast:

ifconfig_eth1=( "dhcp" )

 

jest:

ifconfig_eht0=( "dhcp" )

 

Teraz faktycznie działa, bo Windows na drugim komputerze przydziela sobie ip zgodnie z zakresem podanym w /etc/dnsmasq.conf:

 

dhcp-range=192.168.0.100,192.168.0.250,72h

 

Niestety pojawił się kolejny problem i nadal na drugim kompie internetu nie ma.

Przy starcie systemu dostaję:

 

...

Starting ADSL connection ...

...

Waiting for synchro ...

OK .. Modem is synchronized

 

Starting eth0

Bringing up eth0

192.168.0.1

 

Starting eth1

Bringing up eth1

adsl

Starting ADSL for eth1

TIMED OUT

Starting dnsmasq [!!]

Loading iptables state and starting firewall... [ok]

 

 

Czy przypadkiem "Starting ADSL for eth1" nie próbuje jeszcze raz nawiązać połączenia? I czemu dnsmasq się wywala?

Co ciekawe jeśli w Windows ustawię statyczne ip np. 192.168.0.223 oraz podam ręcznie dns-y z telekomunikacji to gg działa a reszta nie.

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

nie żebym namawiał ale... ja niektóre rzeczy startuję z automatu w systemie a inne z "swojego automatu", proponował bym Ci ponieść same interfejsy aby miały połączenie a resztę wydłubać z palca, potem można wsio w skrypcie umieścić, albo po kolei konfigurować, ja osobiście wolę swój skrypcik(ki) bo wiem co w trawce piszczy :-)

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

... ja niektóre rzeczy startuję z automatu w systemie a inne z "swojego automatu", proponował bym Ci ponieść same interfejsy aby miały połączenie a resztę wydłubać z palca ...

Ja próbowałem zrobić wg podręcznika http://www.gentoo.org/doc/pl/home-router-howto.xml, na pisanie własnych skryptów jestem jeszcze za cienki. Nie za bardzo wiem co należy zrobić.

 

Nie rozumiem dla czego karta eth1 jest wyłączona?

ifconfig -a

 

eth0 Link encap:Ethernet HWaddr 00:0E:A6:AC:40:D3

....

eth1 Link encap:UNSPEC HWaddr 00-00-4C-01-00-00-00-36-00-00-00-00-00-00-00-00

....

eth2 Link encap:Ethernet HWaddr 00:60:4C:6E:6E:53

....

lo Link encap:Local Loopback

....

ppp0 Link encap:Point-to-Point Protocol

 

 

Ponoć eth1 miał być utorzsamiany z ppp0, dlaczego więc:

rc-status

 

local [ started ]

netmount [ started ]

syslog-ng [ started ]

vixie-cron [ started ]

splash [ started ]

adsl [ started ]

net.eth1 [ off ] <- ???

net.eth0 [ started ]

dnsmasq [ started ] <- ??? a przy starcie systemu jest teraz [ !! ] (patrz post wcześniej)

iptables [ started ]

numlock [ started ]

 

 

Czy dobrze rozumiem, że:

eth0 to karta sieciowa zintegrowana (po niej ma chodzić lan), jest połączona skrosowaną skrętką z kompem z Win

eth1 to druga karta - jakaś wirtualna?? - (modem usb adsl) połączona z ppp0

eth2 to firewire na pci

 

Nie wiem co z tym zrobić by zadziałało.

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Ciebie interesuje eth0 i ppp0 - reszte olej, wpisz sobie w /etc/sysctl.conf (tam jest ale z haszem, to zrob jak poniżej)

 

# Disables packet forwardingnet.ipv4.ip_forward = 1

(teraz 3a restarcik - nie pamietam polecenia zeby system sobie odczytał (sysctl --help))

a potem... ja mam DSL (tja...) to mam statycznie dopisane ip w regółach, Ty się musisz oprzeć na interfejscie (ppp0), mniej więcej będzie wyglądało to tak:

 

iptables -A POSTROUTING -s 192.168.0.0/16 -j MASQUERADE -t nat

a potem poświęć trochę czasu (tego co zaoszczędziłeś właśnie) na naukę pisania skryptów :-)

(no i mam nadzieję że niczego nie pominąłem, jak nie działa - to google)

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

OK już działa!

 

Problem leżał w złej interpretacji przeze mnie kolejności kart sieciowych i firewire. Próbowałem udostępniać internet przez firewire, a nie rj45. Po wyjęciu karty pci zniknęło co trzeba, zadziałało co trzeba i jest super (rozumiem jak to działa). Dzięki za zainteresowanie i naprowadzanie.

Edytowane przez Dann

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Dołącz do dyskusji

Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.

Gość
Dodaj odpowiedź do tematu...

×   Wklejono zawartość z formatowaniem.   Przywróć formatowanie

  Dozwolonych jest tylko 75 emoji.

×   Odnośnik został automatycznie osadzony.   Przywróć wyświetlanie jako odnośnik

×   Przywrócono poprzednią zawartość.   Wyczyść edytor

×   Nie możesz bezpośrednio wkleić grafiki. Dodaj lub załącz grafiki z adresu URL.

Ładowanie


×
×
  • Dodaj nową pozycję...