Original Message
On 4/3/25 08:18, Janne Johansson wrote:
> The default route is given by an ip, then the kernel looks up which
> interface contains the network for which the box can reach this ip in a
> single hop. If it can, the route is now shown to be over this interfac
I was under the impression microcode (and most "firmware" in general) was
ephemeral.
--Stephen
On Thu, Apr 03, 2025 at 09:15:26AM +1100, Aaron Mason wrote:
> I've had this happen under Winders - my son's Ryzen 5600G-based PC
> started doing space heater impressions after a microcode update
> atta
Lessons learned are gold.
I am still stuck with the basic case of one firewall for one ISP, because in
the PCI bus the interface connecting with the LAN switch (ix0) sits before the
interface connecting with the gateway (em0), causing obsd to assign ix0 to
egress. Attempts to correct this via h
> Now only today, I had a mediatek wifi card laying around…
> I even
> unplugged everything and put them back in, and still it's not POSTing
Have you tried slowly troubleshooting by pulling out all the cards, then
putting in one thing at a time and trying to post it each time?
PCI cards are
> The problem is the conflict that occurs naturally when connecting any two
> ISPs.
in my not at all humble opinion, with this topology (each ISP presenting the
same subnet on its client side), I would use multiple firewalls. One per ISP.
Use carp if you want to failover or do fancy tricks
I've had this happen under Winders - my son's Ryzen 5600G-based PC
started doing space heater impressions after a microcode update
attached to a Radeon driver came through. If I changed the CPU to one
that hadn't received the update it worked again.
On Thu, Apr 3, 2025 at 9:11 AM Lloyd wrote:
>
>
Hi,
Is there any reason why the amdgpu firmware/driver won't work with
resize BAR enabled? When I enable ReBAR I get:
drm0 at amdgpu0
amdgpu0: msi
drm:pid0:amdgpu_device_init *ERROR* amdgpu_device_ip_init failed
drm:pid0:amdgpu_driver_load_kms *ERROR* Fatal error during GPU init
WARNING !amdgp
Den ons 2 apr. 2025 kl 17:08 skrev otto.cooper :
>
> > The interfaces the default routes point to are members of the "egress"
> > interface group. --- ifconfig(8)
>
> Note the plural.
> If I connect all interfaces to the gateway, only index 1 is promoted to
> egress.
The plural is because ipv4 a
The relevant piece of code seems to be src/sys/net/if.c lines 2912-2966: "add a
group to an interface". This code is for the initiated, as expected. The title
is counterintuitive, because an interface is a physical interface, to be added
to a logical group like egress. So, I am not sure this is
On Wednesday, April 2nd, 2025 at 5:50 PM, Claudio Jeker
wrote:
> egress works. As long as the default route points to ix0 the egress will be
> in ix0.
egress works in the sense that it is singing it and dancing it all by itself,
because if I start the firewall, egress is the LAN which is su
Den ons 2 apr. 2025 kl 19:58 skrev otto.cooper :
> On Wednesday, April 2nd, 2025 at 5:50 PM, Claudio Jeker
> wrote:
> > As long as the default route points to ix0 the egress will be in ix0.
>
> This is what I want to understand. Physically, the default route is the
> gateway. I am in the firewal
> The interfaces the default routes point to are members of the "egress"
> interface group. --- ifconfig(8)
Note the plural.
If I connect all interfaces to the gateway, only index 1 is promoted to egress.
Hello everyone,
I have been working on enabling IPv6 access for OpenVPN clients by
encapsulating IPv6 within IPv4, allowing clients without native IPv6
to reach IPv6 content via the server’s public IPv6.
The ULA address:
-> fdbb:e761:c9ec::/64
Example of address that a client gets assigned from t
I think I am reading it backwards. "The interfaces the default routes point to"
is different than "the interfaces pointing at the default route". The subject
in the sentence is "the default routes".
On Wednesday, April 2nd, 2025 at 5:31 PM, Janne Johansson
wrote:
> Den ons 2 apr. 2025 kl 17:0
Greetings,
I have a fairly old motherboard, foxconn g31 mxp series from 2010 and
it's running on intel pentium dual core. Couple days ago I was curious
about running openbsd on this pc, since I have been running Linux on
it since 2021 or even before that, never had any major issues. The
main reaso
On all OpenBSD systems around here, the interface with index 1 is the only one
in group egress. It seems that OpenBSD blindly does so, based on what interface
comes first at boot time (and its live connection), which depends on its
position on the PCI bus, which ultimately defines its ifconfig "
On Wed, Apr 02, 2025 at 07:31:50PM +0200, Janne Johansson wrote:
> Den ons 2 apr. 2025 kl 17:08 skrev otto.cooper :
> >
> > > The interfaces the default routes point to are members of the "egress"
> > > interface group. --- ifconfig(8)
> >
> > Note the plural.
> > If I connect all interfaces to th
17 matches
Mail list logo
