Re: network mystery!!??

[Ed Greshko]

On 28/03/2022 11:33, Samuel Sieb wrote:
Is it really just me?  I see various people responding.  Do you actually understand what his setup is?  It doesn't make any sense at all to me. 


It is not only you.  I haven't grasped the setup either.

However, I would note that everything was working for him the way he wanted 
until his Broadband supplier
replaced the Cable Modem.

--
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/26/22 23:35, Jack Craig wrote:



On Sat, Mar 26, 2022 at 11:14 PM Samuel Sieb > wrote:


On 3/26/22 22:57, Jack Craig wrote:
 > (internet)---lan connect--- nighthawk>--lan connect-[netgear switch]--

Now we're getting somewhere.  Can you also assign the following IP
addresses from your original email into that diagram?

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

You wrote:

  > 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.

But you list two IP addresses from that subnet.  Did they actually give
you two addresses?  I can ping the .126 one, but not the .121 one.


.121 was supposed to be exported ip, the 126 they said was gateway...

block of 8, 5 usable...


Ok, they give you a small subnet.  If .126 is the gateway, then is that 
your cable modem or the upstream gateway or do you have some computer on 
that address?



1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8  scope host lo
        valid_lft forever preferred_lft forever
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
*2: eno1:  mtu 1500 qdisc fq_codel
state UP group default qlen 1000
     link/ether 50:65:f3:4a:ec:e5 brd ff:ff:ff:ff:ff:ff
     altname enp0s31f6
     inet 10.0.0.101/24  brd 10.0.0.255 scope
global noprefixroute eno1
        valid_lft forever preferred_lft forever
     inet6 fe80::2f5c:874d:5113:3d37/64 scope link noprefixroute
        valid_lft forever preferred_lft forever*
3: virbr0:  mtu 1500 qdisc
noqueue state DOWN group default qlen 1000
     link/ether 52:54:00:06:e4:2a brd ff:ff:ff:ff:ff:ff
     inet 192.168.122.1/24  brd
192.168.122.255 scope global virbr0
        valid_lft forever preferred_lft forever


This doesn't help at all.  You still haven't created a useful diagram 
with IP addresses, so I have no idea how your network is configured. 
You appear to have several different network ranges hooked up somehow.


Is it really just me?  I see various people responding.  Do you actually 
understand what his setup is?  It doesn't make any sense at all to me.

___
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

Very Weird Video Problem: SOLVED

[Richard Kimberly Heck]

I'm posting this just because it was so weird, in the hopes that maybe 
it helps someone somewhere down the road.


Earlier today, videos embedded in web pages just stopped playing on my 
laptop. E.g., if I go to YouTube and click on any video at all, it won't 
start. Or, better, the ad won't. It just kind of sits there with this 
spinning thingy and in some cases pops up a dialog saying "If playback 
doesn't begin shortly, try restarting your device".


Same problem with Chrome, Firefox, and Konqueror. Same problem in both 
KDE and XFCE. Same problem even with a new user. Some kind of system 
problem, apparently.


The web suggested disabling hardware accelaration in Chrome, but that 
didn't help. It turned out that the problem was a mis-configured audio 
device. I'd somehow managed to put the internal audio card into "Analog 
Output Stereo" instead of "Analog Output Duplex". Setting it back 
unblocked the device somehow and allowed the videos to play. Why that 
didn't affect videos playing in VLC, say, I don't know.


Thanks to

https://www.techdim.com/fixed-if-playback-doesnt-begin-shortly-try-restarting-your-device/

for the clue.

Riki

___
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!!??

[Cameron Simpson]

On 28Mar2022 08:42, Cameron Simpson  wrote:
>I'm wondering if you're worrying about routing when you should be
>worrying about the port forward.

Just to follow up to my own post, here's a description of my home LAN:

public-ip-addr
  NBN-modem
192.168.1.0/24
|
  --+---+--
|
192.168.1.2
fw
172.16.1.1
|
  +-+--
  |
172.16.1.6
home-server

I can ssh to my home server because the NBN modem has a public address.  
The configuration required is:

NBN modem: static route to 172.16.1.0/24 via the fw addr, 192.168.1.2.

NBN modem: inbound port fwd of TCP port 22 to 172.16.1.6:22.

fw: Firewall rule permitting TCP traffic to 172.16.1.6:22 from the 
public interface.

