FRsAG

frsag@frsag.org

13 participants
2602 discussions

[JOBS] Offres d'emploi Admin Sys HPC
by Hyacinthe Cartiaux 24 Jun '14

24 Jun '14

Bonjour la liste ! Je me permets d'utiliser FRSAG pour communiquer 2 offres d'emplois intéressantes en CDD de 24 mois, à pourvoir au sein du LCSB (Luxembourg Centre for Systems Biomedicine), sur le campus Belval de l'Université du Luxembourg. Les candidats seront amenés à travailler sur la [plate-forme HPC] (https://hpc.uni.lu/) de l'université et sur les différents projets du LCSB, dans un environnement international et donc anglophone :) Notre environnement technique est à base de Debian (95%)/ Redhat / Centos, Puppet, Xen, OAR, Apache, Icinga, Openldap, Git, Ruby, etc. Il y a une description des postes ici (candidature jusqu'au 1er juillet): * [Offre 1: HPC System Administrator] (http://recruitment.uni.lu/en/details.html?id=QMUFK026203F3VBQB7V7VV4S8&nPos…) * [Offre 2: Junior HPC System Administrator] (http://recruitment.uni.lu/en/details.html?id=QMUFK026203F3VBQB7V7VV4S8&nPos…) Le rémunération est compétitive, si vous avez des questions (ou voulez des précisions), ne pas hésiter hors liste ! Cordialement, -- Hyacinthe Cartiaux PGP KeyID 0x550DF40B

2 1

Intérêt du "VMware vSphere with,Operations Management" pour une PME ?
by Alexandre 23 Jun '14

23 Jun '14

Bonjour à tous, je souhaite savoir si des personnes utilisent "VMware vSphere with,Operations Management". Je ne remets pas en cause l'intérêt du produit pour une grosse société mais pour une PME cela me semble un peu inutile. j'ai regardé le résumé, ca me semble tellement magique : --- VMware vCenterTM Operations Management Suite assure la gestion automatisée des opérations à l’aide de fonctions analytiques brevetées et d’une approche intégrée de la gestion des performances, des capacités et de la configuration. Avec vCenter Operations Management Suite, les services informatiques bénéficient d’une meilleure visibilité et d’informations directement exploitables. Ainsi munis, ils peuvent garantir les niveaux de service, un usage optimal des ressources et la conformité de la configuration dans les environnements virtuels dynamiques et de Cloud Computing. Le tout avec une véritable proactivité. --- Je suis curieux de savoir s'il a des retours positifs sur ce produit. Alexandre.

2 2

Logiciel de sauvegardes pour serveurs GNU/Linux
by Emmanuel Lesouef 21 Jun '14

21 Jun '14

Bonjour, Nouveau sur cette liste, j'aimerai connaître vos avis concernant les logiciels de sauvegardes de serveurs GNU/Linux. Connaissant déjà certains logiciels libres de sauvegardes (Bacula, Backuppc...), j'aimerai savoir s'il existe des logiciels en mesure de sauvegarder des serveurs de fichiers (samba, nfs...) en conservant les droits étendus (libacl) dans le monde "payant" voire "propriétaire" (eurk...). Merci de vos retours. -- Emmanuel Lesouef

8 7

[Jobs] Recherche de formateurs
by Frédéric Reinold 20 Jun '14

20 Jun '14

Bonjour la liste, Je suis le responsable pédagogique premier cycle de l'EPSI Nantes et je cherche pour l'année scolaire qui arrive une poignée d'intervenants pour renforcer notre équipe. En résumé, il s'agit de modules de 20 heures face à des Bac+4 ou Bac+5. Les domaines pour lesquels nous aurions besoin de renforts sont les suivants : - Systèmes et réseau (Gestion et optimisation des réseaux, Technologies des réseaux intégrant voix, image et données...) - Cloud (développement d’une solution Cloud, sécurité du Cloud...) Si quelqu'un est intéressé ou désire plus d'informations, qu'il n'hésite pas à me contacter. Excellente journée, Frédéric Reinold

1 0

Re: [FRsAG] Choix d'un CDN
by Remy Sanchez 19 Jun '14

19 Jun '14

On Wednesday, June 18, 2014 02:00:46 PM Jonathan Leroy wrote: > CDNify est pas mal non plus. Ah CDNify m'intéresse, il n'était pas passé sur mes radars, mais sa couverture de l'Asie et en particulier de l'Inde m'intéresse fortement. Et en plus, le SSL est gratuit. -- Rémy Sanchez http://goodmorningplanet.com/

3 3

double firewall et vpn
by Manu 17 Jun '14

17 Jun '14

Bonjour à vous! Voilà, pour diverses raisons, je monte une architecture avec double firewall enchaîné. Donc : Internet -- (FW1) -- DMZ -- (FW2) -- LAN En réalité FW1 est physique et FW2 est virtualisé. Je ne peux pas actuellement avoir le LAN directement derrière FW1. Ma question est donc : Quelle serait la bonne pratique pour accéder au LAN depuis l'extérieur ? - VPN sur FW1 et automatiquement trusté par FW2 - VPN sur FW1 puis sur FW2... Merci d'avance Manu

4 4

[JOBS] Recherche Stage Système & Réseau
by Ménahem Houri 17 Jun '14

17 Jun '14

Bonjour la liste, Etudiant en fin de 4eme année à Supinfo, je recherche un stage a partir du mois de Juillet sur Paris, motivé et curieux dans le domaine du Système & Réseau n'hésitez pas à me contacter pour toute demande d'information. Pour le CV => http://ovh.to/WEVvP3D Merci d'avance Bien cordialement, Ménahem HOURI

1 0

Baies à donner sur Paris
by aegiap 13 Jun '14

13 Jun '14

Bonjour, Suite à une refonte d'infrastructure, il nous reste des baies dans la suite que nous libérons à Telehouse2, Paris (hint: appelez vos commerciaux !). Elles sont disponibles sur place à Telehouse2. Ce sont six (6) baies APC 42U dimension 600x1000. Elles disposent d'une porte avant et une porte arrière, mais seuls 2 côtés de baie sont disponibles (les 6 faisaient partie d'une même rangée). Elles sont à venir chercher toutes même jour même heure, si plusieurs interessés, il faudra vous mettre d'accord. Les baies sont démontables jusqu'à un certain point : 4 montants, 2 plaques et les portes. Merci de me contacter si vous êtes intéressé. -- aegiap

7 6

Énigme Réseau
by Aurélien Besse 12 Jun '14

12 Jun '14

Bonjour à tous Voici ma config reseau : wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 60:d8:19:cd:ac:ea brd ff:ff:ff:ff:ff:ff inet 192.168.1.33/24 brd 192.168.1.255 scope global wlan0 inet6 fe80::62d8:19ff:fecd:acea/64 scope link valid_lft forever preferred_lft forever ma route : Destination Passerelle Genmask Indic Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 mon routeur est la box du FAI sans aucune route additionnelle allez le meilleur : ping 172.17.2.1 PING 172.17.2.1 (172.17.2.1) 56(84) bytes of data. 64 bytes from 172.17.2.1: icmp_req=1 ttl=247 time=69.8 ms 64 bytes from 172.17.2.1: icmp_req=2 ttl=247 time=78.5 ms 64 bytes from 172.17.2.1: icmp_req=3 ttl=247 time=85.8 ms ping 172.17.3.1 PING 172.17.3.1 (172.17.3.1) 56(84) bytes of data. 64 bytes from 172.17.3.1: icmp_req=1 ttl=56 time=87.1 ms 64 bytes from 172.17.3.1: icmp_req=2 ttl=56 time=87.7 ms 64 bytes from 172.17.3.1: icmp_req=3 ttl=56 time=92.8 ms 64 bytes from 172.17.3.1: icmp_req=4 ttl=56 time=95.7 ms un coup de traceroute et j'ai l'ip public mouaaaaaaahhhhh petite boucle histoire de savoir combien de réseau et bien la j’hallucine . PING 172.17.185.1 (172.17.185.1) 56(84) bytes of data. 64 bytes from 172.17.185.1: icmp_req=1 ttl=248 time=82.2 ms 64 bytes from 172.17.185.1: icmp_req=2 ttl=248 time=75.3 ms --- 172.17.185.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 75.347/78.804/82.261/3.457 ms PING 172.17.186.1 (172.17.186.1) 56(84) bytes of data. 64 bytes from 172.17.186.1: icmp_req=1 ttl=247 time=75.4 ms 64 bytes from 172.17.186.1: icmp_req=2 ttl=247 time=78.7 ms --- 172.17.186.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 75.481/77.105/78.730/1.648 ms PING 172.17.187.1 (172.17.187.1) 56(84) bytes of data. 64 bytes from 172.17.187.1: icmp_req=1 ttl=249 time=86.8 ms 64 bytes from 172.17.187.1: icmp_req=2 ttl=249 time=88.8 ms --- 172.17.187.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 86.801/87.826/88.852/1.067 ms PING 172.17.188.1 (172.17.188.1) 56(84) bytes of data. 64 bytes from 172.17.188.1: icmp_req=1 ttl=250 time=90.1 ms 64 bytes from 172.17.188.1: icmp_req=2 ttl=250 time=80.8 ms --- 172.17.188.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 80.843/85.471/90.100/4.637 ms PING 172.17.189.1 (172.17.189.1) 56(84) bytes of data. 64 bytes from 172.17.189.1: icmp_req=1 ttl=246 time=81.7 ms 64 bytes from 172.17.189.1: icmp_req=2 ttl=246 time=85.3 ms --- 172.17.189.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 81.784/83.577/85.371/1.816 ms PING 172.17.190.1 (172.17.190.1) 56(84) bytes of data. 64 bytes from 172.17.190.1: icmp_req=1 ttl=248 time=88.3 ms 64 bytes from 172.17.190.1: icmp_req=2 ttl=248 time=75.1 ms --- 172.17.190.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 75.129/81.716/88.303/6.587 ms PING 172.17.191.1 (172.17.191.1) 56(84) bytes of data. 64 bytes from 172.17.191.1: icmp_req=1 ttl=248 time=75.6 ms 64 bytes from 172.17.191.1: icmp_req=2 ttl=248 time=81.3 ms --- 172.17.191.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 75.651/78.523/81.395/2.872 ms PING 172.17.192.1 (172.17.192.1) 56(84) bytes of data. 64 bytes from 172.17.192.1: icmp_req=1 ttl=248 time=86.9 ms 64 bytes from 172.17.192.1: icmp_req=2 ttl=248 time=75.0 ms --- 172.17.192.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 75.047/81.007/86.968/5.967 ms PING 172.17.193.1 (172.17.193.1) 56(84) bytes of data. 64 bytes from 172.17.193.1: icmp_req=1 ttl=250 time=80.3 ms 64 bytes from 172.17.193.1: icmp_req=2 ttl=250 time=87.1 ms --- 172.17.193.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 80.377/83.760/87.144/3.395 ms PING 172.17.194.1 (172.17.194.1) 56(84) bytes of data. 64 bytes from 172.17.194.1: icmp_req=1 ttl=249 time=80.8 ms 64 bytes from 172.17.194.1: icmp_req=2 ttl=249 time=85.2 ms --- 172.17.194.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 80.844/83.027/85.210/2.183 ms PING 172.17.195.1 (172.17.195.1) 56(84) bytes of data. 64 bytes from 172.17.195.1: icmp_req=1 ttl=248 time=78.8 ms 64 bytes from 172.17.195.1: icmp_req=2 ttl=248 time=87.3 ms --- 172.17.195.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 78.828/83.086/87.344/4.258 ms PING 172.17.196.1 (172.17.196.1) 56(84) bytes of data. 64 bytes from 172.17.196.1: icmp_req=1 ttl=246 time=81.2 ms 64 bytes from 172.17.196.1: icmp_req=2 ttl=246 time=79.3 ms --- 172.17.196.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 79.317/80.269/81.222/0.993 ms PING 172.17.197.1 (172.17.197.1) 56(84) bytes of data. 64 bytes from 172.17.197.1: icmp_req=1 ttl=248 time=72.7 ms 64 bytes from 172.17.197.1: icmp_req=2 ttl=248 time=76.9 ms --- 172.17.197.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 72.704/74.826/76.949/2.140 ms PING 172.17.198.1 (172.17.198.1) 56(84) bytes of data. 64 bytes from 172.17.198.1: icmp_req=1 ttl=247 time=89.2 ms 64 bytes from 172.17.198.1: icmp_req=2 ttl=247 time=82.5 ms --- 172.17.198.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 82.557/85.926/89.295/3.369 ms PING 172.17.199.1 (172.17.199.1) 56(84) bytes of data. 64 bytes from 172.17.199.1: icmp_req=1 ttl=247 time=84.8 ms 64 bytes from 172.17.199.1: icmp_req=2 ttl=247 time=87.5 ms --- 172.17.199.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 84.885/86.205/87.525/1.320 ms PING 172.17.200.1 (172.17.200.1) 56(84) bytes of data. 64 bytes from 172.17.200.1: icmp_req=1 ttl=247 time=83.0 ms 64 bytes from 172.17.200.1: icmp_req=2 ttl=247 time=82.8 ms --- 172.17.200.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 82.892/82.957/83.022/0.065 ms PING 172.17.201.1 (172.17.201.1) 56(84) bytes of data. 64 bytes from 172.17.201.1: icmp_req=1 ttl=247 time=125 ms 64 bytes from 172.17.201.1: icmp_req=2 ttl=247 time=91.4 ms --- 172.17.201.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 91.458/108.470/125.483/17.015 ms PING 172.17.202.1 (172.17.202.1) 56(84) bytes of data. 64 bytes from 172.17.202.1: icmp_req=1 ttl=246 time=85.3 ms 64 bytes from 172.17.202.1: icmp_req=2 ttl=246 time=84.5 ms --- 172.17.202.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 84.593/84.994/85.396/0.496 ms PING 172.17.203.1 (172.17.203.1) 56(84) bytes of data. 64 bytes from 172.17.203.1: icmp_req=1 ttl=246 time=80.8 ms 64 bytes from 172.17.203.1: icmp_req=2 ttl=246 time=75.5 ms --- 172.17.203.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 75.531/78.203/80.876/2.687 ms PING 172.17.204.1 (172.17.204.1) 56(84) bytes of data. 64 bytes from 172.17.204.1: icmp_req=1 ttl=246 time=92.4 ms 64 bytes from 172.17.204.1: icmp_req=2 ttl=246 time=89.3 ms --- 172.17.204.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 89.361/90.920/92.480/1.588 ms PING 172.17.205.1 (172.17.205.1) 56(84) bytes of data. 64 bytes from 172.17.205.1: icmp_req=1 ttl=249 time=74.6 ms 64 bytes from 172.17.205.1: icmp_req=2 ttl=249 time=80.7 ms --- 172.17.205.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 74.608/77.688/80.769/3.093 ms PING 172.17.206.1 (172.17.206.1) 56(84) bytes of data. 64 bytes from 172.17.206.1: icmp_req=1 ttl=248 time=77.5 ms 64 bytes from 172.17.206.1: icmp_req=2 ttl=248 time=82.9 ms --- 172.17.206.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 77.585/80.289/82.994/2.719 ms PING 172.17.207.1 (172.17.207.1) 56(84) bytes of data. 64 bytes from 172.17.207.1: icmp_req=1 ttl=245 time=79.5 ms 64 bytes from 172.17.207.1: icmp_req=2 ttl=245 time=68.7 ms --- 172.17.207.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 68.772/74.143/79.514/5.371 ms PING 172.17.208.1 (172.17.208.1) 56(84) bytes of data. 64 bytes from 172.17.208.1: icmp_req=1 ttl=243 time=81.1 ms 64 bytes from 172.17.208.1: icmp_req=2 ttl=243 time=77.5 ms --- 172.17.208.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 77.525/79.315/81.106/1.812 ms PING 172.17.209.1 (172.17.209.1) 56(84) bytes of data. 64 bytes from 172.17.209.1: icmp_req=1 ttl=245 time=200 ms 64 bytes from 172.17.209.1: icmp_req=2 ttl=245 time=81.8 ms --- 172.17.209.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 81.824/140.930/200.037/59.107 ms PING 172.17.210.1 (172.17.210.1) 56(84) bytes of data. 64 bytes from 172.17.210.1: icmp_req=1 ttl=246 time=85.5 ms 64 bytes from 172.17.210.1: icmp_req=2 ttl=246 time=80.8 ms --- 172.17.210.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 80.848/83.202/85.556/2.354 ms PING 172.17.211.1 (172.17.211.1) 56(84) bytes of data. 64 bytes from 172.17.211.1: icmp_req=1 ttl=246 time=87.0 ms 64 bytes from 172.17.211.1: icmp_req=2 ttl=246 time=93.5 ms --- 172.17.211.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 87.099/90.315/93.531/3.216 ms PING 172.17.212.1 (172.17.212.1) 56(84) bytes of data. 64 bytes from 172.17.212.1: icmp_req=1 ttl=244 time=290 ms 64 bytes from 172.17.212.1: icmp_req=2 ttl=244 time=90.4 ms --- 172.17.212.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 90.465/190.683/290.902/100.219 ms PING 172.17.213.1 (172.17.213.1) 56(84) bytes of data. 64 bytes from 172.17.213.1: icmp_req=1 ttl=243 time=94.9 ms 64 bytes from 172.17.213.1: icmp_req=2 ttl=243 time=82.6 ms --- 172.17.213.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 82.600/88.753/94.907/6.160 ms PING 172.17.214.1 (172.17.214.1) 56(84) bytes of data. 64 bytes from 172.17.214.1: icmp_req=1 ttl=248 time=68.1 ms 64 bytes from 172.17.214.1: icmp_req=2 ttl=248 time=61.7 ms --- 172.17.214.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 61.717/64.937/68.158/3.230 ms PING 172.17.215.1 (172.17.215.1) 56(84) bytes of data. 64 bytes from 172.17.215.1: icmp_req=1 ttl=245 time=77.8 ms 64 bytes from 172.17.215.1: icmp_req=2 ttl=245 time=78.9 ms --- 172.17.215.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 77.808/78.355/78.902/0.547 ms PING 172.17.216.1 (172.17.216.1) 56(84) bytes of data. 64 bytes from 172.17.216.1: icmp_req=1 ttl=245 time=80.0 ms 64 bytes from 172.17.216.1: icmp_req=2 ttl=245 time=93.0 ms --- 172.17.216.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 80.078/86.573/93.069/6.502 ms PING 172.17.217.1 (172.17.217.1) 56(84) bytes of data. 64 bytes from 172.17.217.1: icmp_req=1 ttl=247 time=73.5 ms 64 bytes from 172.17.217.1: icmp_req=2 ttl=247 time=68.8 ms --- 172.17.217.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 68.864/71.231/73.599/2.382 ms PING 172.17.218.1 (172.17.218.1) 56(84) bytes of data. 64 bytes from 172.17.218.1: icmp_req=1 ttl=241 time=82.6 ms 64 bytes from 172.17.218.1: icmp_req=2 ttl=241 time=74.7 ms --- 172.17.218.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 74.792/78.724/82.656/3.932 ms PING 172.17.219.1 (172.17.219.1) 56(84) bytes of data. 64 bytes from 172.17.219.1: icmp_req=1 ttl=247 time=68.4 ms 64 bytes from 172.17.219.1: icmp_req=2 ttl=247 time=73.1 ms --- 172.17.219.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 68.436/70.773/73.110/2.337 ms PING 172.17.220.1 (172.17.220.1) 56(84) bytes of data. 64 bytes from 172.17.220.1: icmp_req=1 ttl=246 time=78.8 ms 64 bytes from 172.17.220.1: icmp_req=2 ttl=246 time=92.1 ms --- 172.17.220.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 78.887/85.537/92.187/6.650 ms PING 172.17.221.1 (172.17.221.1) 56(84) bytes of data. 64 bytes from 172.17.221.1: icmp_req=1 ttl=246 time=88.7 ms 64 bytes from 172.17.221.1: icmp_req=2 ttl=246 time=68.7 ms --- 172.17.221.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 68.790/78.772/88.754/9.982 ms PING 172.17.222.1 (172.17.222.1) 56(84) bytes of data. 64 bytes from 172.17.222.1: icmp_req=1 ttl=247 time=70.8 ms 64 bytes from 172.17.222.1: icmp_req=2 ttl=247 time=77.9 ms --- 172.17.222.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 70.816/74.393/77.970/3.577 ms PING 172.17.223.1 (172.17.223.1) 56(84) bytes of data. 64 bytes from 172.17.223.1: icmp_req=1 ttl=247 time=79.6 ms 64 bytes from 172.17.223.1: icmp_req=2 ttl=247 time=81.8 ms --- 172.17.223.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 79.689/80.784/81.879/1.095 ms PING 172.17.224.1 (172.17.224.1) 56(84) bytes of data. 64 bytes from 172.17.224.1: icmp_req=1 ttl=247 time=82.2 ms 64 bytes from 172.17.224.1: icmp_req=2 ttl=247 time=89.9 ms --- 172.17.224.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 82.243/86.078/89.913/3.835 ms PING 172.17.225.1 (172.17.225.1) 56(84) bytes of data. 64 bytes from 172.17.225.1: icmp_req=1 ttl=247 time=89.7 ms 64 bytes from 172.17.225.1: icmp_req=2 ttl=247 time=79.7 ms --- 172.17.225.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 79.796/84.787/89.778/4.991 ms PING 172.17.226.1 (172.17.226.1) 56(84) bytes of data. 64 bytes from 172.17.226.1: icmp_req=1 ttl=246 time=83.1 ms 64 bytes from 172.17.226.1: icmp_req=2 ttl=246 time=253 ms --- 172.17.226.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 83.158/168.230/253.302/85.072 ms PING 172.17.227.1 (172.17.227.1) 56(84) bytes of data. 64 bytes from 172.17.227.1: icmp_req=1 ttl=246 time=68.6 ms 64 bytes from 172.17.227.1: icmp_req=2 ttl=246 time=63.2 ms --- 172.17.227.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 63.230/65.948/68.666/2.718 ms PING 172.17.228.1 (172.17.228.1) 56(84) bytes of data. 64 bytes from 172.17.228.1: icmp_req=1 ttl=246 time=69.5 ms 64 bytes from 172.17.228.1: icmp_req=2 ttl=246 time=92.7 ms --- 172.17.228.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 69.526/81.118/92.711/11.595 ms PING 172.17.229.1 (172.17.229.1) 56(84) bytes of data. 64 bytes from 172.17.229.1: icmp_req=1 ttl=249 time=79.2 ms 64 bytes from 172.17.229.1: icmp_req=2 ttl=249 time=75.8 ms --- 172.17.229.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 75.812/77.550/79.288/1.738 ms PING 172.17.230.1 (172.17.230.1) 56(84) bytes of data. 64 bytes from 172.17.230.1: icmp_req=1 ttl=244 time=88.4 ms 64 bytes from 172.17.230.1: icmp_req=2 ttl=244 time=97.2 ms --- 172.17.230.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 88.436/92.821/97.207/4.396 ms PING 172.17.231.1 (172.17.231.1) 56(84) bytes of data. 64 bytes from 172.17.231.1: icmp_req=1 ttl=247 time=84.1 ms 64 bytes from 172.17.231.1: icmp_req=2 ttl=247 time=68.7 ms --- 172.17.231.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 68.765/76.453/84.142/7.693 ms PING 172.17.232.1 (172.17.232.1) 56(84) bytes of data. 64 bytes from 172.17.232.1: icmp_req=1 ttl=243 time=77.8 ms 64 bytes from 172.17.232.1: icmp_req=2 ttl=243 time=71.7 ms --- 172.17.232.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 71.730/74.773/77.817/3.055 ms PING 172.17.233.1 (172.17.233.1) 56(84) bytes of data. 64 bytes from 172.17.233.1: icmp_req=1 ttl=245 time=80.1 ms 64 bytes from 172.17.233.1: icmp_req=2 ttl=245 time=94.2 ms --- 172.17.233.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 80.192/87.217/94.243/7.031 ms PING 172.17.234.1 (172.17.234.1) 56(84) bytes of data. 64 bytes from 172.17.234.1: icmp_req=1 ttl=246 time=89.3 ms 64 bytes from 172.17.234.1: icmp_req=2 ttl=246 time=86.8 ms --- 172.17.234.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 86.864/88.113/89.362/1.249 ms PING 172.17.235.1 (172.17.235.1) 56(84) bytes of data. 64 bytes from 172.17.235.1: icmp_req=1 ttl=246 time=92.6 ms 64 bytes from 172.17.235.1: icmp_req=2 ttl=246 time=90.0 ms --- 172.17.235.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 90.021/91.338/92.655/1.317 ms PING 172.17.236.1 (172.17.236.1) 56(84) bytes of data. 64 bytes from 172.17.236.1: icmp_req=1 ttl=244 time=93.4 ms 64 bytes from 172.17.236.1: icmp_req=2 ttl=244 time=72.7 ms --- 172.17.236.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 72.711/83.104/93.498/10.397 ms PING 172.17.237.1 (172.17.237.1) 56(84) bytes of data. 64 bytes from 172.17.237.1: icmp_req=1 ttl=243 time=73.6 ms 64 bytes from 172.17.237.1: icmp_req=2 ttl=243 time=68.0 ms --- 172.17.237.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 68.021/70.855/73.689/2.834 ms PING 172.17.238.1 (172.17.238.1) 56(84) bytes of data. 64 bytes from 172.17.238.1: icmp_req=1 ttl=248 time=61.3 ms 64 bytes from 172.17.238.1: icmp_req=2 ttl=248 time=76.2 ms --- 172.17.238.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 61.394/68.846/76.298/7.452 ms PING 172.17.239.1 (172.17.239.1) 56(84) bytes of data. 64 bytes from 172.17.239.1: icmp_req=1 ttl=245 time=87.4 ms 64 bytes from 172.17.239.1: icmp_req=2 ttl=245 time=94.4 ms --- 172.17.239.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 87.470/90.935/94.400/3.465 ms PING 172.17.240.1 (172.17.240.1) 56(84) bytes of data. 64 bytes from 172.17.240.1: icmp_req=1 ttl=245 time=97.2 ms 64 bytes from 172.17.240.1: icmp_req=2 ttl=245 time=88.5 ms --- 172.17.240.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 88.517/92.876/97.236/4.370 ms PING 172.17.241.1 (172.17.241.1) 56(84) bytes of data. 64 bytes from 172.17.241.1: icmp_req=1 ttl=247 time=74.6 ms 64 bytes from 172.17.241.1: icmp_req=2 ttl=247 time=58.4 ms --- 172.17.241.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 58.416/66.523/74.631/8.111 ms PING 172.17.242.1 (172.17.242.1) 56(84) bytes of data. 64 bytes from 172.17.242.1: icmp_req=1 ttl=241 time=70.8 ms 64 bytes from 172.17.242.1: icmp_req=2 ttl=241 time=86.2 ms --- 172.17.242.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 70.853/78.549/86.245/7.696 ms PING 172.17.243.1 (172.17.243.1) 56(84) bytes of data. 64 bytes from 172.17.243.1: icmp_req=1 ttl=247 time=73.2 ms 64 bytes from 172.17.243.1: icmp_req=2 ttl=247 time=125 ms --- 172.17.243.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 73.265/99.218/125.171/25.953 ms PING 172.17.244.1 (172.17.244.1) 56(84) bytes of data. 64 bytes from 172.17.244.1: icmp_req=1 ttl=246 time=94.0 ms 64 bytes from 172.17.244.1: icmp_req=2 ttl=246 time=76.5 ms --- 172.17.244.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 76.592/85.307/94.023/8.720 ms PING 172.17.245.1 (172.17.245.1) 56(84) bytes of data. 64 bytes from 172.17.245.1: icmp_req=1 ttl=246 time=79.5 ms 64 bytes from 172.17.245.1: icmp_req=2 ttl=246 time=84.3 ms --- 172.17.245.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 79.598/81.975/84.353/2.394 ms PING 172.17.246.1 (172.17.246.1) 56(84) bytes of data. 64 bytes from 172.17.246.1: icmp_req=1 ttl=58 time=92.7 ms 64 bytes from 172.17.246.1: icmp_req=2 ttl=58 time=111 ms --- 172.17.246.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 92.770/102.302/111.835/9.537 ms PING 172.17.247.1 (172.17.247.1) 56(84) bytes of data. 64 bytes from 172.17.247.1: icmp_req=1 ttl=247 time=102 ms 64 bytes from 172.17.247.1: icmp_req=2 ttl=247 time=90.7 ms --- 172.17.247.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 90.793/96.462/102.132/5.678 ms PING 172.17.248.1 (172.17.248.1) 56(84) bytes of data. 64 bytes from 172.17.248.1: icmp_req=1 ttl=247 time=122 ms 64 bytes from 172.17.248.1: icmp_req=2 ttl=247 time=90.1 ms --- 172.17.248.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 90.181/106.268/122.355/16.087 ms PING 172.17.249.1 (172.17.249.1) 56(84) bytes of data. 64 bytes from 172.17.249.1: icmp_req=1 ttl=57 time=91.0 ms 64 bytes from 172.17.249.1: icmp_req=2 ttl=57 time=72.1 ms --- 172.17.249.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 72.126/81.578/91.030/9.452 ms PING 172.17.250.1 (172.17.250.1) 56(84) bytes of data. 64 bytes from 172.17.250.1: icmp_req=1 ttl=249 time=67.3 ms --- 172.17.250.1 ping statistics --- 2 packets transmitted, 1 received, 50% packet loss, time 1001ms rtt min/avg/max/mdev = 67.333/67.333/67.333/0.000 ms PING 172.17.251.1 (172.17.251.1) 56(84) bytes of data. 64 bytes from 172.17.251.1: icmp_req=1 ttl=249 time=84.9 ms 64 bytes from 172.17.251.1: icmp_req=2 ttl=249 time=81.3 ms --- 172.17.251.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 81.361/83.148/84.935/1.787 ms PING 172.17.252.1 (172.17.252.1) 56(84) bytes of data. 64 bytes from 172.17.252.1: icmp_req=1 ttl=57 time=80.3 ms 64 bytes from 172.17.252.1: icmp_req=2 ttl=57 time=72.6 ms --- 172.17.252.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 72.677/76.504/80.332/3.837 ms PING 172.17.253.1 (172.17.253.1) 56(84) bytes of data. 64 bytes from 172.17.253.1: icmp_req=1 ttl=248 time=68.1 ms 64 bytes from 172.17.253.1: icmp_req=2 ttl=248 time=76.1 ms --- 172.17.253.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 68.169/72.160/76.151/3.991 ms PING 172.17.254.1 (172.17.254.1) 56(84) bytes of data. 64 bytes from 172.17.254.1: icmp_req=1 ttl=50 time=75.4 ms 64 bytes from 172.17.254.1: icmp_req=2 ttl=50 time=76.0 ms --- 172.17.254.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 75.455/75.742/76.029/0.287 ALORS la :) (j'ai commencé à 1) quelqu'un à une idée ???

7 6

[JOB] Recherche contrat d'alternance
by David BOISSAT 11 Jun '14

11 Jun '14

Bonjour la liste FrsAG ! Je suis actuellement à la recherche d’une entreprise soit dans le domaine des telecoms (idéalement type opérateur local) soit qui plus généralement propose des positions d’administration système (plus favorablement GNU/Linux). Ce choix dépend surtout de la licence professionnelle en alternance qui acceptera ma candidature. Je suis motivé, très curieux et apte à m’adapter rapidement. J’ai une petite expérience (3 mois de stage + 1 mois) chez un opérateur télécom local en développement progiciel et aide au déploiement physique d’un réseau événementiel orienté festival estivalier et Wi-Fi haute densité. Vous trouverez à l’adresse suivante mon CV au format PDF: https://db.chroot-me.in/pro/cv/cv_dboissat_FR.pdf Je suis bien conscient que ma recherche est un peu vague et c’est pourquoi je vais préciser ci-dessous le détail de mes recherches, en fonction de la ville et de la formation : - Beziers : LP Administration et Sécurité de Réseaux et LP Intégration des Systèmes Voix et Données. - Clermont-Ferrand : LP Administration et Sécurité des Réseaux et LP Réseaux Sans Fil et Sécurité - Blagnac : LP Réseaux Sans Fil et Sécurité - Colmar : LP Administration et Sécurité de Réseaux et LP Intégration des Systèmes Voix et Données. Je me permets également un crosspost sur la liste FrNOG :) ps: Je me suis inscrit récemment sur ces deux listes, mais je consultais de temps à autre les archives, j’essaie d’être (un peu) plus qu’un candidat qui ne s’inscrit que pour se vendre :) -- David Boissat

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

FRsAG