Jak nasdílet připojení k internetu?

Zdravím,mám malej problém a ten mě hodně trápí:
Mám dvě mašiny,na jedný FC6 a na druhý WinXP… Fedoru bych chtěl použít jako router…
Síťovky mám nastavený:
eth0 = 85.193.x.xx
eth1 = 192.168.0.1
Ve Winech mám:
IP = 192.168.0.2
Brána= 192.168.0.1
A teď nevím jak dál… Zkoušel jsem návody z netu,ale byly k ničemu… Mohli by jste mi sem napsat,jak mám postupovat? Díky moc…

gedit /etc/sysctl.conf

Controls IP packet forwarding

net.ipv4.ip_forward = 1

yum install dnsmasq
gedit /etc/dnsmasq.conf
nastav
dhcp-range
na winech nastav pouzivat DHCP

Jako vzdy - zkus pochopit co vlastne delas, pujde to lip.

Ahoj, mám podobný problém, na PC mám FC6 a na notebooku Mandrivu, potřebuju nastavit aby PC bylo jako router pro notebook.
Díky

Díky moc…hned,jak se dostanu domů,tak to vyzkouším… Mám FC6 asi měsíc (přešel jsem z winů),tak jsem totálně neměl ponětí co s tím…

Pokud clovek chce delat takovouhle vec, mel by mit aspon zakladni poneti o sitich. K tomu nastaveni co je nahore je totiz potreba jeste spravne napsat masky siti. Pro Rudolfa plati to same. Akorat v posledni casti nastavi DHCP pridelovani adresy na Madrive.:slight_smile:

Masku sítě jsem nepsal,protože používám tu,co používá na malý LAN asi každej (255.255.255.0)… už se těšim domů,až budu mít klid od bráchy,protože nebude chtít ke mně na net :slight_smile:

Tak nic…fakt jsem lama… Windows hlásí “omezené nebo žádné připojení”… Zkoušel jsem i z těch příkladů,co jsou v souboru dnsmasq.conf,ale nedělá to nic… Jak mám zadat tu DHCP-RANGE?

Muj dnsmasq.conf obsahuje krom komentaru jen toto:


domain-needed
bogus-priv
filterwin2k
interface=eth1
dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
dhcp-host=00:aa:bb:5B:6D:35,192.168.0.60

sluzbu dnsmasq musite samozrejme spustit
service dnsmasq start
a pokud chcete aby byla startovana pri kazdem spusteni pocitace
chkconfig dnsmasq on
(to same lze doufam realizovat klikanim v menu System/Sprava/Services)

Po editaci sysctl.conf, pokud to neumite jinak, musite tez restarovat pocitac.
To jinak je
echo 1 > /proc/sys/net/ipv4/ip_forward

dhcp-host=00:aa:bb:5B:6D:35,192.168.0.60 - tam má být MAC adresa síťovky počítače,kterej se na mě připojuje?

Pokud chces aby se ti k jednomu pocitaci pridelovala porad stejna adresa tak ano. Pokud ti je jedno jakou adresu z rozsahu ti to prideli tak tento radek muzes vybechat.

dobrá,takže mám DHCP nastavený,ale nemůžu se připojit na žádnou stránku… Ale svoje PC (s linuxem) pingnu… nějakej nápad?
Update -> Ping z venčí funguje,ale třeba counter strike se nepřipojí ani na server podle IP adresy…

A jste si jisty, ze jste nezapomel nastavit ten ip_forward?
Funguje vam na tom windowsim stroji preklad adres (command prompt, nslookup www.seznam.cz)? Nemate ve firewallu FC6 zakazany forward chain
zkuste docasne “service iptables stop”. Na 90% to ale bude tim ip_forwardem.

Mám podobný problem.
Na svém PC (fc6) mám WIFI bcm43xx broadcom a síťovou kartu pro připojení domácí sítě.Chtěl bych poskytnout sdílené připojení k internetu i synovi.
Připojení k internetu funguje, ale nemohu připojit synův počítač s win-xp do domácí sítě. Nastavil jsem sysctl.conf dle návodu.Prosím o radu jak nastavit sítovou kartu a jak nastavit dhcp range.Uvedené návody mi bohužel nefungují.Co mám prosím poskytnout za údaje aby bylo možno poradit …děkuji

