Deja Vu all over again
ME
dugan at passwall.com
Thu Mar 29 21:07:58 PST 2001
If you use the ">> /tmp/netstuff.txt" addition to the command, the output
of those commands will be placed into a file at "/tmp/netsuff.txt" and
then you can copy that to floppy and then bring th floppy to your mac and
attach the file create to send it.
So, the commands run as root would become:
# ifconfig > /tmp/netstuff.txt
# ifconfig eth0 >> /tmp/netstuff.txt
# route -n >> /tmp/netstuff.txt
# cat /proc/interrupts >> /tmp/netstuff.txt
# cat /proc/ioports >> /tmp/netstuff.txt
# cat /resolve.conf >> /tmp/netstuff.txt
# dselect >> /tmp/netstuff.txt
# lsmod >> /tmp/netstuff.txt
Then you would have a text file /tmp/netstuff with the output of all of
these. Copy this to floppy on the linux box and then from floppy to a mac
HD and include it as an attachment.
To use a floppy check out either hfsutils (mac) or try out the mtools with
stuff like mcopy to copy to a PC based FAT floppy. Your mac should be able
to read PC high density disks with FAT if you have PC Exchange.) If you
prefer to use neither, you can check out the mount command in linux (man
ount) and see how you set a mount point, specify a filesystem type and
reference the device (e.g. /dev/fd0).
If you do not use mtools or hfstool, then here are some examples of how
you might mount the floppy in linux for copying the output...
E.G. for mac 1.44Mb disk:
# mkdir /mnt/floppy
# modprobe hfs
# mount -t hfs /dev/fd0 /mnt/floppy
# cp /tmp/netstuff.txt /mnt/floppy/
# umount /mnt/floppy
then it is ok to eject the floppy.. if you eject before umount, then the
data on the disk may and likely will be lost.
E.G for fat floppy:
# mkdir /mnt/floppy
# modprobe msdos
# mount -t msdos /dev/fd0 /mnt/floppy
# cp /tmp/netstuff.txt /mnt/floppy/
# umount /mnt/floppy
*OR*
# mkdir /mnt/floppy
# modprobe vfat
# mount -t vfat /dev/fd0 /mnt/floppy
# cp /tmp/netstuff.txt /mnt/floppy/
# umount /mnt/floppy
Again for whatever method you use, do not forget to umount the floppy.
if modprobe complains, your kernel may have support for those filesystems
built in.
(mtools and hfstools might be good for you to check out as they may seem
easier to use than the above. However, learning how the above works and
what it does is more usefull on other *nix systems where hfstools and
mtools do not xist.)
)
Please also look to answer the questions at the end for your linksys
device. Some of these may shed some light on the problems you face.
-ME
On Thu, 29 Mar 2001, John F. Kohler wrote:
> Thanks for the reply. I have no idea how to cut and paste on a linux
> command line page. The box is capable of connecting online with
> the modem port, and if I only knew how, I'd send the items along.
>
> As it is, I get the command line result, and type it in on my (network friendly)
> macintosh next to the linux on the same desk.
> john
>
>
> ME wrote:
>
> > I am going to assume that this has not yet been resolved and take a stab
> > at it. If this was resolved, and I did not notice, then skip this and
> > please accept my appologies.
> >
> > Could you reboot your Linux box and then as root could you go to a command
> > prompt and run the following command, and then take the contents of the
> > output for each and paste them into one e-mail message for review on the
> > list:
> >
> > # ifconfig
> > # ifconfig eth0
> > # route -n
> > # cat /proc/interrupts
> > # cat /proc/ioports
> > # cat /resolve.conf
> > # dselect
> > # lsmod
> >
> > It is ok to just copy and paste them "as-is" and not try to format them on
> > your own.
> >
> > *OR*
> >
> > If you can be sure there is no file in "/tmp" called "netstuff.txt" then
> > you could append a ">> /tmp/netstuff.txt" to the end of each of the
> > commands listed above and then "attach" the file "/tmp/netstuff.txt" to
> > your e-mail message you send to the list.
> >
> > Also, could you take one of your working machines (macs I think you said
> > you had) on your network that shares use of the router and go to the
> > TCP/IP control panel and give me the following information that should be
> > listed in that control panel of that mac:
> > IP Address :
> > Subnet Mask :
> > Gateway/router :
> > Domain Name Svrs:
> >
> > Please also verify the network you have looks kind of like this:
> > <!-- sorry about this html junk, I assume that the reason for the bad
> > formatting of the previous messages was the use of a mail client by a
> > sender that uses variable width fonts instead of fixed width fonts -->
> >
> > <pre>
> > Mac1------|H|
> > Mac2------|U|-- LINKSYS Router(?) --- DSL
> > Linux Box-|B|
> > </pre>
> >
> > Does your Linksys router (? Assuming it is a router) only use DHCP to hand
> > out IP addresses to clients? Does it allow you to set static addresses
> > too? Are the static addresses in the same range as the DHCP assigned
> > addresses or does their manual only allow static addresses to be outside a
> > certain range? Does the router implement rules to disallow any passing of
> > packets from IP addresses that it does not have listed as having a DHCP
> > lease? Do both of your macs get their address via DHCP/BootP or are they
> > static assignments?
> >
> > Sorry to ask for all of this information again, but I would like to see it
> > all after a reboot so we can be sure no other changes or oddness is in
> > effect for this session.
> >
> > Thanks,
> > -ME
> >
> > On Wed, 28 Mar 2001, John F. Kohler wrote:
> > > I started the netscape browser (version 4.75) and tried to pull up the address
> > > of
> > > the router (192.168.1.1) . On either macintosh also on the router, I get a
> > > screen
> > > with router setup information, and another screen indicating the router
> > > is connected to the DSL line.
> > >
> > > On the Linux box I got the following:
> > >
> > > Netscape:Error
> > >
> > > A network Error occurred.
> > > Unable to connect to server (TCP error. No route to host)
> > > The server may be down or unreachable.
> > >
> > > Try connecting again later.
> > >
> > > -30-
> > >
> > > Trying to ping the router ( 192.168.1.1) from the linux box (192.168.1.4)
> > >
> > >
> > > I got the following sentence over and over again
> > >
> > > >From 192.168.1.4: Destination host Unreachable.
> > >
> > > Trying to get the box to ping its own IP address was successful
> > > time was from 50 usec to 350 usec.
> > >
> > > Trying to get the linux box to ping the macintosh (lc475) next to it, was
> > > successful
> > >
> > > getting times from 1.6 to 4.7 miliseconds.
> > >
> > > Didn't try to ping the iMac, it was turned off.
> > >
> > > John
> > >
> > >
> > >
> > > Dustin Mollo wrote:
> > >
> > > > It seems this message got stuck in the mailing list queue, so I'm resending
> > > > it. Enjoy!
> > > >
> > > > -Dustin
> > > >
> > > > ------------------------------------------------------------
> > > >
> > > > Date: Tue, 27 Mar 2001 11:20:16 -0800
> > > > From: Mitch Petenaude <mrp at bolt.sonic.net>
> > > > To: nblug-talk at lists.sonic.net
> > > > Subject: Re: Deja Vu all over again
> > > >
> > > > Hi John,
> > > >
> > > > Have you set up your DNS server addresses? What is in /etc/resolv.conf?
> > > >
> > > > --Mitch
> > > >
> > > > On Tue, Mar 27, 2001 at 09:16:29AM -0800, John F. Kohler wrote:
> > > > > Although I could ping addresses outside my network, neither
> > > > > Netscape nor Lynx could display a page. So I am still
> > > > > confused.
> > > > >
> > > > > I took a look at /etc/modules.conf
> > > > >
> > > > > alias parport_lowlever parport_pc
> > > > > alias usb-controller usb-uhci
> > > > > alias eth0 ne
> > > > > options ne io=0x2a0 irq=10
> > > > > ~
> > > > > ~
> > > > > ~
> > > > > ~"modules.conf"4L, 109C"
> > > > >
> > > > > Here is /sbin/lsmod:
> > > > >
> > > > > Module Size Used by
> > > > > ide-cd 23628` 0 (autoclean)
> > > > > lockd 31176 1 (autoclean)
> > > > > sunrpc 52964 1 (autoclean) [lockd]
> > > > >
> > > > > ppp 20236 0
> > > > > (autoclean)[unused]
> > > > > slhc 4504 0(autoclean) [ppp]
> > > > > ne 6732 1 (autoclean)
> > > > > 8390 6072 0 (autoclean )
> > > > > [ne]
> > > > > agpgart 18600 0 (unused)
> > > > > usb-uhci 19052 0 (unused
> > > > > usbcore 42088 1(usb-uhci)
> > > > >
> > > > > I tried /proc/interrupts: and got permission denied.
> > > > >
> > > > > John
> > > > >
> > > >
> > > > ----- End forwarded message -----
> > >
> > >
>
>
More information about the talk
mailing list