Re: network mystery!!??

[Cameron Simpson]

I normally don't top post, but there nothing I can meaningfully trim 
from your excellent detailed description. So I'm leaving it below.

To your traceroute, route tracing (IIRC) depends on setting a max hop 
count on the outbound packets. When the hop count is exceeded, you get 
back an ICMP error packet indicating that the count was exceeded from 
the router which decremented the counter to 0.

So to trace a route you send a packet with a max hop count of 1, and get 
a packet back from your router, and that tells you the router IP. Then 
you send one with a max hop count of 2 and get an error packet back from 
the next router upstream, telling you its IP address. And so on.

Plenty of network routers do not respond to pings and do not return 
these error packets - they just drop the packet on the floor. These just 
show up as gaps in the traceroute, because traceroute does not receive 
the ICMP response from the routers at that hop count.

So what you see below is normal. Don't sweat it. Here's an example from 
where I'm sitting to a host on a TPG network:

traceroute to  (14.203.40.46), 64 hops max, 52 byte 
packets
 1  cskk-3g (10.0.0.138)  2.220 ms  1.824 ms  1.716 ms
 2  * * *
 3  10.4.37.50 (10.4.37.50)  31.144 ms  26.018 ms  55.897 ms
 4  10.5.86.65 (10.5.86.65)  33.860 ms  34.792 ms  36.855 ms
 5  10.5.86.72 (10.5.86.72)  49.968 ms  41.517 ms  30.999 ms
 6  203.50.63.96 (203.50.63.96)  35.888 ms  34.900 ms  26.032 ms
 7  bundle-ether26.chw-core10.sydney.telstra.net (203.50.61.96)  27.825 
ms  31.547 ms  31.129 ms
 8  bundle-ether1.chw-edge903.sydney.telstra.net (203.50.11.177)  28.825 
ms  32.709 ms  35.956 ms
 9  aap3461251.lnk.telstra.net (110.145.180.218)  30.886 ms  25.857 ms  
29.599 ms
10  syd-sot-ken-wgw1-be-30.tpgi.com.au (203.219.107.193)  29.719 ms  
28.821 ms  28.611 ms
11  203-221-3-109.tpgi.com.au (203.221.3.109)  33.221 ms  31.921 ms
203-221-3-45.tpgi.com.au (203.221.3.45)  40.022 ms
12  * * *
13  * * *
14  * * *
15  * * *

Cheers,
Cameron Simpson 

