- WLUG - wlug.mailman3.com

Re: Wlug digest, Vol 1 #64 - 2 msgs

by Jim Stith

compaq deskpro - the sequel; i have a viewsonic e771 monitor connected to the deskpro. i checked viewsonic's specs and found horizontal range 30-70khz vertical range 50-120hz both are what rh 70 installs and it does find the 771 although it is called e771-2 by rh. video card is a matrox mellinnium g200(generic) which is correct. i am using 16 bit 800x600. the pop sound is more like the monitor shutting off than any sort of safety device. the reason i want to install graphics is that i want to use webmin for configuration of samba apache etc. i am assuming that graphics has to be installed to use webmin. any other suggestions based on the info. above would be appreciated. thanks jim s. wlug-request(a)mail.wlug.org wrote: > > Message: 1 > To: wlug(a)mail.wlug.org > Subject: Re: [Wlug] compaq deskpro > From: Josh Huber <huber(a)alum.wpi.edu> > Date: 17 May 2001 15:00:50 -0400 > Reply-To: wlug(a)mail.wlug.org > > Jim Stith <stith2(a)earthlink.net> writes: > > [snip] > > In addition to what other people are saying, I have to ask -- why > would you want to install X on a server? > > Save disk space, save memory, and keep things simple. If the console > works, just use it. :) > > -- > Josh Huber > > --__--__-- > > Message: 2 > Date: Fri, 18 May 2001 07:30:32 -0400 > From: doug waud <douglas.waud(a)umassmed.edu> > To: wlug(a)mail.wlug.org > Subject: Re: [Wlug] compaq deskpro > Reply-To: wlug(a)mail.wlug.org > > Hi > > > everything loads fine but when the system tries to go into x and give me > > a login screen, the monitor makes a poping sound and the screen goes > > blank. > > As several responses have indicated already, you are probably driving > the monitor at the wrong frequency. This can be very dangerous (you > can cook a monitor this way) but perhaps not in your case since that > "popping sound" is probably the monitor being new enough to cut itself > off when mistreated. > > In any case, what you have to do is find out the allowable hsync and > vsync > frequencies of the monitor. Since the computer is second hand (I assume) > you may not have the manual. In that case, look on the monitor for some > sort of manufacturer/model number and feed that into google. With luck > and a bit of poking around you should be able to find a spec sheet or > table and get the hsync and vsync frequencies (I found Compaq was not > too shabby when faced with the same issue with my daughter's computer > and a Linux install). Once you have those values, you can tell the > install program what to use (I don't use Red Hat, so I can't give you > chapter and verse here; XF86Config is more generic but a tad cryptic. > If you have to go the latter route, feel free to touch base with me > (probably directly to save traffic to the whole group) and we can, > if necessary, walk through the various steps in XF86Config. > > Incidentally, I vaguely remember that my daughter's Compaq (a Presario) > had a bastard video chip which confused SuSE 6.3 but which 7.0 was > able to deal with. I suspect your box is old enough that this will > not be a problem. > > Finally, Compaq is good about providing manuals. I went into google > and entered compaq deskpro and got to the Compaq site > > which, in turn, had a link to a downloadable pdf manual. > > I suspect you may have to be a bit more specific as to model of > compaq deskpro but you should be able to get the equivalent for > your particular box. Ditto for monitor. This way you can give > the install program hints as to both the video chip and the > sync frequencies. > > Hope this helps a little. > > > i have been going through the faq's and the only thing i have found out > > is that compaq did some strange things around the mbr. > > I don't think this is anywhere near the mbr. > > doug > > PS I agree with John Huber's point that X is unnecessary (and perhaps > even in the way) on a server. However, I can also understand why you > might > want to get X going simply because, like Mount Everest, it's there :-) > > -- > Douglas R Waud > 17 Lantern Lane, Shrewsbury, MA, 01545-2006 > http://www.ummed.edu/pub/d/drw/ >

May 20, 2001

Partition

by colin＠localhost.localdomain

Thanks for the feedback. Resized the WinFAT32 partition successfully (lost no data). Linux partitions expanded (required reformatting that did wipe data.) System appears to remain stable. Colin

May 19, 2001

Re: [Wlug] RealPlayer and Linksys

by Chuck Homic

On Sat, May 19, 2001 at 03:55:15PM -0400, Michael Long wrote: > If I download an *.ra file to disk I am able to open that file and play it > using realplayer. Right... I'm being stupid. The LD_PRELOAD bit was about sound output, not anything about the network. Okay, I'm going to go back to being useless. :) -Chuck

