[c-nsp] VLANs over IP unnumbered

[Manaf Oqlah]

Yes the proxy arp is configured on VLAN interface. no we don't have mobile
ip

On Sun, Jun 15, 2008 at 4:24 AM, Mike Louis <MLouis at nwnit.com> wrote:

> Is proxy arp configured on the interfaces with ip unnumbered command...do
> you have mobile ip configured?
>
> -----Original Message-----
> From: Manaf Oqlah <manafo at gmail.com>
> Sent: Saturday, June 14, 2008 7:05 PM
> To: David Coulson <david at davidcoulson.net>
> Cc: cisco-nsp at puck.nether.net <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] VLANs over IP unnumbered
>
>
> The VLAN interface still up! this is the strange behavior i have, the
> static
> route withdrawn!! i don't know why.
> the mac address still in the table but not in the arp table.
>
> On Sun, Jun 15, 2008 at 1:54 AM, David Coulson <david at davidcoulson.net>
> wrote:
>
> >
> > Manaf Oqlah wrote:
> >
> >> Routing entry for 10.10.0.0/20
> >>  Known via "connected", distance 0, metric 0 (connected, via interface)
> >>  Routing Descriptor Blocks:
> >>  * directly connected, via Vlan111 -------------> Vlan101 is the main
> vlan
> >> on 7600 router which has the ip address 10.10.10.1 (clients gateway)
> >>      Route metric is 0, traffic share count is 1
> >>
> >>
> > What is the status of the VLAN interface for that client when you have a
> > failed lookup? The question is - Why does the static route get withdrawn
> > from the table.
> >
> > David
> >
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
> Note: This message and any attachments is intended solely for the use of
> the individual or entity to which it is addressed and may contain
> information that is non-public, proprietary, legally privileged,
> confidential, and/or exempt from disclosure.  If you are not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution, or copying of this communication is strictly prohibited.  If
> you have received this communication in error, please notify the original
> sender immediately by telephone or return email and destroy or delete this
> message along with any attachments immediately.
>
>