Re: [Hampshire] Samba share on a wireless network

Top Page

Reply to this message
Author: Brian Chivers
Date:  
To: Hampshire LUG Discussion List
Subject: Re: [Hampshire] Samba share on a wireless network
Adam Cripps wrote:
> Calling all samba gurus - I have a machine running Samba on my main
> network and want to make shares available on my wireless network.
> However, it seems that my wireless router has a problem with these
> shares.
>
> My current network is set-up thus:
>
>   ADSL router (DHCP)
>  192.168.1.1
>        |
> ---------------------------------------------------------------------
> |                                  |                          |
> Wireless (DHCP)          Samba               Other machines
> 192.168.1.3                192.168.1.7        192.168.1.*
> 192.168.11.1
>         |
> -------------------------------------
> |                                     |
> Laptop 1                        Laptop 2
> 192.168.11.2                 192.168.11.3

>
> (Apologies if the text representation gets mangled).
>
> Basically, the machines on the 192.168.1.* network can mount the samba
> shares normally, but the laptops in the 192.168.11.* network cannot.
>
> I have placed the following line in my smb.conf file:
>
> hosts allow = 127.0.0.1, 192.168.
>
> but I think this is only half of the story as I have to put in an
> interfaces config line.
> I've read documentation, but it seems to be based around to separate
> networks and I'm not sure what to do with the interfaces part.
>
> Can anyone advise what else I need to add to the smb.conf file to make
> the shares accessible from the wireless network? Ideally, I'd like to
> place this in [globals] as I will be adding a printer later on.
>
> A full copy of the smb.conf file can be seen at:
> http://www.monkeez.org/linux/smb.conf.txt
>
> TIA
> Adam


The quick and dirty way is to change your subnet mask to 255.255.0.0 on your devices and this will
allow the 192.168.1.x to talk to 192.168.11.x without worrying about routing tables etc

Yes I know that this is an illegal subnet mask but it works, we do this in college to allow us to
have a separate subnet for each room of machines. We have servers on 192.168.0.x, domain admins on
192.168.200.x, printers on 192.168.100.x and so on.

It also makes it quite easy to setup egress rules on firewalls etc.

Brian

------------------------------------------------------------------------------------------------
    The views expressed here are my own and not necessarily


                the views of Portsmouth College