- WLUG - wlug.mailman3.com

Re: [Wlug] ALSA - mic trouble

by Jamie Guinan

On Sat, 26 Aug 2006, Eric Stein wrote: > >> Send output of "amixer". > eastein@pippin:~$ amixer <snip> > Simple mixer control 'Mic',0 > Capabilities: pvolume pvolume-joined pswitch pswitch-joined cswitch am> cswitch-joined cswitch-exclusive > Capture exclusive group: 0 > Playback channels: Mono > Capture channels: Front Left - Front Right > Limits: Playback 0 - 31 > Mono: Playback 27 [87%] [off] > Front Left: Capture [on] > Front Right: Capture [on] That's what I was looking for, but it looks Ok. What do the GUI mixers look like? gnome-volume-control, aumix, etc. Can you send a screen shot? It *could* be hardware. I had a line-in port fail on a PC recently. -Jamie

Sept. 3, 2006

bacula

by Mike Leo

Someone at the cook-out mentioned they were using bacula for backups. I have just installed it and I have a DLT tape drive. I have it confugered OK and i can connect to my fd (client) and my sd (storage device). To keep things simple, lets say that I am doing everything on one server. I can label the tapes and even backup to my "File" device. My question is, what/where do I build a list of jobs to run? Lets say I want a "Full" backup of the system, and a seperate backup of just /home. Where do these jobs get defined, etc etc etc. This seems to be the only piece I am missing in the doc's. thanks mike

Sept. 3, 2006

Re: [Wlug] iptables use of --mac-source

by John Stoffel

Frank> On Fri, Sep 01, 2006 at 10:40:25AM -0400, John Stoffel wrote: >> This will only work if you have a bridged network, once you have a >> switch in the way, the MAC address will change. This is because Frank> Nope - a switch is logically identical to a bridge with more Frank> than two ports. A packet forwarded by a router will have the Frank> routers MAC address because the router has to generate a new Frank> ethernet frame with the same ethernet payload as the original Frank> packet, while a switch will blindly forward the packet to Frank> wherever it's FDB tells it to. Details details... don't confuse me with facts! *grin* You're right of course. >> For network switches, each port has it's own MAC address. Basically, Frank> Only if the switch supports spanning tree, and only for Frank> spanning tree - those per-port MACs aren't used for anything Frank> else. Yup, that's the details I mis-remembered. Then again, who pays attention to this stuff any more? *grin* John

Sept. 2, 2006

Re: [Wlug] iptables use of --mac-source

by Frank Sweetser

On Fri, Sep 01, 2006 at 10:40:25AM -0400, John Stoffel wrote: > This will only work if you have a bridged network, once you have a > switch in the way, the MAC address will change. This is because Nope - a switch is logically identical to a bridge with more than two ports. A packet forwarded by a router will have the routers MAC address because the router has to generate a new ethernet frame with the same ethernet payload as the original packet, while a switch will blindly forward the packet to wherever it's FDB tells it to. > For network switches, each port has it's own MAC address. Basically, Only if the switch supports spanning tree, and only for spanning tree - those per-port MACs aren't used for anything else. -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC

Sept. 1, 2006

Re: [Wlug] iptables use of --mac-source

by John Stoffel

Andy> I'm playing with my firewall rules, trying to setup a rule that Andy> will recognize my laptop's mac address on an incoming Andy> connection. Andy> iptables -I INPUT -m mac --mac-source uu:vv:ww:xx:yy:zz -j LOG Andy> - --log-prefix "Laptop Detected: " This will only work if you have a bridged network, once you have a switch in the way, the MAC address will change. This is because you're looking at the low level packets, where the MAC addresses gets re-written to reflect the next hop device that the packet needs to goto to get off the local network segment. Note, this is purely a low level ethernet issue, not an IP issue. Andy> That worked fine. I saw the appropriate log entry when my Andy> laptop ping'd the firewall. The log entry showed the expected Andy> mac address of my laptop. At that time, my laptop was plugged Andy> into my home network, which is connected to the "internal" Andy> interface of my firewall. Andy> I then setup iptables to log all incoming packets from the Andy> firewall's external interface, and I noticed that in the log all Andy> incoming mac source addresses are the same. I didn't expect Andy> this. The address is 00:0b:bf:xx:xx:xx, which I think is a Andy> piece of Cisco hardware, and I don't have any Cisco hardware at Andy> home. Is this some hardware from my ISP ? Yup, it's the MAC address of the upstream ethernet device. Basically, all packets are sent to that MAC address when they go off your network. Basically, what happens is that when you try to goto a new IP address (or when a new IP address attempts to contact you), the low level ethernet stack sends out an ARP (Address Resolution Protocol) request, saying "Who has this IP?" and waiting for a response from some other device. Be-it a bridge, a switch, an actual host, or whatever. This is how the low level ethernet knows where to forward packets within it's network segment. Each hub has just a single MAC address for all it's ports. A computer should have a unique MAC address for each ethernet port, though Suns didn't do this for a long time. The idea was that you couldn't put two seperate interfaces on the same network, since it caused problems. Obviously this was also on bridged networks, not swiched ones, which are the standard today. For network switches, each port has it's own MAC address. Basically, every device on a network (low level, physical medium) has to have a unique MAC address, otherwise you run into problems. This is layer 2 stuff. Layer 1 is the physical media. TCP/IP are layers 3 and 4 respectively. Hopefully this helps. I know I've skipped some details here. John

