Mailing List Archive

1 2  View All
Re: Problems with ripd in quagga-0.96.4 [ In reply to ]
On Thu, 6 Nov 2003 sowmini.varadhan@sun.com wrote:

> well, OPEN_MAX is usually 256.
>
> > And on embedded devices, its easier (and cheaper?) to add memory. Just
> > my opinion.
>
> yes, but zebra is also used on non-embedded devices like workstations.

a workstation is unlikely to have more than 2 interfaces). So I'd say
"open a socket per interface" doesnt hurt workstations.

At the other end of the scale, machines with literally /hundreds/ of
interfaces by means of 802.1q+switches, its better to tweak the
machine to have enough fd's and RAM /once/ than pay run-time costs.

> --Sowmini

regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
warning: do not ever send email to spam@dishone.st
Fortune:
Money isn't everything -- but it's a long way ahead of what comes next.
-- Sir Edmond Stockdale
Re: Problems with ripd in quagga-0.96.4 [ In reply to ]
On Fri, 7 Nov 2003 sowmini.varadhan@sun.com wrote:

> my mistake. I'll work on the fix so that the rebinding only happens
> for Solaris.

Why rebind at all? even for solaris?

>
> --Sowmini

regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
warning: do not ever send email to spam@dishone.st
Fortune:
The only possible interpretation of any research whatever in the `social
sciences' is: some do, some don't.
-- Ernest Rutherford
Re: Problems with ripd in quagga-0.96.4 [ In reply to ]
On Fri, 7 Nov 2003 sowmini.varadhan@sun.com wrote:
<CIACH>
> I'm attaching the diffs below. It's not pretty, but I wanted
> to avoid towing the source address on the stack as a function
> argument, and having a global var is not any different than
> binding the socket's local address up in rip_update_process()
> or rip_request_send() in preparation for rip_send_packet.

OK. Patch tested, works for me. Thanks :)

Best regards,

Krzysztof Olêdzki
Re: Problems with ripd in quagga-0.96.4 [ In reply to ]
On Mon, 10 Nov 2003, Krzysztof Oledzki wrote:

>
>
> On Fri, 7 Nov 2003 sowmini.varadhan@sun.com wrote:
> <CIACH>
> > I'm attaching the diffs below. It's not pretty, but I wanted
> > to avoid towing the source address on the stack as a function
> > argument, and having a global var is not any different than
> > binding the socket's local address up in rip_update_process()
> > or rip_request_send() in preparation for rip_send_packet.
>
> OK. Patch tested, works for me. Thanks :)

Oh! Not so fast. :(( Yes, it works for RIPv2 multicast but it completly
breaks broadcast:

2003/11/19 22:13:41 RIP: broadcast request to eth0
2003/11/19 22:13:41 RIP: SEND request to 192.168.31.255
2003/11/19 22:13:41 RIP: SEND to 192.168.31.255.520
2003/11/19 22:13:41 RIP: SEND to 192.168.31.255.520
2003/11/19 22:13:41 RIP: can't send packet : Bad file descriptor
2003/11/19 22:13:41 RIP: SEND request to 192.168.31.255
2003/11/19 22:13:41 RIP: SEND to 192.168.31.255.520
2003/11/19 22:13:41 RIP: can't send packet : Bad file descriptor
2003/11/19 22:13:41 RIP: select() error: Bad file descriptor

And then ripd exits.

Best Regards,

Krzysztof Olêdzki

1 2  View All