[ale] Network setup

[Christopher Bergeron]

could you send us the output by using route -n ?  that way we can see the
ip#'s and not the names...



-----Original Message-----
From: owner-ale at ale.org [mailto:owner-ale at ale.org]On Behalf Of Glenn C.
To: ale at ale.org
Lasher Jr.
Sent: Thursday, February 01, 2001 12:13 PM
To: Rajani Pai
Cc: ale at ale.org
Subject: Re: [ale] Network setup



Almost.  I still would need the same information from the other machine.


On Tue, 1 Feb 2000, Rajani Pai wrote:

> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> localnet        nitin           255.255.0.0     UG        0 0          0
> eth0
> localnet        *               255.255.0.0     U         0 0          0
> eth0
> loopback        *               255.0.0.0       U         0 0          0
lo
> default         nitin           0.0.0.0         UG        0 0          0
> eth0
>
> eth0      Link encap:Ethernet  HWaddr 00:00:21:FB:1E:CB
>           inet addr:190.160.1.27  Bcast:190.160.255.255  Mask:255.255.0.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:10 Base address:0xfcc0
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:14 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>
> Can you figure out the problem from this?
>
>
> > Wups!  Mental hiccup.  I said ipconfig, I meant ifconfig.  Obviously,
I've
> > been playing with a windblows box.
> >
> > On Wed, 31 Jan 2001, Glenn C. Lasher Jr. wrote:
> >
> > >
> > > Reall, more information is needed, such as:
> > >
> > > IP addresses
> > > Subnet masks
> > > Gateways
> > > Broadcast addr's
> > >
> > > ...etc.
> > >
> > > The best thing to do for diagnostic on this one (at least to give us
> more
> > > info to work with) would be to do the following on both machines:
> > >
> > > ipconfig
> > > netstat -r
> > >
> > > Do these, capture the outputs, and post them here, then the problem
> should
> > > become visible.
> > >
> > > Good luck!
> > >
> > > On Fri, 31 Jan 1997, Rajani Pai wrote:
> > >
> > > > I've set up a network with 2 machines. Each machine has an ethernet
> card(eth8029) and they are connected by means of a cable. Now this setup
> works fine on Windows, but each machine cannot detect the other in Linux.
> I've setup the device drivers and the devices are initialised. When I try
to
> ping the other machine it says "Destination host unreachable"
> > > > Could some one help me out on this?
> > > >
> > > > Thanks,
> > > > Rajani
> > > >
> > > >
> > >
> > >
> >
> > --
> > glasher at nycap.rr.com
> > After 163 days, Verizon still couln't deliver Telocity DSL.
> >
> >
>
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
body.
>

--
glasher at nycap.rr.com
After 163 days, Verizon still couln't deliver Telocity DSL.

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
body.

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.