Hello Eygene,
On Sun, Feb 17, 2008 at 08:11:04PM +0300, Eygene Ryabinkin wrote:
I should more carefully study current OpenBSD CVS: the fix for your
problem was committed 5 months ago. Claudio mentioned it (and he
is the author of the patch itself), but the fix didn't get into 4.2.
The
Josef, good day.
Mon, Feb 18, 2008 at 11:50:24AM +0100, Josef Pojsl wrote:
OK, to the point: the inlined patch should go to the 'files'
directory, named 'patch-p2p_interfaces'. I assume that all my
previous patches to make 4.2 to compile and run were applied.
Thaks a lot, I have applied
Josef, good day.
Thu, Feb 14, 2008 at 06:15:09PM +0300, Eygene Ryabinkin wrote:
OK, I will up my gifX interfaces and will try to simulate your problem.
OK, problem recreated. Will try to understand and fix the issue.
Will drop a mail, once the situation will be more clear.
Thinking,
Thu, Feb 14, 2008 at 07:49:34AM +0300, Eygene Ryabinkin wrote:
I have replaced patch-ospfd_packet.c with the new one,
and OSPF packets can find their way through again now. Unfortunately,
the behavior is the same as with openospfd 4.0; it converges with
right costs etc., but with the wrong
Josef, good day.
Fri, Feb 08, 2008 at 11:53:57AM +0100, Josef Pojsl wrote:
I did try the patch. Unfortunately, the deamon complains about sending packets
over gre interfaces. I cannot see any OSPF traffic on them with tcpdump,
and no routes get added.
Found another OpenBSD/FreeBSD
Wed, Feb 13, 2008 at 10:37:29PM +0300, Eygene Ryabinkin wrote:
Attached is the modified patch for the port itself and the modified
file 'files/patch-ospfd_packet.c': it is the only changed file from
the previous version of my patch. So, if you had already patched
the port to 4.2 with previous
Hello Eygene,
On Wed, Feb 13, 2008 at 10:37:29PM +0300, Eygene Ryabinkin wrote:
Found another OpenBSD/FreeBSD discrepancy: FreeBSD wants to see IP
header's length in the native host order, when it sends the packets
with sendmsg(). Corrected the patch and tried it on my test setup
with Qemu:
Josef, good day.
Wed, Feb 13, 2008 at 09:30:12PM +0100, Josef Pojsl wrote:
On Wed, Feb 13, 2008 at 10:37:29PM +0300, Eygene Ryabinkin wrote:
Found another OpenBSD/FreeBSD discrepancy: FreeBSD wants to see IP
header's length in the native host order, when it sends the packets
with
Josef, good day.
Fri, Feb 08, 2008 at 11:53:57AM +0100, Josef Pojsl wrote:
I did try the patch. Unfortunately, the deamon complains about sending packets
over gre interfaces. I cannot see any OSPF traffic on them with tcpdump,
and no routes get added. Look at what ospfd -dv says:
startup
Hi Eygene,
On Thu, Feb 07, 2008 at 07:57:47PM +0300, Eygene Ryabinkin wrote:
OK, the first patch version is ready. It compiles well and even
starts for the trivial configuration. I will try to test it for
other configurations, but you may test it as well: I will appreciate
it very much.
Hi Eygene,
Thanks a lot for your remarks. I absolutely agree with you
that all columns are correct except the Nexthop.
On Wed, Feb 06, 2008 at 06:21:42PM +0300, Eygene Ryabinkin wrote:
Josef, good day.
Currently I can not answer your question, sorry. I just have the
remark.
Wed, Feb 06,
Me again.
Thu, Feb 07, 2008 at 05:58:32PM +0300, Eygene Ryabinkin wrote:
Thu, Feb 07, 2008 at 03:14:22PM +0100, Claudio Jeker wrote:
On Thu, Feb 07, 2008 at 08:49:44AM +0100, Josef Pojsl wrote:
Thanks a lot for your remarks. I absolutely agree with you
that all columns are correct except
Josef, Claudio, good day.
Thu, Feb 07, 2008 at 03:14:22PM +0100, Claudio Jeker wrote:
On Thu, Feb 07, 2008 at 08:49:44AM +0100, Josef Pojsl wrote:
Thanks a lot for your remarks. I absolutely agree with you
that all columns are correct except the Nexthop.
The nexthop selection for point
On Thu, Feb 07, 2008 at 08:49:44AM +0100, Josef Pojsl wrote:
Hi Eygene,
Thanks a lot for your remarks. I absolutely agree with you
that all columns are correct except the Nexthop.
The nexthop selection for point to point links had a bug in versions
previous to 4.2. This should be fixed in
Hello,
I am trying to use openospfd 4.0 over FreeBSD 6.2 in order
to provide redundancy for routing between LAN 1 and LAN 2.
The picture is as follows:
Locality 1 (LAN 1) Locality 2 (LAN 2)
WAN X
Router 1 WAN Y
Josef, good day.
Currently I can not answer your question, sorry. I just have the
remark.
Wed, Feb 06, 2008 at 03:41:04PM +0100, Josef Pojsl wrote:
ospfctl show rib:
Router 1:
Destination Nexthop Path TypeType CostUptime
0.0.0.2 10.31.2.2
16 matches
Mail list logo
