May 2001 - WLUG - wlug.mailman3.com

Re: [Wlug] Upcoming meetings - topic proposals

by Scott Venier

A VPN is a good idea. PPTP, however, isn't. I highly recomend using some other VPN setup, if at all possible. PPTP on linux doesn't excatly give you a rock solid network conneciton. But, if you have no other options, there are both a client and a server for linux. The server is called PoPToP. Search freshmeat for it. The client lives at http://merced.needsabeating.com/pptp.html. Scott Maintainter of the PPTP-Linux client. On Mon, 7 May 2001, Tom Martinson wrote: > Hello. > > I am new to this LUG. So I would like to say hello. > > Peter said that his wife has to connect to his SaMBa server from UMass. > > When I have had similar situations What I did was to setup a VPN using > PPTP. That way you can block All SMB traffic to the outside world. > Connect to the PPTP termination point with your client. Setup up the > Tunnel and then the SMB information is passed on the inside of the > tunnel. Thus keeping the integrity. Also this gives a smaller > "signature" for your firewall/server to the real world. > > Just a though. > > Peter Gutowski wrote: > > > Well, so far it's not been a problem, although I keep a close watch on suspicious activity. (You'll notice entries for hosts allow and hosts deny. So far that seems to be pretty effective, although I do notice twits trying to access and being denied): > > > > hosts allow = 192.168.3.0/255.255.255.224 192.168.2.0/255.255.255.0 > > 128.119.216.0/255.255.255.0 216.175.212.192/255.255.255.240 > > hosts deny = all # <- no other machines can access > > > > Perhaps you could suggest conf options that allows [incoming] connections, but don't broadcast availability (i.e. is 'invicible' to all but people that know that that machine is a smb server). As I said, I'm not samba expert! (BTW, my wife accesses the system from her computer at UMass) > > > > On Monday, May 7, 2001 11:01 AM, Keller, Tim <Tim.Keller(a)stratus.com> wrote: > > > >> Hey I was looking at the sample smb.conf file (and I've set up a bunch of > >> samba servers as well) and I saw something odd (well odd for > >> me) > >> > >> -- start cut -- > >> # Configure Samba to use multiple interfaces > >> # If you have multiple network interfaces then you must list them > >> # here. See the man page for details. > >> interfaces = 192.168.3.1 24.91.122.146 > >> -- end cut -- > >> > >> >From a home network point of view, why would you want samba to bind to your > >> external (24.xx...) address? Maybe I'm doing something wrong? > >> > >> I personally add rules to my firewall to block outgoing and incoming SMB > >> traffic to the outside world. SMB as a protocol goes (if you could call it > >> that) tends to tell the world more then one would want... > >> > >> Tim. > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 7, 2001

Re: [Wlug] Upcoming meetings - topic proposals

by Peter Gutowski

Well, so far it's not been a problem, although I keep a close watch on suspicious activity. (You'll notice entries for hosts allow and hosts deny. So far that seems to be pretty effective, although I do notice twits trying to access and being denied): hosts allow = 192.168.3.0/255.255.255.224 192.168.2.0/255.255.255.0 128.119.216.0/255.255.255.0 216.175.212.192/255.255.255.240 hosts deny = all # <- no other machines can access Perhaps you could suggest conf options that allows [incoming] connections, but don't broadcast availability (i.e. is 'invicible' to all but people that know that that machine is a smb server). As I said, I'm not samba expert! (BTW, my wife accesses the system from her computer at UMass) On Monday, May 7, 2001 11:01 AM, Keller, Tim <Tim.Keller(a)stratus.com> wrote: >Hey I was looking at the sample smb.conf file (and I've set up a bunch of >samba servers as well) and I saw something odd (well odd for >me) > >-- start cut -- ># Configure Samba to use multiple interfaces ># If you have multiple network interfaces then you must list them ># here. See the man page for details. >interfaces = 192.168.3.1 24.91.122.146 >-- end cut -- > >>From a home network point of view, why would you want samba to bind to your >external (24.xx...) address? Maybe I'm doing something wrong? > >I personally add rules to my firewall to block outgoing and incoming SMB >traffic to the outside world. SMB as a protocol goes (if you could call it >that) tends to tell the world more then one would want... > >Tim. -- Peter Gutowski <peter(a)linuxchamps.com> // tel.: (413) 587-3957 "When in company, put not your hands to any part of the body not usually discovered." --George Washington, _Rules for Civility and Decent Behavior_