On 25Mar2022 19:29, Jack Craig  wrote:
>i have a networking mystery ; i hope someone might give me a clue.
>
>i am working to restore a web server to internet access that is failing
>after att update
>the att older modem (pace 5238ac) with arris BGW210-700.
>
>i have a static ip from att in the range 108.220.213.0/255.255.255.248,
>108.220.213.121 is the external ip for the server.
>
>the bgw210-700 is the primary router/modem and is connected to a 3rd party
>router, netgear nighthawk,
>
>the internal 10.0.0.0/  connects to the netgear nighthawk
>
>ATT's broadband configuration is
>
> Blackhole-ATT (wireless name)
>
>   Broadband connection source  DSL
>   Broadband connection up
>   Broadband network type   lightspeed
>   Broadband ipv4 address   108.90.204.76
>   Broadband gateway address108.90.204.1
>
>outbound packets from the server (WS), are routed from the 10.0.0.1
>nighthawk to the ATT router to the internet.
>
>the 108.90.204.0 network routing from the att router to the att's gateway.
>.76 is the router, .1 is the GW.
>
>sample route, ...
>
>10.0.0.101ws.linuxlighthouse.com (internal IP) 2 packets
>transmitted, 2 received, 0% packet loss, time 1033ms
>10.0.0.1   Blackhole-NH 2
>packets transmitted, 2 received, 0% packet loss, time 1018ms
>192.168.1.254 Blackhole-ATT2
>packets transmitted, 2 received, 0% packet loss, time 1001ms
>108.90.204.76 att subnet (local router)2 packets
>transmitted, 2 received, 0% packet loss, time 1002ms
>108.90.204.1att subnet (remote GW)   2 packets
>transmitted, 2 received, 0% packet loss, time 1001ms
>108.220.213.121   ws.linuxlighthouse.com (public IP) 2 packets transmitted,
>2 received, 0% packet loss, time 1001ms
>108.220.213.126   linuxlighthouse (public GW)  2 packets
>transmitted, 2 received, 0% packet loss, time 1001ms
>
>now the  mystery. where 108.220.213.121 is a publicly visible ip for the
>server, a remote traceroute is wonky!!
>
>consider the below traceroute, it reports hops up to 108.90.204.76,
>stopping there instead of doing one more hop
>
>
>  1<1 ms<1 ms<1 ms  Linksys35675 [192.168.1.1]
>  2 9 ms 8 ms17 ms  142-254-236-209.inf.spectrum.com
>[142.254.236.209]
>  312 ms10 ms11 ms  lag-63.tjngcaac01h.netops.charter.com
>[24.30.172.49]
>  414 ms13 ms13 ms  lag-29.lsaicaev01r.netops.charter.com
>[72.129.18.240]
>  512 ms14 ms11 ms  lag-26.lsancarc01r.netops.charter.com
>[72.129.17.0]
>  619 ms13 ms14 ms  lag-16.lsancarc0yw-bcr00.netops.charter.com
>[66.109.6.102]
>  725 ms37 ms42 ms  lag-3.pr2.lax10.netops.charter.com
>[107.14.19.41]
>  817 ms17 ms17 ms  192.205.32.253
>  922 ms21 ms21 ms  

Re: network mystery!!??

[Ed Greshko]

On 26/03/2022 10:29, Jack Craig wrote:




i have a networking mystery ; i hope someone might give me a clue.

i am working to restore a web server to internet access that is failing after 
att update
the att older modem (pace 5238ac) with arris BGW210-700.

i have a static ip from att in the range 108.220.213.0/255.255.255.248 
, 108.220.213.121 is the external ip for 
the server.

the bgw210-700 is the primary router/modem and is connected to a 3rd party 
router, netgear nighthawk,

the internal 10.0.0.0/   connects to the netgear nighthawk

ATT's broadband configuration is

 Blackhole-ATT (wireless name)

   Broadband connection source      DSL
   Broadband connection             up
   Broadband network type           lightspeed
   Broadband ipv4 address           108.90.204.76
   Broadband gateway address        108.90.204.1


outbound packets from the server (WS), are routed from the 10.0.0.1 nighthawk 
to the ATT router to the internet.

the 108.90.204.0 network routing from the att router to the att's gateway. .76 
is the router, .1 is the GW.

sample route, ...

10.0.0.101 ws.linuxlighthouse.com  (internal IP) 
2 packets transmitted, 2 received, 0% packet loss, time 1033ms
10.0.0.1           Blackhole-NH           2 packets 
transmitted, 2 received, 0% packet loss, time 1018ms
192.168.1.254     Blackhole-ATT      2 packets transmitted, 2 
received, 0% packet loss, time 1001ms
108.90.204.76     att subnet (local router)  2 packets transmitted, 2 
received, 0% packet loss, time 1002ms
108.90.204.1        att subnet (remote GW)               2 packets 
transmitted, 2 received, 0% packet loss, time 1001ms
108.220.213.121 ws.linuxlighthouse.com  (public 
IP) 2 packets transmitted, 2 received, 0% packet loss, time 1001ms
108.220.213.126   linuxlighthouse (public GW)          2 packets transmitted, 2 
received, 0% packet loss, time 1001ms


Sounds like 108.90.204.76 is missing routes. I'm assuming that 108.220.213.121 
previously answered pings
and originally was the final destination of an external traceroute.