Sept. 1, 2006

Re: [Wlug] iptables use of --mac-source

by Justin Odom

Andy, MAC Addresses work at layer 2. When a router receives a packet, it strips off the mac addresses, looks at its destination, appends its own mac addresses, and forwards out the appropriate interface. The MAC your seeing is probably your ISP's router. On 8/31/06, Andy Stewart <andystewart(a)comcast.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > HI everybody, > > I'm playing with my firewall rules, trying to setup a rule that will > recognize my laptop's mac address on an incoming connection. > > I tried this: > > iptables -I INPUT -m mac --mac-source uu:vv:ww:xx:yy:zz -j LOG > - --log-prefix "Laptop Detected: " > > That worked fine. I saw the appropriate log entry when my laptop ping'd > the firewall. The log entry showed the expected mac address of my > laptop. At that time, my laptop was plugged into my home network, which > is connected to the "internal" interface of my firewall. > > I then setup iptables to log all incoming packets from the firewall's > external interface, and I noticed that in the log all incoming mac > source addresses are the same. I didn't expect this. The address is > 00:0b:bf:xx:xx:xx, which I think is a piece of Cisco hardware, and I > don't have any Cisco hardware at home. Is this some hardware from my ISP ? > > I'm guessing somebody is rewriting the packets to replace the source mac > address, but clearly my knowledge of this is lacking, and thus I'm > confused. Any helpers? > > Thanks, > > Andy > > - -- > Andy Stewart, Founder > Worcester Linux Users' Group > Worcester, MA, USA > http://www.wlug.org > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (GNU/Linux) > Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org > > iD8DBQFE95kJHl0iXDssISsRAmcUAJ4zD1PDX+TmZca7gzdmtvf7DwWgxACfUH4B > 3awkKwfmcBN7nmu/WXjsre4= > =6u9G > -----END PGP SIGNATURE----- > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Sept. 1, 2006

iptables use of --mac-source

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI everybody, I'm playing with my firewall rules, trying to setup a rule that will recognize my laptop's mac address on an incoming connection. I tried this: iptables -I INPUT -m mac --mac-source uu:vv:ww:xx:yy:zz -j LOG - --log-prefix "Laptop Detected: " That worked fine. I saw the appropriate log entry when my laptop ping'd the firewall. The log entry showed the expected mac address of my laptop. At that time, my laptop was plugged into my home network, which is connected to the "internal" interface of my firewall. I then setup iptables to log all incoming packets from the firewall's external interface, and I noticed that in the log all incoming mac source addresses are the same. I didn't expect this. The address is 00:0b:bf:xx:xx:xx, which I think is a piece of Cisco hardware, and I don't have any Cisco hardware at home. Is this some hardware from my ISP ? I'm guessing somebody is rewriting the packets to replace the source mac address, but clearly my knowledge of this is lacking, and thus I'm confused. Any helpers? Thanks, Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFE95kJHl0iXDssISsRAmcUAJ4zD1PDX+TmZca7gzdmtvf7DwWgxACfUH4B 3awkKwfmcBN7nmu/WXjsre4= =6u9G -----END PGP SIGNATURE-----

Sept. 1, 2006

My memory leak problem from last week.

by ken jones

I have moved from mozilla mail and mozilla browser to thunderbird mail and firefox browser. The memory leak problem seems to have either gone away completely or greatly been reduced. Interesting... thanks for the suggestions and help. Ken Jones

Aug. 28, 2006

Re: [Wlug] ALSA - mic trouble

by Eric Stein

