Debian firestarter not bridging the internet

Matizek · 01-21-2008, 02:01 PM

Hi!

I have Debian 4.0 installed. For internet I have a ethernet card which connects to a router/modem which allows me to post this

Now I have also a wlan pci card Netgear WG3111v3 which I want to bridge the internet connection to my laptop (asus eee).
What I have already done: I've installed drivers for WG3111v3 with the help of this guide, configured some settings with wlan0 (which I assume as probably wrong) and installed and configured the firestarter. When I want to check the available internet connection on my laptop (winxp - don't kill me) it detects this my bridged network and it can also connect to it.
In windows wifi it says it's connected, but the internet is not working.

If you ask me, I've set wrong ips for gateway and dns and thise stuff, but I don't know how to set them correctly. Can anybody please help me?

Greetz,
Matizek

farslayer · 01-21-2008, 03:01 PM

Would help to see the IP addresses you have configured on the PC, eee, and gateway..

addressing info on the Debian box:
ifconfig /all
route -n
cat /etc/resolve.conf

Is the Linux machine providing dhcp addressing to the asus eee ?

what is the addressing on the asus eee showing ?

what is the ip address of the router ?

Matizek · 01-22-2008, 06:56 AM

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 :|

farslayer · 01-22-2008, 12:56 PM

Ack I'm sorry I mistyped that command it should have read..
cat /etc/resolv.conf
that e should not have been there..

Yes the firewall should start automatically even if you have not opened the firestarter GUI.

you can verify the firewall is started with iptables -L

check the resolv.conf on both linux machines they should both be pointing at the gateway device 192.168.1.254

Matizek · 01-22-2008, 01:21 PM

that commands shows:

Code:

# generated by NetworkManager, do not edit!

search lan


nameserver 192.168.1.254

and iptables -L:

Code:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

and yes, Gateway is on both (asus eee - xp, and server - debian) 192.168.1.254 but internet still doesn't apper to work :/ btw, I can ping the debian server normally from laptop, but I cannot ping router (192.168.1.254) and I cannot ping eee pc from debian server using ping 192.168.2.80

---edit:---

okay now I changed ips to 192.168.0.2(server) and 192.168.0.3(xp) just for the heck of it and I am now able to ping debian from xp and xp from debian. But still can't ping router - no internet :|

Matizek · 01-26-2008, 04:44 PM

Ok I now configured it this way so that I don't have a direct internet access but I have to run proxy on server. Anyway, it works and that's all that matters ;-)