Re: GIT problem

[tomas]

On Tue, May 09, 2023 at 09:47:45PM -0600, William Torrez Corea wrote:
> Command:
> 
> git push master origin
> >
> 
> I want upload my change to branch MAIN but when i want upload my change i
> get the following error:
> 
> remote: Support for password authentication was removed on August 13, 2021.
> > remote: Please see
> > https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls
> > for information on currently recommended modes of authentication.
> > fatal: Authentication failed for '
> > https://github.com/Villelmo/Beginning_Perl.git/'

I am not touching github even with aseptic gloves, so I'm not going
to read what they say, but the error message is pretty clear.

To upload ("push", in git parlance), you need to authenticate to
origin (somewhere at github in your case). Up to now, you have been
using https with password for that -- they disabled that method
because they consider it insecure. So you will have to change
accordingly.

The relevant commands on your side are along the lines of

  # this removes your disfunctional remote called 'origin'
  git remote remove origin
  # this re-adds it
  git remote add origin 

BE CAREFUL: find out what  is BEFORE you do the remove. Your
 might be something like "git:g...@github.com:your/repo/path"
or similar, depending on the instructions at github.

I won't read them -- github gives me skin rashes.

Cheers & good luck.
-- 
t


signature.asc
Description: PGP signature

Re: GIT problem

[Tim Woodall]

On Tue, 9 May 2023, William Torrez Corea wrote:


Command:

git push master origin




shouldn't that be git push origin master? Or even origin main?


I want upload my change to branch MAIN but when i want upload my change i
get the following error:

remote: Support for password authentication was removed on August 13, 2021.

remote: Please see
https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls
for information on currently recommended modes of authentication.
fatal: Authentication failed for '
https://github.com/Villelmo/Beginning_Perl.git/'



You need to do what it says.



*My changes are uploaded to branch MASTER. *


Not sure what this means. You previously sasid the push was rejected.

GIT problem

[William Torrez Corea]

Command:

git push master origin
>

I want upload my change to branch MAIN but when i want upload my change i
get the following error:

remote: Support for password authentication was removed on August 13, 2021.
> remote: Please see
> https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls
> for information on currently recommended modes of authentication.
> fatal: Authentication failed for '
> https://github.com/Villelmo/Beginning_Perl.git/'
>

*My changes are uploaded to branch MASTER. *
-- 

With kindest regards, William.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: relevance of packages in repositories

[zithro]

On 09 May 2023 23:21, Andy Smith wrote:

Hello,

On Tue, May 09, 2023 at 05:40:18AM +0200, zithro wrote:

In short, zero time taken.


For a comparatively large response. Almost as if that was their goal
(trolling)!

Cheers,
Andy



Well he's using 225 chars, me 424, it's only ~ the double ;)
And now I have a template for noobs like him \o/

Plus, if he's never answering back, I'll have an addition to my 
direct-to-trash filter, so I'll never loose time again for him.

Re: relevance of packages in repositories

[Andy Smith]

Hello,

On Tue, May 09, 2023 at 05:40:18AM +0200, zithro wrote:
> In short, zero time taken.

For a comparatively large response. Almost as if that was their goal
(trolling)!

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

> I'd be interested to hear any (even two word) reviews of their sofas…
Provides seating.— Andy Davidson

Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/9/23 07:12, Greg Wooledge wrote:

On Tue, May 09, 2023 at 04:06:14AM -0400, gene heskett wrote:

I think you have said resolv.conf Search directive doesn't work but
nsswitch.conf was mentioned and there is a diff between this machine and one
of the arms. So what do I put in nsswitch.conf to make cups search the hosts
file first?


The bare minimum would be:

hosts:  files dns

Mine contains this:

hosts:  files mdns4_minimal [NOTFOUND=return] dns

and my bpi54 is:
hosts:  files mymachines dns myhostname