Jamie Guinan wrote: > Hi, > > What kind of Mic is it? Some of mine have a small battery, and an > on/off switch, which I tend to forget "on". > > Have you tried other mics? > Non-USB - the kind that just plugs into the sound card like headphones. It never had batteries or a switch. My roommate's mic doesn't work either - it's part of a headset, but doesn't require power either. >> Info: Ubuntu Breezy 5.10 >> Linux pippin 2.6.12-10-386 #1 Tue Jul 18 22:08:27 UTC 2006 i686 GNU/Linux >> >> I'm prepared to spend a good deal of time on this, but I don't know what >> I need to do. If you need more information, let me know how to get it >> and I'll be happy to share it. >> Send output of "amixer". eastein@pippin:~$ amixer Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 27 [87%] [on] Front Right: Playback 27 [87%] [on] Simple mixer control 'Master Mono',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 31 Mono: Playback 0 [0%] [on] Simple mixer control 'PCM',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 28 [90%] [on] Front Right: Playback 28 [90%] [on] Simple mixer control 'Surround',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 0 [0%] [on] Front Right: Playback 0 [0%] [on] Simple mixer control 'Surround Jack Mode',0 Capabilities: Mono: Simple mixer control 'Center',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 31 Mono: Playback 27 [87%] [on] Simple mixer control 'LFE',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 31 Mono: Playback 0 [0%] [on] Simple mixer control 'Line',0 Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 27 [87%] [off] Capture [off] Front Right: Playback 27 [87%] [off] Capture [off] Simple mixer control 'CD',0 Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 27 [87%] [on] Capture [off] Front Right: Playback 27 [87%] [on] Capture [off] Simple mixer control 'Mic',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Mono Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Playback 27 [87%] [off] Front Left: Capture [on] Front Right: Capture [on] Simple mixer control 'Mic Boost (+20dB)',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Mic Select',0 Capabilities: Mono: Simple mixer control 'Video',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Front Left - Front Right Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'Phone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Mono Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Playback 27 [87%] [off] Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined cswitch cswitch-joined Playback channels: Mono Capture channels: Mono Mono: Playback [on] Capture [on] Simple mixer control 'IEC958 Playback AC97-SPSA',0 Capabilities: volume volume-joined Playback channels: Mono Limits: 0 - 3 Mono: 3 [100%] Simple mixer control 'PC Speaker',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 15 Mono: Playback 15 [100%] [on] Simple mixer control 'Aux',0 Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 27 [87%] [off] Capture [off] Front Right: Playback 27 [87%] [off] Capture [off] Simple mixer control 'Mono Output Select',0 Capabilities: Mono: Simple mixer control 'Capture',0 Capabilities: cvolume cswitch cswitch-joined Capture channels: Front Left - Front Right Limits: Capture 0 - 15 Front Left: Capture 13 [87%] [off] Front Right: Capture 13 [87%] [off] Simple mixer control 'Mix',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Front Left - Front Right Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'Mix Mono',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Front Left - Front Right Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'Channel Mode',0 Capabilities: Mono: Simple mixer control 'Duplicate Front',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'External Amplifier',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] eastein@pippin:~$ > Also, what kind of sound chip/card? Onboard? Add-in PCI? eastein@pippin:~$ lspci|grep audio 0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) eastein@pippin:~$ I hope this is enough to tip you off as to what's wrong... Eric

Aug. 26, 2006

Re: [Wlug] ALSA - mic trouble

by Jamie Guinan