May 19, 2001

Re: [Wlug] RealPlayer and Linksys

by Michael Long

If I download an *.ra file to disk I am able to open that file and play it using realplayer. On Saturday 19 May 2001 15:08, Chuck Homic wrote: > On Sat, May 19, 2001 at 02:36:54PM -0400, Michael Long wrote: > > Realaudio only connects through the router successfully on my windoze > > box. On the linux box I have installed it successfully but cannot get get > > it to connect through the router. > > Are you able to get RA to work under Linux *without* going through the > router? The last RA for Linux I installed had some problems which > required an LD_PRELOAD to replace the open() syscall. Pretty hacky stuff. > So first, I'd confirm that the problem is the router and not Real Player > itself. > > -Chuck > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug

May 19, 2001

Re: [Wlug] RealPlayer and Linksys

by Chuck Homic

On Sat, May 19, 2001 at 02:36:54PM -0400, Michael Long wrote: > Realaudio only connects through the router successfully on my windoze > box. On the linux box I have installed it successfully but cannot get get it > to connect through the router. Are you able to get RA to work under Linux *without* going through the router? The last RA for Linux I installed had some problems which required an LD_PRELOAD to replace the open() syscall. Pretty hacky stuff. So first, I'd confirm that the problem is the router and not Real Player itself. -Chuck

May 19, 2001

RealPlayer and Linksys

by Michael Long

I have configured several boxes at home behind a Linksys router #BEFSR81. Both my windoze and linux boxes are able to connect through the router however Realaudio only connects through the router successfully on my windoze box. On the linux box I have installed it successfully but cannot get get it to connect through the router. What should I be looking at in order to solve this? I tried looking at preferences and tried Auto-Configure to no avail. Unfortunately I do not know what RTSP or PNA is or how to use it. Any help will be greatly appreciated. thx, mike

May 19, 2001

Re: [Wlug] Shifting partitions

by Charles R. Anderson

On Fri, 18 May 2001, Brad Noyes wrote: brad> resize partitions. It only runs on windows, but has the brad> ability to manipulate ext2 filesystems. Hope this helps, Partition Magic can be run directly from it's own boot disk as well, which is useful if you don't have Windows installed.

May 19, 2001

Re: [Wlug] Shifting partitions?

by Brad Noyes

Hi, I'm too clear on what you are looking for, so i'm guessing that you want to resize/move a partition. In that case, you may be interested in looking at gnu-parted. A free program that can resize/move partitions. It has a rough interface from what i remember, but it got the job done for me. If you are looking for an easy to use solution there is partition magic, which is a commercial product, that can resize partitions. It only runs on windows, but has the ability to manipulate ext2 filesystems. Hope this helps, On Friday 18 May 2001 12:58, gwlt(a)ma.ultranet.com wrote: > A fast question: > Anyone have experience with the stability of and general > wisdom of shifting the Linux partition on a hard drive on > a dual boot machine? I am trying to upgrade to a newer > kernel and am presented with not enough memory on the > Linux side of the drive. > Encountered error message: > <<An error occurred. Tour system has not enough space > left for installation or upgrade (366821583>188726600)>> > If the endeavor is too risky I can sacrifice the current > Linux install, wipe the partition and install from > scratch. (That does undermine the whole benefit of > purchasing the proprietary upgrade package though.) > Thanks. > Colin ---------------------------------------- Content-Type: application/rtf; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: base64 Content-Description: filename="text1.rtf" ----------------------------------------

May 19, 2001

Shifting partitions?

by gwlt＠ma.ultranet.com

A fast question: Anyone have experience with the stability of and general wisdom of shifting the Linux partition on a hard drive on a dual boot machine? I am trying to upgrade to a newer kernel and am presented with not enough memory on the Linux side of the drive. Encountered error message: <<An error occurred. Tour system has not enough space left for installation or upgrade (366821583>188726600)>> If the endeavor is too risky I can sacrifice the current Linux install, wipe the partition and install from scratch. (That does undermine the whole benefit of purchasing the proprietary upgrade package though.) Thanks. Colin

May 18, 2001

Re: [Wlug] compaq deskpro

by doug waud

