On Fri, Jun 14, 2013 at 10:12:56PM -0700, Joel Mulkey wrote:
> Ondrej,
>
> I can confirm that this did fix the issue. Thank you for fixing this, and so
> quickly.
> Should I assume this change will be included in release 1.3.11?
Yes, of course.
--
Elen sila lumenn' omentielvo
Ondrej 'SanTiag
On Sat, Jun 15, 2013 at 02:41:12PM -0400, Ryan Whelan wrote:
> Wow- thanks for the quick response guys! This works great!
>
> Is it possible to set the dead timer, auth ttype, password, etc per area
> and only override the interface differences (like cost) on a per interface
> basis? (having the
On Tue, Jun 18, 2013 at 08:48:41AM +1200, Sam Russell wrote:
> Is there a set of unit tests for BIRD somewhere? I don't know where I'd
> start building them, but I'm happy to do the legwork on the coding - unit
> testing will make it a lot easier to add new modules and guarantee the
> functionality
Do you have any preferences or recommendations for a unit testing
framework? Distributed network software isn't too hard - if you abstract
out the socket stuff you're just dealing with packets being sent to a
callback function - and if packets can be sent to it, then test data works
fine too. It ta
On Fri, Jun 14, 2013 at 05:41:10PM -0700, Simon Dickhoven wrote:
> OK. I looked at proto/rip/rip.c a bit more and figured that I might as
> well give it a shot and hack around a little bit. I ended up making this
> tiny mod:
Hello
Thanks for the bugreport and patch. As i understand RFC 2080,
That would be helpful- it'd be nice to not have to keep the same setting
in multiple places in the config file
On Tue, Jun 18, 2013 at 4:50 AM, Ondrej Zajicek wrote:
> On Sat, Jun 15, 2013 at 02:41:12PM -0400, Ryan Whelan wrote:
> > Wow- thanks for the quick response guys! This works great!
>
Hi, again
If you were paying attention (unlike myself) you may have noticed that
the below fix doesn't actually make BIRD RFC-compliant.
Rather, it makes BIRD interoperate with other RFC-compliant RIPng routers.
After all, the RFC doesn't state that route advertisements must be sent
with an
Hi
we've got a private AS with two uplinks to our ISP, and we've got a
number of subnets that we advertise. Now we got a new assignment and it
doesn't work as expected.
Here is the situation:
x.x.74.113
x.x.74.114
[DMZ1_box_1]
||
[DMZ1_GW] -- OSPF -- [GW_1] -- OSPF -- [GW_2] -- OSPF -- ...
x
Correction: The RFC does state explicitly that advertisements must be sent with
an HLIM of 255, as well as that receiving routers must check that the HLIM is
255.
So I guess my little patch makes BIRD half-compliant in that respect then :).
- Simon
On Jun 18, 2013, at 17:38, "Simon Dickhoven"
A more detailed topology (with IPs and interface names) would be helpful
to understand the setup better.
Is it possible that your ISP is accepting "le 32" on their BGP session
with GW_2 (and that's the one they checked when you asked them to
verify) but only "le 31" on their BGP session with G
10 matches
Mail list logo
