August 2006 - WLUG - wlug.mailman3.com

Re: [Wlug] storrage suggestion

by Karl Hiramoto

John Stoffel wrote: > Karl> * >= 5TB disk space > Karl> * iSCSI, ATA over Ethernet, or NFS mountable to linux >= 2.6.15 > > Karl> *RAID (must survive single disk failure) and must know when a failure > Karl> happened. > > Let me recommend RAID6 to you as well. > > Karl> * $$/TB is important. > > The most important? > $10K is probably the upper limit. > Karl> * Must be able to sustain minimum 10MB/s disk read on Gbit > Karl> network. normally these will be big multimedia files. > > That's *slow*, are you sure you didn't drop an order of magnitude > here? > > Yes I don't need that much speed, but need a lot of space. In reality most solutions out there will have much higher speeds. > Karl> Yes, i know i can buy a linux PC, and slap in 11 or more 500 GB > Karl> disks and do this RAID5. Something off the shelf, and easy to > Karl> service would be nice. > > It's all a question of budget. Getting a box with a bunch of 3ware > controllers talking to SATA drives in hot-swap bays might be the > ticket. You'll get decent performance too, though not stellar. > Software RAID can be faster, but the 3ware can/should insulate you > from the hardware hot-swap issues. > > Should. > > Take a look at JetStor, or the ATAbeast boxes. They were around > $14k/2Tb three years ago, so they must be cheaper/better now. > > Thanks for those ideas. I also found coraid to be reasonably priced. http://coraid.com/products.html > What about backups? > No, need for backups, as this data is from other sources (mainly DVD, CD) , and could be restored from original media. -- -- Karl Hiramoto http://karl.hiramoto.org/

Aug. 22, 2006

Re: [Wlug] storrage suggestion

by John Stoffel

Karl> * >= 5TB disk space Karl> * iSCSI, ATA over Ethernet, or NFS mountable to linux >= 2.6.15 Karl> *RAID (must survive single disk failure) and must know when a failure Karl> happened. Let me recommend RAID6 to you as well. Karl> * $$/TB is important. The most important? Karl> * Must be able to sustain minimum 10MB/s disk read on Gbit Karl> network. normally these will be big multimedia files. That's *slow*, are you sure you didn't drop an order of magnitude here? Karl> Yes, i know i can buy a linux PC, and slap in 11 or more 500 GB Karl> disks and do this RAID5. Something off the shelf, and easy to Karl> service would be nice. It's all a question of budget. Getting a box with a bunch of 3ware controllers talking to SATA drives in hot-swap bays might be the ticket. You'll get decent performance too, though not stellar. Software RAID can be faster, but the 3ware can/should insulate you from the hardware hot-swap issues. Should. Take a look at JetStor, or the ATAbeast boxes. They were around $14k/2Tb three years ago, so they must be cheaper/better now. What about backups? John

Aug. 22, 2006

storrage suggestion

by Karl Hiramoto

Anyone have suggestions? i need: * >= 5TB disk space * iSCSI, ATA over Ethernet, or NFS mountable to linux >= 2.6.15 *RAID (must survive single disk failure) and must know when a failure happened. * $$/TB is important. * Must be able to sustain minimum 10MB/s disk read on Gbit network. normally these will be big multimedia files. Yes, i know i can buy a linux PC, and slap in 11 or more 500 GB disks and do this RAID5. Something off the shelf, and easy to service would be nice. -- Karl Hiramoto http://karl.hiramoto.org/

Aug. 22, 2006

Re: [Wlug] router/printing problems

by Justin Odom

