上不了网!!!!!!想操刀杀人!!!!!!!!

系统安装、升级讨论
版面规则
我们都知道新人的确很菜,也喜欢抱怨,并且带有浓厚的Windows习惯,但既然在这里询问,我们就应该有责任帮助他们解决问题,而不是直接泼冷水、简单的否定或发表对解决问题没有任何帮助的帖子。乐于分享,以人为本,这正是Ubuntu的精神所在。
回复
luckysir0
帖子: 50
注册时间: 2008-05-25 19:19

上不了网!!!!!!想操刀杀人!!!!!!!!

#1

帖子 luckysir0 » 2008-05-29 22:28

港湾网络,winxp下用的是hammersupplicant,静态ip,在ubuntu下用什么那个客户端可以?????????哀求高手指点指点啊,快疯了。。
头像
adagio
论坛版主
帖子: 22110
注册时间: 2008-02-17 23:47
来自: 美丽富饶的那啥星球

#2

帖子 adagio » 2008-05-29 22:38

:shock:
明天就换大三八!
——8核CPU、8G内存、8T硬盘……
8卡交火,80寸大屏放8个……
IPv8的光纤要8条……

---------------------------------------------------------------------------------
[图片版]新手当自强(续)FAQ
[新手进阶]挂载、fstab、调整linux分区
[图片版]E17桌面环境配置手把手
rucstudent
帖子: 633
注册时间: 2007-05-09 16:52

#3

帖子 rucstudent » 2008-05-29 23:49

我们学校是港湾+DHCP
你可以在网络链接上指定你的静态IP──ubuntu下和XP下没有多少区别,此处省略。
下载我附件的三个包:
libssl0.9.7_0.9.7e-3ubuntu0.6_i386.deb
openssl_0.9.7g-1ubuntu1.5_i386.deb
xsupplicant_1.0.1-1_i386.deb
分别按照这个顺序安装,其中openssl好像已经安装了,而且版本更高
然后切换控制台,进行配置:
sudo gedit /etc/xsupplicant/xsupplicant.conf
下面是配置文件,其中有
---------------------------------------------------------------------------------
# This is an example configuration file for xsupplicant versions after 0.8b.



### GLOBAL SECTION



# network_list: defines all of the networks in this file which

# should be kept in memory and used.Comma delimited list or "all"

# for keeping all defined configurations in memory. For efficiency,

# keep only the networks you might roam to in memory.

# To avoid errors, make sure your default network is always

# in the network_list. In general, you will want to leave this set to

# "all".



network_list = all

#network_list = default, test1, test2



# default_netname: some users may actually have a network named "default".

# since "default" is a keyword in the network section below, you can

# change which is to be used as the replacement for this keyword



default_netname = default

#default_netname = my_defaults



# In the startup_command, first_auth_command, and reauth_command you can

# use "%i" to have xsupplicant fill in the interface that is being used.

# This allows a single network profile to work across different wireless

# cards.



# startup_command: the command to run when xsupplicant is first started.

# this command can do things such as configure the card to associate with

# the network properly.

startup_command = <BEGIN_COMMAND>echo "some command"<END_COMMAND>



# first_auth_command: the command to run when xsupplicant authenticates to

# a wireless network for the first time. This will usually be used to

# start a DHCP client process.

first_auth_command = <BEGIN_COMMAND>dhclient %i<END_COMMAND>



# reauth_command: the command to run when xsupplicant reauthenticates to a

# wireless network. This may be used to have the dhcp client rerequest

# it's IP address.

reauth_command = <BEGIN_COMMAND>echo "authenticated user %i"<END_COMMAND>



# When running in daemon, or non-foreground mode, you may want to have the

# output of the program. So, define a log file here. Each time XSupplicant

# is started, this file will be replaced. So, there is no need to roll the

# log file.

logfile = /var/log/xsupplicant.log



# The auth_period, held_period, and max_starts modify the timers in the state

# machine. (Please reference the 802.1x spec for info on how they are used.)

# For most people, there is no reason to define these values, as the defaults

# should work.



#auth_period = 30



#held_period = 30



#max_starts = 3



# Defining an interface in "allow_interfaces" will bypass the rules that

# xsupplicant uses to determine if an interface is valid. For most people

# this setting shouldn't be needed. It is useful for having xsupplicant

# attempt to authenticate on interfaces that don't appear to be true

# physical interfaces. (i.e. Virtual interfaces such as eth0:1)



#allow_interfaces = eth0, wlan0



# Defining an interface in "deny_interfaces" will prevent xsupplicant from

# attempting to authenticate on a given interface. This is useful if you

# know that you will never do 802.1x on a specific interface. However,

# allows will take priority over denies, so defining the same interface in

# the allow_interfaces, and deny_interfaces will result in the interface

# being used.



#deny_interfaces = eth1



### NETWORK SECTION







# The general format of the network section is a network name followed

# by a group of variables.



# Network names may contain the following characters: a-z, A-Z, 0-9, '-',

# '_', '\', '/'

# Those interested in having an SSID with ANY character in it can use

