If nobody answers this question by the time I get home I'll try and
help; however, in the mean time I do have a couple of suggestions.
Have you tried writing the equivalent program in C using the sockets
API? IE is this a python specific problem or a sockets problem in
general?
The second thing
Paul Thornton writes:
> On 09/02/2015 16:34, Daniel Corbe wrote:
>>
>> For some reason, every time I create a GRE interface on a FreeBSD IPv6
>> gateway, net.inet6.ip6.forwarding is disabled. As long as I manually
>> re-enable it with sysctl, both the GRE tunnel and
For some reason, every time I create a GRE interface on a FreeBSD IPv6
gateway, net.inet6.ip6.forwarding is disabled. As long as I manually
re-enable it with sysctl, both the GRE tunnel and the IPv6 network
behind this machine will continue to work; however, it's certainly far
from ideal.
There'
Generally the answer to your question is no. Two applications cannot
occupy the same port on the same protocol at the same time.
To expand on this answer and to hopefully shed some light on why the
behavior you're observing with your application is absolutely correct;
the calling application (in
"Alexander V. Chernikov" writes:
> On 16.07.2014 21:48, Daniel Corbe wrote:
> Hm. What do you need from bird OSPF implementation?
> IMHO it is much easier to improve and merge bird code instead of
> writing another OSPF implementation from scratch.
>
I can't get
Jan Bramkamp writes:
> On 16.07.2014 19:48, Daniel Corbe wrote:>
>> I hope this it the right place to ask questions about netmap. I'm
>> toying with the idea of writing a netmap-based OSPF implementation
>> because bird's OSPF implementation isn't as go
I hope this it the right place to ask questions about netmap. I'm
toying with the idea of writing a netmap-based OSPF implementation
because bird's OSPF implementation isn't as good as its BGP
implementation, quagga doesn't scale well and openospfd doesn't compile
on 10-RELEASE or CURRENT.
But I
