[Xorp-users] Xorp, pimsm and ethertap
Atanu Ghosh
atanu@ICSI.Berkeley.EDU
Fri, 24 Feb 2006 12:50:22 -0800
>>>>> "Calum" == Calum <caluml@gmail.com> writes:
Calum> Hello Pavlin, I've just tried out the xorpsh interface, and
Calum> it's much easier (for me) to configure the system.
Calum> I am trying to create a BGP peering, but am getting an error
Calum> when I commit:
Calum> # commit Commit Failed 102 Command failed
Calum> AddressFamilyMismatch from line 64 of iptuple.cc: mismatch
Calum> 10.0.0.122 hush[edit]
Calum> I notice that when the interface asks for the local-ip (which
Calum> I missed) ...
Calum> # commit Missing mandatory configuration node "$(@.local-ip)"
Calum> required by node "protocols bgp peer hush" The configuration
Calum> has not been changed. Fix this error, and run "commit"
Calum> again. # create protocols bgp peer hush local-ip Possible
Calum> completions: <text> Set the IP address on this router to use
Calum> for this peering. # create protocols bgp peer hush local-ip
Calum> 10.0.0.122 [edit]
Calum> ..it asks for a "text" input rather than "<IPv4>" as it does
Calum> for most of the other required IP addresses. E.g.
Calum> # create protocols bgp peer hush next-hop ? Possible
Calum> completions: <IPv4> IPv4 next-hop
Calum> Is this text/IPv4 difference intentional?
The peer and local-ip arguments can be text to allow IPv4, IPv6 or
hostname. Without looking at the code I suspect that hush has resolved
to an IPv6 address and the provided local-ip is IPv4 hence the
AddressFamilyMismatch.
Atanu.