On 5/18/19 4:45 AM, Mikael Abrahamsson wrote:
> The area of how the router on the LAN gets the DHCPv6-PD route injected never
> was standardized because consensus couldn't be reached on how to do it, so it
> was glossed over and vendors solved it the way they saw fit. I've seen
>
Hello Amir,
On 5/18/19 1:08 PM, Amir Herzberg wrote:
This discussion is very interesting, I didn't know about this problem,
it has implications to our work on routing security, thanks!
Your welcome..., since long time ago I wanted to expose our findings in
English.
On Sat, May 18, 2019
This discussion is very interesting, I didn't know about this problem, it
has implications to our work on routing security, thanks!
On Sat, May 18, 2019 at 11:37 AM Alejandro Acosta <
alejandroacostaal...@gmail.com> wrote:
>
>If you learn, let's say, up to /22 (v4), and someone hijacks one
Dennis,
You might try FlowViewer https://sourceforge.net/projects/flowviewer
Fairly easy Linux install over top of SiLK, netflow capture and analysis
software from Carnegie-Mellon. SiLK is very robust and FlowViewer
provides a web-based interface with extensive analysis, graphing and
Hello,
As a comment, after receiving several complains and after looking
many cases, we evaluated what is better, to cut the table size filtering
"big" network or "small" networks. Of course this is a difficult
scenario and I guess there are mix thinking about this, however, we
concluded
On 5/18/19 4:44 AM, Radu-Adrian Feurdean wrote:
That one seems to be the simpler form, depending only on an external DHCP
server. It may be enough for some set-ups. Subscriber functionality provides
more options, such as enforcing auth and internal dhcp server that takes data
to be returned
On Fri, May 17, 2019 at 10:43 PM Blake Hudson wrote:
> I manage a network like you describe: Two BGP edge routers, both routers
> accept a full eBGP feed from transit, both share routing information via
> iBGP. Both edge routers in my network have a complete view. If one transit
> provider is
On Tue, 14 May 2019, Brandon Martin wrote:
Is there a standard that defines/recommends behavior for route injection of
snooped DHCPv6-PD (or IA, I guess) assignments on routers running relay
agents?
No, there isn't. However, there is now work ongoing work in the IETF to at
least create a
On Sat, May 18, 2019, at 09:52, Brandon Martin wrote:
> What it does is hook into the DHCPv6 lightweight relay functionality.
> Basically, it just snoops the DHCPv6 replies for a PD assignment and
> inserts a quasi-static route into its table for anything that it sees
> with next-hop
On 5/18/19 2:33 AM, Radu-Adrian Feurdean wrote:
Those being said, I'm interested in how that feature is supported on gear that is not
"subscriber-aware" (you were talking about Arista), since generating routing information
from relayed DHCP(v6) is a big/important part of the "subscriber
On Wed, May 15, 2019, at 04:28, Brandon Martin wrote:
> Is there a standard that defines/recommends behavior for route injection
> of snooped DHCPv6-PD (or IA, I guess) assignments on routers running
> relay agents? That is, snooping or otherwise examining a relayed DHCPv6
> response for a
11 matches
Mail list logo