The "search" directive in /etc/resolv.conf is followed by a space-separated
list of domain names.  Yours should say:

search coyote.den

aha! again: was:
nameserver 192.168.71.1
search hosts,nameserver
Which is not space separated, thank you, I've got it fixed in 2 places 
now. I think.

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver

[chris]

Any update on the status of this Epson printer? The world is dying to know
the outcome of this saga

On Mon, May 8, 2023, 2:35 PM Brad Rogers  wrote:

> On Mon, 8 May 2023 12:37:35 -0400
> chris  wrote:
>
> Hello chris,
>
> >Are we at the point yet where this has enough attention it would have
> >been cheaper to crowd fund a new printer?? 🤣🤣
>
> (smiley noted)
>
> I'm betting even that wouldn't work;  At this point, I'm of the opinion
> (after a quick glance through some of the earlier posts in this thread)
> that the OP may have installed the driver from Debian but has not fired
> up CUPS to actually make use of it.
>
> Given their obvious difficulties with English (not their native tongue,
> so entirely understandable) help from this point would have most likely
> have to take the form of paying them a visit.
>
> --
>  Regards  _   "Valid sig separator is {dash}{dash}{space}"
>  / )  "The blindingly obvious is never immediately apparent"
> / _)rad   "Is it only me that has a working delete key?"
> I'm spending all my money and it's going up my nose
> Teenage Depression - Eddie & The Hot Rods
>

Re: Unable to run virsh on bookworm

[piorunz]

On 09/05/2023 20:10, Sean Whalen wrote:

Hi,

I've installed virt-manager on a Debian bookworm system, and that is
working fine. However, when I try to use the libvirt CLI client, virsh,
I receive this error message:

virsh: /usr/local/lib/x86_64-linux-gnu/libvirt.so.0: version
`LIBVIRT_PRIVATE_9.0.0' not found (required by virsh)

The Fedora package libvirt-libs
 
9.0.0 states that it provides libvirt.so.0(LIBVIRT_PRIVATE_9.0.0)(64bit), so I'm not 
sure why the Debian package wouldn't be the same way, or why virt-manager works but 
virsh does not.

I just filed a bug
 (that was my
time using the Debi an bug tracking system). Is anyone aware of a
workaround for this bug until it is fixed?


Hi Sean,

I use virt-manager on Bookworm and it works very well.
You can investigate and fix this yourself. First, determine to which
package this file belongs:
$ apt-file search libvirt.so.0
libvirt0: /usr/lib/x86_64-linux-gnu/libvirt.so.0
libvirt0: /usr/lib/x86_64-linux-gnu/libvirt.so.0.9000.0

So, you need to install (or reinstall) libvirt0 package to make sure you
have correct version, as Sven suggested in e-mail just before mine.

$ apt-cache policy libvirt0
libvirt0:
  Installed: 9.0.0-3
  Candidate: 9.0.0-3
  Version table:
 *** 9.0.0-3 500
500 http://deb.debian.org/debian bookworm/main amd64 Packages
100 /var/lib/dpkg/status

I have it installed, and its all working for me.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Unable to run virsh on bookworm

[Sven Joachim]

On 2023-05-09 19:10 +, Sean Whalen wrote:

> I've installed virt-manager on a Debian bookworm system, and that is
> working fine. However, when I try to use the libvirt CLI client,
> virsh, I receive this error message:
>
> virsh: /usr/local/lib/x86_64-linux-gnu/libvirt.so.0: version
> `LIBVIRT_PRIVATE_9.0.0' not found (required by virsh)

Note the '/usr/local/lib/…' path here.  This version of libvirt.so.0 is
most likely older than the one in the libvirt0 package.  Probably at
some time in the past you installed it.