Is there any particular reason you are using a 2 router setup? (other than the provided wireless router has poor range?) You could just plug one of the switch ports on the linksys into a switch port on the actiontek and use the linksys as a wap. 2. In gateway setting, all traffic passing from your linksys to the actiontek router is being nat'd through 192.168.1.20. In router mode, all traffic is passing through with its native 192.168.2.0/24 addresses. I think you will have to set up a static route on the actiontek to get the 192.168.2.0/24 to be nat'd out. What does the routing table on the actiontek look like right now? Justin On 8/22/06, Bill Mills-Curran <bill(a)mills-curran.net> wrote: > Thanks for all the suggestions from the group. > > There were several requests for a more clear description of the > setup. Here it is: > > > Verizon FIOS DSL <=> > Actiontek router (192.168.1.1) <=> > LinkSys router (192.168.1.20 <=> 192.168.2.1) > > Linux box (with samba printer): 192.168.1.14 > > windows box (needing to print): 192.168.2.200 > > The fix: > 1. Enable printing from 192.168.2.x in the samba setup. (I'm not > sure that helped, because the LinkSys router was set up as a > gateway, thus the print request showed up from 192.168.1.20.) > > 2. Set up a route to the 192.168.2.x network on my linux box. > > 3. Lots of mucking around with the LinkSys. I also opened it up to > all outside access. I also set "dynamic routing". > > 4. Whacked at the windows box quite a bit. It finally (magically?) > started working. > > Unresolved questions: > > 1. What did I do to make it work? > > 2. Why do I need to keep the LinkSys set with the "gateway" rather > than the "router" setting? If I set "router", then I can access > between the 2 networks nicely, but the 192.168.2.x will not route > to the internet. Maybe I needed a static route? > > It would be nice to understand what was the key. I'd also like to > understand how to set the LinkSys as a router rather than a gateway, > but at least it works and my wife is no longer reminding me how much > linux messes things up. :-) > > Thanks, > Bill > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Aug. 22, 2006

Re: [Wlug] router/printing problems

by Bill Mills-Curran

Thanks for all the suggestions from the group. There were several requests for a more clear description of the setup. Here it is: Verizon FIOS DSL <=> Actiontek router (192.168.1.1) <=> LinkSys router (192.168.1.20 <=> 192.168.2.1) Linux box (with samba printer): 192.168.1.14 windows box (needing to print): 192.168.2.200 The fix: 1. Enable printing from 192.168.2.x in the samba setup. (I'm not sure that helped, because the LinkSys router was set up as a gateway, thus the print request showed up from 192.168.1.20.) 2. Set up a route to the 192.168.2.x network on my linux box. 3. Lots of mucking around with the LinkSys. I also opened it up to all outside access. I also set "dynamic routing". 4. Whacked at the windows box quite a bit. It finally (magically?) started working. Unresolved questions: 1. What did I do to make it work? 2. Why do I need to keep the LinkSys set with the "gateway" rather than the "router" setting? If I set "router", then I can access between the 2 networks nicely, but the 192.168.2.x will not route to the internet. Maybe I needed a static route? It would be nice to understand what was the key. I'd also like to understand how to set the LinkSys as a router rather than a gateway, but at least it works and my wife is no longer reminding me how much linux messes things up. :-) Thanks, Bill

Aug. 22, 2006

Mailing List with web post interface

by Michael Zarozinski

Does anyone know of a mailing list package that allows you to post via a web form along with the standard email interface?

Aug. 21, 2006

Re: [Wlug] router/printing problems

by Jared Greenwald

