NASLite Network Attached Storage

Hi Tony,

I have what seems to be a simple problem:

at home I have a NASLite+ box using subnet 192.168.50.x/255.255.255.0

at work I have a subnet of 192.168.0.x/255.255.255.0

these two networks are connected via an IPSEC tunnel.

When I try to access the NASLite+ box from a computer at work, I get no response (even when pinging)

If I PPTP into my home network from work I CAN access the NASLIte+ box but this is because PPTP server gives up an IP address whereas IPSEC doesn't.

I was wondering if it was possible to give the NASLite+ box a default gateway (which, in this case is also the IPSEC tunnel endpoint) ???

NMB log excerpt:

[2005/03/10 15:40:33, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable
[2005/03/10 15:40:42, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable
[2005/03/10 15:40:46, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable
[2005/03/10 15:40:51, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(137) ERRNO=Network is unreachable
[2005/03/10 15:40:51, 0] nmbd/nmbd_packets.c:reply_netbios_packet(965)
reply_netbios_packet: send_packet to IP 192.168.0.149 port 137 failed
[2005/03/10 15:43:01, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable
[2005/03/10 15:43:10, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable
[2005/03/10 15:43:14, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable
[2005/03/10 16:06:20, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable
[2005/03/10 16:06:24, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable
[2005/03/10 16:06:28, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.0.149(138) ERRNO=Network is unreachable


Thanks

-Hankster-

Currently, NASLite+ does not support a default gateway setting.

I have found there are a number of "extras" that I would like to see on Naslite but at the end of the day it does exactly what it says on the tin, its not like it says it has raid support and doesn't or has the ability to support a default gateway and doesn't. Any of the suggested extras that are mentioned in the forums would be great if they get to be included in future builds but this system was designed for home/small business use as a network attached storage facility, if you need a full server OS then I think Mr Gates has one you can buy for about £500 and if you have a large business network then I'm not sure naslite is really the correct product

I have to agree.

NASLite is not really suitable for a corporate environment due to its lack of security.

I live for network security (both work and play) and I can say from real world experince that most of the time a client has a breach it is actually an employee through mistake or malice.

Not having a default gateway reduces the risk of NASLite being deployed in an environment it is not designed for.

OK so you could put lots of disclaimers all over the place but what would happen is that someone would do it anyway and then when they were hacked the NAS team would have to live with the bad press associated with it. Unfortunately thats just a fact of life

can you map the network drive using a computer on the subnet that CAN access Naslite, then share that mapped drive across the network so it can be picked up from the other subnet over the VPN?

you sure could

(From a newbie) I tried this setup to test this very idea, but couldn't get that to work. I am using Windows XP, connected to my regular network with one NIC and connected to a test NASLite on another NIC. I can map the drive, but cannot share the mapped drive in Windows. What am I doing wrong (besides using Windows). BTW, I am using NASLiteSMB.

Thanks,
Dave