Hi > everything loads fine but when the system tries to go into x and give me > a login screen, the monitor makes a poping sound and the screen goes > blank. As several responses have indicated already, you are probably driving the monitor at the wrong frequency. This can be very dangerous (you can cook a monitor this way) but perhaps not in your case since that "popping sound" is probably the monitor being new enough to cut itself off when mistreated. In any case, what you have to do is find out the allowable hsync and vsync frequencies of the monitor. Since the computer is second hand (I assume) you may not have the manual. In that case, look on the monitor for some sort of manufacturer/model number and feed that into google. With luck and a bit of poking around you should be able to find a spec sheet or table and get the hsync and vsync frequencies (I found Compaq was not too shabby when faced with the same issue with my daughter's computer and a Linux install). Once you have those values, you can tell the install program what to use (I don't use Red Hat, so I can't give you chapter and verse here; XF86Config is more generic but a tad cryptic. If you have to go the latter route, feel free to touch base with me (probably directly to save traffic to the whole group) and we can, if necessary, walk through the various steps in XF86Config. Incidentally, I vaguely remember that my daughter's Compaq (a Presario) had a bastard video chip which confused SuSE 6.3 but which 7.0 was able to deal with. I suspect your box is old enough that this will not be a problem. Finally, Compaq is good about providing manuals. I went into google and entered compaq deskpro and got to the Compaq site which, in turn, had a link to a downloadable pdf manual. I suspect you may have to be a bit more specific as to model of compaq deskpro but you should be able to get the equivalent for your particular box. Ditto for monitor. This way you can give the install program hints as to both the video chip and the sync frequencies. Hope this helps a little. > i have been going through the faq's and the only thing i have found out > is that compaq did some strange things around the mbr. I don't think this is anywhere near the mbr. doug PS I agree with John Huber's point that X is unnecessary (and perhaps even in the way) on a server. However, I can also understand why you might want to get X going simply because, like Mount Everest, it's there :-) -- Douglas R Waud 17 Lantern Lane, Shrewsbury, MA, 01545-2006 http://www.ummed.edu/pub/d/drw/

May 18, 2001

Re: [Wlug] compaq deskpro

by Josh Huber

Jim Stith <stith2(a)earthlink.net> writes: [snip] In addition to what other people are saying, I have to ask -- why would you want to install X on a server? Save disk space, save memory, and keep things simple. If the console works, just use it. :) -- Josh Huber

May 17, 2001

RE: [Wlug] Compaq deskpro

by Bob Brown

Check out http://www.tru64unix.compaq.com/linux/documentation.htm It may be the X configuration settings. What monitor are you using? The MBR on many Compaq PCs point to a diagnostic partition that contains some basic utilities. I have my Armada 7400 set up for RH Linux and Windows. My MBR points to the Compaq diagnostic partition. I originally removed that partition without a problem. However, I later decided the diagnostics were worth 12/15 MBs. I used the Compaq diagnostic floppy (or download from their site) to create the diagnostic partition and load the diagnostics. Linux fdisk knows about the Compaq partition. Bob -----Original Message----- From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On Behalf Of Jim Stith Sent: Thursday, May 17, 2001 11:09 AM To: wlug(a)mail.wlug.org Subject: [Wlug] compaq deskpro well here goes... i got an old compaq deskpro (yes, a stupid mistake... but it was cheap) and wanted to load red hat 7.0 on it and possibly use the deskpro as a intranet server so that i could learn how to set a server up. everything loads fine but when the system tries to go into x and give me a login screen, the monitor makes a poping sound and the screen goes blank. same thing with mandrake and caldera. the screen stays blank. i have gone into the bios and disabled pnp and energy saver but that does not help. i have been going through the faq's and the only thing i have found out is that compaq did some strange things around the mbr. i have no other options open to me and would appreciate any help anyone can give concerning this. thanks jim s. _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 17, 2001

Re: [Wlug] compaq deskpro

by Scott Venier