On Fri, 25 Aug 2006, Eric Stein wrote: > Hi, > > When I first set up my Ubuntu machine, everything worked fine. But for > the last few months (I don't remember exactly how long), my mic has > refused to work. Nothing I use can pick up any signal from it. I've > tried all the mixers (alsamixer, kmix, the built in GNOME mixer), and > none of them show the mic as muted. Is there a way to reset ALSA's > volumes and other mixer settings to defaults? I can't seem to find > information about this online, and this lack of a fully working sound > system has me on the end of my rope. Hi, What kind of Mic is it? Some of mine have a small battery, and an on/off switch, which I tend to forget "on". Have you tried other mics? > Info: Ubuntu Breezy 5.10 > Linux pippin 2.6.12-10-386 #1 Tue Jul 18 22:08:27 UTC 2006 i686 GNU/Linux > > I'm prepared to spend a good deal of time on this, but I don't know what > I need to do. If you need more information, let me know how to get it > and I'll be happy to share it. Send output of "amixer". Also, what kind of sound chip/card? Onboard? Add-in PCI? -Jamie > Eric

Aug. 26, 2006

ALSA - mic trouble

by Eric Stein

Hi, When I first set up my Ubuntu machine, everything worked fine. But for the last few months (I don't remember exactly how long), my mic has refused to work. Nothing I use can pick up any signal from it. I've tried all the mixers (alsamixer, kmix, the built in GNOME mixer), and none of them show the mic as muted. Is there a way to reset ALSA's volumes and other mixer settings to defaults? I can't seem to find information about this online, and this lack of a fully working sound system has me on the end of my rope. Info: Ubuntu Breezy 5.10 Linux pippin 2.6.12-10-386 #1 Tue Jul 18 22:08:27 UTC 2006 i686 GNU/Linux I'm prepared to spend a good deal of time on this, but I don't know what I need to do. If you need more information, let me know how to get it and I'll be happy to share it. Eric

Aug. 26, 2006

My memory leak problem.

by ken jones

Everyone: It is hard to believe that X is the problem. It came with Fedora 4 and no one else seems to be reporting it as a bug. I have another Fedora 4 machine that does not display this swap space problem. Karl's idea of looking carefully at my drivers is a good one. This machine has more than one special driver. It is late now. I am tired. I shall pursue this track tomorrow or Friday. If anyone else is interested in the cut and paste of ps auxw lspci uname -a lsmod vmstat dmesg tell me. I will send you a copy. Thank you all:-) Ken Jones Thank you.

Aug. 24, 2006

Re: [Wlug] Problem with xosview SWAP space.

by Karl Hiramoto

ken jones wrote: > Karl: I hesitate to send this big message to the whole gang. > Attached are the results of your suggestion. Thank you in advance. > Ken Jones > > [root@kjones-fedora kjones]# ps auxw > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > root 3252 51.6 41.7 435956 215064 ? S Aug18 3719:53 /usr/X11R6/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0 > Well it seems most of your memory is used up by the X process. Keep watching this process if it's memory size grows then there may be a memory leak eating up your memory.. I'm not a fedora expert, are there any X updates? have you run yum or updated your system? What version of X are they using? perhaps send your /var/log/xorg.0.log [root@kjones-fedora kjones]# lspci 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro] 01:00.1 Display controller: ATI Technologies Inc Radeon R300 [Radeon 9500 Pro] (Secondary) I see you have an ATI graphics card. Do you know what video driver you are using? perhaps there is a problem there.

Aug. 23, 2006

Re: [Wlug] Problem with xosview SWAP space.

by Andre Lehovich

--- ken jones <kjones(a)ziplink.net> wrote: > I have been running Fedora Core 4 for at least a year. > It has theproblem of slow consumption of swap space - see graphic. The graphic didn't come through here. I bet you're using a binary-blob kernel module (e.g. Nvidia) which is making your system crash. The other possibility is you have an app with a memory leak, using 'ps avx' would help diagnose that. --Andre __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Aug. 23, 2006

Re: [Wlug] Problem with xosview SWAP space.

by Karl Hiramoto

ken jones wrote: > I have been running Fedora Core 4 for at least a year. It has the > problem of slow consumption of swap space - see graphic. After a week > or two it runs out and LINUX crashes. > > I have found no help in GOOGLE which surprises me. Did I install > incorrectly? What do you all think? > I would guess you have a memory leak in an application, kernel, or kernel driver module. Should be able to see what the cause is. send us more info on your system do these commands and paste us the results: ps auxw lspci uname -a lsmod vmstat dmesg

Aug. 23, 2006

Problem with xosview SWAP space.

by ken jones

Aug. 23, 2006

Re: [Wlug] storrage suggestion

by Karl Hiramoto

Doug Mildram wrote: >>> i know i can buy a linux PC, and slap in 11 or more 500 GB disks and do >>> > this RAID5. > > doug> Hate to disrespect our beloved wlug-favorite-OS, but, > Linux for NFS server may be a bad choice....a bad implementation, > I say from 2.4-kernel experience and I dont THINK it improved in 2.6. > (have you used linux NFS server in demanding/loaded situations? > ...the linux load avg goes to 20 as it becomes useless.) I have setup a few servers with 1TB, 1.5TB and 2TB doing NFS, mainly for video streaming and at most 15-20 NFS clients. Using kernel 2.6.15.7 for a while now with no performance complaints. I have seen 15 NFS clients streaming DVD quality mpeg2 video (9mbps) work nicely. Getting over 2TB, tho starts to be a lot of disks and there are heat problems, also problems finding enough drive bays. -- Karl Hiramoto http://karl.hiramoto.org/

Aug. 22, 2006

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