Hmmm... strange... it somehow does not connect today, even though I think yesterday it was connected. I didn't check the ipconfig yesterday but today it says Media disconnected, but it finds the wireless signal and the name of it.
ifconfig -a says on server:
Code:
eth0 Link encap:Ethernet HWaddr 00:18:F3:08:86:8B
inet addr:192.168.1.70 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fe08:868b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:54289 errors:0 dropped:0 overruns:0 frame:0
TX packets:31271 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:27057708 (25.8 MiB) TX bytes:4231062 (4.0 MiB)
Interrupt:177 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 00:18:4D:EF:0B:10
inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:50 Memory:feae0000-feaf0000
route -n:
Code:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
cat /etc/resolve.conf says that resolve.conf does not exist.
No, I'm almost sure that linux doesn't provide dhcp to eee. That's the setting in firewall (firestarter) right?
Addressing on eee shows that media's not connected now...
ip address of the router is 192.168.1.254 I believe.
Thanks
---------------- EDIT: ----------------
Hmm... weird thing is going on... Now windows doesn't even detect the server! may this be the problem:
Code:
matizek@matizek-server:~$ sudo ndiswrapper -l
installed drivers:
wg311v3 driver installed, hardware (11AB:1FAB) present
matizek@matizek-server:~$ sudo ndiswrapper -a 11AB:1FAB wg311v3
couldn't create symlink for "11AB:1FAA.5.conf" -
installation may be incomplete
couldn't create symlink for "11AB:1FAA:6B00:1385.5.conf" -
installation may be incomplete
couldn't create symlink for "11AB:1FAB.5.conf" -
installation may be incomplete
driver 'wg311v3' is not installed (properly)!
---------- EDIT2: ----------
okay this is getting weird.... now I rebooted the server and NOW the eee connects to the debian even though I haven't even started firestarter yet! I mean i don't know if it starts itself but...
to sum up, ipconfig on eee says that IP addr: 192.168.2.80 and Gateway: 192.168.2.10. But the internet still doesn't work :|