TLDR cloud providers expect FreeBSD to behave like linux, and
assign a default interface route to a /32 lease. Without this,
images start up without a default interface. Very inconvenient.
Index: sbin/dhclient/dhclient-script
===
---
I've found a workaround for this issue, but don't understand why this
occurs. Reading RFC1122 has left me none the wiser. What am I missing?
Is this a Linuxism or simple a standardisation loophole?
## Problem
- on 13.1-R, dhclient-set config works for all UDP, & outbound TCP
- but inbound TCP
On Fri, 17 Jun 2022, at 02:38, Mike Jakubik wrote:
> Hi,
>
> I believe you hit the nail on the head! I am now getting consistent
> high speeds, even higher than on Linux! Is this a problem with the
> scheduler? Should someone in that area of expertise be made aware of
> this? More importantly i
I use a port, net/zerotier, that uses if_tap(4) to provide a mesh VPN. If I add
many IPv6 aliases to its /80 routable IPv6 interface, sometime around adding ~
1100 or more aliases, the port dies. If I'm really lucky, system panics. Now
that I'm watching it, no such luck
Am I running into
On Tue, 25 Jun 2019, at 01:05, Thomas Mueller wrote:
> > Hi Tom
> > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html
>
> > NDIS may do what you want but it may suck.
>
> > In terms of time vs effort a 15$ USB Ethernet dongle is going to be your
> > best
On Fri, 21 Jun 2019, at 04:33, Thomas Mueller wrote:
> Is it possible to build and install FreeBSD so as to be bootable and access
> the internet with an Ethernet card that doesn't work in FreeBSD?
>
> Could Ethernet support be obtained through UEFI?
>
> Or could FreeBSD be installed on
On Tue, 26 Jun 2018, at 09:52, Dave Cottlehuber wrote:
>
> The HPET NMI watchdog patch was very timely - works a treat:
> https://reviews.freebsd.org/D15630
>
> > However each time there's no crashdump, & the usual ctrl-alt-esc does't
> > work either.
>
> I
> > > > # invalid IP
> > > >
> > > > TLDR 10.241.0.0/16 is technically not a valid host IP but it has
> > > obviously worked in the past.
Just following this up, kmacy@'s recent commits resolved this - thanks!
Finally, I came up with this, as a way of keeping the "symmetry" of the
0.0 and still
On Mon, 25 Jun 2018, at 23:08, Dave Cottlehuber wrote:
> [cross-posting for advice on general debugging + network-specific thoughts]
The HPET NMI watchdog patch was very timely - works a treat:
https://reviews.freebsd.org/D15630
> However each time there's no crashdump, & the usual ct
[cross-posting for advice on general debugging + network-specific thoughts]
TLDR since a week or so, probably around r335381 I can reliably get my machine
to hang*** by unloading pf, while there's network traffic (e.g. video streaming
or rsync) and waiting a minute or two I still see it with
On Thu, 14 Jun 2018, at 16:01, Andrea Venturoli wrote:
> On 05/21/18 18:10, Andrea Venturoli wrote:
>
> > Thanks to anyone who answered.
> >
> > I'm currently trying net/bounce, as suggested by Eugene.
> > If that won't work properly, I'll sure give plugdaemon a shot.
>
> Just an update in case
On Wed, 30 May 2018, at 17:46, Rodney W. Grimes wrote:
> > > > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> > > > > > lo1: flags=8049 metric 0 mtu 16384
> > > > > > inet 10.241.0.0 netmask 0x
> > > > > > inet 10.241.0.1 netmask 0x
> > > > > > inet
On Wed, 30 May 2018, at 15:40, Dave Cottlehuber wrote:
> I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it>
> doesn't work anymore. Boxes at $DAYJOB use the same config and
> work just> fine on 11.1R/amd64, otherwise I'd be fired this used to work
> ~
I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it doesn't
work anymore. Boxes at $DAYJOB use the same config and work just fine on
11.1R/amd64, otherwise I'd be fired this used to work ~ 1 month ago, both
on my desktop, and my laptop, and now doesn't.
​Have I
On Thu, 14 Sep 2017, at 23:32, Kristof Provost wrote:
> On 14 Sep 2017, at 16:21, Dave Cottlehuber wrote:
> > Outgoing traffic (from a jail) via PF NAT over a LAGG/LACP sometimes
> > has the *backup* CARP IP address assigned to it.
> >
> I think this is your problem.
Hi,
Outgoing traffic (from a jail) via PF NAT over a LAGG/LACP sometimes has
the *backup* CARP IP address assigned to it.
Obivously as this IP is only active on the "other" server, the return
TCP connection traffic never actually gets back to our CARP master, and
the other server sees spurious
hi,
I posted this a week ago to freebsd-questions but got nothing. I hope
its
suitable for asking here.
Today I wanted to observe traffic that is proxied via haproxy between IP
addresses both bound to a lo1 cloned interface.
To my surprise ngrep & tcpdump showed no activity on lo1, but it did
17 matches
Mail list logo
