From: Elias Udechime (euchime@xxxxxxxxx)
Date: Fri Oct 12 2001 - 12:18:54 GMT-3
Thanks guys,
The problem is solved.
--- ohanusi anthony <ohanusi@lagos.sns.slb.com> wrote:
> network 10.10.10.1 0.0.0.63 area 1
>
> should put that interface in area one
>
>
> Ohanusi
>
>
>
>
>
>
>
> >Looks like OSPF isn't advertising the 10.10.10.0/26
> network because OSPF 1
> >only knows to advertise 10.0.0.0/24 - look at the
> distant router's route
> >table for 10.10.10.0/26 - it likely isn't there.
> If the distant end doesn't
> >know about your FE subnet, it can't reply.
> >
> >HTH,
> >
> >CK
> >
> >----- Original Message -----
> >From: "Elias Udechime" <euchime@yahoo.com>
> >To: <euchime@yahoo.com>
> >Cc: <ccielab@groupstudy.com>
> >Sent: Thursday, October 11, 2001 3:57 PM
> >Subject: OSPF interface
> >
> >
> > > I have a laptop and 3640 connected to a hub. The
> PVC
> > > on the 3640 is the only way to get out to the
> next
> > > hop.
> > >
> > > (diagram)
> > >
>
[laptop]----10/100---|HUB|--FE0/0----[3640]---pvc.....
> > >
> > > For some reason, the laptop can't ping past the
> 3640.
> > > I suspect it to be an OSPF problem with the
> FE0/0
> > > interface. F0/0 10.10.10.1/26 with Ip ospf
> network
> > > Non-broadcast
> > >
> > > The 3640 isn't routing between the Ethernet IP
> address
> > > and the PVC IP address 192.168.1.1/30...IP ospf
> > > network point to point
> > >
> > > Sample:
> > >
> > > Router ospf 1
> > > network 10.0.0.0 0.0.0.0.255 area 1
> > > network 192.168.0.0 0.0.255.255 area 0
> > >
> > > Of course from the 3640, you can ping the far
> end
> > > router with no problem.
> > >
> > > Routing between Ethernet interface to ATM
> interface
> > >
> > > Any suggestion?
> > >
> > > Elias
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:18 GMT-3