[egreshko@meimei ~]$ traceroute 108.220.213.121
traceroute to 108.220.213.121 (108.220.213.121), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.434 ms  0.728 ms  0.681 ms
 2  * * *
 3  tpdt-3308.hinet.net (168.95.82.198)  23.574 ms  23.530 ms 23.451 ms
 4  tpdb-3031.hinet.net (220.128.1.102)  7.827 ms 
220-128-1-50.hinet-ip.hinet.net (220.128.1.50)  7.210 ms tpdt-3032.hinet.net 
(220.128.27.94)  7.386 ms
 5  r4102-s2.tp.hinet.net (220.128.7.69)  7.123 ms r4102-s2.tp.hinet.net 
(220.128.14.93)  7.296 ms r4102-s2.tp.hinet.net (220.128.13.93)  7.252 ms
 6  r4002-s2.tp.hinet.net (220.128.6.85)  7.538 ms r4002-s2.tp.hinet.net 
(220.128.6.81)  6.710 ms  6.656 ms
 7  pa-r32.us.hinet.net (202.39.91.29)  133.962 ms  132.083 ms 132.075 ms
 8  32.141.85.13 (32.141.85.13)  133.458 ms  133.358 ms  133.297 ms
 9  12.123.242.38 (12.123.242.38)  138.066 ms  137.303 ms  139.959 ms
10  12.122.149.225 (12.122.149.225)  143.022 ms  137.567 ms  137.573 ms
11  12.122.158.25 (12.122.158.25)  138.446 ms  137.435 ms  138.346 ms
12  * * *
13  99.134.39.24 (99.134.39.24)  136.686 ms  136.506 ms *
14  99.134.39.11 (99.134.39.11)  136.191 ms  136.211 ms  136.066 ms
15  99.161.44.77 (99.161.44.77)  137.461 ms  137.438 ms  138.025 ms
16  108-90-204-76.lightspeed.mtryca.sbcglobal.net (108.90.204.76) 157.627 ms  
157.580 ms  157.980 ms
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Remember if a server that should be visible externally, but isn't. Then 
outbound requests/replies will also fail.

--
Did 황준호 die?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: network mystery!!??

[Samuel Sieb]

On 3/25/22 19:29, Jack Craig wrote:

i have a networking mystery ; i hope someone might give me a clue.

sample route, ...

10.0.0.101 ws.linuxlighthouse.com  
(internal IP) 2 packets transmitted, 2 received, 0% packet loss, time 1033ms
10.0.0.1           Blackhole-NH 
2 packets transmitted, 2 received, 0% packet loss, time 1018ms
192.168.1.254     Blackhole-ATT                        2 
packets transmitted, 2 received, 0% packet loss, time 1001ms
108.90.204.76     att subnet (local router)            2 packets 
transmitted, 2 received, 0% packet loss, time 1002ms
108.90.204.1        att subnet (remote GW)               2 packets 
transmitted, 2 received, 0% packet loss, time 1001ms
108.220.213.121 ws.linuxlighthouse.com  
(public IP) 2 packets transmitted, 2 received, 0% packet loss, time 1001ms
108.220.213.126   linuxlighthouse (public GW)          2 packets 
transmitted, 2 received, 0% packet loss, time 1001ms


now the  mystery. where 108.220.213.121 is a publicly visible ip for the 
server, a remote traceroute is wonky!!


consider the below traceroute, it reports hops up to 108.90.204.76, 
stopping there instead of doing one more hop



   1    <1 ms    <1 ms    <1 ms  Linksys35675 [192.168.1.1]
   2     9 ms     8 ms    17 ms 142-254-236-209.inf.spectrum.com 
 [142.254.236.209]
   3    12 ms    10 ms    11 ms lag-63.tjngcaac01h.netops.charter.com 

[snip]
  15    44 ms    43 ms    43 ms 
108-90-204-76.lightspeed.mtryca.sbcglobal.net 
 [108.90.204.76]

  16     *        *        *     Request timed out.
  17     *        *        *     Request timed out.
  18     *        *        *     Request timed out.
  19

could anyone shed some light on this mystery??


