public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
To: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Cc: Deroo Stijn <S.Deroo@TELEVIC.com>
Subject: Re: [ECOS] freeBSD sets wrong netmask for non-ABC class IP addresses
Date: Wed, 02 Sep 2015 12:14:00 -0000	[thread overview]
Message-ID: <55E6E801.30801@televic.com> (raw)
In-Reply-To: <55C45BDE.1080101@televic.com>

To re-phrase my question:

is CIDR (classless inter-domain routing) supported by the eCos FreeBSD 
stack?
In my experience it is *not*, because we use both /13 and /5 networks 
and both are not fully functional !
So howto enable CIDR in eCos?

Kind regards,
Jürgen

On 08/07/2015 09:18 AM, Lambrecht Jürgen wrote:
> Hi,
>
> The FreeBSD network stack does not accept non-ABC class IP addresses,
> meaning that netmasks must be on 8-bit boundaries.
> (ok, maybe 4-bit works, I did not test that).
> For the interface definition, it is possible to set the correct netmask
> at run time (because it is from from the static configuration).
> For the routing table, it is not possible. (I can share the code if needed)
>
> We have those isolated/private networks:
> - 172.24.0.0/13 -> netmaks 255.248.0.0 -> accepted netmask: 255.255.0.0
> - 80.0.0.0/5 -> netmaks 248.0.0.0 -> accepted netmask: 255.0.0.0
>
> Would anybody know how to fix this?
>
> Kind regards,
> Jürgen
>


-- 
Jürgen Lambrecht
R&D Associate
Mobile: +32 499 644 531
Twitter: JGRLambrecht
Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk

      reply	other threads:[~2015-09-02 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07  7:19 Lambrecht Jürgen
2015-09-02 12:14 ` Lambrecht Jürgen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E6E801.30801@televic.com \
    --to=j.lambrecht@televic.com \
    --cc=S.Deroo@TELEVIC.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).