Re: After f40->f42 upgrade, NAT is not set up.

2025-06-06 Thread fedora
On 7/6/25 05:17, Tim wrote: On Fri, 2025-06-06 at 20:45 +1000, fed...@eyal.emu.id.au wrote: After looking everywhere, and digging into my iptables rules and such, I discovered that NAT is not being set up. I added a rule to my firewall script iptables-legacy -t nat -A POSTROUTING -o et

Re: After f40->f42 upgrade, NAT is not set up.

2025-06-06 Thread fedora
On 7/6/25 09:23, Barry wrote: On 6 Jun 2025, at 11:45, fed...@eyal.emu.id.au wrote: eth0 is the local network, eth1 sees the internet. You are aware that those names can swap which NIC they represent? To be reliable you can have the system use stable NIC naming. Yes I know. The old ifcfg-

Re: After f40->f42 upgrade, NAT is not set up.

2025-06-06 Thread Tim via users
Tim: > > So far as I'm aware, NAT has never been set up automatically, you > > always had to set it up in some way. Joe Zeff: > If you really need NAT, you probably need a router, and that's one of > the things are good at. In general, I'd agree it's the simplest way to do things. But, you can

Re: After f40->f42 upgrade, NAT is not set up.

2025-06-06 Thread Barry
> On 6 Jun 2025, at 11:45, fed...@eyal.emu.id.au wrote: > > eth0 is the local network, eth1 sees the internet. You are aware that those names can swap which NIC they represent? To be reliable you can have the system use stable NIC naming. Barry --

Re: After moving to F41, I still cannot use Wayland

2025-06-06 Thread Go Canes
On Fri, Jun 6, 2025 at 3:36 PM Frédéric wrote: > To solve half of my issues, I was thinking of moving my VM from > VirtualBox to KVM. Maybe some of you could share their experience: > - Has anyone done that before? Yes - I moved a couple of VMs running Windows 10 from VirtualBox to KVM. > - Is

Re: After moving to F41, I still cannot use Wayland

2025-06-06 Thread Patrick O'Callaghan
On Fri, 2025-06-06 at 21:35 +0200, Frédéric wrote: > Hi, > > I moved to F41 and I still cannot use Plasma with wayland because Gimp > and VirtualBox are unusable, in particular because of the mouse. > > To solve half of my issues, I was thinking of moving my VM from > VirtualBox to KVM. Maybe som

Updated 6 machines from Fedora 41 to 42 and all went well, except 1. On it wine 10.8 works, but 10.9 fails.

2025-06-06 Thread Michael D. Setzer II via users
After upgrading Acer notebook, the winehq works with 10.8, but upgrade to 10.9 fails. root@setzconote:~# uname -a Linux setzconote.dyndns.org 6.14.9-300.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 29 14:27:53 UTC 2025 x86_64 GNU/Linux root@setzconote:~# wine notepad MESA-INTEL: warning: Ivy Brid

Re: After moving to F41, I still cannot use Wayland

2025-06-06 Thread Frédéric
> What exactly is the issue? For VirtualBox, I have no mouse in my Windows VM, so quite annoying :=) For Gimp, the widgets get out of the screen, so again quite annoying. Try to place a text on an image and change the font. The font list starts well above the screen. I think there was other issues

Re: After moving to F41, I still cannot use Wayland

2025-06-06 Thread Samuel Sieb
On 6/6/25 12:35 PM, Frédéric wrote: I moved to F41 and I still cannot use Plasma with wayland because Gimp and VirtualBox are unusable, in particular because of the mouse. What issues are you having? I've never had a problem with GIMP in the years I've been using Wayland. Although I've been

Re: After moving to F41, I still cannot use Wayland

2025-06-06 Thread Marco Moock
Am 06.06.2025 um 21:35:42 Uhr schrieb Frédéric: > I moved to F41 and I still cannot use Plasma with wayland because Gimp > and VirtualBox are unusable, in particular because of the mouse. What exactly is the issue? -- Gruß Marco Send unsolicited bulk mail to 1749238542mu...@cartoonies.org --

After moving to F41, I still cannot use Wayland

2025-06-06 Thread Frédéric
Hi, I moved to F41 and I still cannot use Plasma with wayland because Gimp and VirtualBox are unusable, in particular because of the mouse. To solve half of my issues, I was thinking of moving my VM from VirtualBox to KVM. Maybe some of you could share their experience: - Has anyone done that bef

Re: After f40->f42 upgrade, NAT is not set up.

2025-06-06 Thread Joe Zeff
On 06/06/2025 01:17 PM, Tim via users wrote: So far as I'm aware, NAT has never been set up automatically, you always had to set it up in some way. If you really need NAT, you probably need a router, and that's one of the things are good at. -- ___

Re: After f40->f42 upgrade, NAT is not set up.

2025-06-06 Thread Tim via users
On Fri, 2025-06-06 at 20:45 +1000, fed...@eyal.emu.id.au wrote: > After looking everywhere, and digging into my iptables rules and > such, I discovered that NAT is not being set up. > > I added a rule to my firewall script > iptables-legacy -t nat -A POSTROUTING -o eth1 -j MASQUERADE > eth

Re: List available packages in a repo

2025-06-06 Thread Todd Zullinger
Patrick O'Callaghan wrote: > On Thu, 2025-06-05 at 19:48 -0400, Todd Zullinger wrote: >> Essentially, the list command behaves as though '--installed >> --available' are passed if neither are given. >> > > Well, no. If "--available" is given explicitly, it *excludes* the > installed packages exc

Re: network problem after f40->f42 upgrade

2025-06-06 Thread Roger Heflin
You will need to reconfigured the static IP. The old ifcfg* scripts finally got removed I think, something I upgraded broke about that time, and now NetworkManager Drools. On Fri, Jun 6, 2025 at 5:45 AM wrote: > > I recently upgraded f40->f42. > > I have a server with two interfaces, eth1 has in

Re: network problem after f40->f42 upgrade

2025-06-06 Thread Marco Moock
On 06.06.2025 20:45 fed...@eyal.emu.id.au fed...@eyal.emu.id.au wrote: > When I boot the system (switch off) eth0 does not get an IP. Until > f40 it did get a static IP. Why should it get one if the interface is down? If it goes up, the NetworkManager should handle IP addressing. Use that instead

After f40->f42 upgrade, NAT is not set up.

2025-06-06 Thread fedora
I recently upgraded f40->f42. Had issues (see my earlier thread) which I "fixed"... While dealing with that other issue I found that while the server was working just fine, other machines (on a wired connection) still cannot access the internet. After looking everywhere, and digging into my ip

network problem after f40->f42 upgrade

2025-06-06 Thread fedora
I recently upgraded f40->f42. I have a server with two interfaces, eth1 has internet access, eth0 is local through a switch. The switch is usually powered off, unless I use another computer in the house (not often). When I boot the system (switch off) eth0 does not get an IP. Until f40 it did

Re: List available packages in a repo

2025-06-06 Thread Patrick O'Callaghan
On Thu, 2025-06-05 at 19:48 -0400, Todd Zullinger wrote: > Patrick O'Callaghan wrote: > > On Thu, 2025-06-05 at 23:27 +0100, Patrick O'Callaghan wrote: > > > > My conceptual problem is that this makes no logical sense. If I don't > > > > include '--available' than I get a long list of packages whic

Re: gnome

2025-06-06 Thread Will McDonald
On Fri, 6 Jun 2025 at 09:14, Patrick Dupre via users < users@lists.fedoraproject.org> wrote: > Would you know why every time that after I turn off my PC, > the gnome all extension are always turned off when I restart the PC? > I have to turn them on manually every time. > This doesn't appear to b

gnome

2025-06-06 Thread Patrick Dupre via users
Hello, Would you know why every time that after I turn off my PC, the gnome all extension are always turned off when I restart the PC? I have to turn them on manually every time. Thank. === Patrick DUPRÉ