well, it sounds to me like your monitor is the problem. It probably doesn't support the resolution you're trying to drive it at. Hit Crtl-Alt-F1, log in as root, type 'init 3', run the Xconfigurator (I think that's still in redhat 7) and pick a lower resolution and/or refresh rate. And next time, be sure to click the "Test This Configuration" button in the installer. :) Scott On Thu, 17 May 2001, Jim Stith wrote: > well here goes... i got an old compaq deskpro (yes, a stupid mistake... > but it was cheap) and wanted to load red hat 7.0 on it and possibly use > the deskpro as a intranet server so that i could learn how to set a > server up. > > everything loads fine but when the system tries to go into x and give me > a login screen, the monitor makes a poping sound and the screen goes > blank. > > same thing with mandrake and caldera. > > the screen stays blank. i have gone into the bios and disabled pnp and > energy saver but that does not help. > > i have been going through the faq's and the only thing i have found out > is that compaq did some strange things around the mbr. > > i have no other options open to me and would appreciate any help anyone > can give concerning this. > > thanks > > jim s. > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 17, 2001

compaq deskpro

by Jim Stith

well here goes... i got an old compaq deskpro (yes, a stupid mistake... but it was cheap) and wanted to load red hat 7.0 on it and possibly use the deskpro as a intranet server so that i could learn how to set a server up. everything loads fine but when the system tries to go into x and give me a login screen, the monitor makes a poping sound and the screen goes blank. same thing with mandrake and caldera. the screen stays blank. i have gone into the bios and disabled pnp and energy saver but that does not help. i have been going through the faq's and the only thing i have found out is that compaq did some strange things around the mbr. i have no other options open to me and would appreciate any help anyone can give concerning this. thanks jim s.

May 17, 2001

Re: [Wlug] newbie seeks help with kernel upgrade

by Chad Pytel

> libdb-3 is in the db3 package. This is not easy to determine, > unfortunately. The Red Hat up2date service can figure this out > automatically, I believe. I find that http://www.rpmfind.net works well for finding the rpm that provides a a certain executable or library. For example, if you go there and type in 'libdb-3' into the search box, it'll come up with a list of RPM's for different distributions and versions that provide that library - then you just have to pick the most recent one (or the version you need) for your distribution. -Chad +--[ Chad Pytel ]----------------------------------+ (508)756-1329 http://www.chadpytel.com +-------------------------------[ cpytel(a)wpi.edu ]-+ On Thu, 17 May 2001, Charles R. Anderson wrote: > On Thu, 17 May 2001, Dan Crooks wrote: > > dancro> While trying to install the kernel upgrade with rpm I > dancro> received error messages: 1) failed dependencies: > dancro> rpmlib(PayloadFilesHavePrefix) <= 4.0.1 is needed by > dancro> kernel-2.2.19-6.2.1 2) mount < 2.10r conflicts with > dancro> kernel-2.2... 3) nfs-utils < 0.3.1 conflicts with > dancro> kernel-2.2... > dancro> > dancro> Where can I find libdb? How could I determine that for > dancro> myself if I run into another dependency? > > libdb-3 is in the db3 package. This is not easy to determine, > unfortunately. The Red Hat up2date service can figure this out > automatically, I believe. > > You shouldn't need the --replacefiles option to rpm. A conflict usually > means you should use the -U option to rpm so the package is Upgraded, > instead of Installed. Here is the order you will need to follow for the > kernel upgrade. I'm doing this from memory, so I may have forgotten some > dependencies. > > First upgrade rpm. You really should upgrade to all the latest packages > in the Red Hat updates tree, since many security problems are fixed and > the latest packages are required for other updates, as you have > discovered. For instance, I believe there is a new gnorpm that works with > the new rpm-4.0.2. > > The -F option means to only upgrade if an older package of the same name > is already installed (Freshen). > > rpm -Uvh db3-*3.1.17-4.6x.i386.rpm > rpm -Fvh rpm-*4.0.2-6x.i386.rpm popt-1.6.2-6x.i386.rpm > > rpm --rebuilddb (to convert to rpm 4 database files) > > Now install files required by the new kernel: > > rpm -Fvh mount-2.10r-0.6.x.i386.rpm nfs-utils-0.3.1-0.6.x.1.i386.rpm > > Upgrade all the kernel packages except the main one and smp one: > > rpm -Fvh kernel-BOOT-2.2.19-6.2.1.i386.rpm > kernel-doc-2.2.19-6.2.1.i386.rpm kernel-headers-2.2.19-6.2.1.i386.rpm > kernel-ibcs-2.2.19-6.2.1.i386.rpm kernel-pcmcia-cs-2.2.19-6.2.1.i386.rpm > kernel-source-2.2.19-6.2.1.i386.rpm kernel-utils-2.2.19-6.2.1.i386.rpm > > Now choose the right main kernel package for your architecture (i386, > i586, i686, regular or smp), and install that (don't upgrade it so you can > keep the old one around if the new one gives you problems). The i586 and > i686 versions are in their own subdirectories of the updates tree, not in > the i386 subdirectory. > > rpm -ivh kernel-2.2.19-6.2.1.i686.rpm > > (notice the -i option to install instead of upgrade. This leaves the > older versions around for emergencies.) > > Edit /etc/lilo.conf and make a new stanza and edit it for the new version > (copy a stanza from another one in the file). Make sure to change the old > stanza(s) to different labels (like linux.old or something): > > image=/boot/vmlinuz-2.2.19-6.2.1 > label=linux > initrd=/boot/initrd-2.2.19-6.2.1.img > read-only > root=/dev/hda2 > > If you have an initrd line in lilo.conf that isn't empty, you need to > create a new initial ram disk: > > /sbin/mkinitrd /boot/initrd-2.2.19-6.2.1.img 2.2.19-6.2.1 > > Re-run lilo: > > /sbin/lilo > > Now you should be set to "shutdown -r now" and boot the new kernel. > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 17, 2001

Re: [Wlug] newbie seeks help with kernel upgrade

by Charles R. Anderson

On Thu, 17 May 2001, Dan Crooks wrote: dancro> While trying to install the kernel upgrade with rpm I dancro> received error messages: 1) failed dependencies: dancro> rpmlib(PayloadFilesHavePrefix) <= 4.0.1 is needed by dancro> kernel-2.2.19-6.2.1 2) mount < 2.10r conflicts with dancro> kernel-2.2... 3) nfs-utils < 0.3.1 conflicts with dancro> kernel-2.2... dancro> dancro> Where can I find libdb? How could I determine that for dancro> myself if I run into another dependency? libdb-3 is in the db3 package. This is not easy to determine, unfortunately. The Red Hat up2date service can figure this out automatically, I believe. You shouldn't need the --replacefiles option to rpm. A conflict usually means you should use the -U option to rpm so the package is Upgraded, instead of Installed. Here is the order you will need to follow for the kernel upgrade. I'm doing this from memory, so I may have forgotten some dependencies. First upgrade rpm. You really should upgrade to all the latest packages in the Red Hat updates tree, since many security problems are fixed and the latest packages are required for other updates, as you have discovered. For instance, I believe there is a new gnorpm that works with the new rpm-4.0.2. The -F option means to only upgrade if an older package of the same name is already installed (Freshen). rpm -Uvh db3-*3.1.17-4.6x.i386.rpm rpm -Fvh rpm-*4.0.2-6x.i386.rpm popt-1.6.2-6x.i386.rpm rpm --rebuilddb (to convert to rpm 4 database files) Now install files required by the new kernel: rpm -Fvh mount-2.10r-0.6.x.i386.rpm nfs-utils-0.3.1-0.6.x.1.i386.rpm Upgrade all the kernel packages except the main one and smp one: rpm -Fvh kernel-BOOT-2.2.19-6.2.1.i386.rpm kernel-doc-2.2.19-6.2.1.i386.rpm kernel-headers-2.2.19-6.2.1.i386.rpm kernel-ibcs-2.2.19-6.2.1.i386.rpm kernel-pcmcia-cs-2.2.19-6.2.1.i386.rpm kernel-source-2.2.19-6.2.1.i386.rpm kernel-utils-2.2.19-6.2.1.i386.rpm Now choose the right main kernel package for your architecture (i386, i586, i686, regular or smp), and install that (don't upgrade it so you can keep the old one around if the new one gives you problems). The i586 and i686 versions are in their own subdirectories of the updates tree, not in the i386 subdirectory. rpm -ivh kernel-2.2.19-6.2.1.i686.rpm (notice the -i option to install instead of upgrade. This leaves the older versions around for emergencies.) Edit /etc/lilo.conf and make a new stanza and edit it for the new version (copy a stanza from another one in the file). Make sure to change the old stanza(s) to different labels (like linux.old or something): image=/boot/vmlinuz-2.2.19-6.2.1 label=linux initrd=/boot/initrd-2.2.19-6.2.1.img read-only root=/dev/hda2 If you have an initrd line in lilo.conf that isn't empty, you need to create a new initial ram disk: /sbin/mkinitrd /boot/initrd-2.2.19-6.2.1.img 2.2.19-6.2.1 Re-run lilo: /sbin/lilo Now you should be set to "shutdown -r now" and boot the new kernel.

May 17, 2001

sorry about that

by Dan Crooks

I put it on the WLUG WWWBoard, where it obviously belongs. Sorry for the inconvenience. -- Thank you, Dan Crooks

May 17, 2001

newbie seeks help with kernel upgrade

by Dan Crooks

Hi, and thank you in advance for your patience. This deals with upgrading kernel In attempting to install vmware 2.0 in Red Hat 6.2, I was notified that I needed an upgrade to RH6.2 kernel. While trying to install the kernel upgrade with rpm I received error messages: 1) failed dependencies: rpmlib(PayloadFilesHavePrefix) <= 4.0.1 is needed by kernel-2.2.19-6.2.1 2) mount < 2.10r conflicts with kernel-2.2... 3) nfs-utils < 0.3.1 conflicts with kernel-2.2... I understand that I can ignore the conflicts (2,3) by specifying --replacefiles in the rpm command. I decided to upgrade rpm assuming that rpmlib would be included. Using gnorpm I downloaded rpm 4.0-4 and received another error: only packages with major numbers <=3 are supported by this release of rpm. Presumably this message is issued by the currently version of rpm 3.0.4-0.48. This may be a red herring and not important as I continued. I used ncftp to download by specifying "mget rpm-*.rpm" and received four files rpm-4.0.2-6x.i386.rpm, also -build-, -devel-, -python- from RH site. When I tried to install rpm-4.0.2-6x I received an error: failed dependency libdb-3.1.so. Where can I find libdb? How could I determine that for myself if I run into another dependency? Do you have any suggestions/recommendations regarding updating kernel? I am using instructions retrieved from RH titled "Upgrading the Linus Kernel on Red Hat Linux systems" by Red Hat Support last updated 2000 May 17 -- Thank you, Dan Crooks

