Connect wlan0 to eth1

From: Kevin Boergens (kevin_at_boergens.de)
Date: 07/20/04 

Date: Tue, 20 Jul 2004 16:06:38 +0200

Hello!

I think that I should read the networking howto and my question would
disappear, but I'm really in a hurry and would very happy if someone
helped me nonetheless.

I'm using a HP Pavilion ZE5500 with an intern 10/100 Network, configured
as eth0 and a PCMCIA DL-G650+. I'm using Debian Sid.

The driver works now:
###########################################################
Jul 20 15:59:53 localhost kernel: ndiswrapper version 0.8 loaded
Jul 20 15:59:53 localhost kernel: ndiswrapper adding gplus.sys
Jul 20 15:59:54 localhost kernel: PCI: Enabling device 0000:02:00.0
(0000 -> 0002)
Jul 20 15:59:54 localhost kernel: ndiswrapper: Buggy ndis driver trying
to use unintilized spinlock. Trying to recover...ok.
Jul 20 15:59:54 localhost kernel: wlan0: ndiswrapper ethernet device
00:0d:88:98:d9:13 using driver gplus.sys
############################################################

That is what iwconfig says:
############################################################
lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

sit0 no wireless extensions.

wlan0 IEEE 802.11b ESSID:""
           Mode:Managed Frequency:2.462GHz Access Point: FF:FF:FF:FF:FF:FF
           Bit Rate:54Mb/s Tx-Power:0 dBm Sensitivity=0/3
           RTS thr:4096 B Fragment thr:4096 B
           Encryption key:off
           Power Management:off
           Link Quality:100/100 Signal level:-65 dBm Noise level:-256 dBm
           Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
           Tx excessive retries:0 Invalid misc:0 Missed beacon:0
##############################################################

That is what ifconfig says:
##############################################################
eth0 Protokoll:Ethernet Hardware Adresse 00:0D:9D:8B:7F:87
           inet Adresse:192.168.0.87 Bcast:192.168.0.255
Maske:255.255.255.0
           inet6 Adresse: fe80::20d:9dff:fe8b:7f87/64
Gültigkeitsbereich:Verbindung
           UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
           RX packets:17673 errors:0 dropped:0 overruns:0 frame:0
           TX packets:5188 errors:0 dropped:0 overruns:0 carrier:0
           Kollisionen:0 Sendewarteschlangenlänge:1000
           RX bytes:10443241 (9.9 MiB) TX bytes:443726 (433.3 KiB)
           Interrupt:10 Basisadresse:0x5000

lo Protokoll:Lokale Schleife
           inet Adresse:127.0.0.1 Maske:255.0.0.0
           inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
           UP LOOPBACK RUNNING MTU:16436 Metric:1
           RX packets:41204 errors:0 dropped:0 overruns:0 frame:0
           TX packets:41204 errors:0 dropped:0 overruns:0 carrier:0
           Kollisionen:0 Sendewarteschlangenlänge:0
           RX bytes:44189233 (42.1 MiB) TX bytes:44189233 (42.1 MiB)
#################################################################

OK, but what now? I think that I have to "connect" wlan0 to eth1 and
then make eth1 the standard network device. Right? But how?

Thanks in advance,
        Kevin 

-- 
http://www.boergens.de/kevin

Relevant Pages

  • Re: Wireless device appears to be configured properly but I cannot ping my router!
    ... It sees my WAP and the configuration via Network Tools appears to be ... Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 ... Did you verify that the ndiswrapper is setup properly? ... Then why are you telling people to uninstall Network Manager? ...
    (Ubuntu)
  • Re: Wireless interface fails to initialize fully; still need to get DHCP manually
    ... # This file describes the network interfaces available on your system ... ndiswrapper -i bcmwl5.inf in the directory where that file resides (I ... The cause was that PCMCIA services are started in the boot / startup sequence AFTER networking is set up, so at the time the startup procedure is trying to connect to your network PCMCIA services are not running. ... The boot sequence will only attempt to initialise interfaces that have the auto keyword defined in /etc/interfaces. ...
    (Debian-User)
  • Re: NetworkManager tutorials?
    ... Could you explain what you mean by restarting the network since that ... As in 'service network restart' ... I know that ndiswrapper generated some pretty vociferous condemnations ... We're hardly in a position to demand GPL chipsets ...
    (Fedora)
  • Re: Fedora & Ndiswrapper & Mimo Wireless
    ... > than 4k of memory to be able to use the network card. ... The ndiswrapper site used to have kernels for FC ...
    (Fedora)
  • My own network trouble! FC4, you too ...
    ... Either FC3 and FC4 doesn't not recognize automatically that device. ... In FC3 I solved the problem downloading driver and installing as new module. ... Jun 18 12:51:30 localhost kernel: ndiswrapper version 1.2 loaded ...
    (Fedora)