# the ssid tag within the network clause. Otherwise, your ssid will

# be the name of the network.



## The default network is not a network itself. These values are

## the default used for any network parameters not overridden

## in another section. If it's not in your network configuration

## and not in your default, it won't work!!



default

{

# type: the type of this network. wired or wireless, if this value is not

# set, xsupplicant will attempt to determine if the interface is wired or

# wireless. In general, you should only need to define this when

# xsupplicant incorrectly identifies your network interface.

#type = wireless



# wireless_control: If this profile is forced to wired, this will not do

# anything. However, if the interface is forced, or detected to be wireless

# XSupplicant will take control of re/setting WEP keys when the machine

# first starts, and when it jumps to a different AP. In general, you won't

# need to define, or set this value.

# wireless_control = yes



# allow_types: describes which EAP types this network will allow. The

# first type listed will be requested if the server tries to use something

# not in this list.

# allow_types = eap_tls, eap_md5, eap_gtc, eap-otp

allow_types = all



# identity: what to respond with when presented with an EAP Id Request

# Typically, this is the username for this network. Since this can

# be an arbitrary string, enclose within <BEGIN_ID> and <END_ID>

identity = <BEGIN_ID>31278888<END_ID>



# Force xsupplicant to send it's packets to this destination MAC address.

# In most cases, this isn't needed, and shouldn't be defined.

#dest_mac = 00:aA:bB:cC:dD:eE



## method-specific parameters are kept in the method

eap_tls {

user_cert = /path/to/certificate

user_key = /path/to/private/key

user_key_pass = <BEGIN_PASS>password for key<END_PASS>

root_cert = /path/to/root/cert

root_dir = /path/to/valid/root/certs

#crl_dir = /path/to/dir/with/crl

chunk_size = 1398

random_file = /path/to/random/source



# To enable TLS session resumption, you need to set the following

# value to "yes". By default, session resumption is disabled.

#session_resume = yes

}



eap-md5 {

username = <BEGIN_UNAME>31278888<END_UNAME>

password = <BEGIN_PASS>123456<END_PASS>

}



eap-ttls {

#user_cert = /path/to/certificate

#as in tls, define either a root certificate or a directory

# containing root certificates

root_cert = /path/to/root/certificate

#root_dir = /path/to/root/certificate/dir

#crl_dir = /path/to/dir/with/crl

#user_key = /path/to/private/key

#user_key_pass = <BEGIN_PASS>password for key<END_PASS>

chunk_size = 1398

random_file = /path/to/random/source

#cncheck = myradius.radius.com # Verify the server certificate

# has this value in it's CN field.

#cnexact = yes # Should it be an exact match?

#session_resume = yes

# phase2_type defines which phase2 to actually DO. You

# MUST define one of these.

phase2_type = pap

## These are definitions for the different methods you might

## do at phase2. only the one specified above will be used

## but it is valid to leave more than one here for convenience

## and easy switching.

pap {

username = <BEGIN_UNAME>papuser<END_UNAME>

password = <BEGIN_PASS>pappasswd<END_PASS>

}

chap {

username = <BEGIN_UNAME>chapuser<END_UNAME>

password = <BEGIN_PASS>chappasswd<END_PASS>

}

mschap {

username = <BEGIN_UNAME>mschapuser<END_UNAME>

password = <BEGIN_PASS>mschappasswd<END_PASS>

}

mschapv2 {

username = <BEGIN_UNAME>mschapv2user<END_UNAME>

password = <BEGIN_PASS>mschapv2passwd<END_PASS>

}

}



eap-leap {

username = <BEGIN_UNAME>leapuser<END_UNAME>

password = <BEGIN_PASS>leapuserpass!<END_PASS>

}



eap-mschapv2 {

username = <BEGIN_UNAME>eapmschapv2user<END_UNAME>

password = <BEGIN_PASS>eapmschapv2userpass!<END_PASS>

}



eap-peap {

user_cert = /path/to/certificate

# As in tls, define either a root certificate or a directory

# containing root certificates.

#root_cert = /path/to/root/certificate

root_dir = /path/to/root/certificate/dir

crl_dir = /path/to/dir/with/crl

user_key = /path/to/private/key

user_key_pass = <BEGIN_PASS>password for key<END_PASS>

chunk_size = 1398

random_file = /path/to/random/source

cncheck = myradius.radius.com # Verify the server certificate

# has this value in it's CN field.

cnexact = yes # Should it be an exact match?

session_resume = yes



#Currently 'all' is just mschapv2

#If no allow_types is defined, all is assumed

allow_types = all # where all = MSCHAPv2, MD5, OTP, GTC, SIM

#allow_types = eap_mschapv2



# right now you can do any of these methods in PEAP:

eap-mschapv2 {

username = <BEGIN_UNAME>phase2mschapv2<END_UNAME>

password = <BEGIN_PASS>phase2mschapv2pass<END_PASS>

}

}



eap-sim {



# In order to obtain the IMSI from the SIM card, the password

# *MUST* be defined here! Otherwise, you need to specify your

# IMSI as the username below.

username = <BEGIN_UNAME>simuser<END_UNAME>

password = <BEGIN_PASS>simuserpass!<END_PASS>

auto_realm = yes

}

}