To my knowledge, that is the case. I had a previous configuration that involved wireless and wired. I didn't have anything to broadcast wireless other than my linksys wireless router, but I didn't want to use that as the outside-facing router, so that I could have more control than just the NAT the linksys provided. Anyway, I ended up with a strange configuration. On the router Linux box, I had three NICs: one outward facing, one that serves 192.168.1.x, and one that serves 192.168.2.x. The .1.x network is my main network on which I run a fixed-address dhcp as well as local dns and share my printers. The NIC that served the 1.x network was plugged into a switch that services the rest of the house. The 2.x network is kinda tricky. This network was only connected directly to the WAN port of the linksys - so the linksys was "thinking" that it was doing stuff (explaination follows). On the linksys, all forwarding and dhcp was turned off (dhcp is served from the Linux router). What I did was put a crossover cable from one of the switch ports on the router directly to the switch that was serving the 1.x network. This allows any client (wired or wireless) to connect directly to the 1.x network without ever having to deal with the 2.x private network and the effect is that the linksys is an access point without being an access point. It also allows me to share printers and drives across mac/windows/linux (I have all three) without crossing over subnets. (The main reason for me doing this is that its more cost effective usually since routers can usually be found on sale for $30, while access points are usually $100+.) I've recently replaced the router with a straight access point, thus eliminating the need for the 2.x network. I can furnish a diagram upon request. -Jared On 8/21/06, Bill Smith <wsmith(a)chezsmith.com> wrote: > On Sun, 20 Aug 2006 22:41:17 -0400, Bill Mills-Curran wrote: > > >I have a home network with 2 routers. > > > >My 192.168.2.x network has a couple of windows boxes (some wireless) > >behind a linkSys router. This network feeds to my 192.168.1.x network > >which connects to the internet through a second router. My linux box > >(samba print server) is on the 192.168.1.x network and has a static > >IP. I just moved to this setup when I got Verizon FIOS. (Their > >wireless router has poor range.) > > > >Problem. Since moving, I can't print to the samba-served printer from > >the windows boxes. I have modified samba to accept connections from > >the 192.168.2.x machines. Here's my samba log for the machine that > >tries to print. > > I might well be mistaken, but don't Windows systems have to be on the > same network to interact with each other? > > If that is indeed the case, then the Windows systems won't be able to > work with the Samba server very easily. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > William Smith wsmith-at-chezsmith-dot-com > Fall River, MA http://www.chezsmith.com > > "For every complex problem, there is an answer which is > short, simple and wrong." -- H.L. Mencken > * TAG! v3.2 * > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > > >

Aug. 21, 2006

Re: [Wlug] router/printing problems

by Bill Smith

On Sun, 20 Aug 2006 22:41:17 -0400, Bill Mills-Curran wrote: >I have a home network with 2 routers. > >My 192.168.2.x network has a couple of windows boxes (some wireless) >behind a linkSys router. This network feeds to my 192.168.1.x network >which connects to the internet through a second router. My linux box >(samba print server) is on the 192.168.1.x network and has a static >IP. I just moved to this setup when I got Verizon FIOS. (Their >wireless router has poor range.) > >Problem. Since moving, I can't print to the samba-served printer from >the windows boxes. I have modified samba to accept connections from >the 192.168.2.x machines. Here's my samba log for the machine that >tries to print. I might well be mistaken, but don't Windows systems have to be on the same network to interact with each other? If that is indeed the case, then the Windows systems won't be able to work with the Samba server very easily. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- William Smith wsmith-at-chezsmith-dot-com Fall River, MA http://www.chezsmith.com "For every complex problem, there is an answer which is short, simple and wrong." -- H.L. Mencken * TAG! v3.2 *

Aug. 21, 2006

Re: [Wlug] router/printing problems

by Christoph

