telnet and rainmaker
Brian Borowski
brianb at braille.uwo.ca
Sun Mar 10 06:31:01 EST 2002
Janina:
No script does not do any more than capture what happens on your console.
You can just use the host command to do the lookup if it's on the machine,
or if you want to capture all the interaction, then use tcpdump, tethereal,
or dsniff and capture all packets; which will be more painful to analyze.
Brian
On Sat, 9 Mar 2002, Janina Sajka wrote:
> Brian: I think there's a way to capture the interaction between the
> various machines involved, not just what is typed and what goes to screen
> display. In other words, I think seeing the names get resolved, etc., is
> what will identify the problem. Does script do this?
> On Sat, 9 Mar 2002,
> Brian Borowski wrote:
>
> >
> > To capture, just use script, and after you've telnet'ed or whatever you
> > want to do type exit to shutdown script.
> >
> > You should also check, that the rainmaker IP addresses are the same at each
> > of your places where you're getting the different results, maybe a name
> > server is returning bad information, could even be done purposely.
> >
> > Brian
> >
> >
> > On Sat, 9 Mar 2002, Janina Sajka wrote:
> >
> > > Well, we need to capture the data streams to a file. I don't remember how
> > > that's done. Anyone have some advice.
> > >
> > > On Sat, 9 Mar 2002, Gregory Nowak wrote:
> > >
> > > > Janina, thanks for forwarding this to the list. I'm relieved to know that I'm not the only one experiencing this problem. I'd be very much interested in knowing if someone figures out what's causing this problem, and how it could be fixed.
> > > > Greg
> > > >
> > > >
> > > > On Sat, Mar 09, 2002 at 02:23:18PM -0500, Janina Sajka wrote:
> > > > > Jim, and Listers:
> > > > >
> > > > > I'm getting a bit more concerned to figure this out. One scenario buzzing
> > > > > around in my head that might explain this would even potentially be
> > > > > illegal under U.S. telecomm law. So, Jim, I've forwarded my reply back to
> > > > > the list, even though you thought it might just muddy things up there.
> > > > >
> > > > > I think we need to find outexactly what's going on here. It troubles me,
> > > > > for example, that the same installation could yield such different
> > > > > results. I'd like to know, for example, whether exactly the same data is
> > > > > being sent in each case. In other words, is it a terminal or a terminfo
> > > > > kind of issue? Or, is the network responding differently because it is
> > > > > impeding, or dropping some chars? If the latter, that could violate
> > > > > Section 201 of the 1996 Telecomm Act which requires that network
> > > > > transmission not break accessibility features.
> > > > > On Fri, 8 Mar 2002
> > > > > jwantz at hpcc2.hpcc.noaa.gov wrote:
> > > > >
> > > > > > Hi Janina,
> > > > > > I really didn't want to muddy the waters on the speakup list--but I
> > > > > > thought you might find this interesting. When I telnet from this machine
> > > > > > here at work to wunderground.rainmaker.com I get a strange startup screen
> > > > > > with some reference to a null character. When I hit return I get the
> > > > > > regular menus and I can select cities fine but I am unable to retrieve any
> > > > > > data. Control-j and control-m don't matter. It looks exactly like what
> > > > > > has been described by others. However when telneting from my Linux
> > > > > > machine at home, everything works like it should.They are both rh 7.2 and
> > > > > > the telnet clients should be the same. Any ideas?
> > > > > >
> > > > > > Jim
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Janina Sajka, Director
> > > > > Technology Research and Development
> > > > > Governmental Relations Group
> > > > > American Foundation for the Blind (AFB)
> > > > >
> > > > > Email: janina at afb.net Phone: (202) 408-8175
> > > > >
> > > > > Chair, Accessibility SIG
> > > > > Open Electronic Book Forum (OEBF)
> > > > > http://www.openebook.org
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup at braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup at braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > >
> > > --
> > >
> > > Janina Sajka, Director
> > > Technology Research and Development
> > > Governmental Relations Group
> > > American Foundation for the Blind (AFB)
> > >
> > > Email: janina at afb.net Phone: (202) 408-8175
> > >
> > > Chair, Accessibility SIG
> > > Open Electronic Book Forum (OEBF)
> > > http://www.openebook.org
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup at braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> --
>
> Janina Sajka, Director
> Technology Research and Development
> Governmental Relations Group
> American Foundation for the Blind (AFB)
>
> Email: janina at afb.net Phone: (202) 408-8175
>
> Chair, Accessibility SIG
> Open Electronic Book Forum (OEBF)
> http://www.openebook.org
>
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
More information about the Speakup
mailing list