Fwd: [Xorp-users] Xorp, pimsm and ethertap

[Mike Horn]

Hi Calum,

Both the "next-hop" and "local-ip" addresses should be the local interface IP address (10.0.0.122 in your example).  The peer "hush" should either be a resolvable hostname for your BGP peer (not recommended) or should be the IP address of your peer (recommended).

Here is what the updated configuration would look like:

>   protocols {
>       bgp {
>           peer 10.0.0.121 {
>               as: 1
>               peer-port: 179
>               local-port: 179
>               holdtime: 90
>               delay-open-time: 0
>               client: false
>               confederation-member: false
>               disable: false
>               ipv4-unicast: true
>               ipv4-multicast: false
>               ipv6-unicast: false
>               ipv6-multicast: false
>               next-hop: 10.0.0.122
>               local-ip: "10.0.0.122"
>           }
>           local-as: 4
>           bgp-id: 10.0.0.122
>       }

-mike

----- Original Message -----
From: Calum <caluml@gmail.com>
To: xorp-users@xorp.org
Sent: Friday, February 24, 2006 1:37:37 PM GMT-0700
Subject: Re: [Xorp-users] Xorp, pimsm and ethertap

Hello Pavlin,

I've just tried out the xorpsh interface, and it's much easier (for
me) to configure the system.

I am trying to create a BGP peering, but am getting an error when I commit:

# commit
Commit Failed
102 Command failed AddressFamilyMismatch from line 64 of iptuple.cc:
mismatch 10.0.0.122 hush[edit]

I notice that when the interface asks for the local-ip (which I missed) ...

# commit
Missing mandatory configuration node "$(@.local-ip)" required by node
"protocols bgp peer hush"
The configuration has not been changed.
Fix this error, and run "commit" again.
# create protocols bgp peer hush local-ip
Possible completions:
  <text>          Set the IP address on this router to use for this peering.
# create protocols bgp peer hush local-ip 10.0.0.122
[edit]

..it asks for a "text" input rather than "<IPv4>" as it does for most
of the other required IP addresses. E.g.

# create protocols bgp peer hush next-hop ?
Possible completions:
  <IPv4>          IPv4 next-hop


Is this text/IPv4 difference intentional?

Here is my current (uncommited) config from show -all

    interfaces {
        interface taphush {
            default-system-config
            disable: false
            discard: false
            description: ""
            vif taphush {
                disable: false
            }
        }
        restore-original-config-on-shutdown: false
    }
>   protocols {
>       bgp {
>           peer hush {
>               as: 1
>               peer-port: 179
>               local-port: 179
>               holdtime: 90
>               delay-open-time: 0
>               client: false
>               confederation-member: false
>               disable: false
>               ipv4-unicast: true
>               ipv4-multicast: false
>               ipv6-unicast: false
>               ipv6-multicast: false
>               next-hop: 10.0.0.121
>               local-ip: "10.0.0.122"
>           }
>           local-as: 4
>           bgp-id: 10.0.0.122
>       }


I see that the local-ip is as "10.0.0.122" - I think I tried editting
it manually, and setting it to 10.0.0.122, and it didn't make it work.

(I'm using "real" ASs rather than the ones set aside for testing
because I'm lazy. :) )


Calum


--
Ask me about Linux virtual servers.
A80F D3A0 0EFA 23FE@wwwkeys.eu.pgp.net

_______________________________________________
Xorp-users mailing list
Xorp-users@xorp.org
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users