> Short version:
>
> Using FreeBSD as a BGP router has network issues caused by suboptimal
> default IPv4 source address selection when connected to Internet
> Exchanges (which are required to use IPs that aren't routable on the
> Internet). I was hoping to find more elegant workarounds or encour
On Wed, Apr 24, 2024 at 07:10:51AM +0200, Marek Zarychta wrote:
> W dniu 24.04.2024 o 04:12, Gregory Shapiro pisze:
> > Short version:
> >
> > Using FreeBSD as a BGP router has network issues caused by suboptimal
> > default IPv4 source address selection when connected to Internet
> > Exchanges (w
> The mistake your making, IMHO, is that an IX connected eBGP FreeBSD
> router _SHOULD NOT_ be doing ANYTHING other than BGP on the IX
> connected interface, and anything like DNS and outbound SMTP should be
> going inward on the AS, not outward to the internet.
Fair point and thank you for the ad
On 4/23/2024 10:12 PM, Gregory Shapiro wrote:
Short version:
Using FreeBSD as a BGP router has network issues caused by suboptimal
default IPv4 source address selection when connected to Internet
Exchanges (which are required to use IPs that aren't routable on the
Internet). I was hoping to fin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263982
--- Comment #3 from Alex Wied ---
Is there any plan to fix this? It's strange to me that a pfSense router (which
runs FreeBSD) would cause issues for a FreeBSD machine.
--
You are receiving this mail because:
You are the assignee for the
agreed. and one of my mods to the ultrix (~4.3bsd) kernel for
gatekeeper.dec.com back in ~1990 was to use the result of gethostid(3)
if that result was nonzero and if a socket was not already bound. so
named(8) and ntpd(8) and anything else that used explicit binding got
what they expected, but
