> On Oct 20, 2021, at 08:26 , Mel Beckman <m...@beckman.org> wrote: > > Mark, > > As long as we’re being pedantic, January 1, 1983 is considered the official > birthday of the Internet, when TCP/IP first let different kinds of computers > on different networks talk to each other.
January 1, 1983 is actually not that… TCP/IP was running in many locations prior to that date. January 1, 1983 was the day that support for the NCP based internet prior to TCP/IP implementation ended. Further, NCP had actually allowed different kinds of computers on different networks to talk to each other, as had UUCP. > It’s 2021, hence the Internet is less than, not more than, 40 years old. > Given your mathematical skills, I put no stock in your claim that we still > can’t “buy an NMS that just works.” :) No, not really. The Internet is older than the death of NCP, which is the day you are referring to as the birthday of the internet. Owen > > -mel > >> On Oct 20, 2021, at 8:04 AM, Mark Tinka <mark@tinka.africa >> <mailto:mark@tinka.africa>> wrote: >> >> >> >> On 10/20/21 11:55, Nat Fogarty wrote: >> >>> Hi there, >>> >>> I'm interested in what you good folks do in terms of network visibility. >>> >>> My interests are around Service Provider space - visibility for IPoE, >>> PPPoE, TCP(User Experience). >>> >>> I use a product called "VoIPmonitor" for all things VoIP - and it is one of >>> my favourite tools. It is a web gui for sip/rtp/etc. >>> >>> Is there a similar tool in the Ethernet(L2)/IP(L3) space? >>> >>> Are operators using tcpdump/wireshark for this - or is there a >>> voipmonitor-esque tool out there? >> >> It's 2021, and more than 40 years of the Internet, we still can't walk into >> a shop and buy an NMS that just works :-). >> >> Oddly, I was searching for a good system to manage subscriber management on >> our end (Broadband), and we eventually landed on Splynx. >> >> So not sure if you want to see things on the wire (Layer 1 - 4), or if you >> are interested in pretty pictures... >> >> At any rate, you may very well need more than one system to monitor your >> entire network. >> >> Mark. >