May 7, 2001

RE: [Wlug] Upcoming meetings - topic proposals

by Keller, Tim

Hey I was looking at the sample smb.conf file (and I've set up a bunch of samba servers as well) and I saw something odd (well odd for me) -- start cut -- # Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details. interfaces = 192.168.3.1 24.91.122.146 -- end cut --

May 7, 2001

more lp0

by gwlt＠ma.ultranet.com

Andy, Thank you for the leads. I genuinely appreciate all of your time. I have been trying to chase the leads down. When I: ps ax | grep lpd I get: 419 ? S 0:00 lpd 906 pts/0 S 0:00 grep lpd It appears that I have the older file nomenclature of conf.modules and not modules.conf. It should work just the same though. Under modprobe -c I get a note: Note: /etc/conf.modules is more recent than /lib/modules/2.2.15-4mdk/modules.dep In the listing that follows I do have: alias parport_lowlevel parport_pc alias char-major-6 lp There is nothing for parport or lp under "options", Under "commands" I have: pre-install plip modprobe parport_pc ; echo 7 > /proc/parport/0/irq I have to be honest with you and say that I am not sure what that actually means for the system mounting of appropriate the modules or not. Does this mean anything particular to you? Anyone else familiar with the difficulty? Assistance is enormously appreciated. Colin

May 7, 2001

Re: [Wlug] Upcoming meetings - topic proposals

by Tom Martinson

Hello. I am new to this LUG. So I would like to say hello. Peter said that his wife has to connect to his SaMBa server from UMass. When I have had similar situations What I did was to setup a VPN using PPTP. That way you can block All SMB traffic to the outside world. Connect to the PPTP termination point with your client. Setup up the Tunnel and then the SMB information is passed on the inside of the tunnel. Thus keeping the integrity. Also this gives a smaller "signature" for your firewall/server to the real world. Just a though. Peter Gutowski wrote: > Well, so far it's not been a problem, although I keep a close watch on suspicious activity. (You'll notice entries for hosts allow and hosts deny. So far that seems to be pretty effective, although I do notice twits trying to access and being denied): > > hosts allow = 192.168.3.0/255.255.255.224 192.168.2.0/255.255.255.0 > 128.119.216.0/255.255.255.0 216.175.212.192/255.255.255.240 > hosts deny = all # <- no other machines can access > > Perhaps you could suggest conf options that allows [incoming] connections, but don't broadcast availability (i.e. is 'invicible' to all but people that know that that machine is a smb server). As I said, I'm not samba expert! (BTW, my wife accesses the system from her computer at UMass) > > On Monday, May 7, 2001 11:01 AM, Keller, Tim <Tim.Keller(a)stratus.com> wrote: > >> Hey I was looking at the sample smb.conf file (and I've set up a bunch of >> samba servers as well) and I saw something odd (well odd for >> me) >> >> -- start cut -- >> # Configure Samba to use multiple interfaces >> # If you have multiple network interfaces then you must list them >> # here. See the man page for details. >> interfaces = 192.168.3.1 24.91.122.146 >> -- end cut -- >> >> >From a home network point of view, why would you want samba to bind to your >> external (24.xx...) address? Maybe I'm doing something wrong? >> >> I personally add rules to my firewall to block outgoing and incoming SMB >> traffic to the outside world. SMB as a protocol goes (if you could call it >> that) tends to tell the world more then one would want... >> >> Tim. >

May 7, 2001

RE: [Wlug] Upcoming meetings - topic proposals

by Bob Brown