Tento “navod” funguje. Tecka.

covex napsal(a):

Muj dnsmasq.conf obsahuje krom komentaru jen
toto:

domain-needed
bogus-priv
filterwin2k
interface=eth1
dhcp-range=192.168.0.50,192.168.0.150,255.255.255.
0,12h
dhcp-host=00:aa:bb:5B:6D:35,192.168.0.60

sluzbu dnsmasq musite samozrejme spustit
service dnsmasq start
a pokud chcete aby byla startovana pri kazdem
spusteni pocitace
chkconfig dnsmasq on
(to same lze doufam realizovat klikanim v menu
System/Sprava/Services)

Po editaci sysctl.conf, pokud to neumite jinak,
musite tez restarovat pocitac.
To jinak je
echo 1 > /proc/sys/net/ipv4/ip_forward

Poskytnete na FC6:
cat /etc/sysctl.conf /etc/dnsmasq.conf
ifconfig
route -n

na WXP kdyz jsou pripojeny kabelem k FC6:
ipconfig /all
route print

[root@cz1khc ~]# cat /etc/sysctl.conf /etc/dnsmasq.conf

Kernel sysctl configuration file for Red Hat Linux

For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and

sysctl.conf(5) for more details.

Controls IP packet forwarding

net.ipv4.ip_forward = 1

Controls source route verification

net.ipv4.conf.default.rp_filter = 1

Do not accept source routing

net.ipv4.conf.default.accept_source_route = 0

Controls the System Request debugging functionality of the kernel

kernel.sysrq = 0

Controls whether core dumps will append the PID to the core filename.

Useful for debugging multi-threaded applications.

kernel.core_uses_pid = 1

Controls the use of TCP syncookies