Default route for the home server if the fw internal addr.
Default route for the fw is the NBN modem internal addr.
NAT happens only on the NBN modem.

That's all.

Cheers,
Cameron Simpson 
___
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: maybe OT

[Chris Murphy]

On Fri, Mar 18, 2022 at 4:47 PM Paolo Galtieri  wrote:
>
> I'm having issues with a VM.
>
> The VM was originally created under VMware and has worked fine for a
> while.  Today when I booted it up instead of seeing the usual MATE login
> screen I get a login prompt:
>
> f34-01-vm:
>
> no matter what I enter, root or pgaltieri as login it never asks for
> password and immediately says login incorrect.  While it's booting I see
> several [FAILED]... messages, e.g. [FAILED] to start CUPS Scheduler
>
> I booted the system again and this time it dropped into emergency mode.
> In emergency mode I see the following messages in dmesg:
>
> BTRFS info (device sda2): flagging fs with big metadata feature
> BTRFS info (device sda2): disk space caching is enabled
> BTRFS info (device sda2): has skinny extents
> BTRFS info (device sda2): start tree-log replay
> BTRFS info (device sda2): parent transid verify failed on 61849600
> wanted 145639 fount 145637
> BTRFS info (device sda2): parent transid verify failed on 61849600
> wanted 145639 fount 145637
> BTRFS: error (device sda2) in btrfs_replay_log:2423 errno=-5 IO failure
> (Failed to recover log tree)
> BTRFS error (device sda2) open_ctree failed

That's not good. The tree-log is used during fsync as an optimization
to avoid having to do full file system metadata updates. Since the
tree-log exists, we know this file system was undergoing some fsync
write operations which were then interrupted. Either the VM or host
crashed, or one of them was forced to shutdown, or there's a bug that
otherwise prevented the guest operations from completing. Further, the
parent transid verification failure messages indicate some out of
order writes, as if the virtual drive+controller+cache is occasionally
ignoring flush/FUA requests.

I regularly use qemu-kvm VM with cache mode "unsafe". The VM can crash
all day long and at most I lose ~30s of the most recent writes,
depending on the fsync policy of the application doing the writes. But
the file system mounts normally otherwise following the crash. However
if the host crashes while the guest is writing, that file system can
be irreparably damaged. This is expected. So you might want to check
the cache policy being used, make sure that the guest VM is really
shutting down properly before rebooting/shutting down the host.





>
> I ran btrfs check in emergency mode and it came up with a lot of errors.
>
> How do i recover the partition(s) so I can boot the system, or at least
> mount them?

I'd start with
mount -o ro,nologreplay,rescue=usebackuproot

Followed by
mount -o ro,nologreplay,rescue=all

The second one is a bit of a heavy hammer but it's safe insofar as
it's mounting the fs read only and making no changes. It is also
disabling csum checking so any corrupt files still get copied out, and
without any corruption warnings. You can check man 5 btrfs to read a
bit more about the other options and vary the selection. This is
pretty much a recovery operation, i.e. get the important data out.

The repair comment for this particular set of errors:

btrfs rescue zero-log
btrfs check --repair --init-extent-tree
btrfs check --repair

I have somewhat low confidence that it can be repaired rather than
make things worse. So you should start out with the earlier mount
commands to get anything important out of the fs first. IF those don't
work and there's important information to get out, you need to use
btrfs restore.



-- 
Chris Murphy
___
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!!??

[Cameron Simpson]

I'm wondering if you're worrying about routing when you should be 
worrying about the port forward.

Routing: can the server ping, say, 1.1.1.1? Can other hosts at various 
points on your LAN? If so, your routes are just fine.

Also, where are your NAT points? There has to be one on the innermost 
box with a public address, but is there one between your 10. and 192.  
networks? Hopefully the public router is the only thing doing NAT.

