Here's my current setup.

Linux Machine:
wlan0
IP: 192.168.1.25
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1

eth0
IP: 192.168.0.1
Subnet Mask: 255.255.255.0
Gateway: null

Windows Machine:
Local area network:
IP: 192.168.0.2
Subnet Mask: 255.255.255.0
Gateway: 192.168.0.1

I want to forward the internet to my second computer(Windows) from the first(Linux).

I use a cross over cable.

I think that you're going to have to do some searching on how to get this working. My best guess is that if you set up your Linux box as a router, that should do the trick. However I'm kinda out of my league with this so there may be easier ways to do it. There is a nice tutorial on how to set up a linux router here.

Well, I typed in what that link said too. I skiped the DNS and DHCP things though as I do not want them.

Anyway, the internet does not get forwarded. My Windows machine does not surf the net...

Also, I cannot get Azuerus to work. I get green smiley face, but the download speed is 0.0kbps...

I'm afraid I'm not going to be any help on forwarding to the Windows box. I just don't have any experience in doing it since I use a router to share my internet connection. Which actually brings up a question......If you are accessing the internet wirelessly, don't you have a router/AP on your network?

As for Azureus, if you have a smiley green face, that suggests that it is making a connection. Is it possible that you've just picked up a torrent that isn't being seeded?

Nope, there are plenty of seeds. I have no idea why that doesn't work... But I'll end this thread now.

Thanks for the help with NDISWrapper and WPA Supplicant.

Hmm... There seems to be a problem. Whenever I shut down my AP, the system running NDISWrapper/WPA Supplicant locks up. That's going to be a problem as the router I have resets every day at 0500.

Anyone know about this? Do I need to change a setting?

A couple of ideas....

First, I would do some serious digging in your logs to see what is happening after the router reset. It is going to be really tough to guess what is happening without a bit more info.


The other approach to try is that since you know when the router is going to reset, you have a cron job that takes down your wireless card just before, and re-establishes a connection just after.

Logs. What a good idea. Seriously.

Heh, where would I find this information?

Under /var/log I have some things, but what do you want even?

The most likely places are in /var/log/messages or /var/log/syslog. Since you know roughly what time things go kablooie, I'd look for something timestamped around then. I'd also look for messages labelled from wpa_supplicant or your driver. Given that you'r having a complete lockup, the kernel might be a suspect too. And if it has happened more than once, I'd look for similarities around the time it crashes.

Jan 8 01:01:01 fserver crond(pam_unix)[3718]: session opened for user root by (uid=0)
Jan 8 01:01:01 fserver crond(pam_unix)[3718]: session closed for user root
Jan 8 01:03:34 fserver kernel: eth0: link down.
Jan 8 01:03:36 fserver kernel: eth0: link up.
Jan 8 01:14:52 fserver nmbd[2759]: [2006/01/08 01:14:52, 0] nmbd/nmbd.crocess(542)
Jan 8 01:14:52 fserver nmbd[2759]: Got SIGHUP dumping debug info.
Jan 8 01:14:52 fserver nmbd[2759]: [2006/01/08 01:14:52, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
Jan 8 01:14:52 fserver nmbd[2759]: dump_workgroups()
Jan 8 01:14:52 fserver nmbd[2759]: dump workgroup on subnet 192.168.1.25: netmask= 255.255.255.0:
Jan 8 01:14:52 fserver nmbd[2759]: UH(1) current master browser = FSERVER
Jan 8 01:14:52 fserver nmbd[2759]: FSERVER 40049a03 (The FTP Server)
Jan 8 01:14:52 fserver nmbd[2759]: [2006/01/08 01:14:52, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
Jan 8 01:14:52 fserver nmbd[2759]: dump_workgroups()
Jan 8 01:14:52 fserver nmbd[2759]: dump workgroup on subnet 192.168.0.1: netmask= 255.255.255.0:
Jan 8 01:14:52 fserver syslogd 1.4.1: restart.
Jan 8 01:14:52 fserver nmbd[2759]: UH(1) current master browser = FSERVER
Jan 8 01:14:52 fserver nmbd[2759]: FSERVER 40049a03 (The FTP Server)
Jan 8 01:14:52 fserver nmbd[2759]: DALPONIS 40011001 (Dalponis' Computer)
Jan 8 02:01:01 fserver crond(pam_unix)[4755]: session opened for user root by (uid=0)
Jan 8 02:01:01 fserver crond(pam_unix)[4755]: session closed for user root
Jan 8 03:01:01 fserver crond(pam_unix)[5249]: session opened for user root by (uid=0)
Jan 8 03:01:01 fserver crond(pam_unix)[5249]: session closed for user root
Jan 8 04:01:01 fserver crond(pam_unix)[5743]: session opened for user root by (uid=0)
Jan 8 04:01:01 fserver crond(pam_unix)[5743]: session closed for user root
Jan 8 04:02:01 fserver crond(pam_unix)[5753]: session opened for user root by (uid=0)
Jan 8 04:02:11 fserver crond(pam_unix)[5753]: session closed for user root
Jan 8 04:22:01 fserver crond(pam_unix)[6443]: session opened for user root by (uid=0)
Jan 8 04:24:04 fserver crond(pam_unix)[6443]: session closed for user root

Well that is spectacularly unenlightening. I don't see anything abnormal there.

Hm. I guess that one possible approach is to figure out if the problem is with ndiswrapper or with wpa_supplicant. If you feel you can get by with an open AP for a night, I would turn off WPA encryption and see if the crash happens anyway. If it does, at least that rules out wpa_supplicant as a suspect. If it doesn't crash, then we know exactly where the blame lies.

What also might be helpful is a little bit more detail about what is happening when your AP resets. I'm wondering if there is some sort of problem related to IP addresses changing.

Well, I can make the system crash on demand. It says Kernal Panic yada yada yada. I wish there was a log of that...

Well, I thought it could be the 16K/4K issue thing... I tried the 16K one. No go. Still crashes. Argh!

Aw, crud. That was going to be my next suggestion. Did you roll your own kernel or did you find one with a 16K stack?

Yeah, I wish there was a log too as I think that it is likely going to be our only clue. Is there any chance of getting a better grip on what yada yada yada actually is?

The only other thing I can think of is to try a different Windows driver if you can find one.

No, I downloaded a 16k Stack size one. Yeah, it didn't help. I could try another driver, but I have a strange feeling that it's just trying to keep a connection going even though the AP is not there.

How do I get NDISWrapper to join a network without WPA supplicant? As you know, I:
"wpa_supplicant -c /etc/wpa_supplicant.conf -D ndiswrapper -i wlan0 -d -B"

So what would I do to connect without WPA Supplicant?