How are the networks configured? subnet mask, broadcast, routes, etc... what devices deliver dhcp, and what clients use it? How are the routers configured? Route/Bridge? My hunch... you need a static route for 192.168.2.x on the Linux box since it's default route probably points towards the internet. Or, put the static route on the main (other) router. That probably makes more sense... Just guessing though. -cfd On Sun, 2006-08-20 at 22:48 -0400, Bill Mills-Curran wrote: > On Sun, Aug 20, 2006 at 10:41:17PM -0400, Bill Mills-Curran wrote: > > Date: Sun, 20 Aug 2006 22:41:17 -0400 > > From: Bill Mills-Curran <bill(a)mills-curran.net> > > To: Worcester Linux Users Group <wlug(a)wlug.org>, BLU Discuss <discuss(a)blu.org> > > Cc: > > Subject: router/printing problems > > Precedence: list > > > > I have a home network with 2 routers. > > > > My 192.168.2.x network has a couple of windows boxes (some wireless) > > behind a linkSys router. This network feeds to my 192.168.1.x network > > which connects to the internet through a second router. My linux box > > (samba print server) is on the 192.168.1.x network and has a static > > IP. I just moved to this setup when I got Verizon FIOS. (Their > > wireless router has poor range.) > > > > Problem. Since moving, I can't print to the samba-served printer from > > the windows boxes. I have modified samba to accept connections from > > the 192.168.2.x machines. Here's my samba log for the machine that > > tries to print. > > > > [2006/08/20 04:02:21, 1] smbd/server.c:open_sockets_smbd(353) > > Reloading services after SIGHUP > > [2006/08/20 22:17:10, 0] smbd/server.c:main(798) > > smbd version 3.0.14a-2 started. > > Copyright Andrew Tridgell and the Samba Team 1992-2004 > > [2006/08/20 22:27:29, 0] tdb/tdbutil.c:tdb_log(725) > > tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 > > at offset=175296 > > [2006/08/20 22:28:09, 0] tdb/tdbutil.c:tdb_log(725) > > tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 > > at offset=175296 > > > > Any suggestions? > > > > TIA, > > Bill > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > _______________________________________________ > > Discuss mailing list > > Discuss(a)blu.org > > http://olduvai.blu.org/mailman/listinfo/discuss > > > The previous was the smbd.log. Here's the one for the client > 192.168.1.153.log: > > [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) > getpeername failed. Error was Transport endpoint is not connected > [2006/08/20 22:27:25, 0] lib/access.c:check_access(328) > [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) > getpeername failed. Error was Transport endpoint is not connected > Denied connection from (0.0.0.0) > [2006/08/20 22:27:25, 1] smbd/process.c:process_smb(1084) > [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) > getpeername failed. Error was Transport endpoint is not connected > Connection denied from 0.0.0.0 > [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket_data(430) > write_socket_data: write failure. Error = Connection reset by peer > [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket(455) > write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection > reset by > peer > [2006/08/20 22:27:25, 0] lib/util_sock.c:send_smb(647) > Error writing 5 bytes to client. -1. (Connection reset by peer) > [2006/08/20 22:28:32, 0] tdb/tdbutil.c:tdb_log(725) > tdb(/var/cache/samba/printing/hp.tdb): rec_free_read bad magic > 0x42424242 at offset=673736 > > Bill >

Aug. 21, 2006

Re: [Wlug] router/printing problems

by Bill Mills-Curran

On Sun, Aug 20, 2006 at 10:41:17PM -0400, Bill Mills-Curran wrote: > Date: Sun, 20 Aug 2006 22:41:17 -0400 > From: Bill Mills-Curran <bill(a)mills-curran.net> > To: Worcester Linux Users Group <wlug(a)wlug.org>, BLU Discuss <discuss(a)blu.org> > Cc: > Subject: router/printing problems > Precedence: list > > I have a home network with 2 routers. > > My 192.168.2.x network has a couple of windows boxes (some wireless) > behind a linkSys router. This network feeds to my 192.168.1.x network > which connects to the internet through a second router. My linux box > (samba print server) is on the 192.168.1.x network and has a static > IP. I just moved to this setup when I got Verizon FIOS. (Their > wireless router has poor range.) > > Problem. Since moving, I can't print to the samba-served printer from > the windows boxes. I have modified samba to accept connections from > the 192.168.2.x machines. Here's my samba log for the machine that > tries to print. > > [2006/08/20 04:02:21, 1] smbd/server.c:open_sockets_smbd(353) > Reloading services after SIGHUP > [2006/08/20 22:17:10, 0] smbd/server.c:main(798) > smbd version 3.0.14a-2 started. > Copyright Andrew Tridgell and the Samba Team 1992-2004 > [2006/08/20 22:27:29, 0] tdb/tdbutil.c:tdb_log(725) > tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 > at offset=175296 > [2006/08/20 22:28:09, 0] tdb/tdbutil.c:tdb_log(725) > tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 > at offset=175296 > > Any suggestions? > > TIA, > Bill > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > Discuss mailing list > Discuss(a)blu.org > http://olduvai.blu.org/mailman/listinfo/discuss The previous was the smbd.log. Here's the one for the client 192.168.1.153.log: [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2006/08/20 22:27:25, 0] lib/access.c:check_access(328) [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0) [2006/08/20 22:27:25, 1] smbd/process.c:process_smb(1084) [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection reset by peer [2006/08/20 22:27:25, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [2006/08/20 22:28:32, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/hp.tdb): rec_free_read bad magic 0x42424242 at offset=673736 Bill

Aug. 21, 2006