Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Feb 2018 11:40:02 -0800 (PST)
From:      "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
To:        Ryan Stone <rysto32@gmail.com>
Cc:        freebsd-net <freebsd-net@freebsd.org>, phabric-admin@freebsd.org
Subject:   Re: [PATCH] Fix for IPv4 subnet route migration
Message-ID:  <201802281940.w1SJe2bC021561@pdx.rh.CN85.dnsmgr.net>
In-Reply-To: <CAFMmRNxeXgimU0p693db=t1ZU=3cyKgU8R8i8oFqpNFzpAE%2BDQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> Currently, the FreeBSD stack gets itself into a bizarre state if you
> try to change the source IP for a subnet route (yes, this implies
> using two IPs on the same subnet on a system.  Yes, I'm aware this is
> a Bad Idea(TM).  Unfortunately I have a customer that insists on this
> configuration)
> 
> You can see the review description for all of the gory details.  IPv6
> is not affected by the issue so I only had to fix IPv4.  The review is
> here:
> 
> https://reviews.freebsd.org/D14547
> 
> If anybody is interested in reviewing this fix, please subscribe
> yourself to the review.  Thanks!

Herald for umbralla Network seems to be broken, this
review touches sys/netinet code which should of tripped
that rule.  Can someone investigate?

I have manually subscribed.


-- 
Rod Grimes                                                 rgrimes@freebsd.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201802281940.w1SJe2bC021561>