Connect wlan0 to eth1

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 keyff
Power Managementff
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

Kevin Boergens wrote:
> Hello!
>
> [snip]
>
> That is what iwconfig says:
> ################################################## ##########
>
> [snip]
>
> 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 keyff
> Power Managementff
> 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 [snip]
>
> lo [snip]
> ################################################## ###############
>
> 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?

wlan0 is its own interface. You don't "connect" it to anything.
Basically you need to get it to associate with a wireless access point.
When you do, wlan0 will be listed by ifconfig as active.
Note that for an inactive interface, you can say explicitly, e.g.,

ifconfig wlan0

to get info on that interface.

Allen Kistler wrote:
> Kevin Boergens wrote:
>
>> Hello!
>>
>> [snip]
>>
>> That is what iwconfig says:
>> ################################################## ##########
>>
>> [snip]
>>
>> 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 keyff
>> Power Managementff
>> 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 [snip]
>>
>> lo [snip]
>> ################################################## ###############
>>
>> 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?
>
>
> wlan0 is its own interface. You don't "connect" it to anything.
> Basically you need to get it to associate with a wireless access point.
> When you do, wlan0 will be listed by ifconfig as active.
> Note that for an inactive interface, you can say explicitly, e.g.,
>
> ifconfig wlan0
>
> to get info on that interface.

Hi!

> wlan0 is its own interface. You don't "connect" it to anything.
> Basically you need to get it to associate with a wireless access point.
> When you do, wlan0 will be listed by ifconfig as active.
OK, that has worked. Thanks!

ifconfig:
################################################## ####################
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:2903 errors:0 dropped:0 overruns:0 frame:0
TX packets:674 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:1524499 (1.4 MiB) TX bytes:50274 (49.0 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:10357 errors:0 dropped:0 overruns:0 frame:0
TX packets:10357 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:11536441 (11.0 MiB) TX bytes:11536441 (11.0 MiB)

wlan0 Protokoll:Ethernet Hardware Adresse 00:0D:88:989:13
inet Adresse:192.168.0.88 Bcast:192.168.0.255
Maske:255.255.255.0
inet6 Adresse: fe80::20d:88ff:fe98:d913/64
Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:308 (308.0 b)
Interrupt:11 Speicher:d0120000-d0121fff
################################################## ######################

iwconfig:
################################################## ######################
lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

sit0 no wireless extensions.

wlan0 IEEE 802.11b ESSID:"Boergens"
Mode:Managed Frequency:2.462GHz Access Point: 00:01:E3:08:1A:A0
Bit Rate:54Mb/s Tx-Power:0 dBm Sensitivity=0/3
RTS thr:4096 B Fragment thr:4096 B
Encryption key:6162-6364-65 Security mode:restricted
Power Managementff
Link Quality:100/100 Signal level:-63 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
################################################## #######################


I can ping 192.168.0.88 perfectly. But other IPs don't work. (e.g. my
router)
Why? Do I have to tell him that wlan0 is the default device to connect
to others computers?

I searched for a good howto on networking but all I found were updated
in the mid90s. Can someone tell me where to find?

TIA,
Kevin

--
http://boergens.de/kevin

Kevin Boergens wrote:
> Hi!
>
>> wlan0 is its own interface. You don't "connect" it to anything.
>> Basically you need to get it to associate with a wireless access
>> point. When you do, wlan0 will be listed by ifconfig as active.
>
> OK, that has worked. Thanks!
>
> ifconfig:
> ################################################## ####################
> 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:2903 errors:0 dropped:0 overruns:0 frame:0
> TX packets:674 errors:0 dropped:0 overruns:0 carrier:0
> Kollisionen:0 Sendewarteschlangenlänge:1000
> RX bytes:1524499 (1.4 MiB) TX bytes:50274 (49.0 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:10357 errors:0 dropped:0 overruns:0 frame:0
> TX packets:10357 errors:0 dropped:0 overruns:0 carrier:0
> Kollisionen:0 Sendewarteschlangenlänge:0
> RX bytes:11536441 (11.0 MiB) TX bytes:11536441 (11.0 MiB)
>
> wlan0 Protokoll:Ethernet Hardware Adresse 00:0D:88:989:13
> inet Adresse:192.168.0.88 Bcast:192.168.0.255
> Maske:255.255.255.0
> inet6 Adresse: fe80::20d:88ff:fe98:d913/64
> Gültigkeitsbereich:Verbindung
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> Kollisionen:0 Sendewarteschlangenlänge:1000
> RX bytes:0 (0.0 b) TX bytes:308 (308.0 b)
> Interrupt:11 Speicher:d0120000-d0121fff
> ################################################## ######################
>
> iwconfig:
> ################################################## ######################
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> eth1 no wireless extensions.
>
> sit0 no wireless extensions.
>
> wlan0 IEEE 802.11b ESSID:"Boergens"
> Mode:Managed Frequency:2.462GHz Access Point: 00:01:E3:08:1A:A0
> Bit Rate:54Mb/s Tx-Power:0 dBm Sensitivity=0/3
> RTS thr:4096 B Fragment thr:4096 B
> Encryption key:6162-6364-65 Security mode:restricted
> Power Managementff
> Link Quality:100/100 Signal level:-63 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
> ################################################## #######################
>
>
> I can ping 192.168.0.88 perfectly. But other IPs don't work. (e.g. my
> router)
> Why? Do I have to tell him that wlan0 is the default device to connect
> to others computers?
>
> I searched for a good howto on networking but all I found were updated
> in the mid90s. Can someone tell me where to find?
>
> TIA,
> Kevin
>
yes you have, unless you've obtained your ip address with dhclient or
the like.

Else, you should define your route-table, setting wlan0 as the default
to reach the other 192.168.0's

eg. route add -net 192.168.0.0/24 wlan0

Kevin Boergens wrote:
>
> [snip]
>
> ifconfig:
> ################################################## ####################
> eth0 Protokoll:Ethernet Hardware Adresse 00:0D:9D:8B:7F:87
> inet Adresse:192.168.0.87 Bcast:192.168.0.255 [snip]
>
> [snip]
>
> wlan0 Protokoll:Ethernet Hardware Adresse 00:0D:88:989:13
> inet Adresse:192.168.0.88 Bcast:192.168.0.255 [snip]
>
> ################################################## ######################
>
> [snip]
>
> I can ping 192.168.0.88 perfectly. But other IPs don't work. (e.g. my
> router)
> Why? Do I have to tell him that wlan0 is the default device to connect
> to others computers?
>
> I searched for a good howto on networking but all I found were updated
> in the mid90s. Can someone tell me where to find?

You've got two interfaces on the same subnet. That, by itself, isn't
horrible, but you've probably got your box confused about routing.

netstat -nr

If, for example, you unplugged eth0, but the default interface for the
local subnet is eth0, then that would stop things from working.

Hi!
> Else, you should define your route-table, setting wlan0 as the default
> to reach the other 192.168.0's
>
> eg. route add -net 192.168.0.0/24 wlan0

Thank you a lot!

Nice holidays,
Kevin