May 17, 2001

REMINDER: Meeting Wednesday, May 16th, 7:00 PM

by Andy Stewart

Hi everybody, This is a reminder about the upcoming WLUG meeting, to be held in Kinnicutt Hall (a.k.a the usual place) at WPI at 7:00 PM on Wednesday, May 16h. The topic for discussion will be the practical use of IPCHAINS. What does that mean? This meeting, Doug Waud and I will present to you ways to use IPCHAINS to implement a firewall. This is not theory, this is practice...what to type, what it does, and why. This talk will build on the more detailed information presented by Bob Ziegler at our last meeting. Doug will start with a presentation of the simpler case of getting a firewall up which supports masquerading (that is, getting multiple machines on your home network to share one IP address, as you would for cable modem, for example), e-mail, and browsing. I will follow up with more detailed examples of IPCHAINS code from my own firewall script for allowing certain services through the firewall to the home network. Although firewalling is a complex topic, we're hoping to distill out of that complexity enough information so that a person can get started toward implementing a secure firewall. I'm looking forward to a good turnout at this meeting. Come on down! Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

May 14, 2001

RE: [Wlug] charter.net & ssh

by Bill Mills-Curran

Charles, Answers below... On Thu, 10 May 2001, Charles R. Anderson wrote: > Date: Thu, 10 May 2001 15:02:41 -0400 (EDT) > From: Charles R. Anderson <cra(a)WPI.EDU> > Reply-To: wlug(a)mail.wlug.org > To: "'wlug(a)mail.wlug.org'" <wlug(a)mail.wlug.org> > Subject: RE: [Wlug] charter.net & ssh > > Are you doing uni-directional NAT on the Linksys? Are there any firewall > rules defined on the Linksys? Yes, at least I believe that's it. When I was testing, I configured port 22 to translate to my internal address. > > In addition to allowing packets from outside to port 22 on your SSH > server, do you allow outgoing packets from your SSH server on port 22 to > local ephemeral ports (1024-65535) on the outside clients? I believe that all outgoing packets are passed & translated by default. (I've never heard them called ephemeral. I've always called them transient.) Thanks, Bill

