Folks,
In several days of running, I've seen unsolicited net-to-gateway [malicious]
traffic - summarily discarded by the snat plugin - as follows:
* Mirai botnet [tcp -> port 5747]
* Microsoft WSDAPI [tcp -> port 5358]
* Telnet [tcp -> port 23]
* HTTP alternate [tcp -> port 81]
“It should just work...”
I’m vastly more familiar with Ubuntu, which is why I went there.
Thanks… Dave
From: Bernier, Daniel [mailto:daniel.bern...@bell.ca]
Sent: Tuesday, January 24, 2017 11:55 AM
To: Dave Barach (dbarach) ; vpp-dev
Subject: Re: [vpp-dev] vpp home gateway use-case added to
Hi Dave,
Quick question would you see any hurdles running it over CentOS?
… newer Netgate’s ship with CentOS by default
Thanks,
Daniel Bernier | Bell Canada
From: on behalf of "Dave Barach (dbarach)"
Date: Tuesday, January 24, 2017 at 8:23 AM
To: vpp-dev
Subject: [vpp-dev
In case folks are interested, see: https://wiki.fd.io/view/VPP/VPP_Home_Gateway
Note that the exercise resulted in the addition of a couple of new features for
the snat plugin, and a jira ticket: https://jira.fd.io/browse/VPP-612
___
vpp-dev mailing l
+Billy
On 01/11/2017 07:00 PM, Dave Barach (dbarach) wrote:
Dear Tom,
I’m now running my “work” subnet behind a vpp gateway. In fact, if you
see this message, it’s working... (;-).
Cool. I assume this is the box,
https://www.netgate.com/products/rcc-ve-4860.html. It is a 2.4 GHz
rangely
Dear Tom,
I’m now running my “work” subnet behind a vpp gateway. In fact, if you see this
message, it’s working... (;-).
See below for a vpp config w/ IRB. The “lstack” tap interface allows host stack
access, and provides a path for clients on the bridged interfaces to reach the
dhcp server. I
