[rbak-nsp] Looback and intercontext - ping didn't respond

Michał Korzeniowski Michal.Korzeniowski at metrointernet.pl
Thu Jan 27 15:37:54 EST 2011


For me, the main 127.0.0.1 works. In the context is not, apparently so it
should be.

 You must turn: service inter-context routing

 You should not create any interface connection.
 Routing simply enforces the command:

 eg.

 [BGP]
 ip route 83.142.196.0/24 context BRAS




MK



On 11-01-27 17:41, "Piotrek S." <komuch at gmail.com> wrote:

>Hi,
>
>This is my first mail and i put the first steps with SE100.
>So... Hello world! :)
>
>My problem is trivial - i can't connect two or more contexts via
>intercontext interface.
>So i tried to ping local interface:
>
>[local]rbak01#show ip interface brief
>Thu Jan 27 17:27:59 2011
>Name              Address                   MTU   State    Bindings
>local-mgmt-if     192.168.201.66/24         1500  Up       (inter-cxt-lan)
>
>with no success:
>
>PING 192.168.201.66 (192.168.201.66): source 192.168.201.66, 36 data
>bytes,
>timeout is 1 second
>.....
>
>Why didn't respond ?
>
>and another strange thing (for me):
>
>[BGP]rbak01#ping 127.0.0.1
>PING 127.0.0.1 (127.0.0.1): 36 data bytes,
>timeout is 1 second
>.....
>
>127.0.0.1 in context BGP didn't respond. Why ?
>
>
>Many thanks for help.
>
>Regards
>_______________________________________________
>redback-nsp mailing list
>redback-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/redback-nsp




More information about the redback-nsp mailing list