LinuxForum.Fans
Тема

DHCP-Сервер на Debian Squeeze и Windows 7

Автор: ivoffka84 2 сообщений 2478 просмотров
#238496

Доброго времени суток.
Имеется маршрутизатор на Debian Squeeze (2.6.32-5-686) с тремя интерфейсами.
Первый (eth0) - смотрит в сторону провайдера, второй (eth1) и беспроводная карточка в режиме Ad-hoc (wlan0) объеденены в мост (br0) и смотрят в локальную сеть.
На маршрутизаторе на инт. br0 поднят DHCP-сервер. При подключении компа с Win7 к eth0 все работает прекрасно, параметры сети принимаются с dhcp-сервера. При подключении к беспроводной карточке - эффекта ноль.
---/etc/init.d/interfaces

Показать

# The loopback network interface
auto lo
iface lo inet loopback

# to provider
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

auto eth1
allow-hotplug eth1
iface eth1 inet static
address 192.168.90.90
network 192.168.90.0
netmask 255.255.255.0
broadcasr 192.168.90.255

auto wlan0
iface wlan0 inet static
address 192.168.91.50
netmask 255.255.255.0
network 192.168.91.0
broadcast 192.168.91.255
wireless-essid forge
wireless-mode Ad-hoc
wireless-channel 3
wireless-rate 54M

auto br0
iface br0 inet static
bridge_ports eth1 wlan0
address 192.168.50.50
netmask 255.255.255.0
network 192.168.50.0
broadcast 192.168.50.255

Вывод ifconfig:

Показать
br0 Link encap:Ethernet HWaddr 00:c0:26:a7:f0:5e
inet addr:192.168.50.50 Bcast:192.168.50.255 Mask:255.255.255.0
inet6 addr: fe80::2c0:26ff:fea7:f05e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1488 errors:0 dropped:0 overruns:0 frame:0
TX packets:349 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:120768 (117.9 KiB) TX bytes:23874 (23.3 KiB)

eth0 Link encap:Ethernet HWaddr 00:22:b0:04:83:e3
inet addr:192.168.30.3 Bcast:192.168.30.255 Mask:255.255.255.0
inet6 addr: fe80::222:b0ff:fe04:83e3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13624 errors:0 dropped:0 overruns:0 frame:0
TX packets:8998 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13301303 (12.6 MiB) TX bytes:2513450 (2.3 MiB)
Interrupt:21 Base address:0xa000

eth1 Link encap:Ethernet HWaddr 00:c0:26:a7:f0:5e
UP 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)
Interrupt:22 Base address:0xa400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2172 (2.1 KiB) TX bytes:2172 (2.1 KiB)

wlan0 Link encap:Ethernet HWaddr b0:48:7a:e0:fe:df
inet6 addr: fe80::b248:7aff:fee0:fedf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1773 errors:0 dropped:0 overruns:0 frame:0
TX packets:429 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:173441 (169.3 KiB) TX bytes:39981 (39.0 KiB)

При попытке подключения, tshark показывает такую картинку:

Показать
tshark -i br0
Running as user "root" and group "root". This could be dangerous.
Capturing on br0
0.000000 0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xec765fca
0.000283 192.168.50.50 -> 255.255.255.255 DHCP DHCP Offer - Transaction ID 0xec765fca
0.124830 IntelCor_18:14:6c -> Broadcast ARP Who has 169.254.184.74? Tell 0.0.0.0
1.124863 IntelCor_18:14:6c -> Broadcast ARP Who has 169.254.184.74? Tell 0.0.0.0
2.124932 IntelCor_18:14:6c -> Broadcast ARP Who has 169.254.184.74? Tell 0.0.0.0
3.129434 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
3.208645 169.254.184.74 -> 169.254.255.255 NBNS Registration NB NOTE<20>
3.220921 169.254.184.74 -> 224.0.0.22 IGMP V3 Membership Report / Join group 224.0.0.252 for any sources
3.226567 169.254.184.74 -> 169.254.255.255 NBNS Registration NB NOTE<00>
3.228122 169.254.184.74 -> 169.254.255.255 NBNS Registration NB WORKGROUP<00>
3.266552 169.254.184.74 -> 224.0.0.22 IGMP V3 Membership Report / Join group 239.255.255.250 for any sources
3.625208 169.254.184.74 -> 224.0.0.22 IGMP V3 Membership Report / Join group 224.0.0.252 for any sources / Join group 239.255.255.250 for any sources
3.878642 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
3.957658 169.254.184.74 -> 169.254.255.255 NBNS Registration NB NOTE<20>
3.975704 169.254.184.74 -> 169.254.255.255 NBNS Registration NB NOTE<00>
3.977599 169.254.184.74 -> 169.254.255.255 NBNS Registration NB WORKGROUP<00>
4.628684 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
4.707834 169.254.184.74 -> 169.254.255.255 NBNS Registration NB NOTE<20>
4.726129 169.254.184.74 -> 169.254.255.255 NBNS Registration NB NOTE<00>
4.728008 169.254.184.74 -> 169.254.255.255 NBNS Registration NB WORKGROUP<00>
5.001087 0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xec765fca
5.001383 192.168.50.50 -> 255.255.255.255 DHCP DHCP Offer - Transaction ID 0xec765fca
5.380453 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
5.457797 169.254.184.74 -> 169.254.255.255 NBNS Registration NB NOTE<20>
5.475863 169.254.184.74 -> 169.254.255.255 NBNS Registration NB NOTE<00>
5.477160 169.254.184.74 -> 169.254.255.255 NBNS Registration NB WORKGROUP<00>
6.129764 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
6.880790 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
7.632205 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
8.381787 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
9.131919 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
9.883554 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
10.633014 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
11.383063 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
12.139380 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
12.143147 0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xec765fca
12.143413 192.168.50.50 -> 255.255.255.255 DHCP DHCP Offer - Transaction ID 0xec765fca
12.889130 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
13.639167 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
14.390801 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
15.140244 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
15.890226 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
16.641910 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
17.391395 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
18.141491 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
18.893172 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
19.642515 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
20.394397 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
21.143874 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
21.893604 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
22.643671 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
23.394991 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
24.144731 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
24.894784 169.254.184.74 -> 169.254.255.255 NBNS Name query NB ISATAP<00>
27.897164 0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xec765fca
27.897460 192.168.50.50 -> 255.255.255.255 DHCP DHCP Offer - Transaction ID 0xec765fca

Т.е. запросы на получение айпишника и сетевых параметров приходят, но тупо виндой игнорятся.

В syslog'е аналогичная информация:

Показать
Mar 17 21:03:17 forge kernel: [ 5047.316508] device br0 left promiscuous mode
Mar 17 21:03:21 forge dhcpd: DHCPDISCOVER from <MAC-адрес ноута> (Note) via br0
Mar 17 21:03:21 forge dhcpd: DHCPOFFER on 192.168.50.8 to <MAC-адрес ноута> (Note) via br0
Mar 17 21:03:38 forge dhcpd: DHCPDISCOVER from <MAC-адрес ноута> (Note) via br0
Mar 17 21:03:38 forge dhcpd: DHCPOFFER on 192.168.50.8 to <MAC-адрес ноута> (Note) via br0

Кто нибудь сталкивался?

UPD: Если вручную выставить айпишник на ноуте, вывод пингов на 192.168.50.50 показывает, что заданный узел недоступен. Хотя tshark также показывает наличие сетевой активности.

#238497

Сообщения без тегов подобное этому буду безжалостно сносить, надоело. :[
Исправь.

Войдите или зарегистрируйтесь, чтобы ответить.