[经验]Globespan USB ADSL 成功上网记
成功安装了基于Globespan GS7070-174 008D A2芯片的USB ADSL Modem（长虹CH200）的驱动程序。方法是这样的：如果要驱动这一类型的usb adsl modem
首先要下载两个驱动包 ：
1.synch bin文件包,这个包包含了所有bin文件,bin文件的作用在于让你的modem和电信局端同步,不同的设备可能使用不同的bin,我的modem用第01、15、49等.我大部份都试过只要小于62K的都可用,所以可不用下载直接使用第二个包里面带的 synch01.bin
文件名:eciadsl_synch_bin.tar.gz
2.下载驱动程序.
驱动程序要下载cvs版本,这样才可一支持他的列表中没有的设备
文件名:eciadsl_usermode_cvs.tar.gz
下载页面：
http://eciadsl.flashtux.org/download.php?lang=en
安装过程:
1.在驱动程序的解压文件夹中运行:
./configure
make
make install
2，设置上网参数
make cfg 3,设置参数命令
#eciadsl-config-tk
设置时vid1/pid1和vid2/vid2几个参数需要以下命令：
#eciadsl-probe-device
选择你的USB ADSL设置之后，出现 vid1/pid1和vid2/vid2 数值
填到相应的地方。
下面是我在WINDOWS下面看到的ADSL信息给大家做参照：
RFC 1483 IPOATM衔接LLC的封装
驱动程序版本号：1.11.0007Q-A (LanUsb)
固件版本号Q43
设置选择的如图：LLC-SNAP-RFC1483-BRID.......
DHCP要选择上(电信没有给我固定IP和网关)
注意：
确定vpi/vci的参数正确，否则eciadsl-start、eciadsl-doctor是找不到你的猫的
4，测试一下。
#eciadsl-doctor
看到PPP0什么的，最后不动了。哪么就测试通过了!
Ctrl+C 退出程序。
5，运行#eciadsl-start 结果如下成功!
-----------------------------------------------------
# eciadsl-start
Setting up USB support...
Preliminary USB device filesystem is OK
Uploading firmware...
GlobeSpan GS7070 USB ADSL WAN Modem compatible modem found (in 2001ms)
eciadsl-firmware: success
firmware loaded successfully
Synchronization...
OK eciadsl-synch: success
Synchronization successful
Connecting to provider...
Connection successful
Setting up route table...
Waiting for tap0...
# ifconfig 查看一下是不是多一个东西
lo Link encap:Local Loopback
inet addr:127.0.0.1Mask:255.0.0.0
UP LOOPBACK RUNNINGMTU:16436Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1400 (1.3 Kb)TX bytes:1400 (1.3 Kb)
tap0 Link encap:EthernetHWaddr 00:FF:6A:55:28:13
UP BROADCAST RUNNING MULTICASTMTU:1500Metric: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)
----------------------------------------------------
注意：如果运行之后再运行eciadsl-start出现错误，哪么去看一下进程。杀死eciadsl-pppoeci等与eciadsl有关的进程。
6.使用rp-pppoe软件.
(自己参照的REDHAT9上ADSL最终解决方案)
运行adsl-setup.按照提示输入认证用的用户名密码,dns等.
还要注意,它还会问你使用哪个网络界面拨号,一定要选择刚刚多出来的那个.(我的系统里是tap0 你的系统可能会不同. 如 tun0 )
7，运行adsl-start
# adsl-start
# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1Mask:255.0.0.0
UP LOOPBACK RUNNINGMTU:16436Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1700 (1.6 Kb)TX bytes:1700 (1.6 Kb)
ppp0 Link encap:Point-to-Point Protocol
inet addr:222.211.4.141P-t-P:222.211.0.1Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICASTMTU:1492Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:54 (54.0 b)TX bytes:54 (54.0 b)
tap0 Link encap:EthernetHWaddr 00:FF:A0:F8:74:45
UP BROADCAST RUNNING MULTICASTMTU:1500Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:532 (532.0 b)TX bytes:365 (365.0 b) ==============================================================================
E C I A D S L
==============================================================================
Since usermode v0.10, scripts have been renamed.
You'll find below table with old & new names:
Old name: New name:
-------- --------
eciconf.sh->eciadsl-config-tk
eciconftxt.sh->eciadsl-config-text
startmodem->eciadsl-start
(-)->eciadsl-stop
eci-doctor.sh->eciadsl-doctor
eci-load1->eciadsl-firmware
eci-load2->eciadsl-synch
pppoeci->eciadsl-pppoeci
probe_device.sh->eciadsl-probe-device
probe_synch.sh->eciadsl-probe-synch
makeconfig->eciadsl-makeconfig
remove_dabusb->eciadsl-remove-dabusb
check-hdlc-bug->eciadsl-check-hdlc-bug
check-hdlc->eciadsl-check-hdlc
eci_data.pl->eciadsl-data.pl
eci_uc.pl->eciadsl-uc.pl
eci_vendor_device.pl->eciadsl-vendor-device.pl
eci-eeprom->eciadsl-eeprom
For compatibility with previous versions, some symbolic links are now created
at installation process (make install) :
startmodem --> eciadsl-startmodem
eci-load1 --> eciadsl-firmware
eci-load2 --> eciadsl-synch
pppoeci --> eciadsl-pppoeci
------------------------------------------------------
2004-04-23, FlashCode <[email protected]>
http://eciadsl.flashtux.org
# modprobe-r dabusb && rm-f$(modprobe-l | grep dabusb) && depmod-a
# /usr/bin/eciadsl-start| T log.txt 最后一个问题，怎么让程序自动运行
eciadsl-start
我不明白官方站的解答？
--------------------用官方网站的解答--东方快车翻译的----
在靴子时间发射eciadsl开始是可能的吗？
答案:是它是,例如使用init.d,或/etc/ppp/ppp_on_boot为Debian
用户。
使它可能使用init.d:
先决条件:
-安装并且配置的ECIADSL司机
来源包装的ECIADSL,可得到在:
http://eciadsl.flashtux.org/download.php?lang=en
复制rc.adsl文件到/etc/init.d:
>cp rc.adsl/etc/init.d
>chmod + x/etc/init.d/rc.adsl
(rc.adsl文件装有版本>= 0.7(或CVS))
为Debian，公平的类型作为根:update-rc.d rc.adsl默认15
为另外的分发，看在下面:
在/etc/rc.d,每个rc *.d目录相当于一init的runlevel。
为
实例,runlevel 5是通向绘画的登录的一个(这是
在大部分的Linux系统上的缺省值,但是有时它是3),这样/etc/rc.d/rc5.d
属于那水平。
你将发现更多的有关init水平的消息:
>男人inittab
或看你的/etc/inittab文件。
知道init水平哪个缺省值是竭力想达到的靴子，发现行象一样
追求在/etc/inittab文件:
id:5:initdefault:
这里,缺省值水平是
5.为军事行动在下面,在靴子比如说我们使用init拉平5。
你不得不知道当你的系统进入init水平时，它叫所有
K*从最后水平的文件,然后调用所有的S*文件从新
水平。
所有的这些K*并且S*文件在/etc/rc.d/rc< init水平>.d那他们
属于。
事实上,这些S*并且K*文件是symlink，并且到脚本的意义定位了
(多半时间)在/etc/init.d。
Eash S*文件象这一样:Sxxyyyyy,在xx是一个2数字数字的地方，并且
yyyyy服务名字(名字是人的友好,但是你能将它放作为
你想要的任何东西)。
所有的Sxxyyyyy文件被叫跟随xx数字(逐渐地),那时
由服务名字(yyyyy,字母增加的命令)。
例如:
>ls/etc/rc.d/rc5.d
出现
S01foo
S15bar
S99dummy
K10makemyday
K80whatthefuck
(当心,仅仅它是一个例子)。
这样什么时候init拉平5在进入,它将叫S01foo,S15bar然后S99dummy。
什么时候5留的init水平,为K这是同样的的*文件。
但是追求
系统,他们被请同样的的顺序(由xx逐渐地),或在一
颠倒顺序(由xx渐减地)。
你现在知道所有的这材料怎么工作,你能做成相关的链接
/etc/init.d在/etc/rc.d/rc5.d:
>ln-s/etc/init.d/rc.adsl/etc/rc.d/rc5.d/S90adsl
>ln-s/etc/init.d/rc.adsl/etc/rc.d/rc5.d/K90adsl
在你创造这些链接以前，保证S90是相关的,这件工具
那S90*将毕竟被称为另外的网络服务。
当然,查证K90也是相关的。
根据一些系统
(相反杀死顺序)这将是好一些的使用K00，但是简单地想到
杀死连接的最好的顺序。
一旦所有的symlinks被做，由重新启动你的系统你能测试它。
没有重新启动你能也测试它:关上你的X11会议,开一
在控制台模式的根会议,那时:
>init 3
那时
>init 5
理解了它做的，吗？
它意味着离开到init的水平5拉平3的init,那时
回到init水平
5.相关的S*并且K*链接将被叫！ 用adsl-start可以上网的话直接在adsl-setup里设置让它开机自动不行吗？ 复制rc.adsl文件到/etc/init.d:
>cp rc.adsl/etc/init.d
>chmod + x/etc/init.d/rc.adsl
然后在/etc/rc.d/rc3.d和/etc/rc.d/rc5.d中分别做个rc.adsl的链接，链接名称为Sxxadsl,其中xx为数字，最好在所有的网络服务之前。 别用东方快车，贴英文的。 我不是很清楚这方面的技术
是不是精华？ Question 5.0 :Is it possible to launch eciadsl-start at boot time?
Answer :Yes it is, using init.d for instance, or /etc/ppp/ppp_on_boot for Debian
users.
Making it possible using init.d:
Pre-requisites:
- ECIADSL driver installed and configured
- the ECIADSL sources package, available at:
http://eciadsl.flashtux.org/download.php?lang=en
Copy the rc.adsl file to /etc/init.d:
> cp rc.adsl /etc/init.d
> chmod +x /etc/init.d/rc.adsl
(the rc.adsl file is provided with version >= 0.7 (or CVS))
For Debian, just type as root: update-rc.d rc.adsl defaults 15
For other distributions, see below :
In /etc/rc.d, each rc*.d directory corresponds to an init's runlevel. For
instance, runlevel 5 is the one that leads to a graphical login (this is
default on most Linux systems, but sometimes it's 3), so /etc/rc.d/rc5.d
belongs to that level.
You will find more information about init levels:
> man inittab
or look at your /etc/inittab file.
To know which default init level is reached at boot, find a line like the
following in /etc/inittab file:
id:5:initdefault:
Here, default level is 5.
For the operations below, let's say we use init level 5 at boot.
You have to know that when your system enters an init level, it calls all
the K* files from the last level, then call all the S* files from the new
level. All these K* and S* files are in /etc/rc.d/rc<init level>.d they
belong to.
In fact, these S* and K* files are symlink, and point to scripts located
(most of the times) in /etc/init.d.
Eash S* file is like this: Sxxyyyyy, where xx is a 2-digit number, and
yyyyy a service name (the name is human friendly, but you can set it as
anything you want).
All Sxxyyyyy files are called following the xx number (increasingly), then
by the service name (yyyyy, alphabetical increasing order).
For instance:
> ls /etc/rc.d/rc5.d
shows
S01foo
S15bar
S99dummy
K10makemyday
K80whatthefuck
(take care, it's only an example).
So when init level 5 in entered, it will call S01foo, S15bar then S99dummy.
When init level 5 is left, this is the same for K* files. But following the
system, they are called in the same order (by xx increasingly), or in a
reverse order (by xx decreasingly).
Now you know how all this stuff works, you can make the relevant links to
/etc/init.d in /etc/rc.d/rc5.d:
> ln -s /etc/init.d/rc.adsl /etc/rc.d/rc5.d/S90adsl
> ln -s /etc/init.d/rc.adsl /etc/rc.d/rc5.d/K90adsl
Before you create these links, ensure that the S90 is relevant, this means
that S90* will be called after all other network services.
Of course, verify that K90 is relevant too. According to some systems
(reverse kill order) this would be better to use K00, but simply think of
the best order to kill the connection.
Once all the symlinks are done, you can test it by rebooting your system.
You can also test it without rebooting: close your X11 session, open a
root session in console mode, then:
> init 3
then
> init 5
Understood what it does? It means leaving init level 5 to init level 3, then
coming back to init level 5. The relevant S* and K* links will be called!
页:
[1]