# In this network definition, "test1" is the friendly name. It can match

# the essid of the network, which means you won't have to set the "ssid"

# variable. However, if it doesn't match, you need to set the "ssid"

# variable in order for the network to be detected correctly.

test1

{

type = wired

# ssid: you should not define this unless you have characters

# other than those specified above in the ssid of your network

ssid = <BEGIN_SSID>mvemjsnp<END_SSID>



allow_types = all

identity = <BEGIN_ID>Check this out- any char!#$<END_ID>



}





test2

{

# ssid: you should not define this unless you have characters

# other than those specified above in the ssid of your network

ssid = <BEGIN_SSID>up to 32 character ASCII string<END_SSID>

identity = <BEGIN_ID>testuser@testnet.com<END_ID>



allow_types = eap-tls

type = wireless

}



test3

{

# ssid: you should not define this unless you have characters

# other than those specified above in the ssid of your network

ssid = <BEGIN_SSID>foo-network!<END_SSID>



type = wired



identity= <BEGIN_ID>this will work too<END_ID>

}



--------------------------------------------------------------------------------------------------
里面有2个 31278888,一个123456,那是学号和密码,修改成你的,然后保存即可上网,其他的不要改动。重启电脑后,ubuntu不需要和FC一样拨号,他自己会自动连接,不要输入xsupplicant -i eth0之类的命令,ok,上网搞定。

----------------------------------------------------------------------------------------------------
如果你要待机或者挂起,唤醒以后xsupplicant是不能上网的,这时候,执行:
sudo killall dhclient && sudo killall xsupplicant && sudo xsupplicant -i eth0
你可以在新建一个快捷键,命令就是上面的
这样一定可以上网!!!!

PS:
1. xsupplicant必须要保证这个版本,你可以在安装后新利得里面搜索xsupplicant,并且选择强制选定版本,以后升级就不会升级xsupplicant了
2.因为我的是DHCP自动获取IP,你的是指定静态IP,光在网络里面选择指定IP可能不够,需要在上面那一大托配置里面找到,把dhcp改成静态IP的选项,你可以找一下~~
rucstudent
帖子: 633
注册时间: 2007-05-09 16:52

#4

帖子 rucstudent » 2008-05-29 23:53

受不了了,三更半夜的居然速度还这么慢!!!!!!!!
你留个邮箱我吧三个包给你发了──如果你没有找全的话

喉一句:

论坛速度太tmd慢了@!@#!@#!@@!
头像
adagio
论坛版主
帖子: 22110
注册时间: 2008-02-17 23:47
来自: 美丽富饶的那啥星球

#5

帖子 adagio » 2008-05-29 23:59

:shock:
明天就换大三八!
——8核CPU、8G内存、8T硬盘……
8卡交火,80寸大屏放8个……
IPv8的光纤要8条……

---------------------------------------------------------------------------------
[图片版]新手当自强(续)FAQ
[新手进阶]挂载、fstab、调整linux分区
[图片版]E17桌面环境配置手把手
头像
芬言芬语
帖子: 409
注册时间: 2008-02-27 14:14
来自: Hangzhou

#6

帖子 芬言芬语 » 2008-05-30 7:26

希望快解决吧,不然有人要遭殃了哈
http://wiki.ubuntu.org.cn/Navigation
还有太多要学习了!
Linux的世界,我永远是只菜鸟!
头像
hcym
帖子: 15634
注册时间: 2007-05-06 2:46

#7

帖子 hcym » 2008-05-30 8:22

:shock:
头像
zhaoyannian
帖子: 226
注册时间: 2008-03-07 12:32

#8

帖子 zhaoyannian » 2008-05-30 10:51

想杀人就杀吧!记得多杀贪官污吏,别杀普通百姓。
luckysir0
帖子: 50
注册时间: 2008-05-25 19:19

#9

帖子 luckysir0 » 2008-05-30 12:49

呵呵,谢谢大家关心,
zepto
帖子: 3
注册时间: 2007-08-21 15:13

#10

帖子 zepto » 2008-05-30 13:04

lz的网卡是不是Realtek 8168/8111
如果是请参考此贴
viewtopic.php?t=119236
peterparker
帖子: 1
注册时间: 2009-05-01 13:58

Re: 上不了网!!!!!!想操刀杀人!!!!!!!!

#11

帖子 peterparker » 2009-05-01 14:03

试过并不可以连网。
头像
jioyo源
帖子: 3476
注册时间: 2008-10-08 13:48

Re: 上不了网!!!!!!想操刀杀人!!!!!!!!

#12

帖子 jioyo源 » 2009-05-01 14:07

:em20
--------------------------------------
论坛精华贴全集:http://forum.ubuntu.org.cn/viewtopic.php?f=48&t=199845
book:http://forum.ubuntu.org.cn/viewtopic.php?f=21&t=198286
回复