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] how does ecos build its routing tables?
Date: Wed, 17 Oct 2012 16:10:00 -0000 [thread overview]
Message-ID: <507ED856.5070406@televic.com> (raw)
In-Reply-To: <507D74EB.90001@televic.com>
On 10/16/2012 04:53 PM, Lambrecht Jürgen wrote:
> Hello,
>
> We cannot set our routing tables correct!
> We use the freeBSD network stack.
>
> We configure it with a fixed IP adress (172.24.0.0/13) with netmask
> 255.248.0.0.
> But always in the routing table the netmaskk 255.255.0.0 is present??
> How is this possible?
We also have a network with netmask 248.0.0.0, and then in the routing
table the netmask 255.0.0.0 is present.
So I think the freeBSD network stack only can set the netmask in the
routing table per byte.
Can somebody confirm this?
Any solution?
Regards,
Jürgen
> Here the result of a print of the routing tables (I use functions that
> you can find back on the ecos mailing list):
> -----------------------------------------------------------------
> Televic telnet shell. Welcome.
>
> $> ifconfig
>
> Routing tables
> Destination Gateway Mask Flags Interface
> 127.0.0.0 127.0.0.1 255.0.0.0 UG lo0
> 127.0.0.1 127.0.0.1 UH lo0
> 172.24.0.0 172.24.0.0 255.255.0.0 U eth0
> Interface statistics
> eth0 IP: 172.24.0.11, Broadcast: 172.31.255.255, Netmask: 255.248.0.0
> UP BROADCAST RUNNING MULTICAST MTU: 1500, Metric: 0
> Rx - Packets: 44, Bytes: 3660, Tx - Packets: 23, Bytes: 2090
> lo0 IP: 127.0.0.1, Broadcast: 127.0.0.1, Netmask: 255.0.0.0
> UP LOOPBACK RUNNING MULTICAST MTU: 16384, Metric: 0
> Rx - Packets: 0, Bytes: 0, Tx - Packets: 0, Bytes: 0
> -----------------------------------------------------------------
> Our RedBoot uses the 255.255.0.0 netmask, could that explain it?
>
> And when we add the correct route and then delete the wrong route, our
> network connection goes away - a ping fails..
>
> Any help is appreciated!
>
> Kind regards,
> Jürgen
>
> -
> Jürgen Lambrecht
> R&D Associate
> 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
>
--
Jürgen Lambrecht
R&D Associate
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
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2012-10-17 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 14:53 Lambrecht Jürgen
2012-10-17 16:10 ` 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=507ED856.5070406@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).