- You likely want to use the lo0 interface for this (although I suppose
lo1 will suffice, but lo0 is the 'standard' loopback address (don't beat
me up about my use of the word 'standard'))
- Stop using the term 'dummy' in reference to any interface. There is no
such thing. You are referring to the loopback interface, the interface
that doesn't actually bind to a particular physical network interface on
your box. Take a hint- Henning is getting annoyed with you... that can't
help you in any way.
- Using the loopback interface for peering sessions has been prescribed
by many for many years now because it allows EBGP sessions assigned to
it to persist even if one or more physical interfaces drops. However, in
reality, I have found that this is usually disastrous. You normally
don't want the peer session to outlast the production circuit the routes
are intended to traverse, or you risk receiving routes that lead to
nowhere, and that's always bad. The most common use I can think of for
proper use of loopback interfaces for BGP peering is for IBGP sessions,
not EBGP sessions. I'll ask what are you intending to use it for,
because your previous statements are not clear ("What i want to
accomplish and wanted to do is to be able to use such an interface when
all the NIC on my machines are alloted for BGP").
If someone else here has a different philosophy regarding BGP peers
configured on loopbacks, share it.
Ducking,
danno
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of [EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 5:54 PM
To: misc@openbsd.org
Subject: Re: Dummy Interface In OpenBGPd
The thing is, after I creatd /etc/hostname.lo1 as stated and I tring to
ping it from other devices
within that network, it is not reachable. I put network 10.83.66.128/32
in my /etc/bgpd.conf but
still I can only ping this interface from that host it is put in but not
from the other host.
Some hints? Should I manually add a route to it in the kernel routing
table?
> On Wed, Feb 07, 2007 at 12:07:56PM -0000, [EMAIL PROTECTED] wrote:
>> Does that categorically mean there is no way, as of the moment, in
>> openbgp to use a dummy interface just like in Quagga?
>>
>
> There are no dummy interfaces. If you like to use a loopback interface
> create one.
>
> # cat > /etc/hostname.lo1
> inet 10.83.66.128 255.255.255.255 NONE
> # sh /etc/netstart lo1
>
> That's it. You have a loopback address that can be used in bgpd.
>
> neighbor 10.83.66.164 {
> remote-as 65123
> local-address 10.83.66.128
> }
>
> I guess that's what you are looking for. bgpd does not realy care
about
> interfaces. Interfaces and their link state are only used to figure
out
> the availability of nexthops.
>
> Btw. for ospfd you can use "interface lo1" to reliably redistribute
the
> loopback address.
>
> --
> :wq Claudio
>
>> > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2007-02-07 12:31]:
>> >> As I read the openbgpd documentation, there is not a single point
wherein in the examples a
>> >> dummy
>> >> interface is being used. Is a dummy interface supported in
OpenBGP?
>> >
>> > -vvv :)
>> >
>> > from bgpd's perspective, an interface is an interface, mostly.
>> >
>> > --
>> > 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
