Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've been searching and searching and can't get the last piece of this put together....
I hope the diagram tells what takes too many words to say
Wireless ISP ---> Linux box(that I cannot modify) --> Netgear WGT624v2 router (192.168.0.1)
WIRED NETWORK 1 (downstairs connecting 2 WinXP Pro machines)
Linux box (Debian Sarge) connnected to Netgear router via wireless to be DHCP server and router for WIRED NETWORK 2 (upstairs) so I don't have to run cables up through my house
I want to connect downstairs network where ISP connection comes in and upstairs network without running cable.
SOLVED SO FAR:
Linux machine working via wireless and assigning IP addresses with DHCP on wired network 2 (I went through 2 wireless cards to get this working right - Don't buy a wireless card with a Realtek 8185 chipset to use in Linux - too many headaches)
The connected machines (other than the Linux box) in Network 2 cannot see the Netgear router, nor any machines on Network 1, nor (of course) the Internet.
Not sure exactly where the problem lies - either in the Netgear router or in the Linux router. - but I think in the Linux machine something I don't have right.
I've been reading on bridging and routing, trying to find the answer to this for a week now. It's not impossible, is it? Hope someone can help.
Last edited by rogerthehart; 03-10-2007 at 05:08 PM.
Do you have IP forwarding enabled on the debian wireless computer. The others in the wired network need to use it's NIC IP address as the default gateway. I had something slightly similar where I used my laptop as a gateway to my wireless router. I used the subnet 192.168.1.0/25 on the wireless side and 192.168.1.128/25 on the wired side. I don't understand why, but it wouldn't work until I modprobed the ip_conntrack module even though I wasn't using NAT.
You're doing something more complicated because you have two computers routing traffic instead of just one.
From your post, it sounds like the debian computer is connected to the internet so the wireless laptop is routing traffic correctly. Things would work out easier if the router was wireless. Then the wireless laptop and the debian wireless host would be two hosts on the wireless network and the debian machine could route the wired network traffic straight to the router.
Did you check if the ip_conntrack module is loaded? On your last question, you are describing routing and not a bridge. A bridge fragments a network to reduce traffic or to regulate traffic between segments.
You might want to post the routes on the two machines with wireless. Do you have a route on the debian machine for the wireless network as well as the wireless laptop? Otherwise, traffic destined for it may be destined for the default gateway instead.
Post what the subnets are as well and the outputs of route.
The wireless laptop really has nothing to do with my problem. It connects only to the Netgear router and has no problems under win2000.
I would think that making the ath0 ip address (192.168.0.4) the gateway for eth0 should work, but when I un-comment that line I get "network is unreachable" and "failed to bring up eth0". I guess that won't work.