News

Byarshadrad

myLG v0.2.6 has been released

The myLG version 0.2.6 has been released. the traceroute function is enhanced, the network discovery IPv6 added and few bugs fixed in this version. the web dashboard technology changed to AnggularJS 2 and I added the trace route web dashboard. now you can trace any host and see the real time result on the web.

mylg_web_dashboard

Download : http://mylg.io/download

User Guide : http://mylg.io/doc

Byarshadrad

myLG v0.2.5 has been released

I’m glad for seeing the different websites reviewing myLG properly and it’s getting the attention. please see the highlighted changes at the new version: 0.2.5 as below:

  • Enhanced hping with trace feature and other new options
  • Quick NMS – SNMP 1/2c/3 support
  • Enhanced and bug fixed real-time trace-route

As Golang 1.7 added the new package called httptrace we integrated it to the hping. now you can see more details including connection and first-byte read times. there are different new options has been added like proxy support, disable compression, enable keep alive and etc.

sc-hping-trace

BTW, I need to say special thanks for enhancing hping to Emil Thelin, he helped me on this part.

Quick NMS is a network monitoring through SNMP to monitor interfaces. it could be server’s interfaces or devices. It supports all the vendors that they implemented standard SNMP like Juniper and Cisco. you can see the interfaces as a report or real-time with 10 seconds refresh time. I think that would be useful during troubleshooting.

sc-nms-report

The trace-route now supports Geo IP information including the distance between source and destination IP addresses. it supports IPv4/IPv6 ICMP/UDP.

trace route realtime

Other news that happened recently:

The new documentation added : http://mylg.io/doc/
The RPM package added : http://mylg.io/dl/linux/mylg-0-2.5.x86_64.rpm

Reviewed by the websites this week:
http://linoxide.com
https://orebibou.com

Please let me know if you have any suggestions.

Best regards,
Mehrdad Arshad Rad

Byarshadrad

myLG vs MTR (my trace route)

There are reasons to use myLG real-time traceroute over MTR (my trace route)
First of all, I respect to MTR as I used to it for a long time (more than 11 years) and it was really helpful but I think we need more information to see the better view of the traceroute once we’re in the middle of a troubleshooting. we can grab other metrics/information from different places but it would be nice to have all at our terminal together. this real-time traceroute is one of the myLG features.

P.S all the features that appear in the below screenshot will be available at next release (v0.2.5)

mylg_traceroute_realtime

Byarshadrad

myLG and SNMP

Hey Guys,

Developing SNMP features has been started at myLG, the goal of this phase is connecting to any device by SNMP and get proper information in middle of the troubleshooting. already it can be able to show interfaces statistics including essential metrics like traffic, packet per second, error, discard IN/OUT. I would love to get your suggestion in this regard. please let me know here as comment or  mylg.io/contact.

Best,
Mehrdad

Byarshadrad

mylg v0.2.4 released

New Feature: Real-time trace route IPv4 & IPV6
Enhanced: HTTP Ping and Dump
Bug Fixed: Dig

The real time trace route is similar to MTR (my trace route) but it shows AS number per each hop and the holder (company name). if each hop is balancing between different routers they will be highlighted real time. you can change the display mode to graph and see the RTT history for last hop at your terminal. it support IPv4 and IPv6 networks.

mylg_rt_trace

mylg_rt_trace2

 

Byarshadrad

Dig command enhanced / written pure Go

Dig

ns/united states/redwood city> dig yahoo.com
Trying to query server: 204.152.184.76 united states redwood city
;; opcode: QUERY, status: NOERROR, id: 19850
;; flags: qr rd ra;
yahoo.com.  728 IN  MX  1 mta6.am0.yahoodns.net.
yahoo.com.  728 IN  MX  1 mta5.am0.yahoodns.net.
yahoo.com.  728 IN  MX  1 mta7.am0.yahoodns.net.
yahoo.com.  143013  IN  NS  ns4.yahoo.com.
yahoo.com.  143013  IN  NS  ns6.yahoo.com.
yahoo.com.  143013  IN  NS  ns2.yahoo.com.
yahoo.com.  143013  IN  NS  ns5.yahoo.com.
yahoo.com.  143013  IN  NS  ns1.yahoo.com.
yahoo.com.  143013  IN  NS  ns3.yahoo.com.

;; ADDITIONAL SECTION:
ns1.yahoo.com.  561456  IN  A   68.180.131.16
ns2.yahoo.com.  27934   IN  A   68.142.255.16
ns3.yahoo.com.  532599  IN  A   203.84.221.53
ns4.yahoo.com.  532599  IN  A   98.138.11.157
ns5.yahoo.com.  532599  IN  A   119.160.247.124
ns6.yahoo.com.  143291  IN  A   121.101.144.139
ns1.yahoo.com.  51624   IN  AAAA    2001:4998:130::1001
ns2.yahoo.com.  51624   IN  AAAA    2001:4998:140::1002
ns3.yahoo.com.  51624   IN  AAAA    2406:8600:b8:fe03::1003
ns6.yahoo.com.  143291  IN  AAAA    2406:2000:108:4::1006
;; Query time: 1204 ms

