Hello,
The release is :
bgp1 # uname -rsv
OpenBSD 3.9 GENERIC#617
and yes 212.x.x.253 is my neigbhor.
bgp1 # ifconfig carp0
carp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
carp: BACKUP carpdev em0 vhid 1 advbase 1 advskew 100
groups: carp
inet 212.x.x.254 netmask 0xfffffffc broadcast 212.xxx.xxx.255
bgp1 # ifconfig em0
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:07:e9:24:aa:38
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::207:e9ff:fe24:aa38%em0 prefixlen 64 scopeid 0x1
bgp1 # bgpctl neighbor 212.x.x.253 up
request processed
bgp1 # route -n get 212.x.x.253
route to: 212.x.x.253
destination: 212.x.x.253
interface: carp0
if address: 212.x.x.254
flags: <UP,HOST,DONE,LLINFO,CLONED>
recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu
expire
0 0 0 0 0 0 0
1169
bgp1 # bgpctl sh next
Nexthop State
212.x.x.253 valid
64.x.x.148 valid em1 UP, Ethernet, active, 100 MBit/s
bgp1 # bgpctl sh interfaces
Interface Nexthop state Flags Link state
carp5 ok UP CARP, master
carp6 ok UP CARP, master
carp0 ok UP CARP, master
lo0 ok UP unknown
enc0 invalid unknown
pfsync0 ok UP unknown
pflog0 invalid unknown
hme7 ok UP Ethernet, active, 100 MBit/s
hme6 ok UP Ethernet, active, 100 MBit/s
hme5 invalid UP Ethernet, no carrier
hme4 ok UP Ethernet, active, 100 MBit/s
hme3 ok UP Ethernet, active, 100 MBit/s
hme2 invalid Ethernet, unknown
hme1 invalid Ethernet, unknown
hme0 invalid Ethernet, unknown
em1 ok UP Ethernet, active, 100 MBit/s
em0 ok UP Ethernet, active, 100 MBit/s
Henning Brauer wrote:
>
> * ClaudeBrassel <[EMAIL PROTECTED]> [2006-10-26 12:44]:
>> carp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>> carp: MASTER carpdev em0 vhid 1 advbase 1 advskew 100
>> groups: carp
>> inet 212.xxx.xxx.254 netmask 0xfffffffc broadcast 212.xxx.xxx.255
>
>> ip_interroute="212.xx.xx.253"
>> neighbor $ip_interroute {
>> remote-as 8928
>> descr "peering interroute"
>> local-address 212.xxx.xxx.254
>> holdtime 180
>> holdtime min 3
>> announce self
>> }
>
> you'll likely want a "depend on carp0" within the neighbor definition
> for interroute, but taht is related to your issue.
>
>> bgp1 # bgpctl sh next
>> Nexthop State
>> 212.xxx.xxx.253 valid
>
> so .253 is the interroute router right?
>
> [ show rib ]
>> *> 195.68.0.0/17 212.xxx.xxx.254 100 0 8928 8220 i
>
> please show "route -n get 212.xxx.xxx.253"
> also, what release are you on? we fixed some cases where the interface
> pointer was missing in messages on the routing socked, and I think that
> was post-3.9
>
>> If I delete the carp and bring the em0 with the ip up everything works
>> great
>
> yeah. carp plays fast with routes. and screws up. it fiddles with the
> interface route, and that is broken for at least unnumbered interfaces.
> ryan and I need to find some time to sit over this together.
>
> nontheless. I have a similar setup with a carp interface to an exchange
> point network, and that works just fine - with something close to 4.0.
>
> --
> Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED]
> BS Web Services, http://bsws.de
> Full-Service ISP - Secure Hosting, Mail and DNS Services
> Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam
>
>
>
--
View this message in context:
http://www.nabble.com/OpenBGP---carp-interface-tf2513187.html#a7009644
Sent from the openbsd user - misc mailing list archive at Nabble.com.
