Da allora ho solo aumentato la ram del mio portatile da 512mb a 2gb ed installato gnome..
Ora sono 2 giorni che la rete va, non va, si blocca.. un disastro. Gli stessi errori li ho anche se mi collego wireless senza crittografia..
i miei file di configurazione sono:
wpa_supplicant.conf
Codice: Seleziona tutto
# This line enables the use of wpa_cli which is used by rc.wireless
# if possible (to check for successful association)
ctrl_interface=/var/run/wpa_supplicant
# By default, only root (group 0) may use wpa_cli
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA protected network, supply your own ESSID and WPAPSK here:
network={
scan_ssid=0
ssid="osiris"
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk=ce1e470006264398bccabcc9a1c0363d1ff3b1eddf379e1f75da3cf5719aba68
}
# Plaintext connection (no WPA, no IEEE 802.1X),
# nice for hotel/airport types of WiFi network.
network={
key_mgmt=NONE
priority=0
}
rc.inet1.conf
Codice: Seleziona tutto
/etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.
# =============================================================================
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
GATEWAY=""
# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"
## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
WLAN_ESSID[4]=osiris
#WLAN_MODE[4]=Managed
##WLAN_RATE[4]="54M auto"
##WLAN_CHANNEL[4]="auto"
##WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPADRIVER[4]="wext"
#WLAN_WPADRIVER[4]="ndiswrapper"
## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes" # If you don't want the DHCP server to change
# your default gateway
#DHCP_IPADDR[4]="" # Request a specific IP address from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by prepending
# 'WLAN_' to the parameter's name. Useful for
# those with multiple wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=thekey"
# Some drivers require a private ioctl to be
# set through the iwpriv command. If more than
# one is required, you can place them in the
# IWPRIV parameter (separated with the pipe (|)
# character, see the example).
Codice: Seleziona tutto
root@darkstar:~# /etc/rc.d/rc.inet1 restart
/sbin/dhcpcd: not running
Polling for DHCP server on interface eth0:
Broadcasting DHCP_DISCOVER
timed out waiting for a valid DHCP server response
/etc/rc.d/rc.inet1: wlan0 information: 'Any ESSID'
Error for wireless request "Set Nickname" (8B1C) :
SET failed on device wlan0 ; Operation not supported.
Polling for DHCP server on interface wlan0:
Broadcasting DHCP_DISCOVER
broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255
dhcpIPaddrLeaseTime=86400 in DHCP server response.
dhcpT1value is missing in DHCP server response. Assuming 43200 sec
dhcpT2value is missing in DHCP server response. Assuming 75600 sec
DHCP_OFFER received from (192.168.1.1)
Broadcasting DHCP_REQUEST for 192.168.1.2
dhcpIPaddrLeaseTime=86400 in DHCP server response.
dhcpT1value is missing in DHCP server response. Assuming 43200 sec
dhcpT2value is missing in DHCP server response. Assuming 75600 sec
DHCP_ACK received from (192.168.1.1)
Broadcasting ARPOP_REQUEST for 192.168.1.2
root@darkstar:~#
root@darkstar:~# ping http://www.google.it
PING http://www.l.google.com (209.85.135.103) 56(84) bytes of data.
64 bytes from mu-in-f103.1e100.net (209.85.135.103): icmp_seq=1 ttl=53 t
ime=109 ms
64 bytes from mu-in-f103.1e100.net (209.85.135.103): icmp_seq=2 ttl=53 t
ime=435 ms
64 bytes from mu-in-f103.1e100.net (209.85.135.103): icmp_seq=3 ttl=53 t ime=315 ms
64 bytes from mu-in-f103.1e100.net (209.85.135.103): icmp_seq=4 ttl=53 t ime=79.8 ms
64 bytes from mu-in-f103.1e100.net (209.85.135.103): icmp_seq=5 ttl=53 t ime=602 ms
64 bytes from mu-in-f103.1e100.net (209.85.135.103): icmp_seq=6 ttl=53 t ime=1957 ms
64 bytes from 209.85.135.103: icmp_seq=7 ttl=53 time=1014 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
^C
--- http://www.l.google.com ping statistics ---
25 packets transmitted, 7 received, 72% packet loss, time 56032ms
rtt min/avg/max/mdev = 79.872/645.082/1957.713/611.751 ms, pipe 2
root@darkstar:~#
root@darkstar:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1575 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1380 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=990 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=93.9 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=436 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=148 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=50.6 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=174 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
^C
--- 192.168.1.1 ping statistics ---
24 packets transmitted, 8 received, 66% packet loss, time 42115ms
rtt min/avg/max/mdev = 50.657/606.364/1575.012/578.996 ms, pipe 2
root@darkstar:~#inutile dire che con xp funge tutto benone...
any ideas?
piuttosto che errore è ping: sendmsg: No buffer space available ???? 
come si aumenta il buffer della coda di messaggi? perchè a me da questo errore ed altri no? da cosa può dipendere?
:cf