Don't do it. It's a hack and there are other forwarding plane things
that don't like it. Read as..it may or may not always work.
Burn another /32 for your loopback.
Rodney
Aaron wrote:
Loopback interfaces do not go down, so I'm not sure what benefit you are
getting besides the ability to blackhole the 10.10.10.0/24 if the ethernet
goes down.
On Mon, Aug 3, 2009 at 11:09, Michael Ulitskiy <[email protected]> wrote:
Hello,
Guys, are there any drawbacks of doing the following:
interface Lo0
ip address 10.10.10.1 255.255.255.0
!
interface FastEthernet0/0.1
encapsulation dot1q 1 native
ip unnumbered Lo0
!
ip route 10.10.10.0 255.255.255.0 FastEthernet0/0.1
!
as opposed to having ip address configured directly on the interface as
usual?
I need that ip address to stay always up regardless of Fa0/0 state, 'cause
it's used for other services that should stay up
and I'd prefer to avoid assigning another ip address exclusively for
loopback use.
It seems to work in my lab, but I thought I'd better ask...
Thanks,
Michael
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