> The Fedora package libvirt-libs
> 
> 9.0.0 states that it provides
> libvirt.so.0(LIBVIRT_PRIVATE_9.0.0)(64bit), so I'm not sure why the
> Debian package wouldn't be the same way, or why virt-manager works but
> virsh does not.
>
> I just filed a bug
>  (that was
> my time using the Debian bug tracking system). Is anyone aware of a
> workaround for this bug until it is fixed?

You can and you have to fix it yourself, by moving the locally installed
libvirt.so.0 out of the way.

Cheers,
   Sven

Unable to run virsh on bookworm

[Sean Whalen]

Hi,

I've installed virt-manager on a Debian bookworm system, and that is 
working fine. However, when I try to use the libvirt CLI client, virsh, 
I receive this error message:


virsh: /usr/local/lib/x86_64-linux-gnu/libvirt.so.0: version 
`LIBVIRT_PRIVATE_9.0.0' not found (required by virsh)


The Fedora package libvirt-libs 
 
9.0.0 states that it provides 
libvirt.so.0(LIBVIRT_PRIVATE_9.0.0)(64bit), so I'm not sure why the 
Debian package wouldn't be the same way, or why virt-manager works but 
virsh does not.


I just filed a bug 
 (that was my 
time using the Debian bug tracking system). Is anyone aware of a 
workaround for this bug until it is fixed?


--
Respectfully,
Sean Whalen


signature.asc
Description: OpenPGP digital signature

Re: Logging off an X session closes all ssh -X connections started previously from outside X

[Dan Ritter]

zithro wrote: 
> On 09 May 2023 17:47, Vincent Lefevre wrote:
> > BTW, you should also try GNU Screen to see if you have the same issue
> > with it (this could help debugging).
> 
> Do you mean trying "ssh u@h screen" ?
> Never tried screen with GUI apps, does that work ?

Not in a useful way. For the equivalent of screen for X11, you
can try nxagent or workarounds like xvnc.

-dsr-

Re: Logging off an X session closes all ssh -X connections started previously from outside X

[Greg Wooledge]

On Tue, May 09, 2023 at 08:07:26PM +0200, zithro wrote:
> I use Ctrl-D to close ssh sessions, "~." does not work, I get "bash: command
> not found".

To use the tilde commands in the ssh client, they have to be at the
"beginning of a line", which means you have to press Enter first.  Or
at least have the ssh client in a position where it believes you've
pressed Enter recently enough.

For my own sanity, I just think of them as 3-character sequences,
  Enter ~ .  and so on.

Re: Logging off an X session closes all ssh -X connections started previously from outside X

[zithro]

On 09 May 2023 18:06, Vincent Lefevre wrote:

On 2023-05-05 15:04:27 +0200, zithro wrote:


journalctl after GUI LOGOFF


[...]

May 05 14:09:14 debzit sshd[14246]: Received disconnect from IP.IP.IP.IP
port 38524:11: disconnected by user

  

"disconnected by user": Doesn't this mean that it is the client that
did the disconnection (for whatever reason)?


I dunno, but it happens when the server-side logoff is requested from X ...
Can't see the relation : how can a server X logoff send a request to the 
ssh command on the client ?!?!


However I just tried, I killed an ssh session from the server, didn't 
get the "disconnect" message in logs.
Although I don't know if killing (via SIGTERM) is equivalent to what 
whatever the system uses to close the ssh sessions when my problem is 
happening.



This is the message I observe when I disconnect the ssh session from
the client (with "~.") instead of terminating the program (e.g. shell)
on the server side.


Same here for normal exits, or I think so ?
I use Ctrl-D to close ssh sessions, "~." does not work, I get "bash: 
command not found".



[...]

May 05 14:09:14 debzit sshd[14113]: Received disconnect from IP.IP.IP.IP
port 38512:11: disconnected by user

[...]

Ditto.


Yep, as it's just another ssh session started the exact same way than 
the others ;)




Starting the ssh session with "ssh -vvv" might help to find the reason.



Yes, need to test that too ...

Re: Logging off an X session closes all ssh -X connections started previously from outside X

[zithro]

On 09 May 2023 17:47, Vincent Lefevre wrote:

Hi,

On 2023-05-04 21:07:17 +0200, zithro wrote:

Here is what happens chronologically :

1. I start various SSH connections to a host, some normal, some with X
forwarding, like that: "ssh user@host" and "ssh -X -n user@host GUI_APP"
(like firejail firefox, firejail thunderbird, etc). There's no user
connected under X yet, only the greeter is displayed.

2. using VNC or rdesktop, I then log on to X on the machine, do some stuff,
then hit "log off" from the desktop menu.
Immediately, ALL the previous SSH connections started in step 1 get closed,
hence all the shells and the GUI apps (firefox, etc) !


I have a similar setup (I also use lightdm and systemd) and do the
same kind of thing, but I haven't noticed any such issue.


Damn, now I wanna know the differences between our setups ^^
Do you also have several DE installed (but not running concurrently) ?


BTW, you should also try GNU Screen to see if you have the same issue
with it (this could help debugging).


Do you mean trying "ssh u@h screen" ?
Never tried screen with GUI apps, does that work ?


More precisely, I have 2 machines: one at home and one at my lab.
At home, I have an almost persistent X session (I log out only
when I need), and from it I ssh to my machine at my lab and keep
this ssh session open also almost persistently.

At my lab, I log in when I arrive and always log out when I leave,
but this never affects the ssh session I have at home.

Note also that I normally also have a GNU Screen running on both
machines (but not always). In any case, the X login/logout via
lightdm at my lab never affects ssh and GNU Screen.


Dammit (although happy for you ^^).


User lingering is disabled on both machines. And no changes to
logind.conf at my lab (KillUserProcesses is "no" by default).


As said in other posts, dunno how user lingering is configured on my setups.
Tried to grep "linger" in /etc (on server), only found references to 
SElinux.
logind.conf also has "#KillUserProcesses=no". Can it be declared 
elsewhere, ie. outside of /etc ?




I never use the -X ssh option, but I use X11 forwarding by default
(ForwardX11 yes), so I suppose that this is equivalent to -X.



No, AFAIK "ForwardX11 yes" is just to *allow* X11 forwarding, not to 
enable it on all ssh connections.
Ie. running "ssh u@h GUI_APP" without "-X" does not provide the DISPLAY 
var, and so fails running GUI_APP with "Unable to init server: Could not 
connect: Connection refused".

Do you use "UsePAM yes" in sshd_config (server-side option only) ?

Thanks for your input, it confirms it's a problem in my config, not in 
the software.

Re: Logging off an X session closes all ssh -X connections started previously from outside X

[Vincent Lefevre]

On 2023-05-05 15:04:27 +0200, zithro wrote:
> 
> journalctl after GUI LOGOFF
> 
[...]
> May 05 14:09:14 debzit sshd[14246]: Received disconnect from IP.IP.IP.IP
> port 38524:11: disconnected by user
 

"disconnected by user": Doesn't this mean that it is the client that
did the disconnection (for whatever reason)?

This is the message I observe when I disconnect the ssh session from
the client (with "~.") instead of terminating the program (e.g. shell)
on the server side.

[...]
> May 05 14:09:14 debzit sshd[14113]: Received disconnect from IP.IP.IP.IP
> port 38512:11: disconnected by user
[...]

Ditto.

Starting the ssh session with "ssh -vvv" might help to find the reason.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Was it a good idea to buy an Epson printer?

[Brad Rogers]

On Tue, 9 May 2023 15:04:19 +
Schwibinger Michael  wrote:

Hello Schwibinger,

>the printer is not printing.
>
>Is this a better explanation?

No.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
Hey there, Mr Average, you don't exist, you never did
Persons Unknown - Poison Girls


pgp0y8ohaE0ys.pgp
Description: OpenPGP digital signature

Re: Logging off an X session closes all ssh -X connections started previously from outside X

[Vincent Lefevre]

Hi,

On 2023-05-04 21:07:17 +0200, zithro wrote:
> Here is what happens chronologically :
> 
> 1. I start various SSH connections to a host, some normal, some with X
> forwarding, like that: "ssh user@host" and "ssh -X -n user@host GUI_APP"
> (like firejail firefox, firejail thunderbird, etc). There's no user
> connected under X yet, only the greeter is displayed.
> 
> 2. using VNC or rdesktop, I then log on to X on the machine, do some stuff,
> then hit "log off" from the desktop menu.
> Immediately, ALL the previous SSH connections started in step 1 get closed,
> hence all the shells and the GUI apps (firefox, etc) !

I have a similar setup (I also use lightdm and systemd) and do the
same kind of thing, but I haven't noticed any such issue.

BTW, you should also try GNU Screen to see if you have the same issue
with it (this could help debugging).

More precisely, I have 2 machines: one at home and one at my lab.
At home, I have an almost persistent X session (I log out only
when I need), and from it I ssh to my machine at my lab and keep
this ssh session open also almost persistently.

At my lab, I log in when I arrive and always log out when I leave,
but this never affects the ssh session I have at home.

Note also that I normally also have a GNU Screen running on both
machines (but not always). In any case, the X login/logout via
lightdm at my lab never affects ssh and GNU Screen.

User lingering is disabled on both machines. And no changes to
logind.conf at my lab (KillUserProcesses is "no" by default).

I never use the -X ssh option, but I use X11 forwarding by default
(ForwardX11 yes), so I suppose that this is equivalent to -X.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

AW: AW: AW: Was it a good idea to buy an Epson printer?

[Schwibinger Michael]

I don't know if you did anything wrong -- if your printer is an Epson with the
Ecotank feature, that may be exactly correct.  What did you expect?

Good afternoon
Thank You

The problem is
the printer is not printing.

Is this a better explanation?


I expext do use the working driver.

Regards
Sophie



Von: rhkra...@gmail.com 
Gesendet: Mittwoch, 3. Mai 2023 13:08
An: Schwibinger Michael 
Betreff: Re: AW: AW: Was it a good idea to buy an Epson printer?

Intentionally replying off list and top posting:

Are you a real (flesh and blood,  human) person or some kind of bot?

Are you making any progress in getting your problem(s) solved?

What is your native language?

I find your emails very hard to understand, and I'm quite sure others do as
well, so if you are a real person and really need nelp, you need to improve
your writing.

If there is a debian list in your native language, I suggest that you ask for
help there, in your native language.

If not, and you're not getting the help you need here but have nowhere else to
ask, you need to phrase your questions better.

If that is what you have to do, I suggest you start over, with a statement of
the current status of your problem and your overall objective.

My general understanding at this point is that you bought an Epson printer (of
a certain model number and it is either not working or not working the way you
expect.

Don't reply to me (I am not even close to being an expert in getting a printer
to run under Debian / Linux / cups), but start a new thread on the debian-user
list if that is what you need to do.

And, in future replies, pay attention to how other well formatted replies look
-- I've created an example below.

Good luck!

An example of replying (to your post).  First rule -- delete what is not
relevant to your reply -- note that I've delected the first two lines of your
reply (Good Morning, Thank You)

On Wednesday, May 03, 2023 05:31:02 AM Schwibinger Michael wrote:
> Print setting is saying:
>
> Epson Ecotank.
>
> What do I do wrong?

I don't know if you did anything wrong -- if your printer is an Epson with the
Ecotank feature, that may be exactly correct.  What did you expect?


Note that I deleted lots of old irrelevant stuff:





--
rhk

(sig revised 20230312 -- modified first paragraph, some other irrelevant
wordsmithing)

| No entity has permission to use this email to train an AI.

If you reply: snip, snip, and snip again; leave attributions; avoid HTML;
avoid top posting; and keep it "on list".  (Oxford comma (and semi-colon)
included at no charge.)  If you revise the topic, change the Subject: line.
If you change the topic, start a new thread.

Writing is often meant for others to read and understand (legal documents
excepted?) -- make it easier for your reader by various means, including
liberal use of whitespace (short paragraphs, separated by whitespace / blank
lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and
references.

If someone has already responded to a question, decide whether any response
you add will be helpful or not ...

A picture is worth a thousand words.  A video (or "audio"): not so much --
divide by 10 for each minute of video (or audio) or create a transcript and
edit it to 10% of the original.

A speaker who uses ahhs, ums, or such may have a real physical or mental
disability, or may be showing disrespect for his listeners by not properly
preparing in advance and thinking before speaking. (That speaker might have
been "trained" to do this by being interrupted often if he pauses.)  (Remember
Cicero who did not have enough time to write a short missive.)

A radio (or TV) station which broadcasts speakers with high pitched voices (or
very low pitched / gravelly voices) (which older people might not be able to
hear properly) disrespects its listeners.   Likewise if it broadcasts
extraneous or disturbing sounds (like gunfire or crying), or broadcasts
speakers using their native language (with or without an overdubbed
translation).

A person who writes a sig this long probably has issues and disrespects (and
offends) a large number of readers. ;-)
'

Re: repeat of previous question that has gone unansweredseveraltimes.

[Greg Wooledge]

On Tue, May 09, 2023 at 04:06:14AM -0400, gene heskett wrote:
> I think you have said resolv.conf Search directive doesn't work but
> nsswitch.conf was mentioned and there is a diff between this machine and one
> of the arms. So what do I put in nsswitch.conf to make cups search the hosts
> file first?

The bare minimum would be:

hosts:  files dns

Mine contains this:

hosts:  files mdns4_minimal [NOTFOUND=return] dns


The "search" directive in /etc/resolv.conf is followed by a space-separated
list of domain names.  Yours should say:

search coyote.den

Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/8/23 07:49, Brian wrote:

On Mon 08 May 2023 at 00:23:43 -0400, gene heskett wrote:

Brian, I found the secret sauce. Armed with the knowledge that Mike had 
moved, I found his new site, and found the answer in 5 minutes under the 
"printer sharing" link.  Something is broken when using a client.conf 
that contains the ServerName directive as it does not work from a 
hostname file lookup, but does work if the ServerName is the ipv4 
address:631


Possibly the result of my system not having a working dhcpd except the 
relay in the router to my isp's dns.


I think you have said resolv.conf Search directive doesn't work but 
nsswitch.conf was mentioned and there is a diff between this machine and 
one of the arms. So what do I put in nsswitch.conf to make cups search 
the hosts file first?


I think that, with some PEBKAC has been the problem all along.

Thanks Brian, take care & stay well.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: WiFi Not Working After System Reinstallation

[Marko Ranđelović]

On 5/8/23 17:02, debian-u...@howorth.org.uk wrote:

Marko Randjelovic  wrote:

Both systems are fully updated Bullseye on a laptop. I have two
access points, let's call them A and B. When I connect to A, DHCP
does not work. When I connect to B, DHCP works, laptop gets an IP
address and internet works without problems. On the other hand, my
mobile phone can successfully connect to both. Both APs have enabled
DHCP server and I made sure the IP ranges do not overlap.


what does

$ journalctl | grep dhcp

show when it should be connecting to A?



Hi,


Your command does not output anything important. Here's a wider selection:


May 09 11:09:06 rus wpa_supplicant[2309]: Successfully initialized 
wpa_supplicant
May 09 11:09:06 rus dhclient[2320]: Internet Systems Consortium DHCP 
Client 4.4.1
May 09 11:09:06 rus dhclient[2320]: Copyright 2004-2018 Internet Systems 
Consortium.

May 09 11:09:06 rus dhclient[2320]: All rights reserved.
May 09 11:09:06 rus dhclient[2320]: For info, please visit 
https://www.isc.org/software/dhcp/

May 09 11:09:06 rus dhclient[2320]:
May 09 11:09:06 rus dhclient[2320]: Listening on 
LPF/wlp3s0/yy:yy:yy:yy:yy:yy

May 09 11:09:06 rus dhclient[2320]: Sending on LPF/wlp3s0/yy:yy:yy:yy:yy:yy
May 09 11:09:06 rus dhclient[2320]: Sending on   Socket/fallback
May 09 11:09:06 rus dhclient[2320]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 8
May 09 11:09:07 rus wpa_supplicant[2310]: wlp3s0: 
CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
May 09 11:09:14 rus dhclient[2320]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 10
May 09 11:09:24 rus dhclient[2320]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 7
May 09 11:09:31 rus dhclient[2320]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 8
May 09 11:09:39 rus dhclient[2320]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 21
May 09 11:10:00 rus dhclient[2320]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 7

May 09 11:10:07 rus dhclient[2320]: No DHCPOFFERS received.
May 09 11:10:07 rus dhclient[2320]: No working leases in persistent 
database - sleeping.
May 09 11:10:07 rus avahi-autoipd(wlp3s0)[2335]: Found user 
'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 112).
May 09 11:10:07 rus avahi-autoipd(wlp3s0)[2335]: Successfully called 
chroot().
May 09 11:10:07 rus avahi-autoipd(wlp3s0)[2335]: Successfully dropped 
root privileges.
May 09 11:10:07 rus avahi-autoipd(wlp3s0)[2335]: Starting with address 
169.254.12.207
May 09 11:10:12 rus avahi-autoipd(wlp3s0)[2335]: Callout BIND, address 
169.254.12.207 on interface wlp3s0
May 09 11:10:16 rus avahi-autoipd(wlp3s0)[2335]: Successfully claimed IP 
address 169.254.12.207

Re: WiFi Not Working After System Reinstallation

[Marko Ranđelović]

On 5/8/23 18:17, Lee wrote:

On 5/8/23, Marko Randjelovic  wrote:

Both systems are fully updated Bullseye on a laptop. I have two access
points, let's call them A and B. When I connect to A, DHCP does not
work. When I connect to B, DHCP works, laptop gets an IP address and
internet works without problems. On the other hand, my mobile phone
can successfully connect to both. Both APs have enabled DHCP server
and I made sure the IP ranges do not overlap.

Does access point A have mac-address security enabled?
OpenWRT calls it mac address filter and gives you the choice of
  - disabledallows anyone to connect
  - allow listed only   list of mac addresses that are allowed to
connect to the AP
  - allow all except listed   why one would pick this instead of allow
listed only??



This option is disabled.



Does the AP have any logging that you could look at?  (dhcp)?diagnostics?

Regards
Lee


Hi Lee,


A has logging feature, B does not. I tried to connect several times to 
A, but nothing was logged. Then I changed to B, but at the first try 
also rising the interface failed and nothing was logged. Second attempt 
succeeded with the following logged:


Index  Time  Type  Level  Log Content
6    1st day 17:31:43    DHCP     NOTICE     DHCPS:Send NAK
5    1st day 17:31:43    DHCP     NOTICE     DHCPS:Wrong Server id or 
request an invalid ip
4    1st day 17:31:43    DHCP     NOTICE     DHCPS:Recv REQUEST from 
yy:yy:yy:yy:yy:yy
3    1st day 17:31:43    DHCP     NOTICE     DHCPS:Send OFFER with ip 
192.168.1.125
2    1st day 17:31:42    DHCP     NOTICE     DHCPS:Recv DISCOVER from 
yy:yy:yy:yy:yy:yy

1    1st day 17:22:17    OTHER     INFO     User clear system log.

Regards