[driverloader] Can't connect to internet

Linuxant support (Jonathan) support at linuxant.com
Tue Mar 1 11:00:14 EST 2005


Hi,

for the need to disable the 'eth0' ethernet interface in order to use 
the wireless interface, it is quite possible that you will need to 
activate an option similar to 'set as the default route' for the 'wlan0' 
wireless interface, it will probably solve this problem.

This option is automatically set by DriverLoader when you setup your 
connection with DHCP only but if since you use static information for 
the wireless interface, you will probably have to manually activate it.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com


ken wrote:
> Aaah, you hit on it!  Like I said, it must be something simple.
> First I stopped my firewall completely and lo and behold it worked!
> 
> But then I thought, that doesn't make any sense I should be able to use
> a firewall with this, *especially* as its a wireless connection.  When I
> went back to the firewall (using YaST) to see if there was some setting
> I just needed to check I noticed that the firewall first asks you for
> the internal interface you want to protect.  Huh?  All of them of
> course.  Turns out you have to space delimit the list of interfaces. 
> When I first installed SUSE it only auto-picked up my eth0 and not my
> wlan0 so it had only added that entry.  So I added wlan0, restarted the
> firewall, and my wlan0 works with the firewall now.
> 
> I still have to keep my eth0 disabled though.  Oh well, I can live with
> that.
> 
> Thanks!
> 
> Ken
> 
> 
> On Mon, 2005-02-28 at 12:41, Linuxant support (Jonathan) wrote:
> 
>>Hi,
>>
>>do you have any error message in your 'dmesg' when you try to use the 
>>wireless interface? If you try to send packets with the wireless 
>>interface, does the number of sent packets increases in the output of 
>>the 'ifconfig wlan0' command in a root shell?
>>
>>Since you was able to resolve an address with the first 'ping' command, 
>>it is possible that this is a simple firewall issue. You could also try 
>>to disable the firewall on your machine, it could be the source of the 
>>problem.
>>
>>You could also try to disable all protection on your access point to see 
>>if there is the source of the problem. For example, MAC address filters, 
>>firewall, etc... You could try to connect to this access point with 
>>another wireless card, OS or machine just to make sure that the access 
>>point is not the problem. Finally, you could upgrade the firmware of the 
>>access point.
>>
>>Regards,
>>
>>
>>Jonathan
>>Technical specialist / Linuxant
>>www.linuxant.com
>>support at linuxant.com
>>
>>
>>ken wrote:
>>
>>>I've just installed the driverloader (trial version but will definitely
>>>buy if this works!) using the x86_64 rpm for SuSe 9.2 kernel
>>>2.6.8-24.11-default.  Its installed on my new 64-bit Compaq Presario
>>>R3000 with Broadcom BCM4306 802.11b/g wireless LAN controller.  I
>>>installed the drivers netbc564.inf and BCMWL564.SYS form the linuxant
>>>website.  So far so good, the device shows up in Yast and I configured
>>>it.  Problem is I can't connect to the internet still.  :(  Well I can
>>>connect through eth0 but not wlan0.
>>>
>>>I have even gone so far as to disable my eth0 connection and connect to
>>>the wireless with a static IP address to avoid any DHCP related issues. 
>>>Still no go.  Here is some output with the eth0 and DHCP disabled.  I
>>>hope someone can help me.  I imagine it must be something really simple
>>>that I'm overlooking?
>>>
>>>As you can see below I can't even ping my router (192.168.2.1) even
>>>though I am able to locate the router, as evidenced by the fact that it
>>>picked up the broadcast SSID of "casa crow".  Doesn't have anything to
>>>do with the space in the name does it?  I havn't resorted to that yet!
>>>
>>>Notice also the "Warning:  no interface active" reported by the SuSe
>>>firewall when the network is restarted.  Obviously that is the source of
>>>the problem but why?
>>>
>>>Thanks for any help,
>>>
>>>Ken
>>>
>>>
>>>saturn:/tmp # /etc/init.d/network restart
>>>Shutting down network interfaces:
>>>    eth0      device: Realtek Semiconductor Co., Ltd.
>>>RTL-8139/8139C/8139C+ (rev 10)
>>>    eth0      configuration: eth-id-00:0f:b0:44:b4:e2                
>>>done
>>>    wlan0     device: Broadcom Corporation BCM4306 802.11b/g Wireless
>>>doneController (rev 03)
>>>Shutting down service network  .  .  .  .  .  .  .  .  .  .  .  .  . 
>>>done
>>>Hint: you may set mandatory devices in /etc/sysconfig/network/config
>>>Setting up network interfaces:
>>>    lo
>>>    lo        IP address: 127.0.0.1/8                                
>>>done
>>>    eth0      device: Realtek Semiconductor Co., Ltd.
>>>RTL-8139/8139C/8139C+ (rev 10)
>>>    eth0      configuration: eth-id-00:0f:b0:44:b4:e2
>>>    eth0      Startmode is 'off'                                     
>>>skipped
>>>    wlan0     device: Broadcom Corporation BCM4306 802.11b/g Wireless
>>>LAN Controller (rev 03)
>>>    wlan0     warning: using NO encryption
>>>    wlan0     IP address: 192.168.2.137/24                           
>>>done
>>>Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  . 
>>>done
>>>SuSEfirewall2: Warning: no interface active
>>>SuSEfirewall2: Firewall rules successfully set from
>>>/etc/sysconfig/SuSEfirewall2
>>>saturn:/tmp # ip route
>>>192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.137
>>>169.254.0.0/16 dev wlan0  scope link
>>>127.0.0.0/8 dev lo  scope link
>>>default via 192.168.2.1 dev wlan0
>>>
>>>
>>>saturn:/tmp # ping www.samsix.com
>>>PING samsix.com (69.65.19.208) 56(84) bytes of data.
>>>
>>>--- samsix.com ping statistics ---
>>>10 packets transmitted, 0 received, 100% packet loss, time 8998ms
>>>
>>>
>>>saturn:/tmp # ip route
>>>192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.137
>>>169.254.0.0/16 dev wlan0  scope link
>>>127.0.0.0/8 dev lo  scope link
>>>default via 192.168.2.1 dev wlan0
>>>
>>>saturn:/tmp # iwconfig
>>>lo        no wireless extensions.
>>>
>>>eth0      no wireless extensions.
>>>
>>>sit0      no wireless extensions.
>>>
>>>wlan0     IEEE 802.11-DS  ESSID:"casa crow"  Nickname:"saturn"
>>>          Mode:Managed  Frequency:2.437 GHz  Access Point:
>>>00:50:F2:CB:F4:06
>>>          Bit Rate=11 Mb/s   Tx-Power=25 dBm
>>>          RTS thr:off   Fragment thr:off
>>>          Encryption key:off
>>>          Power Management:off
>>>          Link Quality=94/94  Signal level=-16 dBm  Noise level=-154 dBm
>>>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>>>          Tx excessive retries:0  Invalid misc:5518   Missed beacon:0
>>>
>>>
>>>saturn:/tmp # ping 192.168.2.1
>>>PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
>>>
>>>--- 192.168.2.1 ping statistics ---
>>>4 packets transmitted, 0 received, 100% packet loss, time 2998ms
>>>
>>>saturn:/tmp # cat /etc/sysconfig/network/ifcfg-wlan0
>>>BOOTPROTO='static'
>>>MTU=''
>>>REMOTE_IPADDR=''
>>>STARTMODE='auto'
>>>USERCONTROL='no'
>>>WIRELESS_AP=''
>>>WIRELESS_AUTH_MODE='open'
>>>WIRELESS_BITRATE='auto'
>>>WIRELESS_CHANNEL=''
>>>WIRELESS_DEFAULT_KEY='0'
>>>WIRELESS_ESSID=''
>>>WIRELESS_FREQUENCY=''
>>>WIRELESS_KEY=''
>>>WIRELESS_KEY_0=''
>>>WIRELESS_KEY_1=''
>>>WIRELESS_KEY_2=''
>>>WIRELESS_KEY_3=''
>>>WIRELESS_KEY_LENGTH='128'
>>>WIRELESS_MODE='Managed'
>>>WIRELESS_NICK=''
>>>WIRELESS_NWID=''
>>>WIRELESS_POWER='yes'
>>>WIRELESS_WPA_PSK=''
>>>_nm_name='static-0'
>>>BROADCAST='192.168.2.255'
>>>IPADDR='192.168.2.137'
>>>NETMASK='255.255.255.0'
>>>NETWORK='192.168.2.0'
>>>DHCLIENT_MODIFY_RESOLV_CONF='yes'
>>>DHCLIENT_SET_DEFAULT_ROUTE='yes'
>>>
>>>
>>>_______________________________________________
>>>driverloader mailing list
>>>driverloader at lists.linuxant.com
>>>https://www.linuxant.com/mailman/listinfo/driverloader
>>
> 
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader


More information about the driverloader mailing list