Thanks a lot Stuart! Really appreciate your insights.
I've been running some more tests and here are some new results:
1.
Without MAC spoofing and a statically assigned IP address, axe lasted
around twelve days on an AX88772B before throwing the following error:
axe0: watchdog timeout
hopefully copying to bugs@ (if I remember how to do that correctly
from slrn/gmane..) Please keep that in CC's when replying. Earlier misc@
mail copied in below to keep things together in one place.
On 2021-08-06, beebeet...@posteo.de wrote:
> > My first suggestion might be to stay with a
Sorry, there was a typo: The problem *does disappear* with
`lladdr random` removed .
It seems that with `lladdr random` removed, the problem does not
seem to disappear.
> My first suggestion might be to stay with a single lladdr for a
> while to see if your setup works for more than a day and a half.
Thanks for the suggestion!
It seems that with `lladdr random` removed, the problem does not
seem to disappear.
lladdr random
Why this line?
I was wondering
On Thu, Aug 5, 2021 at 6:29 AM Stuart Henderson wrote:
>
> On 2021-08-03, beebeet...@posteo.de wrote:
> > Hi all,
> >
> > Me again on some DHCP-related issues...
> >
> > So I started using OpenBSD as my home router around two weeks ago,
> > running openBSD 6.9. It obtains its IP address from the
On 2021-08-03, beebeet...@posteo.de wrote:
> Hi all,
>
> Me again on some DHCP-related issues...
>
> So I started using OpenBSD as my home router around two weeks ago,
> running openBSD 6.9. It obtains its IP address from the ISP via
> DHCP. The setup is pretty simple, just the following two
On 8/3/2021 11:57 AM, beebeet...@posteo.de wrote:
> The router works fine most of the time -- except that it stops
> working every one and a half day, and I have to reset the modem
> for it to work again.
In my experience with my ISP (Comcast in the US), I note the following:
When the lladdr
Hi all,
Me again on some DHCP-related issues...
So I started using OpenBSD as my home router around two weeks ago,
running openBSD 6.9. It obtains its IP address from the ISP via
DHCP. The setup is pretty simple, just the following two lines in
my hostname.if file:
lladdr random
inet autoconf
On 7/19/21 1:23 AM, Theo de Raadt wrote:
gwes wrote:
On 7/18/21 8:55 PM, Theo de Raadt wrote:
Lots of excellent reasons.
Is there any document available which describes your concept of how
systems running OpenBSD are used?
E.g. mobile laptop, home user desktop, office desktop, single
gwes wrote:
> On 7/18/21 8:55 PM, Theo de Raadt wrote:
> > Lots of excellent reasons.
> >
> >
> Is there any document available which describes your concept of how
> systems running OpenBSD are used?
>
> E.g. mobile laptop, home user desktop, office desktop, single local
> net server, multiple
On 7/18/21 8:55 PM, Theo de Raadt wrote:
Lots of excellent reasons.
Is there any document available which describes your concept of how
systems running OpenBSD are used?
E.g. mobile laptop, home user desktop, office desktop, single local net
server, multiple local servers,
single gateway,
Sonic wrote:
> On Sun, Jul 18, 2021 at 3:55 PM Stuart Henderson wrote:
> >
> > The bits that can't be handled are the more per-interface things ("fetch
> > an address but ignore dns or the default route on interface X however do
> > fetch them from interface Y", or "my ISP won't give me a lease
On Sun, Jul 18, 2021 at 3:55 PM Stuart Henderson wrote:
>
> The bits that can't be handled are the more per-interface things ("fetch
> an address but ignore dns or the default route on interface X however do
> fetch them from interface Y", or "my ISP won't give me a lease without
> providing a
On 2021-07-17, Sonic wrote:
> On Sat, Jul 17, 2021 at 11:20 AM Theo de Raadt wrote:
>>
>> Instead, we are focusing on 99% of the use cases.
>
> I hardly think that wanting to override your ISP's name servers is
> outside of the 99% use cases. Of course it wouldn't be the first time
> I am wrong.
On 2021-07-18, Martin wrote:
> Hi,
>
> I confirm that dhclient don't read(apply) /etc/dhclient.conf configuration
> beginning from 6.9am64 and set in /etc/resolv.conf ISP search domain and
> nameserver(s) even without any complex setup in name resolution:
Not sure what that's about, I don't
Hi,
I confirm that dhclient don't read(apply) /etc/dhclient.conf configuration
beginning from 6.9am64 and set in /etc/resolv.conf ISP search domain and
nameserver(s) even without any complex setup in name resolution:
$ cat /etc/resolv.conf
search domain.name
nameserver ISP.nameserver
On Sat, Jul 17, 2021 at 11:20 AM Theo de Raadt wrote:
>
> Instead, we are focusing on 99% of the use cases.
I hardly think that wanting to override your ISP's name servers is
outside of the 99% use cases. Of course it wouldn't be the first time
I am wrong.
> You might want to look into using
On 2021-07-17, Sonic wrote:
> Ah yes, my bad, had a line without the parens around the dhcp
> interface reference.
> This issue is resolved.
> Oddly enough it never affected many previous snapshots which used
> dhcpcd in place of dhcpleased.
OpenBSD never had dhcpcd in base, if you had
Sonic wrote:
> On Fri, Jul 16, 2021 at 10:35 PM Theo de Raadt wrote:
> > We are moving from a model where dhclient on 1 interface believes it is
> > MASTER of /etc/resolv.conf and a bunch of system aspects, and the
> > userbase is familiar with a pile of hacky control knobs in
> >
On Fri, Jul 16, 2021 at 10:35 PM Theo de Raadt wrote:
> We are moving from a model where dhclient on 1 interface believes it is
> MASTER of /etc/resolv.conf and a bunch of system aspects, and the
> userbase is familiar with a pile of hacky control knobs in
> dhclient.conf.
>
> Towards a model
Theo de Raadt writes:
> Sonic wrote:
>
> > Having some issues after a sysupgrade to the latest snapshot (of this
> > writing) - OpenBSD 6.9-current (GENERIC.MP) #131.
> >
> > Seems the base change to dhcpleased/resolvd has presented some issues.
>
> This is intentional.
>
> We are moving from a
On Fri, 2021-07-16 at 21:57 -0400, Sonic wrote:
> Having some issues after a sysupgrade to the latest snapshot (of this
> writing) - OpenBSD 6.9-current (GENERIC.MP) #131.
>
> Seems the base change to dhcpleased/resolvd has presented some issues.
> Pf does not start on boot as it claims my dhcp
On Fri, Jul 16, 2021 at 09:57:21PM -0400, Sonic wrote:
> Having some issues after a sysupgrade to the latest snapshot (of this
> writing) - OpenBSD 6.9-current (GENERIC.MP) #131.
>
> Seems the base change to dhcpleased/resolvd has presented some issues.
> Pf does not start on boot as it claims my
Sonic wrote:
> Having some issues after a sysupgrade to the latest snapshot (of this
> writing) - OpenBSD 6.9-current (GENERIC.MP) #131.
>
> Seems the base change to dhcpleased/resolvd has presented some issues.
This is intentional.
We are moving from a model where dhclient on 1 interface
Having some issues after a sysupgrade to the latest snapshot (of this
writing) - OpenBSD 6.9-current (GENERIC.MP) #131.
Seems the base change to dhcpleased/resolvd has presented some issues.
Pf does not start on boot as it claims my dhcp interface has no
address, however after logging in I can
25 matches
Mail list logo
