Работа с Yota под Ubuntu 8.04

Работа с Yota под Ubuntu 8.04

Качаем и ставим зависимости:

http://packages.ubuntu.com/jaunty/i386/libusb-1.0-0-dev/download
http://packages.ubuntu.com/jaunty/i386/libusb-1.0-0/download

Качаем драйвер:

cd ~/
wget http://madwimax.googlecode.com/files/madwimax-0.0.2.tar.gz

Распаковываем:

tar -xvzf madwimax-0.0.2.tar.gz
madwimax-0.0.2/
madwimax-0.0.2/src/
madwimax-0.0.2/src/protocol.c
madwimax-0.0.2/src/protocol.h
madwimax-0.0.2/src/tap_dev.c
madwimax-0.0.2/src/tap_dev.h
madwimax-0.0.2/src/wimax.c
madwimax-0.0.2/src/wimax.h
madwimax-0.0.2/NEWS
madwimax-0.0.2/TODO
madwimax-0.0.2/Makefile
madwimax-0.0.2/README
madwimax-0.0.2/scripts/
madwimax-0.0.2/scripts/udev/
madwimax-0.0.2/scripts/udev/z60_madwimax.rules
madwimax-0.0.2/INSTALL
madwimax-0.0.2/COPYING

Собираем:

cd madwimax-0.0.2
ls
COPYING INSTALL Makefile NEWS README scripts src TODO

make
gcc -c -g -Wall src/protocol.c -o src/protocol.o
gcc -c -g -Wall src/tap_dev.c -o src/tap_dev.o
src/tap_dev.c:213: предупреждение: ‘tap_test_flag’ defined but not used
gcc -c -g -Wall src/wimax.c -o src/wimax.o
gcc -o wimax src/protocol.o src/tap_dev.o src/wimax.o -lusb-1.0

Запускаем:

sudo ./wimax
[sudo] password for ХХХХХ:
Could not find/open device

Подключаем железку и запускаем ещё раз:)

sudo ./wimax
claimed interface
Continuous async read start...
Chip info: cmc730_v2.1
Firmware info: u200_rev1-2.2.50-BK15
MAC: 00:21:d2:1e:62:b1
Allocated tap interface: tap0
Network found.
RSSI: -60 CINR: 18.750000 TX Power: 57344 Frequency: 2525000
BSID: 00:00:15:01:22:c6
State: NEGO Number: 2 Response: 1
RSSI: -59 CINR: 21.000000 TX Power: 65523 Frequency: 2525000
BSID: 00:00:15:01:22:c6
State: NORMAL Number: 3 Response: 2
RSSI: -59 CINR: 21.500000 TX Power: 65524 Frequency: 2525000
BSID: 00:00:15:01:22:c6
State: NORMAL Number: 3 Response: 2
RSSI: -59 CINR: 21.750000 TX Power: 65524 Frequency: 2525000
BSID: 00:00:15:01:22:c6

Теперь в другом терминале запускаем DHCP-Client:

ifconfig

lo Link encap:Локальная петля (Loopback)
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Диапазон:Узел
ВВЕРХ LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1276 errors:0 dropped:0 overruns:0 frame:0
TX packets:1276 errors:0 dropped:0 overruns:0 carrier:0
коллизии:0 txqueuelen:0
RX bytes:65836 (64.2 KB) TX bytes:65836 (64.2 KB)

tap0 Link encap:Ethernet HWaddr 00:21:d2:1e:62:b1
inet6 addr: fe80::221:d2ff:fe1e:62b1/64 Диапазон:Ссылка
ВВЕРХ BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
коллизии:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)

sudo dhclient tap0
[sudo] password for XXXX:
There is already a pid file /var/run/dhclient.pid with pid 11013
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/tap0/00:21:d2:1e:62:b1
Sending on LPF/tap0/00:21:d2:1e:62:b1
Sending on Socket/fallback
DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 5
DHCPOFFER of 94.25.137.241 from 94.25.136.1
DHCPREQUEST of 94.25.137.241 on tap0 to 255.255.255.255 port 67
DHCPACK of 94.25.137.241 from 94.25.136.1
bound to 94.25.137.241 -- renewal in 5071 seconds.

route -n
Таблица маршутизации ядра протокола IP
Destination Gateway Genmask Flags Metric Ref Use Iface
94.25.136.0 0.0.0.0 255.255.254.0 U 0 0 0 tap0
0.0.0.0 94.25.136.1 0.0.0.0 UG 0 0 0 tap0

ping ya.ru
PING ya.ru (213.180.204.8) 56(84) bytes of data.
64 bytes from ya.ru (213.180.204.8): icmp_seq=1 ttl=56 time=124 ms
64 bytes from ya.ru (213.180.204.8): icmp_seq=2 ttl=56 time=575 ms
64 bytes from ya.ru (213.180.204.8): icmp_seq=3 ttl=56 time=100 ms
64 bytes from ya.ru (213.180.204.8): icmp_seq=4 ttl=56 time=105 ms

--- ya.ru ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms


Наслаждаемся ваймаксом:))))))

Огромный респект автору драйвера:
http://community.livejournal.com/yota_ru/126960.html

ПЫ.СЫ.: Выход по Ctrl-C , в том терминале где запущен драйвер.

Комментариев нет:

Отправить комментарий