Re: Home LAN/WAN network problem

Daniel,


On 2010-07-12 16:28, Daniel Pittman wrote:
> Philip Rhoades<[email protected]>  writes:
>
>> I have re-organised my home LAN/WAN setup (mainly to use default IP address
>> ranges of the modems/routers) as shown in the attached diag.
>
> Alas that you picked 10.1.1/24 for your internal network; that may well cause
> you regret when you want to VPN in to an employer who also chose the same
> range, or get a 3G router, or whatever else, in future.  Much better is to
> pick your range like this:
>
> bash -c 'echo "My network is: 10.$((32+RANDOM%192)).$((32+RANDOM%192))/24"'
>
> That gives you a pretty reasonable change of having a unique network block, so
> no annoying connectivity problems in the future.
>
> Anyway, unsolicited advice aside ...


I may need to reconsider later I guess but I wanted to stick to the 
default IP range defaults for the ADSL modem and WiFi router at the moment.


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


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


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


>> - I can't print from the server to the printer
>
> I have no idea on this one: how are they wired up?  Which print software are
> you using?  How did you configure it?  Can you ping / HTTP to the printer?


Did you look at the diagram? - the laser printer is wire connected to an 
ethernet port on the WiFi router.  I had previously set the printer 
using lpr/lpd which was fine but now I can't even ping the printer from 
the server - I have reset factory defaults on the printer and it is 
getting an IP address happily from the DHCP server on the WiFi router (I 
can see this on the client list on the WiFi router).


> Heck, is it a "network sharing" connected USB printer hanging off the router,
> or even the wireless AP?


I thought it was clear from the diagram that it was a network printer - 
I see now though that I mislabelled the connection as "wireless" instead 
of "wired".

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