May 10, 2001

RE: [Wlug] charter.net & ssh

by Charles R. Anderson

Are you doing uni-directional NAT on the Linksys? Are there any firewall rules defined on the Linksys? In addition to allowing packets from outside to port 22 on your SSH server, do you allow outgoing packets from your SSH server on port 22 to local ephemeral ports (1024-65535) on the outside clients? Traceroute also uses either ICMP (Windows) or UDP+ICMP (Unix) to high numbered ports. On Thu, 10 May 2001, Bill Mills-Curran wrote: bcurra> It never makes it. BTW, if you're looking to try this bcurra> yourself, I've turned off the forwarding on my router. I bcurra> probably should have left it on so that I could work with bcurra> the Charter people. bcurra> 13 24-216-218-3.hsacorp.net (24.216.218.3) 5.489 ms 5.842 ms 6.198 ms bcurra> 14 10.254.1.2 (10.254.1.2) 6.192 ms 9.664 ms 6.756 ms

May 10, 2001

RE: [Wlug] charter.net & ssh

by Keller, Tim

Bill, I make it to the same point. Looks like the 10.254.1.2 is the gateway onto that segment of Ethernet, this would indicate that they do blocking at the router (at least to me and i'm not a network expert...) Tim. -----Original Message----- From: Bill Mills-Curran [mailto:bcurran@clariion.com] Sent: Thursday, May 10, 2001 2:09 PM To: 'wlug(a)mail.wlug.org' Subject: RE: [Wlug] charter.net & ssh Tim, It never makes it. BTW, if you're looking to try this yourself, I've turned off the forwarding on my router. I probably should have left it on so that I could work with the Charter people. Bill traceroute to 24.240.184.215 (24.240.184.215), 30 hops max, 40 byte packets 1 clar45sec (128.221.45.11) 0.870 ms 0.892 ms 0.829 ms 2 sobo-clariion-gw.us.dg.com (128.221.35.65) 1.238 ms 0.740 ms 0.829 ms 3 webo-atm-oc3.us.dg.com (128.221.35.61) 1.851 ms 1.232 ms 1.286 ms 4 128.221.22.60 (128.221.22.60) 1.408 ms 1.063 ms 1.791 ms 5 128.221.4.66 (128.221.4.66) 1.141 ms 1.629 ms 1.113 ms 6 128.221.23.23 (128.221.23.23) 1.917 ms 1.076 ms 1.113 ms 7 us-customs2.us.dg.com (128.221.131.14) 1.580 ms 1.613 ms 2.193 ms 8 uunet-gw.us.dg.com (128.221.122.1) 3.197 ms 2.035 ms 1.939 ms 9 500.Serial4-1-0.GW3.BOS1.ALTER.NET (157.130.222.33) 3.365 ms 3.313 ms 3.132 ms 10 196.ATM2-0.XR1.BOS1.ALTER.NET (152.63.25.122) 3.839 ms 3.410 ms 3.814 ms 11 191.ATM7-0.GW3.BOS1.ALTER.NET (146.188.177.209) 3.342 ms 3.221 ms 3.449 ms 12 hsa-noxford-t3.customer.alter.net (157.130.220.226) 5.158 ms 5.753 ms 5.425 ms 13 24-216-218-3.hsacorp.net (24.216.218.3) 5.489 ms 5.842 ms 6.198 ms 14 10.254.1.2 (10.254.1.2) 6.192 ms 9.664 ms 6.756 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * On Thu, 10 May 2001, Keller, Tim wrote: > Date: Thu, 10 May 2001 11:30:26 -0400 > From: "Keller, Tim" <Tim.Keller(a)stratus.com> > Reply-To: wlug(a)mail.wlug.org > To: "'wlug(a)mail.wlug.org'" <wlug(a)mail.wlug.org> > Subject: RE: [Wlug] charter.net & ssh > > Bill, > > Try doing a traceroute on port 22 to your machine and see where along the > line it get stopped. > > It's probably a default security thing they have setup, you could probably > call up tech support and have them remove the blocks for specific ports... > > Tim. > > -----Original Message----- > From: Bill Mills-Curran [mailto:bcurran@clariion.com] > Sent: Thursday, May 10, 2001 11:30 AM > To: Worcester Linux Users Group > Subject: [Wlug] charter.net & ssh > > > I got my new Charter cable modem and Linksys router set up recently, > but I find that Charter seems to be blocking inbound access. I've the > the sshd running, and I set the router to pass port 22 to my linux > box. I can even connect if I ssh outbound to the router DHCP address, > so it looks like my end of the configuration is correct. > > Anybody experience anything like this? Do you think that Charter will > allow incoming requests to my system? > > TIA, > Bill > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 10, 2001

RE: [Wlug] charter.net & ssh

by Bill Mills-Curran

Tim, It never makes it. BTW, if you're looking to try this yourself, I've turned off the forwarding on my router. I probably should have left it on so that I could work with the Charter people. Bill traceroute to 24.240.184.215 (24.240.184.215), 30 hops max, 40 byte packets 1 clar45sec (128.221.45.11) 0.870 ms 0.892 ms 0.829 ms 2 sobo-clariion-gw.us.dg.com (128.221.35.65) 1.238 ms 0.740 ms 0.829 ms 3 webo-atm-oc3.us.dg.com (128.221.35.61) 1.851 ms 1.232 ms 1.286 ms 4 128.221.22.60 (128.221.22.60) 1.408 ms 1.063 ms 1.791 ms 5 128.221.4.66 (128.221.4.66) 1.141 ms 1.629 ms 1.113 ms 6 128.221.23.23 (128.221.23.23) 1.917 ms 1.076 ms 1.113 ms 7 us-customs2.us.dg.com (128.221.131.14) 1.580 ms 1.613 ms 2.193 ms 8 uunet-gw.us.dg.com (128.221.122.1) 3.197 ms 2.035 ms 1.939 ms 9 500.Serial4-1-0.GW3.BOS1.ALTER.NET (157.130.222.33) 3.365 ms 3.313 ms 3.132 ms 10 196.ATM2-0.XR1.BOS1.ALTER.NET (152.63.25.122) 3.839 ms 3.410 ms 3.814 ms 11 191.ATM7-0.GW3.BOS1.ALTER.NET (146.188.177.209) 3.342 ms 3.221 ms 3.449 ms 12 hsa-noxford-t3.customer.alter.net (157.130.220.226) 5.158 ms 5.753 ms 5.425 ms 13 24-216-218-3.hsacorp.net (24.216.218.3) 5.489 ms 5.842 ms 6.198 ms 14 10.254.1.2 (10.254.1.2) 6.192 ms 9.664 ms 6.756 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * On Thu, 10 May 2001, Keller, Tim wrote: > Date: Thu, 10 May 2001 11:30:26 -0400 > From: "Keller, Tim" <Tim.Keller(a)stratus.com> > Reply-To: wlug(a)mail.wlug.org > To: "'wlug(a)mail.wlug.org'" <wlug(a)mail.wlug.org> > Subject: RE: [Wlug] charter.net & ssh > > Bill, > > Try doing a traceroute on port 22 to your machine and see where along the > line it get stopped. > > It's probably a default security thing they have setup, you could probably > call up tech support and have them remove the blocks for specific ports... > > Tim. > > -----Original Message----- > From: Bill Mills-Curran [mailto:bcurran@clariion.com] > Sent: Thursday, May 10, 2001 11:30 AM > To: Worcester Linux Users Group > Subject: [Wlug] charter.net & ssh > > > I got my new Charter cable modem and Linksys router set up recently, > but I find that Charter seems to be blocking inbound access. I've the > the sshd running, and I set the router to pass port 22 to my linux > box. I can even connect if I ssh outbound to the router DHCP address, > so it looks like my end of the configuration is correct. > > Anybody experience anything like this? Do you think that Charter will > allow incoming requests to my system? > > TIA, > Bill > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 10, 2001

RE: [Wlug] charter.net & ssh

by Keller, Tim

Bill, Try doing a traceroute on port 22 to your machine and see where along the line it get stopped. It's probably a default security thing they have setup, you could probably call up tech support and have them remove the blocks for specific ports... Tim. -----Original Message----- From: Bill Mills-Curran [mailto:bcurran@clariion.com] Sent: Thursday, May 10, 2001 11:30 AM To: Worcester Linux Users Group Subject: [Wlug] charter.net & ssh I got my new Charter cable modem and Linksys router set up recently, but I find that Charter seems to be blocking inbound access. I've the the sshd running, and I set the router to pass port 22 to my linux box. I can even connect if I ssh outbound to the router DHCP address, so it looks like my end of the configuration is correct. Anybody experience anything like this? Do you think that Charter will allow incoming requests to my system? TIA, Bill _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 10, 2001

charter.net & ssh

by Bill Mills-Curran

I got my new Charter cable modem and Linksys router set up recently, but I find that Charter seems to be blocking inbound access. I've the the sshd running, and I set the router to pass port 22 to my linux box. I can even connect if I ssh outbound to the router DHCP address, so it looks like my end of the configuration is correct. Anybody experience anything like this? Do you think that Charter will allow incoming requests to my system? TIA, Bill

May 10, 2001