Port forward: have you inspected the inbound port forward settings on 
the router (the box with the public IP address, I've lost track). You 
need one mapping inbound TCP to ws-public-address:443 to 
ws-lan-address:443.

Can you run a tcpdump on one of the routers in the chain to see what 
happens? My local firewall's a UNIX box so I can do this there to watch 
any traffic between an internal host and the outer world.

ANd of course what others have been saying: traceroute does not tell you 
everything: various nodes may not respond as needed, and it certainly 
will not be passed through to your WS server inless the inbound rule is 
wide open (all traffic types), which would be a bad thing.

Cheers,
Cameron Simpson 
___
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: Fedora 35 swapon: /swapfile: swapon failed: Invalid argument

[Chris Murphy]

On Thu, Mar 24, 2022 at 6:36 AM Brad Bell  wrote:
>
> I am doing algorithmic differentiation with very large tapes and my jobs 
> sometimes run out of memory.

So the workload is producing a substantial amount of anonymous pages.
It's kinda hard to tell what to do to optimize without a decent amount
of knowledge about the workload's behavior. So you'd have to just
change some things and see if the performance improves. I tentatively
expect that you'd be better off disabling zram-generator, setting up a
swap partition or file, and optionally enabling zswap (which is a
different thing than zram). On the plus side, this frees up quite a
lot of memory (roughly half), but on the negative side it might
increase swap thrashing - it really depends on the workload. But zswap
has the benefit of using Least Recently Used (LRU) to evict pages from
the in-memory compressed cache pool to the conventional swap file.
That way it's the stale pages going to disk and the active ones being
compressed in memory.

Also, for what it's worth, on Btrfs I use /var/swap/swapfile1
/var/swap/swapfile2 ... and so on. Where "varswap" is a subvolume
located on the top-level of the file system (next to install time
default subvolumes "root" and "home") and has chattr +C set on it.
That way should I take snapshots of root (or even var in some custom
configurations) I'm not snapshotting the swapfiles. Snapshotting the
swap files ends up making them subject to COW again, and that's
incompatible with using them as swapfiles. The entry in fstab looks
like this:

UUID=$uuid /var/swap   btrfs   noatime,subvol=varswap 0 0

man 5 btrfs has a SWAPFILE SUPPORT section that's fairly detailed steps.

--
Chris Murphy
___
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!!??

[Jack Craig]

On Sun, Mar 27, 2022 at 2:41 AM Tim via users 
wrote:

> Tim:
> >> Your ISP may be ignoring pings, many other services in between, and
> >> even your own router.
>
> Jack Craig:
> > but why can  i traceroute up to my side of the me<-->isp lan
> > segment??
>
> Because some of the equipment responds, others don't.  If you look back
> at your first posting (repasted below), you'll see there's some in the
> middle that don't respond, either.  They don't stop the connection
> going through past them, they just don't respond to pings.
>
>   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
>
>
>
> > the att rtr knows of the public ip, why doesnt it get used? the
> > mystery so far.
>
> When it comes to things close to you, working backwards, inside your
> LAN you have your own private IPs.  Your router will have its inside IP
> and an outside IP given to it by your ISP (those you can easily find
> out).  What your router first connects to at your ISP may have your-
> side and their-side IPs.  There will be routes going through the
> internals of the ISP through to their supplier.  And then there's all
> the interconnects to more of the web.
>
> For pings, and more to the point, HTTP traffic to your webserver, they
> have to get through all of that.  I think you're just going to have to
> talk to your ISP about why HTTP traffic doesn't get through.
>
> Though do look through your router's settings again.  There may be
> firewall or privacy options that block things.  And you would need to
> set up forwarding/routing rules go pass HTTP through it to your
> webserver.  Some routers have a DMZ zone feature (demilitarised zone),
> where all traffic you haven't specifically set a rule up for can be
> forwarded through to a specific LAN IP, or to a ethernet specific
> socket on the router.  Beware, though, it's unfiltered and unprotected
> by any firewall.  All the gumph on the internet trying to connect to
> you will be allowed through it.
>
>
>
> * the test to change the server ip partially works; that is the srvr can
> see the world, but my access to the rest of my internal 10.0.0.0 is not
> accessible.*

*if i ad the 10.0.0./24  route to the routing for
108.220.213.121 could i not then get to internal and external networks??*




*default via 10.0.0.1 dev eno1 proto static metric 100 10.0.0.0/24
 dev eno1 proto kernel scope link src 10.0.0.101 metric
100 192.168.122.0/24  dev virbr0 proto kernel
scope link src 192.168.122.1 linkdown *



> --
>
> 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
>
___
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

rtkt-daemon spamming on log file

[Javier Perez]

Hi
Checking up my logfile with journalctl -f I noticed a flood of
"rtkit-daemon[1034]: Supervising 16 threads of 13 processes of 1 users."
Why is that happening?
Don't know when it started but it is kind of annoying when I try to keep
track of events on my desktop

Is there any better way to stop it? I've been googling about it but all
"solutions" just make a change on the rtkit-daemon priority level,

JP


-- 
--
 /\_/\
 |O O|  pepeb...@gmail.com
  Javier Perez
   While the night runs
   toward the day...
  m m   Pepebuho watches
from his high perch.
___
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

[Tim via users]

R. G. Newbury wrote:
>> And did that version have an exception for when the sacrifice is to
>> be undertaken if being undertaken *in California*?

Joe Zeff:
> Having spent most of my 72 years in California, I know that the most 
> important thing is to make sure you're using black candles.
> 

It's much harder to find a virgin these days.

-- 
 
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

Re: network mystery!!??

[Tim via users]

Tim:
>> Your ISP may be ignoring pings, many other services in between, and
>> even your own router.

Jack Craig:
> but why can  i traceroute up to my side of the me<-->isp lan
> segment?? 

Because some of the equipment responds, others don't.  If you look back
at your first posting (repasted below), you'll see there's some in the
middle that don't respond, either.  They don't stop the connection
going through past them, they just don't respond to pings.

  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



> the att rtr knows of the public ip, why doesnt it get used? the
> mystery so far.

When it comes to things close to you, working backwards, inside your
LAN you have your own private IPs.  Your router will have its inside IP
and an outside IP given to it by your ISP (those you can easily find
out).  What your router first connects to at your ISP may have your-
side and their-side IPs.  There will be routes going through the
internals of the ISP through to their supplier.  And then there's all
the interconnects to more of the web.

For pings, and more to the point, HTTP traffic to your webserver, they
have to get through all of that.  I think you're just going to have to
talk to your ISP about why HTTP traffic doesn't get through.

Though do look through your router's settings again.  There may be
firewall or privacy options that block things.  And you would need to
set up forwarding/routing rules go pass HTTP through it to your
webserver.  Some routers have a DMZ zone feature (demilitarised zone),
where all traffic you haven't specifically set a rule up for can be
forwarded through to a specific LAN IP, or to a ethernet specific
socket on the router.  Beware, though, it's unfiltered and unprotected
by any firewall.  All the gumph on the internet trying to connect to
you will be allowed through it.

 
-- 
 
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

Re: network mystery!!??

[Ed Greshko]

On 27/03/2022 15:52, Ed Greshko wrote:

On 27/03/2022 15:15, Jack Craig wrote:



On Sun, Mar 27, 2022 at 12:12 AM Jack Craig  wrote:



    On Sun, Mar 27, 2022 at 12:06 AM Ed Greshko  wrote:

    On 27/03/2022 15:04, Jack Craig wrote:
    >
    >
    > On Sat, Mar 26, 2022 at 11:53 PM Ed Greshko  
wrote:
    >
    >     On 27/03/2022 14:40, Jack Craig wrote:
    >     > but srvr is on 10.0.0.101, att rtr is between 192.168.1.254 and 
108.90.204.76.
    >     >
    >     > still make sense??
    >
    >     I see
    >
    >     To test, I want you to make the server a static ip address of 
108.220.213.121 and then connect it to the
    >     BGW210-700.


what routing/gateway should the srvr use for this test??



The server itself.

I'm suspecting your new device is unable to act as a pass though to other 
routers.


To be more specific, it doesn't have to be the server.

Take any Linux Box, manually configure the eithernet port to have a public IP 
address.  Connect it to the new ATT
router and see if you have connectivity.


--
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!!??

[Ed Greshko]

On 27/03/2022 15:15, Jack Craig wrote:



On Sun, Mar 27, 2022 at 12:12 AM Jack Craig  wrote:



On Sun, Mar 27, 2022 at 12:06 AM Ed Greshko  wrote:

On 27/03/2022 15:04, Jack Craig wrote:
>
>
> On Sat, Mar 26, 2022 at 11:53 PM Ed Greshko  
wrote:
>
>     On 27/03/2022 14:40, Jack Craig wrote:
>     > but srvr is on 10.0.0.101, att rtr is between 192.168.1.254 and 
108.90.204.76.
>     >
>     > still make sense??
>
>     I see
>
>     To test, I want you to make the server a static ip address of 
108.220.213.121 and then connect it to the
>     BGW210-700.


what routing/gateway should the srvr use for this test??



The server itself.

I'm suspecting your new device is unable to act as a pass though to other 
routers.


--
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!!??

[Jack Craig]

On Sun, Mar 27, 2022 at 12:12 AM Jack Craig 
wrote:

>
>
> On Sun, Mar 27, 2022 at 12:06 AM Ed Greshko 
> wrote:
>
>> On 27/03/2022 15:04, Jack Craig wrote:
>> >
>> >
>> > On Sat, Mar 26, 2022 at 11:53 PM Ed Greshko 
>> wrote:
>> >
>> > On 27/03/2022 14:40, Jack Craig wrote:
>> > > but srvr is on 10.0.0.101, att rtr is between 192.168.1.254 and
>> 108.90.204.76.
>> > >
>> > > still make sense??
>> >
>> > I see
>> >
>> > To test, I want you to make the server a static ip address of
>> 108.220.213.121 and then connect it to the
>> > BGW210-700.
>>
>
what routing/gateway should the srvr use for this test??


> >
>> > It seems the BGW210-700 may not be as capable as the pace 5238ac
>> was.
>> >
>> >
>> > ok, first thing in the morning. I screw everything up that I do after
>> midnight!  :(
>> >
>>
>> The other idea is to connect a device via WiFi and see what IP address
>> gets assigned to it.
>>
>
> well, the 2.4 on the att rtr is dhcp'ing 192.168.1.63 to 192.168.1.253
>
> the netgear is dhcp'in 10.0.0.20 - 10.0.0.99
>
>>
>> --
>> 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
>>
>
___
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!!??

[Jack Craig]

On Sun, Mar 27, 2022 at 12:06 AM Ed Greshko  wrote:

> On 27/03/2022 15:04, Jack Craig wrote:
> >
> >
> > On Sat, Mar 26, 2022 at 11:53 PM Ed Greshko 
> wrote:
> >
> > On 27/03/2022 14:40, Jack Craig wrote:
> > > but srvr is on 10.0.0.101, att rtr is between 192.168.1.254 and
> 108.90.204.76.
> > >
> > > still make sense??
> >
> > I see
> >
> > To test, I want you to make the server a static ip address of
> 108.220.213.121 and then connect it to the
> > BGW210-700.
> >
> > It seems the BGW210-700 may not be as capable as the pace 5238ac was.
> >
> >
> > ok, first thing in the morning. I screw everything up that I do after
> midnight!  :(
> >
>
> The other idea is to connect a device via WiFi and see what IP address
> gets assigned to it.
>

well, the 2.4 on the att rtr is dhcp'ing 192.168.1.63 to 192.168.1.253

the netgear is dhcp'in 10.0.0.20 - 10.0.0.99

>
> --
> 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
>
___
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!!??

[Ed Greshko]

On 27/03/2022 15:04, Jack Craig wrote:



On Sat, Mar 26, 2022 at 11:53 PM Ed Greshko  wrote:

On 27/03/2022 14:40, Jack Craig wrote:
> but srvr is on 10.0.0.101, att rtr is between 192.168.1.254 and 
108.90.204.76.
>
> still make sense??

I see

To test, I want you to make the server a static ip address of 
108.220.213.121 and then connect it to the
BGW210-700.

It seems the BGW210-700 may not be as capable as the pace 5238ac was.


ok, first thing in the morning. I screw everything up that I do after midnight! 
 :(



The other idea is to connect a device via WiFi and see what IP address gets 
assigned to it.

--
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!!??

[Jack Craig]

On Sat, Mar 26, 2022 at 11:53 PM Ed Greshko  wrote:

> On 27/03/2022 14:40, Jack Craig wrote:
> > but srvr is on 10.0.0.101, att rtr is between 192.168.1.254 and
> 108.90.204.76.
> >
> > still make sense??
>
> I see
>
> To test, I want you to make the server a static ip address of
> 108.220.213.121 and then connect it to the
> BGW210-700.
>
> It seems the BGW210-700 may not be as capable as the pace 5238ac was.
>

ok, first thing in the morning. I screw everything up that I do after
midnight!  :(


> --
> 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
>
___
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!!??

[Ed Greshko]

On 27/03/2022 14:40, Jack Craig wrote:

but srvr is on 10.0.0.101, att rtr is between 192.168.1.254 and 108.90.204.76.

still make sense??


I see

To test, I want you to make the server a static ip address of 108.220.213.121 
and then connect it to the
BGW210-700.

It seems the BGW210-700 may not be as capable as the pace 5238ac was.

--
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!!??

[Jack Craig]

On Sat, Mar 26, 2022 at 11:06 PM Ed Greshko  wrote:

> On 27/03/2022 13:57, Jack Craig wrote:
> >
> >
> > On Sat, Mar 26, 2022 at 10:20 PM Ed Greshko 
> wrote:
> >
> > On 27/03/2022 12:19, Jack Craig wrote:
> > > after much wailing and gnashing of teeth, att did send a tech and
> for general internet access its fine.
> > > just not working with my configuration...
> > >
> > > at the moment, trying to find a static route option for att rtr.
> > >
> > > static routes on the internal router wont help, right??
> >
> > I guess I don't really understand what HW and Physical Configuration.
> >
> > You have a DSL router.  The router has 4 Ethernet ports.  In your
> configuration, what are these ports connected to?
> >
> >
> > ok, ...
> >
> > (internet)---lan connect--- nighthawk>--lan connect-[netgear switch]--
> >
> > make sense?
> >
>
> Is your srvr configured manually?  Meaning, a static IP?
>
> If so, try connecting the bgw210700 directly to the srvr.  Then try
> accessing sites from the server.
>

but srvr is on 10.0.0.101, att rtr is between 192.168.1.254 and
108.90.204.76.

still make sense??


>
> --
> 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
>
___
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!!??

[Jack Craig]

On Sat, Mar 26, 2022 at 11:14 PM Samuel Sieb  wrote:

> On 3/26/22 22:57, Jack Craig wrote:
> > (internet)---lan connect--- > nighthawk>--lan connect-[netgear switch]--
>
> Now we're getting somewhere.  Can you also assign the following IP
> addresses from your original email into that diagram?
>
> 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
>
> You wrote:
>
>  > 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.
>
> But you list two IP addresses from that subnet.  Did they actually give
> you two addresses?  I can ping the .126 one, but not the .121 one.


.121 was supposed to be exported ip, the 126 they said was gateway...

block of 8, 5 usable...





> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
> default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
>valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
>valid_lft forever preferred_lft forever
>
>
>
>
>
>
> *2: eno1:  mtu 1500 qdisc fq_codel state
> UP group default qlen 1000link/ether 50:65:f3:4a:ec:e5 brd
> ff:ff:ff:ff:ff:ffaltname enp0s31f6inet 10.0.0.101/24
>  brd 10.0.0.255 scope global noprefixroute eno1
>  valid_lft forever preferred_lft foreverinet6
> fe80::2f5c:874d:5113:3d37/64 scope link noprefixroutevalid_lft
> forever preferred_lft forever*
> 3: virbr0:  mtu 1500 qdisc noqueue
> state DOWN group default qlen 1000
> link/ether 52:54:00:06:e4:2a brd ff:ff:ff:ff:ff:ff
> inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
>valid_lft forever preferred_lft forever
>

current srv config, static,



> ___
> 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: network mystery!!??

[Samuel Sieb]

On 3/26/22 22:57, Jack Craig wrote:
(internet)---lan connect---nighthawk>--lan connect-[netgear switch]--


Now we're getting somewhere.  Can you also assign the following IP 
addresses from your original email into that diagram?


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


You wrote:

> 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.


But you list two IP addresses from that subnet.  Did they actually give 
you two addresses?  I can ping the .126 one, but not the .121 one.

___
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!!??

[Ed Greshko]

On 27/03/2022 13:57, Jack Craig wrote:



On Sat, Mar 26, 2022 at 10:20 PM Ed Greshko  wrote:

On 27/03/2022 12:19, Jack Craig wrote:
> after much wailing and gnashing of teeth, att did send a tech and for 
general internet access its fine.
> just not working with my configuration...
>
> at the moment, trying to find a static route option for att rtr.
>
> static routes on the internal router wont help, right??

I guess I don't really understand what HW and Physical Configuration.

You have a DSL router.  The router has 4 Ethernet ports.  In your 
configuration, what are these ports connected to?


ok, ...

(internet)---lan connect-lan 
connect-[netgear switch]--

make sense?



Is your srvr configured manually?  Meaning, a static IP?

If so, try connecting the bgw210700 directly to the srvr.  Then try accessing 
sites from the server.

--
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