On Tue, 2025-03-18 at 21:01 +0100, Patrick Dupre via users wrote:
> I need to login on 192.168.8.1
> (the manual says 192.168.1.1 !!)
>
> But, it seems that the DNS does not work
> ping 192.168.8.1 does not answer
> while I can connect through the interface http
If the device has changed IPs t
On Tue, 2025-03-18 at 22:37 +0100, Patrick Dupre via users wrote:
> 127.0.0.1 localhost localhost.localdomain
> ::1 localhost localhost.localdomain localhost6
> localhost6.localdomain6 Teucidide teucidide
Adding your own hostname to the loopback address *can* be a problem.
You may not
Tim:
> > Supposedly, it could show an ordinary user something they shouldn't
> > know, hence the increased security, now.
Stephen Morris:
> It depends on what environment you are in, if you are in an
> organisational environment then it is possible that it may show
> something that is sensitive
Am 18.03.2025 um 22:37:49 Uhr schrieb Patrick Dupre via users:
> ping 172.217.18.99 works
Good, that means IPv4 internet works. Now test 2a00:1450:4001:830::2003
> I tried the DNS 192.168.1.1 which works with the other dongle, but
> not with the new one.
Show ip r s
ip -6 r s
resolvectl
--
Gr
Am 18.03.2025 um 21:01:11 Uhr schrieb Patrick Dupre via users:
> I need to login on 192.168.8.1
> (the manual says 192.168.1.1 !!)
>
> But, it seems that the DNS does not work
> ping 192.168.8.1 does not answer
> while I can connect through the interface http
Some devices don't reply to ICMP.
> On 18 Mar 2025, at 07:29, Tim via users wrote:
>
> Supposedly, it could show an ordinary user something they shouldn't
> know, hence the increased security, now.
As I understand the risk it is the presences of addresses in dmesg output of
kernel internals that are required for attacking the
On Wed, 2025-03-19 at 09:36 +1100, Stephen Morris wrote:
> On 18/3/25 09:20, Will McDonald wrote:
> > On Mon, 17 Mar 2025 at 21:54, Stephen Morris
> > wrote:
> >
> > Having run tracer after a system update how do I determine
> > what it is referring to with the following messages:
>
On 03/18/2025 01:03 PM, Patrick Dupre via users wrote:
I cannot connect to 192.168.1.1
ping 192.168.1.1 does not respond
This is the issue
Try using traceroute instead. If it responds with "no route to host"
you know what your basic difficulty is right there.
--
_
On 18/3/25 09:20, Will McDonald wrote:
On Mon, 17 Mar 2025 at 21:54, Stephen Morris
wrote:
Having run tracer after a system update how do I determine
what it is referring to with the following messages:
You should restart:
* These applications manually:
DiscoverNo
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
=
On 18/3/25 17:45, Marco Moock wrote:
Am 18.03.2025 um 09:02:25 Uhr schrieb Stephen Morris:
[ 69.310393] systemd-fstab-generator[1889]: Checking was requested
for "192.168.1.12:/mnt/HD/HD_a2", but it is not a device.
Please post /etc/fstab and check the last number in the line.
The sixth
On 18/3/25 18:28, Tim via users wrote:
On Tue, 2025-03-18 at 08:43 +1100, Stephen Morris wrote:
Thanks Todd, it's been quite a while since I've used DMESG, but I don't
remember ever having to use sudo with it, nor do I remember ever seeing
the message about kernel buffer access being denied, but
Am 18.03.2025 um 21:35:50 Uhr schrieb Patrick Dupre via users:
> 127.0.0.1 localhost localhost.localdomain
> ::1 localhost localhost.localdomain localhost6
> localhost6.localdomain6
Add the hostname of your system to that list and remove the entries
with the 192.168 IPs.
--
Gruß
Marco
Am 18.03.2025 um 21:21:52 Uhr schrieb Patrick Dupre via users:
> why I cannot ping 192.168.8.1 ?
> while I can http://192.168.8.1
Because the dongle doesn't respond to ICMP, even when required by the
RfCs. Don't stick on that, even when it is nasty.
> Is it in /etc/hosts ?
> I have
> 192.168.1.1
> To: users@lists.fedoraproject.org
> Subject: Re: Dongle USB
>
> Am 18.03.2025 um 21:21:52 Uhr schrieb Patrick Dupre via users:
>
> > why I cannot ping 192.168.8.1 ?
> > while I can http://192.168.8.1
>
> Because the dongle doesn't respond to ICMP, even when required by the
> RfCs. Don't stick o
Every thing OK, I just cannot connect to 198.162.1.1
Mar 18 19:41:43 Teucidide NetworkManager[1491]: [1742323303.4263]
audit: op="connection-update" uuid="8c65db7d-46fe-35b3-a83a-3c8ab886c056"
name="one_touch" args="connection>
Mar 18 19:41:55 Teucidide NetworkManager[1491]: [1742323315.7381
On 03/18/2025 02:01 PM, Patrick Dupre via users wrote:
But, it seems that the DNS does not work
ping 192.168.8.1 does not answer
If you're pinging by IP address, DNS isn't involved.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubs
Hello,
I made progresses.
I need to login on 192.168.8.1
(the manual says 192.168.1.1 !!)
But, it seems that the DNS does not work
ping 192.168.8.1 does not answer
while I can connect through the interface http
nmcli connection
NAME UUID TYPE DEVI
Am 18.03.2025 um 20:00:26 Uhr schrieb Patrick Dupre via users:
> Mar 18 19:42:46 Teucidide NetworkManager[1491]:
> [1742323366.9843] manager: NetworkManager state is now CONNECTED_LOCAL
> Mar 18 19:42:46 Teucidide NetworkManager[1491]: [1742323366.9847]
> audit: op="connection-activate" uuid=
>
> Am 18.03.2025 um 18:02:45 Uhr schrieb Patrick Dupre via users:
>
> > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> > 1 _gateway (192.168.8.1) 2.223 ms !N 2.197 ms !N *
>
> Is the cellular connection established in this situation?
>
> Can you check that in modemmanager-
Am 18.03.2025 um 18:02:45 Uhr schrieb Patrick Dupre via users:
> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> 1 _gateway (192.168.8.1) 2.223 ms !N 2.197 ms !N *
Is the cellular connection established in this situation?
Can you check that in modemmanager-gui?
What does dme
On 3/12/25 10:51 AM, Robert McBroom via users wrote:
On 3/10/25 4:20 AM, Zbigniew Jędrzejewski-Szmek wrote:
On Sun, Mar 09, 2025 at 04:34:35PM -0400, Robert McBroom wrote:
On 3/9/25 2:06 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Sun, Mar 09, 2025 at 06:45:24PM +0100, Michal Schorm wrote:
Hi
> On 18 Mar 2025, at 15:54, Patrick Dupre via users
> wrote:
>
> After tons of tries, my old LTE works !!!
> But the new still does not work.
It has been a very long time since I last looked at this stuff so may be out of
date.
Look at the logs for ModemManager and NetworkManager.
Modem ma
>
> Am 18.03.2025 um 16:53:37 Uhr schrieb Patrick Dupre via users:
>
> > After tons of tries, my old LTE works !!!
>
> What did you change?
Nothings
>
> > 5: virbr0: mtu 1500 qdisc noqueue state
> > DOWN group default qlen 1000
> > link/ether 52:54:00:99:2e:c5 brd ff:ff:ff:ff:ff:ff
> >
>
> Am 18.03.2025 um 13:15:31 Uhr schrieb Patrick Dupre via users:
>
> > 4 months ago, I could used my LTE USB Dongle because I could
> > not connect to 192.168.1.1.
> > There has no reason for that.
> > Anyway, I decided to buy a new Dongle. But I am facing the same
> > issue.
> > lsusb is fine.
Am 18.03.2025 um 16:53:37 Uhr schrieb Patrick Dupre via users:
> After tons of tries, my old LTE works !!!
What did you change?
> 5: virbr0: mtu 1500 qdisc noqueue state
> DOWN group default qlen 1000
> link/ether 52:54:00:99:2e:c5 brd ff:ff:ff:ff:ff:ff
> inet 192.168.122.1/24 brd 192.
Hi All,
Is there an RDP server that runs on Fedora and that
has multi-factor authentication? And that runs well.
Many thanks,
-T
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraprojec
Am 18.03.2025 um 13:15:31 Uhr schrieb Patrick Dupre via users:
> 4 months ago, I could used my LTE USB Dongle because I could
> not connect to 192.168.1.1.
> There has no reason for that.
> Anyway, I decided to buy a new Dongle. But I am facing the same
> issue.
> lsusb is fine.
>
> Could it be
Hello,
4 months ago, I could used my LTE USB Dongle because I could
not connect to 192.168.1.1.
There has no reason for that.
Anyway, I decided to buy a new Dongle. But I am facing the same
issue.
lsusb is fine.
Could it be an issue with fedora? after an update?
I already tried to use a previous
On Tue, 2025-03-18 at 08:43 +1100, Stephen Morris wrote:
> Thanks Todd, it's been quite a while since I've used DMESG, but I don't
> remember ever having to use sudo with it, nor do I remember ever seeing
> the message about kernel buffer access being denied, but it just means I
> will now have
30 matches
Mail list logo
