On 1/22/24 10:23, Max Nikulin wrote:
On 22/01/2024 02:50, gene heskett wrote:
browser: chromium
It was also true here using the file:// prefix, trying look at the
html versions of the man pages in /usr/share/local/docs.
/usr/share may be unavailable inside snap or flatpack sandboxes, so it
On 22/01/2024 02:50, gene heskett wrote:
browser: chromium
It was also true here using the file:// prefix, trying look at the html
versions of the man pages in /usr/share/local/docs.
/usr/share may be unavailable inside snap or flatpack sandboxes, so it
is expected. Even /etc/hosts, /etc/re
Hello,
On Mon, Oct 02, 2023 at 04:45:25PM +0300, Petros Pap wrote:
> root@server:~# mysql -u root
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
> password: NO)
I believe that the Debian packaging of MariaDB is by default set up
to allow s
from Webmin and create databases from phpmyadmin
and i can login to mysql
root@server:~# mysql -u root
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
password: NO)
root@server:~# mysql -u root -p
Enter password:
Welcome to the MariaDB monitor. Commands en
Forwarded-Proto $scheme;
> proxy_set_header Connection "";
> allow 192.168.0.0/24;
> allow 127.0.0.1;
> deny all;
> }
>
> This changes it from a port number to a URL path, allows your
> local network and localhost to access it, and deni
}
This changes it from a port number to a URL path, allows your
local network and localhost to access it, and denies it to
others, should they come across the path.
Apache and other webservers can do similar things.
-dsr-
On Fri, 16 Apr 2021 17:26:36 +0300
Reco wrote:
> Hi.
>
> On Fri, Apr 16, 2021 at 09:45:13AM -0400, Celejar wrote:
> > I have various web (HTTP, not HTTPS) apps (e.g., pi-hole, Home
> > Assistant) running on localhost (either actually on localhost, or on
> > an
Hi.
On Fri, Apr 16, 2021 at 09:45:13AM -0400, Celejar wrote:
> I have various web (HTTP, not HTTPS) apps (e.g., pi-hole, Home
> Assistant) running on localhost (either actually on localhost, or on
> another host but accessed via 'localhost' via ssh port forwarding
&g
Hi,
I have various web (HTTP, not HTTPS) apps (e.g., pi-hole, Home
Assistant) running on localhost (either actually on localhost, or on
another host but accessed via 'localhost' via ssh port forwarding
(LocalForward) that require cookies to function (even before logging
in). When Fire
On Sun, 2 Feb 2020 19:40:24 +
"Russell L. Harris" wrote:
> I am attempting to configure Apache2 (in Debian 10) as a local server
> for web site development.
>
> I see on the "Apache2 Debian Default Page" the Debian logo; the
> browser reports the image loc
ver
> for web site development.
>
> I see on the "Apache2 Debian Default Page" the Debian logo; the
> browser reports the image location as:
>
> http://localhost/icons/openlogo-75.png
>
> But when I use midnight commander to snoop around \var and other
> dir
I am attempting to configure Apache2 (in Debian 10) as a local server
for web site development.
I see on the "Apache2 Debian Default Page" the Debian logo; the
browser reports the image location as:
http://localhost/icons/openlogo-75.png
But when I use midnight commander to sn
On Tue 03 Dec 2019 at 16:13:19 -0500, Gene Heskett wrote:
> On Tuesday 03 December 2019 14:23:34 Brian wrote:
>
> > On Tue 03 Dec 2019 at 13:17:21 -0500, Gene Heskett wrote:
> > > On Tuesday 03 December 2019 11:37:59 Pierre Frenkiel wrote:
> > > > On Sat, 30 Nov 2019, Roberto C. Sanchez wrote:
>
On Tue, 3 Dec 2019, Brian wrote:
I wish I could have confidence in your interpretation of what you see.
The pop-up has two blank fields. Why you maintain the default user is
"root" and it needs to be changed is beyond me.
Yes, I maintain it...
I don't have 2 blank fields,
but 2 fields co
On Tuesday 03 December 2019 15:58:45 Pierre Frenkiel wrote:
> On Tue, 3 Dec 2019, Gene Heskett wrote:
> > When it pops up the requester, did you change it from the default
> > root to your name you've added to lpadmin and your passwd? That
> > works here.
>
>yes, I do that, and my password is
On Tuesday 03 December 2019 14:23:34 Brian wrote:
> On Tue 03 Dec 2019 at 13:17:21 -0500, Gene Heskett wrote:
> > On Tuesday 03 December 2019 11:37:59 Pierre Frenkiel wrote:
> > > On Sat, 30 Nov 2019, Roberto C. Sanchez wrote:
> > > It has a been a while, but my recollection is that you add a
On Tue, 3 Dec 2019, Gene Heskett wrote:
When it pops up the requester, did you change it from the default root to
your name you've added to lpadmin and your passwd? That works here.
yes, I do that, and my password is refused, as well as the root one
On Tue 03 Dec 2019 at 13:17:21 -0500, Gene Heskett wrote:
> On Tuesday 03 December 2019 11:37:59 Pierre Frenkiel wrote:
>
> > On Sat, 30 Nov 2019, Roberto C. Sanchez wrote:
> > It has a been a while, but my recollection is that you add a
> > normal user to the lpadmin group. Then by authenti
On Tuesday 03 December 2019 11:37:59 Pierre Frenkiel wrote:
> On Sat, 30 Nov 2019, Roberto C. Sanchez wrote:
> It has a been a while, but my recollection is that you add a
> normal user to the lpadmin group. Then by authenticating as that user
> you can administer through the web interface.
>
On Tue 03 Dec 2019 at 17:37:59 +0100, Pierre Frenkiel wrote:
> On Sat, 30 Nov 2019, Roberto C. Sanchez wrote:
>It has a been a while, but my recollection is that you add a normal user
>to the lpadmin group. Then by authenticating as that user you can
>administer through the web interf
On Sat, 30 Nov 2019, Roberto C. Sanchez wrote:
It has a been a while, but my recollection is that you add a normal user
to the lpadmin group. Then by authenticating as that user you can
administer through the web interface.
hi Roberto,
alas, I already did that, without success.
n
On Sat, 30 Nov 2019, Roberto C. Sanchez wrote:
It has a been a while, but my recollection is that you add a normal user
to the lpadmin group. Then by authenticating as that user you can
administer through the web interface.
hi Roberto,
alas, I already did that, without success.
b
On Sat, Nov 30, 2019 at 06:01:18PM +0100, Pierre Frenkiel wrote:
> hi,
> I tried to add a printer using the localhost:631 cups interface,
> but the root password was refused, as well as mine
> To be sure that the provided password was valid, I reset it with the
> passwd command
hi,
I tried to add a printer using the localhost:631 cups interface,
but the root password was refused, as well as mine
To be sure that the provided password was valid, I reset it with the
passwd command.
can anybody explain that?
best regards,
--
Pierre Frenkiel
My home linux/Debian/buster machine has suddenly made samba 'shares'
invisible to my Win7 virtual machine (running under kvm/qemu).
Using smbclient I get two different responses:
smbclient -L localhost
only gives the error-message response:
Unable to initialize messagi
000=gene
>
> What is this telling me?
That your X server isn't listening to TCP. Which is normal in this
century. That's why we have DISPLAY=:0 instead of DISPLAY=localhost:0.
(Or, your X server isn't running at all. But since you seemed to expect
to see something, I'm g
without -nolisten tcp flag. Unfortunately:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
localhost being added to access control list
xterm: Xt error: Can't open display: localhost:0.0
Any suggestions??
Did you check port 6000?
root@pc6:~# netstat -anp | grep 6000
tcp 0 0 0.0.0.0
:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
localhost being added to access control list
xterm: Xt error: Can't open display: localhost:0.0
Any suggestions??
Did you check port 6000?
root@pc6:~# netstat -anp | grep 6000
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 2684/Xorg
tcp6
On 9/23/18 4:00 PM, Gene Heskett wrote:
> On Sunday 23 September 2018 06:30:01 Étienne Mollier wrote:
> > Maybe try:
> >
> > xhost +LOCAL:
> > DISPLAY=localhost:0.0 xterm
>
> On which machine? The target of the ssh login, or this one
> with the comfy
On Sunday 23 September 2018 10:36:01 Rob van der Putten wrote:
Humm, my puzzle for X11Forwarding has even more pieces.
copy/pasted from the konsole logged into the rock64, running stretch
gene@rock64:~$ sudo netstat -anp|grep 6000
[sudo] password for gene:
gene@rock64:~$ sudo netstat -anp|grep 6
On Sunday 23 September 2018 09:20:34 Étienne Mollier wrote:
> On 9/23/18 5:06 PM, Grzesiek Sójka wrote:
> > $ xhost +LOCAL: ; DISPLAY=localhost:0.0 xterm
> > non-network local connections being added to access control list
> > xterm: Xt error: Can't open display: localho
Hi there
On 23/09/2018 13:48, Grzegorz Sójka wrote:
I need to allow remote applications to connect to xorg. Since I log in
using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is
running without -nolisten tcp flag. Unfortunately:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
Xorg
> > is running without -nolisten tcp flag. Unfortunately:
> >
> > $ xhost +localhost; DISPLAY=localhost:0.0 xterm
> > localhost being added to access control list
> > xterm: Xt error: Can't open display: localhost:0.0
> >
> > Any suggestions??
>
>
On 9/23/18 5:14 PM, Grzesiek Sójka wrote:
> On 9/23/18 1:06 PM, Étienne Mollier wrote:
> > ssh -YC user@remotehost
>
> I do not need encryption since all machines are in the same
> network segment. So I prefer not to use ssh.
In that case, perhaps you should simply test with remote
clients; I
On 9/23/18 5:06 PM, Grzesiek Sójka wrote:
> $ xhost +LOCAL: ; DISPLAY=localhost:0.0 xterm
> non-network local connections being added to access control list
> xterm: Xt error: Can't open display: localhost:0.0
Whoops, however the DISPLAY=localhost:0.0 was a typo of mine.
DISPLAY=:0
On 9/23/18 1:06 PM, Étienne Mollier wrote:
On 9/23/18 2:59 PM, The Wanderer wrote:
On 2018-09-23 at 10:24, Grzesiek Sójka wrote:
On 9/23/18 10:30 AM, Étienne Mollier wrote:
Maybe try:
xhost +LOCAL:
DISPLAY=localhost:0.0 xterm
It does not work:
# xhost +LOCAL; DISPLAY
Étienne Mollier (2018-09-23):
> or removing “-nolisten” to Xorg parameters:
Finally somebody in this thread who payed attention in the last fifteen
years...
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
On 9/23/18 2:59 PM, The Wanderer wrote:
> On 2018-09-23 at 10:24, Grzesiek Sójka wrote:
> > On 9/23/18 10:30 AM, Étienne Mollier wrote:
> > > Maybe try:
> > >
> > > xhost +LOCAL:
> > > DISPLAY=localhost:0.0 xterm
> >
> > It does not
/etc/lxdm/lxdm.conf.
Thus Xorg is running without -nolisten tcp flag. Unfortunately:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
localhost being added to access control list
xterm: Xt error: Can't open display: localhost:0.0
Any suggestions??
Maybe try:
xhost +LOCAL:
DI
using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf.
>>> Thus Xorg is running without -nolisten tcp flag. Unfortunately:
>>>
>>> $ xhost +localhost; DISPLAY=localhost:0.0 xterm
>>> localhost being added to access control list
>>> xterm: Xt error: Can
tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running
without -nolisten tcp flag. Unfortunately:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
localhost being added to access control list
xterm: Xt error: Can't open display: localhost:0.0
Any suggestions??
Maybe try:
xhost +
in
>>> using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running
>>> without -nolisten tcp flag. Unfortunately:
>>>
>>> $ xhost +localhost; DISPLAY=localhost:0.0 xterm
>>> localhost being added to access control list
>
:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
localhost being added to access control list
xterm: Xt error: Can't open display: localhost:0.0
Any suggestions??
Maybe try:
xhost +LOCAL:
DISPLAY=localhost:0.0 xterm
It does not work:
# xhost +LOCAL; DISPLAY=localhost:0.0
On 9/23/18 1:48 PM, Grzegorz Sójka wrote:
> Hi there,
>
> I need to allow remote applications to connect to xorg. Since I log in using
> lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without
> -nolisten tcp flag. Unfortunately:
>
> $ xhost +localho
Hi there,
I need to allow remote applications to connect to xorg. Since I log in
using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is
running without -nolisten tcp flag. Unfortunately:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
localhost being added to access control list
Debian Stretch, roundcube 1.2.3+dfsg.1-4+deb9u1
Roundcube has created new user_id, with mail_host as FQDN and not
localhost as previously. last_login with user where mail_host is
localhost was 21. March, today login is mail_host FQDN.
Can I fix this in the database so address books etc of
On Sun, 26 Nov 2017 19:11:23 +0100
Ulf Volmer wrote:
> On 26.11.2017 18:48, Rainer Dorsch wrote:
>
> > root@scw:/etc/logrotate.d# cat /etc/mysql/debian.cnf
> > # Automatically generated for Debian scripts. DO NOT TOUCH!
> > [client]
> > host = localhost
&g
On 26.11.2017 18:48, Rainer Dorsch wrote:
> root@scw:/etc/logrotate.d# cat /etc/mysql/debian.cnf
> # Automatically generated for Debian scripts. DO NOT TOUCH!
> [client]
> host = localhost
> user = root
> password =
> socket = /var/run/mysqld/mysqld.sock
>
On Sonntag, 26. November 2017 17:01:23 CET Joe wrote:
> On Sun, 26 Nov 2017 16:35:24 +0100
>
> Ulf Volmer wrote:
> > On 26.11.2017 15:57, Rainer Dorsch wrote:
> > > mysqladmin: connect to server at 'localhost' failed
> > > error: 'Access de
On Sun, 26 Nov 2017 16:35:24 +0100
Ulf Volmer wrote:
> On 26.11.2017 15:57, Rainer Dorsch wrote:
>
> > mysqladmin: connect to server at 'localhost' failed
> > error: 'Access denied for user 'root'@'localhost' (using password:
> > NO)&#
On 26.11.2017 15:57, Rainer Dorsch wrote:
> mysqladmin: connect to server at 'localhost' failed
> error: 'Access denied for user 'root'@'localhost' (using password: NO)'
> error: error running shared postrotate script for '/var/log/mysql/mys
Hello,
I get (daily :-) mails from my cron.daily with the content
Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /
etc/cron.daily )
/etc/cron.daily/logrotate:
mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root&
Greetings;
I found the problem, something had replaced the index.html, which was a
link to the front-page.html of my web site with the default apache
index.html.
Restored that by rm'ing the renamed copy of it, then cp'd the ~ version
back to the real one, voila! Web page functions normally.
I
is lite@lite*
> > *and hostname gives *
> > *lite@lite:/opt/lampp$ hostname*
> > *lite.umbb.dz <http://lite.umbb.dz>*
> >
> >
> > *bin/mysql*
> >
> > *ERROR 1045 (28000): Acces s denied for user
> > 'lite'@'localhost
e.umbb.dz <http://lite.umbb.dz>*
>
>
> *bin/mysql*
>
> *ERROR 1045 (28000): Acces s denied for user 'lite'@'localhost' (using
> password: YES)*
>
> *Here it tries to connect as 'lite'@'localhost', I am
> not 'lite'@&
>
>
> *bin/mysql*
>
> *ERROR 1045 (28000): Acces s denied for user 'lite'@'localhost' (using
> password: YES)*
>
> *Here it tries to connect as 'lite'@'localhost', I am
> not 'lite'@'localhost', but lite@lite*
*Thanks for reply and links*
*But I am sure, the problem is in mysql.*
*Look at this: *
*my count is lite@lite*
*and hostname gives *
*lite@lite:/opt/lampp$ hostname*
*lite.umbb.dz <http://lite.umbb.dz>*
*bin/mysql*
*ERROR 1045 (28000): Acces s denied for user 'lite'@&#
Abdelkader Belahcene wrote:
> thanks a lot for any idea
This has nothing to do with mysql or debian, but with wordpress. Please
refer the manual or subscribe to the wordpress list.
Perhaps someone else here may help you, but it would be OT IMO.
regards
On 04/11/2017 07:45 AM, Abdelkader Belahcene wrote:
Thanks for reply;
I give more details.
I install wordpress on my machine, it works fine on local, I mean i if
write in the browser localhost/wordpress, it 's OK.
I can use myIP/worpress on a remote machine to connect my server, It
Thanks for reply;
I give more details.
I install wordpress on my machine, it works fine on local, I mean i if
write in the browser localhost/wordpress, it 's OK.
I can use myIP/worpress on a remote machine to connect my server, It seems
working fine, I get the main page,
BUT, CSS files ar
On Mon, 10 Apr 2017 07:51:56 +0100
Abdelkader Belahcene wrote:
> My machine has another name than localhost like lite.bela.umbb,
> when I install mysql, it always takes the the localhost as the name
> of the machine. this yields in a problem for me, when I use for
> example wor
My machine has another name than localhost like lite.bela.umbb,
when I install mysql, it always takes the the localhost as the name of the
machine. this yields in a problem for me, when I use for example wordpress
and I want a remote connection. because the localhost stored in DB is
irrelevant
Yes, this indeed was the problem!
For some reason the mail was being sent to "user" even though I had no user
named that.
Thanks a bunch! I have had this problem for quite a while and never could
figure out how to fix it.
On Thu, Mar 2, 2017 at 5:34 AM, Bonno Bloksma wrote:
> Hi,
>
> >[]
Hi,
>[]
> so, if I want to use mail.example.com as my fqdn, and the old fqdn was
> something.else and r...@something.else was redirecting mail to
> m...@something.else ... then what do I need to change in Exim to make this
> happen?
Is it maybe the aliases setting?
Probably you edited the
Have you tried sudo dpkg-reconfigure exim4-config
Which Settings you have there?
Am 01.03.2017 um 21:40 schrieb Jiangsu Kumquat:
> I changed my server name and fqdn and now the mail to root@localhost is
> bouncing.
>
> I went into every file that had the old name and changed it to
I changed my server name and fqdn and now the mail to root@localhost is
bouncing.
I went into every file that had the old name and changed it to the new name
but it still doesn't work. I did "grep -r something.else /etc" to find all
the files.
so, if I want to use mail.example
I changed my server name and fqdn and now the mail to root@localhost is
bouncing.
I went into every file that had the old name and changed it to the new name
but it still doesn't work. I did "grep -r something.else /etc" to find all
the files.
so, if I want to use mail.example
*proof* that it is in control
of said private part, which the host account (test) can check).
The ssh-agent is just in charge of keeping unlocked private keys around
so that you only have to unlock them with your passphrase once per
session.
> My great mistake was to think that localhost, alt
to restart ssh.
By the way, when I logged in via ssh (to *test*) now I was greeted by
"Last login [time of my connection attempt]from localhost". So, I
understand that I had logged into *test* via su - test and then had
connected to *test* (from *test*) via localhost using ssh! Is this
interpretation correct?
Thanks to both of you again.
Stephan
ser --disabled-password
>> What do I want to do?
>> I'd like to login to this account "test" from my normal user account by
>> ssh via pubkey authentication. My (normal) user account has its keys
>> generated and properly deposited on localhost. I logged into
Stephan Beck:
> Thanks, Greg. I trimmed your message just to let you know that it does
> not work.
To be clear: after having found my solution I did your test (only the
test reproduced at the end of your message) and my solution does not work.
Thanks
Stephan
Thanks, Greg. I trimmed your message just to let you know that it does
not work.
Greg Wooledge:
> On Fri, Sep 23, 2016 at 12:31:00PM +, Stephan Beck wrote:
> As user stephan, to test that it works:
>
> stephan@hostname:~$ ssh test@localhost id
>
> If your username isn&#
Hi,
Stephan Beck:
> Hi
>
> Stephan Beck:
>> Hi
>>
>> to...@tuxteam.de:
>>> On Thu, Sep 22, 2016 at 03:35:00PM +, Stephan Beck wrote:
>>>
>>>
>
>> How do I get this public key onto localhost?
>
> No need to reply, I&#
d a solution and other chimed in with sage advice.
> >
>
> Well, I have another one :-), a question, not a solution yet.
>
>
> I have created a new user account with
> adduser --disabled-password
> What do I want to do?
> I'd like to login to this account &quo
Hi
Stephan Beck:
> Hi
>
> to...@tuxteam.de:
>> On Thu, Sep 22, 2016 at 03:35:00PM +, Stephan Beck wrote:
>>
>>
> How do I get this public key onto localhost?
No need to reply, I'll send the answer to document my solution within
minutes.
Stephan
(normal) user account has its keys
> generated and properly deposited on localhost. I logged into the account
> "test" via su - test, creating a keypair. Fine.
Typically, you want to create the keypair as the user on the machine which
will be the client. This way the private key
do?
I'd like to login to this account "test" from my normal user account by
ssh via pubkey authentication. My (normal) user account has its keys
generated and properly deposited on localhost. I logged into the account
"test" via su - test, creating a keypair. Fine.
How do
_echo_ignore_broadcasts = 0
>
> equals to
>
> 'do not ignore icmp echo broadcasts'.
Karl, Reco,
That did it. "ping localhost" now works. For the record, here are the results
of systemctl --system:
* Applying /etc/sysctl.conf ...
net.ipv4.icmp_echo_ignore_all =
On 26/08/14, Karl E. Jorgensen (k...@jorgensen.org.uk) wrote:
> > sysctl --system
> > * Applying /etc/sysctl.d/99-sysctl.conf ...
> > net.ipv4.icmp_echo_ignore_all = 0
> > net.ipv4.icmp_echo_ignore_broadcasts = 0
>
> These caught my eye: Ignore all ICMP ? That would stop ping
> (a.k.a. ICMP echo)
Hi.
On Wed, 27 Aug 2014 00:27:24 +0100
Brian wrote:
> On Wed 27 Aug 2014 at 02:01:14 +0400, Reco wrote:
>
> > And, by the way, ipv6 has nothing to do with this problem, although the
> > output of ipv6 routing tables looks abnormal to me too.
>
> You could very well be correct. But, should the
Hi.
On Tue, 26 Aug 2014 23:12:05 +0100
"Karl E. Jorgensen" wrote:
> > > 4) sysctl --system
> > sysctl --system
> > * Applying /etc/sysctl.d/99-sysctl.conf ...
> > net.ipv4.icmp_echo_ignore_all = 0
> > net.ipv4.icmp_echo_ignore_broadcasts = 0
>
> These caught my eye: Ignore all ICMP ? That woul
On Wed 27 Aug 2014 at 02:01:14 +0400, Reco wrote:
> And, by the way, ipv6 has nothing to do with this problem, although the
> output of ipv6 routing tables looks abnormal to me too.
You could very well be correct. But, should the OP decide to continue
without ipv6, he may find systemd to be unfor
Hi
On Tue, Aug 26, 2014 at 03:50:25PM -0400, John wrote:
> On 25/08/14, Reco (recovery...@gmail.com) wrote:
>
> > Date: Mon, 25 Aug 2014 22:13:41 +0400
> > From: Reco
> > To: debian-user@lists.debian.org
> > Subject: Re: No localhost - I'm stumped
> > X-
Hi.
On Tue, 26 Aug 2014 15:50:25 -0400
John wrote:
> -A POSTROUTING -j MASQUERADE
This is the source of your trouble. You're redirecting packets intended
to go via loopback to nat with this rule, which is obviously wrong.
I suggest you to try this rule instead:
iptables -t nat -A POSTROUTING
On Tue 26 Aug 2014 at 15:50:25 -0400, John wrote:
> On 25/08/14, Reco (recovery...@gmail.com) wrote:
> >
> > 3) strace ping6 -c2 ip6-localhost
>
> I've left this one out, since I recompiled the kernel without ip6
> support. "ping6 localhost" had produced
On 25/08/14, Reco (recovery...@gmail.com) wrote:
> Date: Mon, 25 Aug 2014 22:13:41 +0400
> From: Reco
> To: debian-user@lists.debian.org
> Subject: Re: No localhost - I'm stumped
> X-Spam-Status: No, score=-11.2 required=4.0 tests=DKIM_SIGNED,DKIM_VALID,
> DKIM
to a fix.
Probably won't do you any good, since you have a basic kernel facility
(ip routing) in a broken state.
> Still, it would be nice to _understand_ ...
Can you please post the output of (run it all as root):
1) iptables-save
2) strace ping -c2 localhost
3) strace ping6 -c2 ip6-lo
welcome.
> >
> > Some things to try here:
> >
> >
http://unix.stackexchange.com/questions/26487/can-ping-any-hosts-but-localhost-whats-wrong
>
> Thanks for the help and the link; it's useful. But alas, nothing from it
s=
> olved my problem. I think next I'll try reinstall
On 24/08/14, Curt (cu...@free.fr) wrote:
> On 2014-08-24, John wrote:
> >
> > I've tried everything I can think of, and hints regarding what to try next
> > would be higholy welcome.
>
> Some things to try here:
>
> http://unix.stackexchange.com/questions/
On Sun 24 Aug 2014 at 13:43:25 -0400, John wrote:
> For some days now, localhost has not responded to anything. I've tried
> everything, and am stumped. Here are a few indications:
>
> netstat -an |grep 631
> tcp0 0 127.0.0.1:631 0.0.0.0:*
On 2014-08-24, John wrote:
>
>
> I've tried everything I can think of, and hints regarding what to try next
> would be higholy welcome.
>
Some things to try here:
http://unix.stackexchange.com/questions/26487/can-ping-any-hosts-but-localhost-whats-wrong
--
To UNSUBSCR
For some days now, localhost has not responded to anything. I've tried
everything, and am stumped. Here are a few indications:
ifconfig shows lo is working:
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
Brian wrote:
> Bob Proulx wrote:
> > Brian wrote:
> > > or, if the domain name is left blank,
> > > 127.0.1.1 foo
> > > would be seen.
> >
> > Doesn't it create an entry like this? I will need to test it in order
> > to see what it creates in that case.
> > 127.0.1.1 foo.localdoma
On Fri 13 Jun 2014 at 15:28:48 -0600, Bob Proulx wrote:
> Brian wrote:
> > Bob Proulx wrote:
> > > Brian wrote:
> > > > True. What do think about the lack of '127.0.1.1 localhost' in
>
> It is the "127.0.1.1 localhost" to which I was
Brian wrote:
> Bob Proulx wrote:
> > Brian wrote:
> > > True. What do think about the lack of '127.0.1.1 localhost' in
It is the "127.0.1.1 localhost" to which I was disagreeing. That
would be unusual. It is still the loopback device so off the top of
m
On Thu 12 Jun 2014 at 16:23:37 -0600, Bob Proulx wrote:
> Brian wrote:
> > Tom H wrote:
> > > Brian wrote:
> > > > Teresa e Junior wrote:
> > > >> $ cat /etc/hostname
> > > >> localhost
> > ...
> > True. What do think about
Brian wrote:
> Tom H wrote:
> > Brian wrote:
> > > Teresa e Junior wrote:
> > >> $ cat /etc/hostname
> > >> localhost
> ...
> True. What do think about the lack of '127.0.1.1 localhost' in
> etc/hosts? Squeeze and Wheezy installs w
configs as follows (assuming your machine's name is
'mpdserver'):
/etc/hostname:
mpdserver
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 mpdserver
(you can also use the lan IP here if it is fixed and enabling the IPv6
entries could also help)
mpd.conf:
bind_to_address "
sure
you adjust your configs as follows (assuming your machine's name is
'mpdserver'):
/etc/hostname:
mpdserver
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 mpdserver
(you can also use the lan IP here if it is fixed and enabling the IPv6
entries could also help)
mpd.conf:
bind_to_addr
I believe it's got something to do with NetworkManager, because mpc
started working as soon as I run:
$ sudo service network-manager stop
And then I run this, and while trying to connect, or later if connecting
fails, mpc won't work again:
$ sudo service network-manager start
The version of N
1 - 100 of 593 matches
Mail list logo
