Windows, Wifi and local lan

D

drhowarddrfine

I moved in with my son while my house is being remodeled. I have a Windows laptop that I connect to his home network wirelessly. I have a Linksys WRT54G that I would like to use with two FreeBSD boxes on a local network but also with the Windows notebook wired in. I changed the IP of the router to 192.168.1.2 and started the local addresses at 192.168.1.200. I left DHCP on and plugged the ethernet cables for all the computers into the lan side only.

This worked once. I was able to ping the FreeBSD boxes and tried to connect via ssh. It asked me to accept the security stuff for ssh and, after saying "yes", it hung. Any attempts afterwards only gets me a port rejected response.

I switched everything off, then on, but now none of that works and, plugging the ethernet cable from the laptop to the router blocks internet access on the Windows computer.

I so rarely deal with the networking side once it's set up that I tend to forget everything. Hints or tips please.
 
Since you're not using any of the wireless of the WRT54G why don't you just buy a cheap (10-15 euro) switch?
 
I assume there's already a modem and router that connects to the internet. That also has a DHCP server built-in. You don't need the one in your WRT54G as everything will end up on the same subnet anyway. The existing router will serve the IP addresses.
 
But the router isn't connected to the modem or any other router. I only want it connected to the Windows laptop via ethernet.
 
I figured something like that. If I'm not mistaken you can set the WRT54G as a wireless client. Use that to connect the WRT54G to your son's wireless network. Turn off the DHCP service on the WRT54G, IP addresses will be served by your son's router. Connect all your machines to the ethernet ports on the WRT54G.
 
I found a HOWTO on that. The FreeBSD boxes do not need to be on the 'net though that would be nice. Maybe I need to look into "bridging"?
 
No need for that, the WRT54G will bridge automatically. This basically means that all your machines will become part of the same network as your son's.

All you have to do is turn on DHCP on your machine, and yes, your FreeBSD machine would then also be able to connect to the internet using your son's network.
 
What did you mean,"turn on DHCP on your machine"? I assume you mean the Windows laptop but I don't know how to do that unless you mean with ICS in Sharing?

I thought this thread would do the trick but after I change the IP address of the router, I can access it for only about a minute till I lose it altogether.

So this didn't fall into place easily and I'm poking around too much but I don't have the thought to put too much thought into it. Appreciate any help.
 
He meant use dhcp on your hosts to acquire ip addresses.
Sorry if I'm missing anything, why do u want to use linksys router if your son already has one?

Did you connect it like this:

Code: 
Laptop!----->!Linksys--------son's_router----Internet
              [no dhcp]      [dhcp]
 
Connect WRT54G to your son's router with ethernet cable. Turn off DHCP/routing on WRT54G so that it works like regular switch. Let your son's router handle all DHCP. Now your FreeBSD boxes wired in WRT54G, as well as windows laptop should belong to the same network.
 
drhowarddrfine said:
plugged the ethernet cables for all the computers into the lan side only.
Click to expand...
The laptop need to be plugged in wan/internet (not wlan, wan, this isn't a typo) port. Because wrt54g run as NAT by default, it should have 2 IP addresses, one for wan facing side (received from son's router), one for lan side you should give one (preferably someting like 192.168.[red]2[/red].1). DHCP on wrt54g handles adresses for boxes connected to lan ports. (Unless you configure wrt54g as bridge or set port forwarding, the laptop won't be able to ssh any of freebsd boxes. If you do bridge, you need to turn off DHCP on wrt54g.)

drhowarddrfine said:
It asked me to accept the security stuff for ssh and, after saying "yes", it hung. Any attempts afterwards only gets me a port rejected response.
Click to expand...
Did you run sshd (ssh server) on the box being ssh'd?
 
bbzz said:
Connect WRT54G to your son's router with ethernet cable.
Click to expand...
I can't. It's physically too far. It's wireless only. I want to be able to network on a local lan between the notebook and the freebsd machines but, far preferably, have wifi available to the notebook, at least.
 
PseudoCylon said:
The laptop need to be plugged in wan/internet (not wlan, wan, this isn't a typo) port. Because wrt54g run as NAT by default, it should have 2 IP addresses, one for wan facing side (received from son's router), one for lan side you should give one (preferably someting like 192.168.[red]2[/red].1). DHCP on wrt54g handles adresses for boxes connected to lan ports. (Unless you configure wrt54g as bridge or set port forwarding, the laptop won't be able to ssh any of freebsd boxes. If you do bridge, you need to turn off DHCP on wrt54g.)
Click to expand...
I tried that first but it's been so long I think I'll try it again in case I did something wrong.
Did you run sshd (ssh server) on the box being ssh'd?
Click to expand...
There are two of those boxes and both are from my home office where I've done that for years.
 
Turn off ICS on the windows laptop, you don't need it. Set it to automatically get an IP address (DHCP).

You'll end up with something like this:

Code: 
[Son's wifi router]--(wireless)----[WRT54G]--(wired)--[FreeBSD/Windows]

Turn off NAT and the DHCP service on the WRT54G, it should be a straight bridge.
 
If I remember correctly, WRT54G (and most Linksys routers as well) can't be used as WiFi client with the official firmware.
I suggest the following configuration:
Code: 
/Son's router/ -> /WiFi/Windows Laptop
                           /ethernet/
                        WRT54G used as switch, DHCP should not be used
                           /ethernet/
                        FreeBSD Box
There is a even easier solution, requiring only a crossover cable, since you say that the FreeBSD box do not require internet connection:
Code: 
/Son's router/ -> /WiFi/Windows Laptop
                           /ethernet port/
                        Cross over ethernet cable
                           /ethernet port/
                        FreeBSD Box

If you need non-permanent internet connection on the FreeBSD box, you could use:
Code: 
/Son's router/ -> /WiFi/Windows Laptop, WiFi and Local Area Connections bridged, Automatic IP assigned on the bridge
                           /ethernet/
                        WRT54G used as switch, DHCP disabled / or / Cross over ethernet cable
                           /ethernet/
                        FreeBSD Box, ethernet configured with DHCP
 
drhowarddrfine said:
I can't. It's physically too far. It's wireless only. I want to be able to network on a local lan between the notebook and the freebsd machines but, far preferably, have wifi available to the notebook, at least.
Click to expand...

Ah, ok, I got it now. It wasn't clear why you need WRT router.

In this case, you need to get a new firmware for your router, since the stock doesn't support bridging. I have the same setup. Go to http://www.dd-wrt.com/site/index and get new firmware. Then setup your router to be in "repeater bridge mode". Turn off DHCP, NAT, regular routing. This will allow you to connected everything to your own router (via cable or wifi), which will then pass everything to your son's router via wifi.
 
Yeah, I've tried all the ideas above. It's interesting I'm able to connect for a minute or so but I presume the addresses are getting released and disconnect me. Thanks guys.
 
You must log in or register to reply here.
Back
Top