Re: Home LAN/WAN network problem

Philip Rhoades <[email protected]> Tue, 13 Jul 2010 01:00:31 +1000
Newsgroups gmane.org.user-groups.slug.chat
Organization Pricom Pty Ltd
Message-ID <[email protected]>
Daniel,


On 2010-07-12 23:29, Daniel Pittman wrote:
> Philip Rhoades<[email protected]>  writes:
>> On 2010-07-12 16:28, Daniel Pittman wrote:
>>> Philip Rhoades<[email protected]>   writes:
>
> [...]
>
>>>> Everything works fine except:
>>>> - I can't ssh from the server to the Netbook (it works fine the other way)
>>>
>>> You didn't say where these were connection, so I am guessing that the server
>>> is on the wired network, and the netbook is on wireless, right?
>>
>> Yes - it is the computer labelled "Server" as opposed to "Old Server". I used
>> a dotted connection for the netbook to indicate a wireless connection.  Did
>> you look at the diagram? - I thought it was clear . .
>
> I didn't even notice the diagram existed until you pointed it out, so no.
> Um, and it did answer the question, and sorry for wasting your time as a
> result of not spotting it.


No worries - I thought the diag wasn't clear enough or something . .


>>> In future, it helps to say that, because now I am just guessing at your
>>> problem.  However: your wireless device shows that it uses the 192.168.1/24
>>> range for "LAN and Wireless", and 10.1.1/24 for "WAN".
>>>
>>> On these devices "WAN" usually means "the far side of a NAT layer", which
>>> means that what you are seeing in terms of ssh (from wireless to wired, but
>>> not wired to wireless) is more or less what I would expect.
>>>
>>> Personally, I solved this by turning *off* all the routing, DHCP, DNS, etc
>>> features on the wireless router,
>>
>> Right . .
>>
>>> then plugging a *LAN* port on it into the switch providing the internal
>>> network.
>>
>> Not sure what you mean - can you draw it?
>
> No, but I can perhaps explain:
>
> You know how you have the printer plugged in to the "LAN" side of the wireless
> router?  If you take the cable plugged into the "WAN" port and plug it,
> instead, into a spare port on the same "LAN" side as the printer you will have
> done what I was talking about.
>
> Aw, heck, lemme draw it anyway:
>
>   unplug the ADSL modem here
>             |
>             |
>    +-----| wan |-----+
>    |                 |
>    | wireless router |
>    |                 |
>    |-| |-| |-| |-| |-+
>       |           |
>       |           \----<- plug the ADSL modem in here instead
>     printer


Right - that is how I had it previously before the re-arrangement and 
the printer did indeed work with no problems but I still couldn't ssh 
from the netbook to the server even though everything was on the 
192.168.0 range of IP addresses.  In the messing around I was resetting 
factory configurations - so it was less hassle to leave them as defaults.


>>> That makes it a wireless bridge, with DHCP served by the server on the LAN,
>>> and no protection at all between wired or wireless clients.  For my set of
>>> risks this was great.
>>
>> Sounds OK for me too but I still can't visualise it . .
>
> Hopefully the picture and description help there. :)


Yep but that means all the dynamic addresses will be on the 10.1.1 range 
as well?


> Anyway, make sure you turn off the DHCP service on the Wireless Router
> *before* you move the cable from the WAN port to a LAN port on it.


Right.


> Otherwise you have two of 'em running, and that will make your life a misery.


Yep.

Thanks,

Phil.
-- 
Philip Rhoades

GPO Box 3411
Sydney NSW	2001
Australia
E-mail:  [email protected]
-- 
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html