Andy, I would also enjoy some additional discussion on firewalls. Here are my suggestions for additional topics; 1) ipchains and dial out PPP. Setting up a fire wall for dialing into your favorite ISP. 2) ELF Files. How to read and map an ELF file. How to extract and use symbols. 3) Reading Linux crash dumps. Starting point and what to look for. Absolute locations in the dump. Interesting Linux data structures. 4) Writing a basic Linux driver. 5) Embedded Linux - There appears to be significantly more "Embedded Linux" job opportunities than "Linux" opportunities. How are they different? How do you move from Linux to embedded Linux? 6) Creating the ultimate ".emacs" file. Simple and useful Thanks, Bob -----Original Message----- From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On Behalf Of Andy Stewart Sent: Sunday, May 06, 2001 9:38 PM To: Worcester Linux Users' Group Subject: [Wlug] Upcoming meetings - topic proposals HI everybody, For our next meeting, I would like to have somebody finish the thread from the last meeting or two by explaining the contents of their firewall script and why the series of ipchains commands works for them. This might be helpful to folks who are either considering implementing a firewall or who want to understand the canned script that they got from wherever. My idea for a subsequent meeting was to have a newbie meeting as we haven't had one in quite some time. One idea I had was to discuss a shell: a) bash - scripting, command line "tricks" perhaps go over a "real" script, such as a startup script in /etc/init.d/wherever... Another idea would be to discuss the use of digital cameras with Linux. Are there other topics people would like to see? Are there volunteers to take on these topics? Perhaps there is a topic more interesting to you? Thanks in advance for your input, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 7, 2001

Re: [Wlug] Upcoming meetings - topic proposals

by Peter Gutowski

Tom, Your comments indicate a distinct need. For now, you might be interested in checking out my sample commented smb.conf file at: http://www.linuxchamps.com/docs/samba/smbconf.html I'm not a samba expert by any means, but have been enough around the block with it to make it work. HTH. On Monday, May 7, 2001 8:27 AM, Thomas Carey <tcarey70(a)hotmail.com> wrote: > >Andy, >The Firewall topic sounds great. First off, I am a newbie (been >toying around with Linux for the last year and a half off and >on), and want to increase my Linux knowledge. I have been >successful in setting up Linux as a web server, and as an FTP >server. The one thing I have been unable to get working is >Samba file and print services. I would love to have someone >show me the proper way to get this up and running. I am >currently using RH7 (for the server), and Win98SE for the >client machine. I would be willing to bring those machines, as >well as a small hub for us to work on. This is a feature of Linux that I really want to use. >Thanks for your time. > >Tom Carey > > -- Peter Gutowski <peter(a)linuxchamps.com> // tel.: (413) 587-3957 "When in company, put not your hands to any part of the body not usually discovered." --George Washington, _Rules for Civility and Decent Behavior_

May 7, 2001

Re: [Wlug] Upcoming meetings - topic proposals

by Thomas Carey

May 7, 2001

Upcoming meetings - topic proposals

by Andy Stewart

HI everybody, For our next meeting, I would like to have somebody finish the thread from the last meeting or two by explaining the contents of their firewall script and why the series of ipchains commands works for them. This might be helpful to folks who are either considering implementing a firewall or who want to understand the canned script that they got from wherever. My idea for a subsequent meeting was to have a newbie meeting as we haven't had one in quite some time. One idea I had was to discuss a shell: a) bash - scripting, command line "tricks" perhaps go over a "real" script, such as a startup script in /etc/init.d/wherever... Another idea would be to discuss the use of digital cameras with Linux. Are there other topics people would like to see? Are there volunteers to take on these topics? Perhaps there is a topic more interesting to you? Thanks in advance for your input, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

May 7, 2001

Re: Fwd: Re: [Wlug] Lp0 issues

by Wesley Allen

Sorry, I though mandrake was mentioned earlier in the thread. It is mandrake 7.2 ---------- Original Message ---------------------------------- From: Keith Wright <kwright(a)gis.net> Reply-To: wlug(a)mail.wlug.org Date: Fri, 4 May 2001 15:17:32 -0400 >> From: "Wesley Allen" <wallen(a)mail.lexchristian.org> >> >> Go up to 7.2, > >Of what? Redhat? Too high a number, I think. > >I did my homework, looking through all old messages in this thread >and found only > >> I have been making myself at home in KDE 1.1.2 under Linux 2.2.15-4mdk > >but there's no Linux kernel 7.2, nor I think KDE. > >-- > -- Keith Wright <kwright(a)free-comp-shop.com> > >Programmer in Chief, Free Computer Shop <http://www.free-comp-shop.com> > --- Food, Shelter, Source code. --- >_______________________________________________ >Wlug mailing list >Wlug(a)mail.wlug.org >http://mail.wlug.org/mailman/listinfo/wlug >

May 5, 2001