Your question and description are very confusing.  Can you try again 
with the details more organized?
What are you trying to traceroute to at the end?  The route in the 
traceroute doesn't match the "route" from earlier.  I don't understand 
what you think should be after that last hop.
ISPs don't always let traceroute requests go through depending on which 
method you're using.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

network mystery!!??

[Jack Craig]

i have a networking mystery ; i hope someone might give me a clue.

i am working to restore a web server to internet access that is failing
after att update
the att older modem (pace 5238ac) with arris BGW210-700.

i have a static ip from att in the range 108.220.213.0/255.255.255.248,
108.220.213.121 is the external ip for the server.

the bgw210-700 is the primary router/modem and is connected to a 3rd party
router, netgear nighthawk,

the internal 10.0.0.0/  connects to the netgear nighthawk

ATT's broadband configuration is

 Blackhole-ATT (wireless name)

   Broadband connection source  DSL
   Broadband connection up
   Broadband network type   lightspeed
   Broadband ipv4 address   108.90.204.76
   Broadband gateway address108.90.204.1


outbound packets from the server (WS), are routed from the 10.0.0.1
nighthawk to the ATT router to the internet.

the 108.90.204.0 network routing from the att router to the att's gateway.
.76 is the router, .1 is the GW.

sample route, ...

10.0.0.101ws.linuxlighthouse.com (internal IP) 2 packets
transmitted, 2 received, 0% packet loss, time 1033ms
10.0.0.1   Blackhole-NH 2
packets transmitted, 2 received, 0% packet loss, time 1018ms
192.168.1.254 Blackhole-ATT2
packets transmitted, 2 received, 0% packet loss, time 1001ms
108.90.204.76 att subnet (local router)2 packets
transmitted, 2 received, 0% packet loss, time 1002ms
108.90.204.1att subnet (remote GW)   2 packets
transmitted, 2 received, 0% packet loss, time 1001ms
108.220.213.121   ws.linuxlighthouse.com (public IP) 2 packets transmitted,
2 received, 0% packet loss, time 1001ms
108.220.213.126   linuxlighthouse (public GW)  2 packets
transmitted, 2 received, 0% packet loss, time 1001ms

now the  mystery. where 108.220.213.121 is a publicly visible ip for the
server, a remote traceroute is wonky!!

consider the below traceroute, it reports hops up to 108.90.204.76,
stopping there instead of doing one more hop


  1<1 ms<1 ms<1 ms  Linksys35675 [192.168.1.1]
  2 9 ms 8 ms17 ms  142-254-236-209.inf.spectrum.com
[142.254.236.209]
  312 ms10 ms11 ms  lag-63.tjngcaac01h.netops.charter.com
[24.30.172.49]
  414 ms13 ms13 ms  lag-29.lsaicaev01r.netops.charter.com
[72.129.18.240]
  512 ms14 ms11 ms  lag-26.lsancarc01r.netops.charter.com
[72.129.17.0]
  619 ms13 ms14 ms  lag-16.lsancarc0yw-bcr00.netops.charter.com
[66.109.6.102]
  725 ms37 ms42 ms  lag-3.pr2.lax10.netops.charter.com
[107.14.19.41]
  817 ms17 ms17 ms  192.205.32.253
  922 ms21 ms21 ms  cr1.la2ca.ip.att.net [12.122.128.102]
 1024 ms25 ms25 ms  12.122.158.41
 11 *** Request timed out.
 12 *** Request timed out.
 1323 ms21 ms23 ms  99.134.39.15
 1425 ms24 ms26 ms  99.161.44.79
 1544 ms43 ms43 ms
108-90-204-76.lightspeed.mtryca.sbcglobal.net [108.90.204.76]
 16 *** Request timed out.
 17 *** Request timed out.
 18 *** Request timed out.
 19


could anyone shed some light on this mystery??

tia,jackc...
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Help configuring internal network

[Michael Hennebry]

It seems I badly misnterpreted the verb "to give".

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[R. G. Newbury]

Date: Fri, 25 Mar 2022 01:02:01 -0700