net.ipv4.tcp_syncookies = 1

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 (without 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 from 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 DHCP and DNS 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=

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=

If you want dnsmasq to provide only DNS service on an interface,

configure it as shown above, and then use the following line to

disable DHCP on it.

#no-dhcp-interface=

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 # s, 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=tux

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.1,192.168.0.2,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=00:00:e8:64:8e:28,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.2

#dhcp-host=id:tomda,192.168.0.2

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

Send extra options which are tagged as “red” to any machine whose

MAC address matches the pattern.

#dhcp-mac=red,00:60:8C:::*

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

hostname - 12

broadcast address - 28

Override the default route supplied by dnsmasq, which assumes the

router is the same machine as the one running dnsmasq.

#dhcp-option=3,1.2.3.4

Override the default route supplied by dnsmasq and send no default

route at all. Note that this only works for the options sent by

default (1, 3, 6, 12, 28) the same line will send a zero-length option

for all other option numbers.

#dhcp-option=3

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 “tux”

dhcp-option=40,tux

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.0.2

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 RFC-3442 classless static routes (note the netmask encoding)

#dhcp-option=121,192.168.1.0/24,1.2.3.4,10.0.0.0/8,5.6.7.8

Send vendor-class specific options encapsulated in DHCP option 43.

The meaning of the options is defined by the vendor-class so

options are sent only when the client supplied vendor class

matches the class given here. (A substring match is OK, so “MSFT”

matches “MSFT” and “MSFT 5.0”). This example sets the

mtftp address to 0.0.0.0 for PXEClients.

#dhcp-option=vendor:PXEClient,1,0.0.0.0

Send microsoft-specific option to tell windows to release the DHCP lease

when it shuts down. Note the “i” flag, to tell dnsmasq to send the

value as a four-byte integer - that’s what microsoft wants. See

http://technet2.microsoft.com/WindowsServer/en/library/a70f1bb7-d2d4-49f0-96d6-4b7414ecfaae1033.mspx?mfr=true

#dhcp-option=vendor:MSFT,2,1i

Send the Encapsulated-vendor-class ID needed by some configurations of

Etherboot to allow is to recognise the DHCP server.

#dhcp-option=vendor:Etherboot,60,“Etherboot”

Send options to PXELinux. Note that we need to send the options even

though they don’t appear in the parameter request list, so we need

to use dhcp-option-force here.

See http://syslinux.zytor.com/pxe.php#special for details.

Magic number - needed before anything else is recognised

#dhcp-option-force=208,f1:00:74:7e

Configuration file name

#dhcp-option-force=209,configs/common

Path prefix

#dhcp-option-force=210,/tftpboot/pxelinux/files/

Reboot time. (Note ‘i’ to send 32-bit value)

#dhcp-option-force=211,30i

Set the boot filename for BOOTP. You will only need

this is you want to boot machines over the network and you will need

a TFTP server; either dnsmasq’s built in TFTP server or an

external one. (See below for how to enable the TFTP server.)

#dhcp-boot=pxelinux.0

Enable dnsmasq’s built-in TFTP server

#enable-tftp

Set the root directory for files availble via FTP.

#tftp-root=/var/ftpd

Make the TFTP server more secure: with this set, only files owned by

the user dnsmasq is running as will be send over the net.

#tftp-secure

Set the boot file name only when the “red” tag is set.

#dhcp-boot=net:red,pxelinux.red-net

An example of dhcp-boot with an external server: the name and IP

address of the server are given after the filename.

#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

Run an executable when a DHCP lease is created or destroyed.

The arguments sent to the script are “add” or “del”,

then the MAC address, the IP address and finally the hostname

if there is one.

#dhcp-script=/bin/echo

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 ,,,,

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

The following line shows how to make dnsmasq serve an arbitrary PTR

record. This is useful for DNS-SD. (Note that the

domain-name expansion done for SRV records _does_not

occur for PTR records.)

#ptr-record=_http._tcp.dns-sd-services,“New Employee Page._http._tcp.dns-sd-services”

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
conf-dir=/etc/dnsmasq.d
[root@cz1khc ~]#

[root@cz1khc ~]# ifconfig
eth0 Link encap:Ethernet HWadr 00:06:25:09:C8:D9
inet adr:192.168.100.19 Všesměr:192.168.100.255 Maska:255.255.255.0
inet6-adr: fe80::206:25ff:fe09:c8d9/64 Rozsah:Linka
AKTIVOVÁNO VŠESMĚROVÉ_VYSÍLÁNÍ BĚŽÍ MULTICAST MTU:1500 Metrika:1
RX packets:135686 errors:0 dropped:0 overruns:0 frame:0
TX packets:14680 errors:0 dropped:0 overruns:0 carrier:0
kolizí:0 délka odchozí fronty:1000
RX bytes:160834462 (153.3 MiB) TX bytes:1048552 (1023.9 KiB)
Přerušení:11

eth1 Link encap:Ethernet HWadr 00:01:02:9C:3D:B9
inet adr:192.168.0.5 Všesměr:192.168.0.255 Maska:255.255.255.0
AKTIVOVÁNO VŠESMĚROVÉ_VYSÍLÁNÍ MULTICAST MTU:1500 Metrika:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
kolizí:0 délka odchozí fronty:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Přerušení:11 Vstupně/Výstupní port:0xc000

eth2 Link encap:Ethernet HWadr 00:00:E8:64:8E:28
inet adr:192.168.0.6 Všesměr:192.168.0.255 Maska:255.255.255.0
inet6-adr: fe80::200:e8ff:fe64:8e28/64 Rozsah:Linka
AKTIVOVÁNO VŠESMĚROVÉ_VYSÍLÁNÍ BĚŽÍ MULTICAST MTU:1500 Metrika:1
RX packets:73 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:84 dropped:0 overruns:0 carrier:156
kolizí:1326 délka odchozí fronty:1000
RX bytes:10477 (10.2 KiB) TX bytes:19934 (19.4 KiB)
Přerušení:12 Vstupně/Výstupní port:0xc800

lo Link encap:Místní smyčka
inet adr:127.0.0.1 Maska:255.0.0.0
inet6-adr: ::1/128 Rozsah:Počítač
AKTIVOVÁNO SMYČKA BĚŽÍ MTU:16436 Metrika:1
RX packets:2091 errors:0 dropped:0 overruns:0 frame:0
TX packets:2091 errors:0 dropped:0 overruns:0 carrier:0
kolizí:0 délka odchozí fronty:0
RX bytes:5885752 (5.6 MiB) TX bytes:5885752 (5.6 MiB)

[root@cz1khc ~]#
[root@cz1khc ~]# route -n
Směrovací tabulka v jádru pro IP
Adresát Brána Maska Přízn Metrik Odkaz Užt Rozhraní
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
0.0.0.0 192.168.100.254 0.0.0.0 UG 0 0 0 eth0
[root@cz1khc ~]#

Konfiguraci dnsmasq jste okopiroval ponekud bez rozmyslu, takze tam mate nastaveni pro moji sit, nikoli pro vasi, navic tam mate DVAKRAT specifikovany dhcp-range - to nevim co si z toho dnsmasq vybere, asi spis nic a ohlasi chybu. Doporucoval bych pouzit i definici rozhranni na kterem ma dnsmasq naslouchat (interface=).

V pocitaci mate tri sitove karty - z toho jedna zrejme 192.168.100.19 jde ven, k jedne ze zbylych je zrejme pripojovan notebook, ale ke ktere? Jaktoze mate obe ve stejne siti (192.168.0.x s maskou 255.255.255.0)? To by znamenalo, ze se obe karty pripojuji ke stejnemu segmentu ethernetu, coz je krapet zvlastni. Co z toho je drat a co bezdrat?

na zaklade tveho nastaveni sitovek, nejjednodussi zpusob jak to zprovoznit pres command-line je zadat tyto prikazy jako root:


echo 1 > /proc/sys/net/ipv4/ip_forward

iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

iptables -A FORWARD -i eth1 -j ACCEPT
iptables -A FORWARD -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT

pro vetsi kouzla je jiz potreba mit poneti o iptables…

!POZOR!: po restartu jiz nebude fungovat… pro uchovani je potreba toto nastaveni ulozit:

gedit /etc/sysctl.conf


# Controls IP packet forwarding
net.ipv4.ip_forward = 1 

a pro uchovani iptables nastaveni i po restartu je potreba tento prikaz:


iptables-save > /etc/sysconfig/iptables

Problem s nastavenim NAT pres iptables je ten, ze vetsina poskytovatelu prideluje adresu pres dhcp a toto bude spolehlive fugnovat pouze v sitich s pevnou konfiguraci, protoze pocitacum za NATem bude potreba rucne nastavit IP a DNS. Dnsmasq dela to, ze funguje na k poskytovateli pripojenem pocitaci, jako dynamicky dhcp pro dalsi pripojene klienty a posila jim udaje menene na zaklade toho co dostane od ISP.

jj, mas pravdu, vcera jsem si neuvedomil, ze potrebujes jeste preklad DNS…

to se da vyresit pro tento pripad takto:

iptables -t nat -A PREROUTING -d 192.168.0.1 -p udp --dport 53 -j DNAT --to-destination <ip_dns_serveru_od _poskytovatele>
iptables -t nat -A POSTROUTING -s <ip_dns_serveru_od _poskytovatele> -p udp --dport 53 -j SNAT --to-source 192.168.0.1

ja vim covexi, s dnsmasq si nemusim zjistovat ip dns serveru… :wink: je to proste jen dalsi zpusob…

par jednoduchych prikazu a ses na netu… ale jak uz jsem psal, pro vetsi kouzla je potreba mit poneti o iptables… pro nasdileni pripojeni kamaradovi, prip. druhemu PC doma, je tohle dostacujici…

Ja v zásade doma používam proxy. Asi preto že nemám inú možnosť, iba dial pripojenie. Teraz mám pppd edge.
Proxyserver squid je vo fedore, ale viac sa mi páči privoxy.