Suport technique et veille technologique
Aujourd’hui, les grandes entreprises et administrations publiques hésitent entre continuer à utiliser des logiciels propriétaires ou basculer vers les Logiciels Libres. Pourtant, la plupart des logiciels libres sont capables de bien traiter les données issues des logiciels propriétaire, et parfois avec une meilleur compatibilité.
C’est alors la barrière de la prise en main qui fait peur, et pourtant...
Les logiciels libres
L’aspect « Logiciel Libre » permet une évolution rapide et une plus grande participation des utilisateurs. Les aides et tutoriels foisonnent sur Internet ou sont directement inclus dans le logiciel lui-même.
Enfin, les concepteurs sont plus proches des utilisateurs, ce qui rend les logiciels libres plus agréable à utiliser et conviviaux.
Grâce à la disponibilité des logiciels libres, vous trouverez facilement des services de support techniques et la licence n’est plus un frein à l’utilisation de ces logiciels par votre personnel.
Notre support technique concerne essentiellement les logiciels libres, que ce soit sous forme de services ponctuels ou de tutoriels.
- Novembre 2019 -
I created a bot to
answer BGP
queries over the fediverse (decentralized
social
network, best known implementation being Mastodon). What for? Well,
mostly for the fun, but also because I need from time to time to
find out the origin AS for an IP address or
prefix, and I don't have a direct access to a DFZ router. This article is
to document this project.
The idea was originally suggested during my lightning talk at RIPE 76 meeting in
Marseille.
First, how to use it. Once you have a
Fediverse account (for Mastodon, see
https://joinmastodon.org/
), you
write to @bgp@botsin.space
. You just tell it
the IP address (or IP prefix) you want to know about and it
replies with the actually announced prefix and the origin
AS. There are also links to the RIPE Stat
service, for more details. Here is an example, with the answer:
The bot replies with the same level of confidentiality as the
query. So, if you want the request to be private, use the "direct"
mode. Note that the bot itself is very indiscreet: it logs
everything, and I read it. So, your direct messages will be
private only from third parties, not from the bot
administrator.
If you are a command-line fan, you can use the madonctl tool to
send the query to the bot:
% madonctl toot "@bgp@botsin.space 2a01:e34:ec2a:94a0::4"
You can even make a shell function:
# Definition (in a startup file)
whichasn() {
madonctl toot --visibility direct "@bgp@botsin.space $1"
}
# Usage
% whichasn
You can also, instead of an IP address, just send "info" and the
bot will reply with details about the number of prefixes and AS it knows.
There is also a more classical (non-fediverse) Web interface, at
https://bgp.bortzmeyer.org/IPADDRESS
. For
instance, with curl :
% curl https://bgp.bortzmeyer.org/159.89.230.222
159.89.224.0/20 1406
Note that, unlike the fediverse interface, the Web interface is
not really necessary, you could use other online services such
as
RIPE
Stat. Here is an example with RIPE Stat (we use
jq to parse the resulting JSON):
% curl -s https://stat.ripe.net/data/routing-status/data.json\?resource=185.49.140.0 | jq .data.resource
"185.49.140.0/22"
Now, the implementation of the bot. (You can get all the files
at https://framagit.org/bortzmeyer/fediverse-bgp-bot/
.)
The code is derived from my DNS
bot so I won't repeat here most of the stuff, only the
BGP-specific things.
The bot backend could call directly the RIPE stat API
mentioned above. But there is a limit in the number of requests
and, if the bot is popular, it could be blacklisted. Same thing for
other online services. Hence my choice of getting the raw RIS dumps. Parsing
them and serving them to the bot is done by the WhichASN
daemon.
Other useful services and readings for the
BGP fans:
- We rely on the excellent RIS
(Routing Information Service), which collects and stores
BGP information, before making them available to the
public.
- There are other ways to access RIS data, such as RIPE Stat or RIS Live.
- The RouteViews project has
several
useful tools, such as a DNS
interface. It would solve the rate-limiting issue but,
unfortunately, it works only with
IPv4.
- I also like the Qrator API (but you
need to register).
- I could also have used BGPstream.
- There are also several whois
servers distributing BGP information such as
whois.cymru.com
or whois.bgpmon.net
.
RFC 9562: Universally Unique IDentifiers (UUIDs)
- 12 mai -
Ce RFC normalise les UUID, une famille d'identificateurs uniques, obtenus sans registre central. Il remplace l'ancienne norme, le RFC 4122, avec (...)
RFC 9490: Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN)
- 9 mai -
Aujourd'hui, l'essentiel du trafic sur l'Internet est chiffré, et pour d'excellentes raisons. Pas question de revenir là-dessus, mais, ceci dit, il (...)
RFC 9557: Date and Time on the Internet: Timestamps with Additional Information
- 29 avril -
Ce RFC modifie légèrement le format des estampilles temporelles du RFC 3339, changeant à la marge une définition et, surtout, permettant d'y attacher (...)
RFC 9567: DNS Error Reporting
- 27 avril -
Lorsqu'un résolveur DNS détecte un problème avec une zone, l'empêchant de résoudre les noms dans cette zone, il n'avait pas de moyen simple et (...)
RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
- 8 avril -
Ces deux nouveaux types d'enregistrement DNS, SVCB et sa variante HTTPS, permettent de donner des informations supplémentaires à un client réseau (...)