;; CHAOS CLASS BIND
version.bind.   0   CH  TXT "9.10.4-P1"
hostname.bind.  0   CH  TXT "fred.isc.org"

Dig Trace:


ns/united states/redwood city> dig yahoo.com +trace
.	12457	IN	NS	h.root-servers.net.
.	12457	IN	NS	l.root-servers.net.
.	12457	IN	NS	d.root-servers.net.
.	12457	IN	NS	k.root-servers.net.
.	12457	IN	NS	j.root-servers.net.
.	12457	IN	NS	i.root-servers.net.
.	12457	IN	NS	e.root-servers.net.
.	12457	IN	NS	b.root-servers.net.
.	12457	IN	NS	c.root-servers.net.
.	12457	IN	NS	g.root-servers.net.
.	12457	IN	NS	m.root-servers.net.
.	12457	IN	NS	a.root-servers.net.
.	12457	IN	NS	f.root-servers.net.
from: 204.152.184.76#53 in 26 ms
com.	172800	IN	NS	a.gtld-servers.net.
com.	172800	IN	NS	b.gtld-servers.net.
com.	172800	IN	NS	c.gtld-servers.net.
com.	172800	IN	NS	d.gtld-servers.net.
com.	172800	IN	NS	e.gtld-servers.net.
com.	172800	IN	NS	f.gtld-servers.net.
com.	172800	IN	NS	g.gtld-servers.net.
com.	172800	IN	NS	h.gtld-servers.net.
com.	172800	IN	NS	i.gtld-servers.net.
com.	172800	IN	NS	j.gtld-servers.net.
com.	172800	IN	NS	k.gtld-servers.net.
com.	172800	IN	NS	l.gtld-servers.net.
com.	172800	IN	NS	m.gtld-servers.net.
from: h.root-servers.net.#53 in 96 ms
yahoo.com.	172800	IN	NS	ns1.yahoo.com.
yahoo.com.	172800	IN	NS	ns5.yahoo.com.
yahoo.com.	172800	IN	NS	ns2.yahoo.com.
yahoo.com.	172800	IN	NS	ns3.yahoo.com.
yahoo.com.	172800	IN	NS	ns4.yahoo.com.
from: a.gtld-servers.net.#53 in 37 ms
yahoo.com.	1800	IN	SOA	ns1.yahoo.com. hostmaster.yahoo-inc.com. 2016082401 3600 300 1814400 600
yahoo.com.	1800	IN	A	98.139.183.24
yahoo.com.	1800	IN	A	206.190.36.45
yahoo.com.	1800	IN	A	98.138.253.109
yahoo.com.	300	IN	AAAA	2001:4998:58:c02::a9
yahoo.com.	300	IN	AAAA	2001:4998:c:a06::2:4008
yahoo.com.	300	IN	AAAA	2001:4998:44:204::a7
yahoo.com.	1800	IN	MX	1 mta6.am0.yahoodns.net.
yahoo.com.	1800	IN	MX	1 mta5.am0.yahoodns.net.
yahoo.com.	1800	IN	MX	1 mta7.am0.yahoodns.net.
yahoo.com.	172800	IN	NS	ns1.yahoo.com.
yahoo.com.	172800	IN	NS	ns4.yahoo.com.
yahoo.com.	172800	IN	NS	ns2.yahoo.com.
yahoo.com.	172800	IN	NS	ns3.yahoo.com.
yahoo.com.	172800	IN	NS	ns6.yahoo.com.
yahoo.com.	172800	IN	NS	ns5.yahoo.com.
yahoo.com.	1800	IN	TXT	"v=spf1 redirect=_spf.mail.yahoo.com"
from: ns1.yahoo.com.#53 in 18 ms

GitHub

https://github.com/mehrdadrad/mylg/blob/master/ns/ns.go

Byarshadrad

Advanced trace route

Advanced trace route with autonomous number and prefix holder @ v0.2.2

traceroute

Byarshadrad

Dump and search at payload in hex/string format

Now you can dump payload in hex/string format like (hexdump -C) and search at payload. the code is available at github and the features will be available at next version.

local> dump -s http -x

Byarshadrad

mylg v0.2.1 released

packets

Changes:
- New: Network LAN Discovery
- Enhanced packet analyzer 
- Enhanced whois for prefixes
- Fixed minor bugs
Screen Shot 2016-08-05 at 3.58.52 PM
Save packets to pcap file
local> dump !udp -w /home/user1/mypcap -c 100000
Byarshadrad

mylg v0.2.0 released

packets

Now myLG can print out pretty packets on a network interface based on what you need. it supports Berkeley Packet Filter (BPF) syntax for instance:

local> dump tcp and port 445
or
local> dump !tcp

packet_analyzer