Samuel Sieb wrote

Subject: Re: pipewire and wireplumber
R. G. Newbury wrote:

DJ Delorie  wrote

Geoffrey Leach  writes:

Is there a 'Getting Started With pipewire' and/or wireplumber
somewhere? Or should they 'just work' and I need to check my
connections?

As a non-gnome (and non-display-manager) user, I share these .xsession
snippets:

# Required by pipewire, at least
export XDG_RUNTIME_DIR=$(mktemp -d/tmp/$(id -u)-runtime-dir.XXX)

# Required by most things
eval `dbus-launch --sh-syntax --exit-with-session`

pipewire &
pipewire-pulse &
(sleep 2 ; wireplumber & ) &


There wasn't a pipewire-specific config; it uses the same ALSA backend
as pulseaudio used.

If you don't mind answering, was it a Rhode Island Red cockerel or a hen
which you sacrificed to learn these arcane secrets? And, full-moon at
midnight, or dark of the moon? Or did this take moving up to a goat?
Or are you a graduate of Hogwarts? Because I am quite sure that none of
these snippets show up anywhere in the so-called documentation. Pure
magic, just like any sufficiently advanced technology.



That's because they aren't necessary.  For any standard desktop all
those pieces are already setup for you.  Notice how he said
"non-display-manager user".  Those are only necessary if you don't have
a graphical login session.


Non-display-manager user or not, those might be necessary even if you 
have a graphical login session. I installed the KDE spin of Fedora 35 on 
Monday. A bare metal install: I partitioned the sda drive and formatted 
it during the install.
I had NO audio. And nothing I did allowed the system to even *find* any 
audio hardware. I played a fugue's worth of combinations and read 
everything I could find.
Unfortunately, as noted in this thread, there is no install guide. It 
just works - NOT. I saw an error message about XDG_RUNTIME_DIR and spent 
most of an evening down that rabbit-hole, but nothing worked. Pipewire 
would not even find a module which its own rpm had installed. In the 
end, I basically inverted the lines of the install process script I was 
playing with, and re-installed pulseaudio.


Audio works fine now. My opinion of pipewire is, that like pulseaudio 
and systemd were, it has been released far too early in its beta stages. 
It took a couple of years for each of pulseaudio and systemd to reach 
adequate levels of instalability and reliability. Likely the same for 
pipewire.


Geoff
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[DJ Delorie]

Roger Heflin  writes:
> He has a graphical login session.

I very clearly stated that I did not.  I boot to a text login prompt,
log in, and run "exec xinit .xsession -- -listen tcp -retro" (I have a
script for it called "x" :)

I've never had much luck getting login managers to run my weird
environment correctly.

> I am going to guess he is using straight-X windows with one of the
> ancient simple window managers (twm, mwm).

fvwm2 :-)

> DJ: are you the same DJ Delorie that did the work 30 years ago on
> djgcc for DOS?  If so, that was some good work.  I used it for some
> image processing work.

Yes.  You're welcome!  It's always good to hear that someone found my
work useful.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[DJ Delorie]

"R. G. Newbury"  writes:
> If you don't mind answering, was it a Rhode Island Red cockerel or a hen 
> which you sacrificed to learn these arcane secrets? And, full-moon at 
> midnight, or dark of the moon? Or did this take moving up to a goat?

It took a LOT of googling to find the one person who mentioned it
elsewhere in the space-time continuum.

> Or are you a graduate of Hogwarts? Because I am quite sure that none of 
> these snippets show up anywhere in the so-called documentation. Pure 
> magic, just like any sufficiently advanced technology.

IIRC it was Arch's or Gentoo's forums that had this bare-metal-gem.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[stan via users]

On Fri, 25 Mar 2022 10:35:55 -0700
Geoffrey Leach  wrote:

> It appears that I should try rawhide. Short of removing the elevant
> packages, is there anything else that I should know about making the
> transition?

That seems a little drastic!  While rawhide is far more stable now than
the rawhides of yore, it still has occasional issues because it is
where all the discontinuous changes are introduced.  I first started
using rawhide when it was f35.  Like you, I found pipewire to be
*difficult* [1].  So, also like you, I switched back to pulseaudio.
When rawhide became f36, I noticed the swap command, used it.  I then
read that wireplumber was going to obsolete pipewire-manager, and
switched to it.  With the exception of the setting of the default
device and the recent glitch (that, as far as I know didn't get into
stable versions), wireplumber 4.8.2, I have had no problems.  I also
have a simple use case, though I have multiple cards.  I was able to
set up everything satisfactorily using pavucontrol.  I don't use the
command line equivalents, so I don't know if they work, but I didn't
need them.

As far as I am aware, the same versions in rawhide are in the stable
releases, after they pass muster in rawhide.

1.  I was using pulseaudio-equalizer, and I didn't find an equivalent
for pipewire, so I was reluctant to give it up.  Later, I found the
easyeffects package for pipewire that provides an equalizer, so I made
the switch.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[Patrick O'Callaghan]

On Fri, 2022-03-25 at 10:35 -0700, Geoffrey Leach wrote:
> It appears that I should try rawhide. Short of removing the elevant
> packages, is there anything else that I should know about making the
> transition?

If you go ahead, note that Rawhide issues should be discussed on the
Fedora Test list rather than here.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[Geoffrey Leach]

It appears that I should try rawhide. Short of removing the elevant
packages, is there anything else that I should know about making the
transition?

On Fri, Mar 25, 2022 at 6:59 AM stan via users <
users@lists.fedoraproject.org> wrote:

> On Thu, 24 Mar 2022 14:07:27 -0700
> Geoffrey Leach  wrote:
>
> > I've just installed Fedora 35 and have discovered to my dismay that
> > previously-working (not at all sophisticated) audio no longer works.
> >
> > Is there a 'Getting Started With pipewire' and/or wireplumber
> > somewhere? Or should they 'just work' and I need to check my
> > connections?
>
> I'm successfully using wireplumber and pipewire in rawhide, since it
> was f36. I think I had your issue as some point.  But, just like with
> pulseaudio, it turned out to be that the default device was incorrect.
> I used pavucontrol, still present though it is no longer pulseaudio
> under the covers, and set the default device to the one I wanted, and
> it has worked fine ever since.
>
> There was a recent glitch with a wireplumber update that caused sound to
> stop working, but it was fixed within a few days.
>
> In summary, for me sound is just working with wireplumber and pipewire
> replacing pulseaudio.  And, since it is inevitable that they are going
> to replace pulseaudio, might as well bite the bullet and get them
> working.  When replacing pulseaudio with pipewire, use the swap command,
> dnf swap pulseaudio pipewire-pulseaudio
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[Steve Underwood]

On 25/03/2022 04:42, R. G. Newbury wrote:

Geoffrey Leach  wrote:


Obviously we are guinea pigs for this premature piece of software.


Could not agree more with the last sentence. To get audio recognized 


It works both ways. I have had long term problems with pulseaudio that 
disappeared when I tried an early version of pipewire for Fedora, in the 
days before pipewire became the default. Pipewire wasn't really complete 
the last time I checked. Specifically, surround sound with PCM was 
buggy, and surround sound with things like AC3, which worked with 
pulseaudio, didn't work at all with pipewire. However, for stereo setups 
it fixed all the problems I had.


Regards,

Steve

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[stan via users]

On Thu, 24 Mar 2022 14:07:27 -0700
Geoffrey Leach  wrote:

> I've just installed Fedora 35 and have discovered to my dismay that
> previously-working (not at all sophisticated) audio no longer works.
> 
> Is there a 'Getting Started With pipewire' and/or wireplumber
> somewhere? Or should they 'just work' and I need to check my
> connections?

I'm successfully using wireplumber and pipewire in rawhide, since it
was f36. I think I had your issue as some point.  But, just like with
pulseaudio, it turned out to be that the default device was incorrect.
I used pavucontrol, still present though it is no longer pulseaudio
under the covers, and set the default device to the one I wanted, and
it has worked fine ever since.

There was a recent glitch with a wireplumber update that caused sound to
stop working, but it was fixed within a few days.

In summary, for me sound is just working with wireplumber and pipewire
replacing pulseaudio.  And, since it is inevitable that they are going
to replace pulseaudio, might as well bite the bullet and get them
working.  When replacing pulseaudio with pipewire, use the swap command,
dnf swap pulseaudio pipewire-pulseaudio
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[Patrick O'Callaghan]

On Fri, 2022-03-25 at 00:42 -0400, R. G. Newbury wrote:
> > > Obviously we are guinea pigs for this premature piece of
> > > software.
> 
> Could not agree more with the last sentence.

Bear in mind that Fedora is where we are always guinea pigs to some
extent. That's part of the deal.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[Roger Heflin]

He has a graphical login session.   I am going to guess he is using
straight-X windows with one of the ancient simple window managers (twm,
mwm).   I have used similar setups on set-top boxes where memory is limited
and gnome is overcomplicated and often gets in the way of it working.

DJ:  are you the same DJ Delorie that did the work 30 years ago on djgcc
for DOS?   If so, that was some good work.  I used it for some image
processing work.



On Fri, Mar 25, 2022 at 3:03 AM Samuel Sieb  wrote:

> On 3/24/22 21:49, R. G. Newbury wrote:
> >
> > DJ Delorie  wrote
> >
> >> Geoffrey Leach  writes:
> >>> Is there a 'Getting Started With pipewire' and/or wireplumber
> >>> somewhere? Or should they 'just work' and I need to check my
> >>> connections?
> >>
> >> As a non-gnome (and non-display-manager) user, I share these .xsession
> >> snippets:
> >>
> >> # Required by pipewire, at least
> >> export XDG_RUNTIME_DIR=$(mktemp -d /tmp/$(id -u)-runtime-dir.XXX)
> >>
> >> # Required by most things
> >> eval `dbus-launch --sh-syntax --exit-with-session`
> >>
> >> pipewire &
> >> pipewire-pulse &
> >> (sleep 2 ; wireplumber & ) &
> >>
> >>
> >> There wasn't a pipewire-specific config; it uses the same ALSA backend
> >> as pulseaudio used.
> >
> > If you don't mind answering, was it a Rhode Island Red cockerel or a hen
> > which you sacrificed to learn these arcane secrets? And, full-moon at
> > midnight, or dark of the moon? Or did this take moving up to a goat?
> > Or are you a graduate of Hogwarts? Because I am quite sure that none of
> > these snippets show up anywhere in the so-called documentation. Pure
> > magic, just like any sufficiently advanced technology.
>
> That's because they aren't necessary.  For any standard desktop all
> those pieces are already setup for you.  Notice how he said
> "non-display-manager user".  Those are only necessary if you don't have
> a graphical login session.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

[Samuel Sieb]

On 3/24/22 21:49, R. G. Newbury wrote:


DJ Delorie  wrote


Geoffrey Leach  writes:

Is there a 'Getting Started With pipewire' and/or wireplumber
somewhere? Or should they 'just work' and I need to check my
connections?


As a non-gnome (and non-display-manager) user, I share these .xsession
snippets:

# Required by pipewire, at least
export XDG_RUNTIME_DIR=$(mktemp -d /tmp/$(id -u)-runtime-dir.XXX)

# Required by most things
eval `dbus-launch --sh-syntax --exit-with-session`

pipewire &
pipewire-pulse &
(sleep 2 ; wireplumber & ) &


There wasn't a pipewire-specific config; it uses the same ALSA backend
as pulseaudio used.


If you don't mind answering, was it a Rhode Island Red cockerel or a hen 
which you sacrificed to learn these arcane secrets? And, full-moon at 
midnight, or dark of the moon? Or did this take moving up to a goat?
Or are you a graduate of Hogwarts? Because I am quite sure that none of 
these snippets show up anywhere in the so-called documentation. Pure 
magic, just like any sufficiently advanced technology.


That's because they aren't necessary.  For any standard desktop all 
those pieces are already setup for you.  Notice how he said 
"non-display-manager user".  Those are only necessary if you don't have 
a graphical login session.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Help configuring internal network

[Samuel Sieb]

On 3/25/22 00:48, Tim via users wrote:

R. G. Newbury:

edit your /etc/hosts file to give the hdhomerun unit a fixed IP
address.



Tim 
When has the /etc/hosts file ever given anything an IP address?


R. G. Newbury

You are correct, and I am completely wrong. A static address for
the computer would be set by editing
/etc/sysconfig/network-scripts/ifcfg-eno1 (or whatever) or using
the network config gui to do the same thing.


Michael Hennebry:

Huh?

 From man hosts:
SYNOPSIS
/etc/hosts

   For each host a single line should be present
with the following information:

   IP_address canonical_hostname [aliases...]




Samuel Sieb:

That's not *giving* anything an IP address.  It's assigning a name
for the local host to be able to *lookup* an IP address.


Samuel, I can't tell if you've misunderstood, or grammar has gone out
of whack.  The hosts file is doing nothing to enable looking up an IP
address just because it's given a name to the local host.  Sure, it
gives an answer for the things written in it, but it does nothing else.
It answers no other questions.  It gives no other clues about how to
work out other addresses.  Naming the local loopback address does
nothing to aid looking up other addresses.


I know exactly how the thread progressed and I was replying to Michael 
who seemed to be implying that the hosts file should be giving something 
an IP address.  Maybe he was replying to the wrong thing, but I have no 
way to know that.  I also didn't say anything about a loopback address, 
so I don't know where that is coming from.  Maybe you are 
misunderstanding what I wrote.  The second sentence is directly related 
to the first one.  i.e. The hosts file assigns a name to an IP address 
so that the local host (the one holding the hosts file) can find that IP 
address.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Help configuring internal network

[Tim via users]

R. G. Newbury:
> edit your /etc/hosts file to give the hdhomerun unit a fixed IP
> address.


Tim >>> When has the /etc/hosts file ever given anything an IP address?

R. G. Newbury
>>> You are correct, and I am completely wrong. A static address for
>>> the computer would be set by editing
>>> /etc/sysconfig/network-scripts/ifcfg-eno1 (or whatever) or using
>>> the network config gui to do the same thing.

Michael Hennebry:
>> Huh?
>>
>> From man hosts:
>> SYNOPSIS
>>/etc/hosts
>>
>>   For each host a single line should be present
>>with the following information:
>>
>>   IP_address canonical_hostname [aliases...]



Samuel Sieb:
> That's not *giving* anything an IP address.  It's assigning a name
> for the local host to be able to *lookup* an IP address.


The above posts are in sequence, how the thread progressed, and the
thread was written with the responses in that sequence, with each
message containing all that text.  Read through them before replying. 
Don't just read the top one and respond to that.  It's already been
answered.


Michael, when replying to messages, reply to the right one.  Your
"huh?" posting should NOT have been to the one where R G Newbury,
started going on ifcfg files, but one or two prior where hosts was
being misunderstood.  By now, that mistake had been addressed and
corrected.  Don't just hop into a thread, miles later and discuss
something that has already passed by.  If you want to redundantly add
to a thread, go back and reply to the right one.


Samuel, I can't tell if you've misunderstood, or grammar has gone out
of whack.  The hosts file is doing nothing to enable looking up an IP
address just because it's given a name to the local host.  Sure, it
gives an answer for the things written in it, but it does nothing else.
It answers no other questions.  It gives no other clues about how to
work out other addresses.  Naming the local loopback address does
nothing to aid looking up other addresses.

 
-- 
 
uname -rsvp
Linux 3.10.0-1160.59.1.el7.x86_64 #1 SMP Wed Feb 23 16:47:03 UTC 2022 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure