[opensuse] Leap 15. Privoxy fails to start but here, unlike TW, does not seem to segfault?
I am puzzled. sudo systemctl status privoxy.service ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-11-23 10:57:00 CET; 28min ago Process: 6246 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/ privoxy.pid --user privoxy /etc/config (code=exited, sta> Process: 6245 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/ libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exi> Process: 6244 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc> nov 23 10:56:58 roadrunner.suse systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Control process exited, code=exited status=1 nov 23 10:57:00 roadrunner.suse systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Unit entered failed state. nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Failed with result 'exit-code'. lines 1-12/12 (END) For some reasons it does not start. I tried with sudo journalctl -xe but no errors appear of privoxy. How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile. Network is via networkmanager and wireless. Privoxy should be started at boot. Thank you. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile.
I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile. I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it. That is weird. Privoxy should write to var/log/privoxy when nothing set, and
In data venerdì 23 novembre 2018 11:51:50 CET, Carlos E. R. ha scritto: this is mandatory. But in /var/log there is not log. So probably diverted to journalctl but journalctl does not report errors.... sudo dmesg clean, just a lot of martians from multicast... nothing else. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data venerdì 23 novembre 2018 11:51:50 CET, Carlos E. R. ha scritto:
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile. I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it.
That is weird. Privoxy should write to var/log/privoxy when nothing set, and this is mandatory. But in /var/log there is not log. So probably diverted to journalctl but journalctl does not report errors.... sudo dmesg clean, just a lot of martians from multicast... nothing else.
Maybe it doesn't get far enough to be able to start logging. Try starting it from the command line, non-forking and/or in debug mode, with the appropriate arguments. -- Per Jessen, Zürich (3.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 23 novembre 2018 12:38:16 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 11:51:50 CET, Carlos E. R. ha
scritto:
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile.
I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it.
That is weird. Privoxy should write to var/log/privoxy when nothing set, and this is mandatory. But in /var/log there is not log. So probably diverted to journalctl but journalctl does not report errors.... sudo dmesg clean, just a lot of martians from multicast... nothing else.
Maybe it doesn't get far enough to be able to start logging. Try starting it from the command line, non-forking and/or in debug mode, with the appropriate arguments. roadrunner:~ # sudo privoxy --no-daemon 2018-11-23 15:30:07.480 7fea5458ff00 Info: Privoxy version 3.0.26 2018-11-23 15:30:07.480 7fea5458ff00 Info: Program name: privoxy 2018-11-23 15:30:07.480 7fea5458ff00 Fatal error: can't check configuration file '/root/config': No such file or directory
With sudo this is worse sudo privoxy --no-daemon 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Privoxy version 3.0.26 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Program name: privoxy 2018-11-23 15:29:16.102 7fb7a4624f00 Fatal error: can't check configuration file '/home/entropia/config': No such file or directory So I tried: sudo systemctl status privoxy.service ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-11-23 10:57:00 CET; 4h 30min ago nov 23 10:56:58 roadrunner.suse systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Control process exited, code=exited status=1 nov 23 10:57:00 roadrunner.suse systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Unit entered failed state. nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Failed with result 'exit-code'. All this writes nothing, reports nothing, logs nothing. The debug options are set in the config file. Which are: debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. debug 1024 # Actions that are applied to all sites and maybe overruled later on. debug 4096 # Startup banner and warnings debug 8192 # Non-fatal errors I also created the directory /var/log/privoxy. Nothing. As mute as a goldfish. WTF! What am I doing wrong? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [11-23-18 09:36]:
In data venerdì 23 novembre 2018 12:38:16 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 11:51:50 CET, Carlos E. R. ha
scritto:
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile.
I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it.
That is weird. Privoxy should write to var/log/privoxy when nothing set, and this is mandatory. But in /var/log there is not log. So probably diverted to journalctl but journalctl does not report errors.... sudo dmesg clean, just a lot of martians from multicast... nothing else.
Maybe it doesn't get far enough to be able to start logging. Try starting it from the command line, non-forking and/or in debug mode, with the appropriate arguments. roadrunner:~ # sudo privoxy --no-daemon 2018-11-23 15:30:07.480 7fea5458ff00 Info: Privoxy version 3.0.26 2018-11-23 15:30:07.480 7fea5458ff00 Info: Program name: privoxy 2018-11-23 15:30:07.480 7fea5458ff00 Fatal error: can't check configuration file '/root/config': No such file or directory
With sudo this is worse
sudo privoxy --no-daemon 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Privoxy version 3.0.26 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Program name: privoxy 2018-11-23 15:29:16.102 7fb7a4624f00 Fatal error: can't check configuration file '/home/entropia/config': No such file or directory
So I tried:
sudo systemctl status privoxy.service ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-11-23 10:57:00 CET; 4h 30min ago
nov 23 10:56:58 roadrunner.suse systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Control process exited, code=exited status=1 nov 23 10:57:00 roadrunner.suse systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Unit entered failed state. nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Failed with result 'exit-code'.
All this writes nothing, reports nothing, logs nothing. The debug options are set in the config file. Which are:
debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. debug 1024 # Actions that are applied to all sites and maybe overruled later on. debug 4096 # Startup banner and warnings debug 8192 # Non-fatal errors
I also created the directory /var/log/privoxy. Nothing. As mute as a goldfish. WTF! What am I doing wrong?
what version of privoxy and what repo. there was an issue with 3.0.26-1 on tw from OSS, which was corrected by 3.0.26-3 (iirc) from factory server. I don't have leap 15 to check. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [11-23-18 09:36]:
In data venerdì 23 novembre 2018 12:38:16 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 11:51:50 CET, Carlos E. R. ha
scritto:
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile.
I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it.
That is weird. Privoxy should write to var/log/privoxy when nothing set, and this is mandatory. But in /var/log there is not log. So probably diverted to journalctl but journalctl does not report errors.... sudo dmesg clean, just a lot of martians from multicast... nothing else.
Maybe it doesn't get far enough to be able to start logging. Try starting it from the command line, non-forking and/or in debug mode, with the appropriate arguments.
roadrunner:~ # sudo privoxy --no-daemon 2018-11-23 15:30:07.480 7fea5458ff00 Info: Privoxy version 3.0.26 2018-11-23 15:30:07.480 7fea5458ff00 Info: Program name: privoxy 2018-11-23 15:30:07.480 7fea5458ff00 Fatal error: can't check configuration file '/root/config': No such file or directory
With sudo this is worse
sudo privoxy --no-daemon 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Privoxy version 3.0.26 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Program name: privoxy 2018-11-23 15:29:16.102 7fb7a4624f00 Fatal error: can't check configuration file '/home/entropia/config': No such file or directory
So I tried:
sudo systemctl status privoxy.service ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities
Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-11-23 10:57:00 CET; 4h
30min ago
nov 23 10:56:58 roadrunner.suse systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Control process exited, code=exited status=1 nov 23 10:57:00 roadrunner.suse systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Unit entered failed state. nov 23 10:57:00 roadrunner.suse systemd[1]: privoxy.service: Failed with result 'exit-code'.
All this writes nothing, reports nothing, logs nothing. The debug options are set in the config file. Which are:
debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. debug 1024 # Actions that are applied to all sites and maybe overruled later on. debug 4096 # Startup banner and warnings debug 8192 # Non-fatal errors
I also created the directory /var/log/privoxy. Nothing. As mute as a goldfish. WTF! What am I doing wrong?
what version of privoxy and what repo. there was an issue with 3.0.26-1 on tw from OSS, which was corrected by 3.0.26-3 (iirc) from factory server. I don't have leap 15 to check. It is the standard repo of Leap and a very standard installation:
In data venerdì 23 novembre 2018 15:48:22 CET, Patrick Shanahan ha scritto: privoxy --version Privoxy version 3.0.26 (https://www.privoxy.org/) So I will have to report this as well? I did for TW, but this requires a new bug report for leap I think. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data venerdì 23 novembre 2018 12:38:16 CET, Per Jessen ha scritto:
Maybe it doesn't get far enough to be able to start logging. Try starting it from the command line, non-forking and/or in debug mode, with the appropriate arguments.
roadrunner:~ # sudo privoxy --no-daemon 2018-11-23 15:30:07.480 7fea5458ff00 Info: Privoxy version 3.0.26 2018-11-23 15:30:07.480 7fea5458ff00 Info: Program name: privoxy 2018-11-23 15:30:07.480 7fea5458ff00 Fatal error: can't check configuration file '/root/config': No such file or directory
This look like it is defaulting to a config of "~/config" - you need to run it like this: privoxy --no-daemon <configfile>
With sudo this is worse
sudo privoxy --no-daemon 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Privoxy version 3.0.26 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Program name: privoxy 2018-11-23 15:29:16.102 7fb7a4624f00 Fatal error: can't check configuration file '/home/entropia/config': No such file or directory
It is the same problem, it defaults to '~/config' when you don't specify a config file. Please show us output from "systemctl cat privoxy". That'll tell us how it is meant to be started. Specifically, with which config file. -- Per Jessen, Zürich (3.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 23 novembre 2018 16:31:31 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 12:38:16 CET, Per Jessen ha scritto:
Maybe it doesn't get far enough to be able to start logging. Try starting it from the command line, non-forking and/or in debug mode, with the appropriate arguments.
roadrunner:~ # sudo privoxy --no-daemon 2018-11-23 15:30:07.480 7fea5458ff00 Info: Privoxy version 3.0.26 2018-11-23 15:30:07.480 7fea5458ff00 Info: Program name: privoxy 2018-11-23 15:30:07.480 7fea5458ff00 Fatal error: can't check configuration file '/root/config': No such file or directory
This look like it is defaulting to a config of "~/config" - you need to run it like this:
privoxy --no-daemon <configfile>
With sudo this is worse
sudo privoxy --no-daemon 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Privoxy version 3.0.26 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Program name: privoxy 2018-11-23 15:29:16.102 7fb7a4624f00 Fatal error: can't check configuration file '/home/entropia/config': No such file or directory
It is the same problem, it defaults to '~/config' when you don't specify a config file.
Please show us output from "systemctl cat privoxy". That'll tell us how it is meant to be started. Specifically, with which config file. # /usr/lib/systemd/system/privoxy.service [Unit] Description=Privoxy Web Proxy With Advanced Filtering Capabilities After=network.target
[Service] Type=forking PIDFile=/run/privoxy.pid ExecStartPre=-/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts / etc/localtime /var/lib/privoxy/etc/ ExecStartPre=-/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 / var/lib/privoxy/lib64/ ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data venerdì 23 novembre 2018 16:31:31 CET, Per Jessen ha scritto:
Please show us output from "systemctl cat privoxy". That'll tell us how it is meant to be started. Specifically, with which config file.
# /usr/lib/systemd/system/privoxy.service [Unit] Description=Privoxy Web Proxy With Advanced Filtering Capabilities After=network.target
[Service] Type=forking PIDFile=/run/privoxy.pid ExecStartPre=-/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts / etc/localtime /var/lib/privoxy/etc/ ExecStartPre=-/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 / var/lib/privoxy/lib64/
Okay, so those ExecStartPre prepare the chroot in /var/lib/privoxy/
ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config
Try running it, as root, like this: /usr/sbin/privoxy --chroot --user privoxy --no-daemon /etc/config I think a config file of '/etc/config' is a bit odd, I owuld have expected maybe '/etc/privoxy.conf'. Maybe also show us output of 'grep privoxy /etc/passwd' - it should list /var/lib/privoxy as homedir. -- Per Jessen, Zürich (3.4°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 23 novembre 2018 16:46:22 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 16:31:31 CET, Per Jessen ha scritto:
Please show us output from "systemctl cat privoxy". That'll tell us how it is meant to be started. Specifically, with which config file.
# /usr/lib/systemd/system/privoxy.service [Unit] Description=Privoxy Web Proxy With Advanced Filtering Capabilities After=network.target
[Service] Type=forking PIDFile=/run/privoxy.pid ExecStartPre=-/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts / etc/localtime /var/lib/privoxy/etc/ ExecStartPre=-/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 / var/lib/privoxy/lib64/
Okay, so those ExecStartPre prepare the chroot in /var/lib/privoxy/
ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config
Try running it, as root, like this:
/usr/sbin/privoxy --chroot --user privoxy --no-daemon /etc/config
I think a config file of '/etc/config' is a bit odd, I owuld have expected maybe '/etc/privoxy.conf'.
Maybe also show us output of 'grep privoxy /etc/passwd' - it should list /var/lib/privoxy as homedir.
# /usr/sbin/privoxy --chroot --user privoxy --no-daemon /etc/config 2018-11-23 16:59:53.760 7f62f5d38f00 Info: Privoxy version 3.0.26 2018-11-23 16:59:53.761 7f62f5d38f00 Info: Program name: /usr/sbin/privoxy 2018-11-23 16:59:53.763 7f62f5d38f00 Info: Loading filter file: /etc/ default.filter 2018-11-23 16:59:53.766 7f62f5d38f00 Info: Loading filter file: /etc/ user.filter 2018-11-23 16:59:53.769 7f62f5d38f00 Info: Loading actions file: /etc/match- all.action 2018-11-23 16:59:53.769 7f62f5d38f00 Info: Loading actions file: /etc/ default.action 2018-11-23 16:59:53.772 7f62f5d38f00 Info: Loading actions file: /etc/ user.action 2018-11-23 16:59:53.773 7f62f5d38f00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address cannot assign requested address? Maybe a firewalld issue? Which service has to be allowed in firewalld to run privoxy. Client or server or none or both? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 23 novembre 2018 17:01:31 CET, stakanov ha scritto:
In data venerdì 23 novembre 2018 16:46:22 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 16:31:31 CET, Per Jessen ha scritto:
Please show us output from "systemctl cat privoxy". That'll tell us how it is meant to be started. Specifically, with which config file.
# /usr/lib/systemd/system/privoxy.service [Unit] Description=Privoxy Web Proxy With Advanced Filtering Capabilities After=network.target
[Service] Type=forking PIDFile=/run/privoxy.pid ExecStartPre=-/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts / etc/localtime /var/lib/privoxy/etc/ ExecStartPre=-/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 / var/lib/privoxy/lib64/
Okay, so those ExecStartPre prepare the chroot in /var/lib/privoxy/
ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config
Try running it, as root, like this:
/usr/sbin/privoxy --chroot --user privoxy --no-daemon /etc/config
I think a config file of '/etc/config' is a bit odd, I owuld have expected maybe '/etc/privoxy.conf'.
Maybe also show us output of 'grep privoxy /etc/passwd' - it should list /var/lib/privoxy as homedir.
# /usr/sbin/privoxy --chroot --user privoxy --no-daemon /etc/config 2018-11-23 16:59:53.760 7f62f5d38f00 Info: Privoxy version 3.0.26 2018-11-23 16:59:53.761 7f62f5d38f00 Info: Program name: /usr/sbin/privoxy 2018-11-23 16:59:53.763 7f62f5d38f00 Info: Loading filter file: /etc/ default.filter 2018-11-23 16:59:53.766 7f62f5d38f00 Info: Loading filter file: /etc/ user.filter 2018-11-23 16:59:53.769 7f62f5d38f00 Info: Loading actions file: /etc/match- all.action 2018-11-23 16:59:53.769 7f62f5d38f00 Info: Loading actions file: /etc/ default.action 2018-11-23 16:59:53.772 7f62f5d38f00 Info: Loading actions file: /etc/ user.action 2018-11-23 16:59:53.773 7f62f5d38f00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address
cannot assign requested address? Maybe a firewalld issue? Which service has to be allowed in firewalld to run privoxy. Client or server or none or both?
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de Found this page, going to try (is from two years ago but would not surprise me. https://superuser.com/questions/1125854/cant-start-privoxy
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1. Networkmanager with more than one user open seems a mess in KDE. It shows I am connected to network "ssid B" while I am connected to network "ssid A". The first user that did set up the connection is shown rightly that you are connected to ssid A. I will report that as a bug too, as this is again a kind of regression they had in the past. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1.
Right. Is 192.168.0.1 specified in the config file? /var/lib/privoxy/etc/config. I'm not familiar with setting up privoxy, do you need to manually configure your browser to use this proxy? I think it might be more practical to use e.g. 127.0.0.1 (or another one, just assign it first). https://www.privoxy.org/user-manual/config.html Hah, according to the manual above, the default is 127.0.0.1:8118 :-) You may want to ponder why it's using 192.68.0.1 instead of the default. -- Per Jessen, Zürich (3.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [11-23-18 11:29]:
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1. Networkmanager with more than one user open seems a mess in KDE. It shows I am connected to network "ssid B" while I am connected to network "ssid A". The first user that did set up the connection is shown rightly that you are connected to ssid A. I will report that as a bug too, as this is again a kind of regression they had in the past.
your machines localhost address is 127.0.0.1. 192.168.0.1 is either your routers config address of the address the router give your machine, but it is NOT localhost. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [11-23-18 11:29]:
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1. Networkmanager with more than one user open seems a mess in KDE. It shows I am connected to network "ssid B" while I am connected to network "ssid A". The first user that did set up the connection is shown rightly that you are connected to ssid A. I will report that as a bug too, as this is again a kind of regression they had in the past.
your machines localhost address is 127.0.0.1. 192.168.0.1 is either your routers config address of the address the router give your machine, but it is NOT localhost. In the config it is 127.0.0.1. And the internal subnet is 198.168.xx.xx where
In data venerdì 23 novembre 2018 17:42:56 CET, Patrick Shanahan ha scritto: the x values are clearly different to the 192.168.0.1 I have no clue why this is given to privoxy. ifconig gives the correct values. And the wireless gives the correct value. arp -a gives the correct value. So this is IMO the problem. For some reason it is not updated on the real IP. Where could that happen? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/23/2018 12:05 PM, stakanov wrote:
In the config it is 127.0.0.1. And the internal subnet is 198.168.xx.xx where the x values are clearly different to the 192.168.0.1 I have no clue why this is given to privoxy. ifconig gives the correct values. And the wireless gives the correct value. arp -a gives the correct value.
Since RFC 1918 addresses cannot be reached from off the local network, there is no need to hide them. The gateway address must be within the subnet used. 192.168.0.1 is often used, but can be any address, other than the broadcast address, within your subnet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data venerdì 23 novembre 2018 17:42:56 CET, Patrick Shanahan ha scritto:
* stakanov <stakanov@eclipso.eu> [11-23-18 11:29]:
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1. Networkmanager with more than one user open seems a mess in KDE. It shows I am connected to network "ssid B" while I am connected to network "ssid A". The first user that did set up the connection is shown rightly that you are connected to ssid A. I will report that as a bug too, as this is again a kind of regression they had in the past.
your machines localhost address is 127.0.0.1. 192.168.0.1 is either your routers config address of the address the router give your machine, but it is NOT localhost.
In the config it is 127.0.0.1. And the internal subnet is 192.168.xx.xx where the x values are clearly different to the 192.168.0.1 I have no clue why this is given to privoxy.
More importantly, where does privoxy get it from? When you started it from the command line, it still got hold of 192.168.0.1, weird odd.
ifconig gives the correct values. And the wireless gives the correct value. arp -a gives the correct value.
So this is IMO the problem. For some reason it is not updated on the real IP. Where could that happen?
It never would/should be. There should be no reason to change the privoxy config just because your IP address changes. Use localhost/127.0.0.1. -- Per Jessen, Zürich (3.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 23 novembre 2018 18:45:25 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 17:42:56 CET, Patrick Shanahan ha
scritto:
* stakanov <stakanov@eclipso.eu> [11-23-18 11:29]:
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1. Networkmanager with more than one user open seems a mess in KDE. It shows I am connected to network "ssid B" while I am connected to network "ssid A". The first user that did set up the connection is shown rightly that you are connected to ssid A. I will report that as a bug too, as this is again a kind of regression they had in the past.
your machines localhost address is 127.0.0.1. 192.168.0.1 is either your routers config address of the address the router give your machine, but it is NOT localhost.
In the config it is 127.0.0.1. And the internal subnet is 192.168.xx.xx where the x values are clearly different to the 192.168.0.1 I have no clue why this is given to privoxy.
More importantly, where does privoxy get it from? When you started it from the command line, it still got hold of 192.168.0.1, weird odd.
ifconig gives the correct values. And the wireless gives the correct value. arp -a gives the correct value.
So this is IMO the problem. For some reason it is not updated on the real IP. Where could that happen?
It never would/should be. There should be no reason to change the privoxy config just because your IP address changes. Use localhost/127.0.0.1.
Well, none of my boxes have 192.168.0.1. I have a fritzbox giving the internal network. This PC running network manager and is on wlan on a dlan-wlan adapter from devolo. Ifconfig: entropia@roadrunner:~> ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 5c:ff:xx:xx:xx:xx txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xf2500000-f2520000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 4333 bytes 2507074 (2.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4333 bytes 2507074 (2.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.50.37 netmask 255.255.255.0 broadcast 192.168.50.255 inet6 fd00::a8b3:ce25:xxxx:xxxx prefixlen 64 scopeid 0x0<global> inet6 fe80::1a0a:a1f2:xxxx:xxxx prefixlen 64 scopeid 0x20<link> inet6 fd00::a56e:d62e:xxxx:xxxx prefixlen 64 scopeid 0x0<global> ether 0a:ed:72:8d:xx:xx txqueuelen 1000 (Ethernet) RX packets 14854 bytes 10603559 (10.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 9974 bytes 1248429 (1.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 arp -a gives: fritz.box (192.168.50.1) at 9c:c7:a6:84:9b:c6 [ether] on wlan1 sudo ifup <13>Nov 23 19:16:08 entropia: Network is managed by 'NetworkManager.service' -
skipping
I do not understand to be honest. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data venerdì 23 novembre 2018 18:45:25 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 17:42:56 CET, Patrick Shanahan ha
scritto:
* stakanov <stakanov@eclipso.eu> [11-23-18 11:29]:
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1. Networkmanager with more than one user open seems a mess in KDE. It shows I am connected to network "ssid B" while I am connected to network "ssid A". The first user that did set up the connection is shown rightly that you are connected to ssid A. I will report that as a bug too, as this is again a kind of regression they had in the past.
your machines localhost address is 127.0.0.1. 192.168.0.1 is either your routers config address of the address the router give your machine, but it is NOT localhost.
In the config it is 127.0.0.1. And the internal subnet is 192.168.xx.xx where the x values are clearly different to the 192.168.0.1 I have no clue why this is given to privoxy.
More importantly, where does privoxy get it from? When you started it from the command line, it still got hold of 192.168.0.1, weird odd.
ifconig gives the correct values. And the wireless gives the correct value. arp -a gives the correct value.
So this is IMO the problem. For some reason it is not updated on the real IP. Where could that happen?
It never would/should be. There should be no reason to change the privoxy config just because your IP address changes. Use localhost/127.0.0.1.
Well, none of my boxes have 192.168.0.1.
And it is not specified in the config either? There is no file in /var/lib/privoxy that contains 192.168.0.1 ? find /var/lib/privoxy -type f | xargs grep 192.168 -- Per Jessen, Zürich (3.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data venerdì 23 novembre 2018 19:30:30 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 18:45:25 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 17:42:56 CET, Patrick Shanahan ha
scritto:
* stakanov <stakanov@eclipso.eu> [11-23-18 11:29]:
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1. Networkmanager with more than one user open seems a mess in KDE. It shows I am connected to network "ssid B" while I am connected to network "ssid A". The first user that did set up the connection is shown rightly that you are connected to ssid A. I will report that as a bug too, as this is again a kind of regression they had in the past.
your machines localhost address is 127.0.0.1. 192.168.0.1 is either your routers config address of the address the router give your machine, but it is NOT localhost.
In the config it is 127.0.0.1. And the internal subnet is 192.168.xx.xx where the x values are clearly different to the 192.168.0.1 I have no clue why this is given to privoxy.
More importantly, where does privoxy get it from? When you started it from the command line, it still got hold of 192.168.0.1, weird odd.
ifconig gives the correct values. And the wireless gives the correct value. arp -a gives the correct value.
So this is IMO the problem. For some reason it is not updated on the real IP. Where could that happen?
It never would/should be. There should be no reason to change the privoxy config just because your IP address changes. Use localhost/127.0.0.1.
Well, none of my boxes have 192.168.0.1.
And it is not specified in the config either? There is no file in /var/lib/privoxy that contains 192.168.0.1 ?
find /var/lib/privoxy -type f | xargs grep 192.168
There it is, actually I do not know why it is there: # find /var/lib/privoxy -type f | xargs grep 192.168 /var/lib/privoxy/etc/config:# address 192.168.0.1 on your local private network /var/lib/privoxy/etc/config:# (192.168.0.0) and has another outside connection with a /var/lib/privoxy/etc/config: listen-address 192.168.0.1:8118 /var/lib/privoxy/etc/config:# Allow access from any host on the 26-bit subnet 192.168.45.64 /var/lib/privoxy/etc/config:# to anywhere, with the exception that 192.168.45.73 may not /var/lib/privoxy/etc/config:# permit-access 192.168.45.64/26 /var/lib/privoxy/etc/config:# deny-access 192.168.45.73 www.dirty-stuff.example.com /var/lib/privoxy/etc/config:# forward 192.168.*.*/ . /var/lib/privoxy/log/logfile:2018-11-23 10:38:29.409 7f9468ae3f00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address /var/lib/privoxy/log/logfile:2018-11-23 10:56:59.018 7fa206d0ff00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address /var/lib/privoxy/log/logfile:2018-11-23 17:18:04.708 7f609c410f00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address /var/lib/privoxy/log/logfile:2018-11-23 17:59:52.906 7f38f3fb1f00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address "/var/lib/privoxy/etc/config: listen-address 192.168.0.1:8118" is so to say the culprit. Should this not be set to local host by default? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/11/2018 19.39, stakanov wrote:
In data venerdì 23 novembre 2018 19:30:30 CET, Per Jessen ha scritto:
stakanov wrote:
find /var/lib/privoxy -type f | xargs grep 192.168
There it is, actually I do not know why it is there: # find /var/lib/privoxy -type f | xargs grep 192.168 /var/lib/privoxy/etc/config:# address 192.168.0.1 on your local private network /var/lib/privoxy/etc/config:# (192.168.0.0) and has another outside connection with a /var/lib/privoxy/etc/config: listen-address 192.168.0.1:8118 /var/lib/privoxy/etc/config:# Allow access from any host on the 26-bit subnet 192.168.45.64 /var/lib/privoxy/etc/config:# to anywhere, with the exception that 192.168.45.73 may not /var/lib/privoxy/etc/config:# permit-access 192.168.45.64/26 /var/lib/privoxy/etc/config:# deny-access 192.168.45.73 www.dirty-stuff.example.com /var/lib/privoxy/etc/config:# forward 192.168.*.*/ . /var/lib/privoxy/log/logfile:2018-11-23 10:38:29.409 7f9468ae3f00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address /var/lib/privoxy/log/logfile:2018-11-23 10:56:59.018 7fa206d0ff00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address /var/lib/privoxy/log/logfile:2018-11-23 17:18:04.708 7f609c410f00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address /var/lib/privoxy/log/logfile:2018-11-23 17:59:52.906 7f38f3fb1f00 Fatal error: can't bind to 192.168.0.1:8118: Cannot assign requested address
"/var/lib/privoxy/etc/config: listen-address 192.168.0.1:8118" is so to say the culprit. Should this not be set to local host by default?
Educated guess: No. This is an unused address in your local network, where privoxy listen for connections. Thus any machine in your LAN may use that proxy. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
stakanov wrote:
In data venerdì 23 novembre 2018 18:45:25 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 17:42:56 CET, Patrick Shanahan ha
scritto:
* stakanov <stakanov@eclipso.eu> [11-23-18 11:29]:
what it does: I tries to assign localhost address to 192.168.0.1 on 8118 but..... my localhost address is different from 192.168.0.1 and is attributed and should be updated via networkmanager. It is a total other subnet. It is logical that it cannot get an address for 192.168.0.1. Networkmanager with more than one user open seems a mess in KDE. It shows I am connected to network "ssid B" while I am connected to network "ssid A". The first user that did set up the connection is shown rightly that you are connected to ssid A. I will report that as a bug too, as this is again a kind of regression they had in the past.
your machines localhost address is 127.0.0.1. 192.168.0.1 is either your routers config address of the address the router give your machine, but it is NOT localhost.
In the config it is 127.0.0.1. And the internal subnet is 192.168.xx.xx where the x values are clearly different to the 192.168.0.1 I have no clue why this is given to privoxy.
More importantly, where does privoxy get it from? When you started it from the command line, it still got hold of 192.168.0.1, weird odd.
ifconig gives the correct values. And the wireless gives the correct value. arp -a gives the correct value.
So this is IMO the problem. For some reason it is not updated on the real IP. Where could that happen?
It never would/should be. There should be no reason to change the privoxy config just because your IP address changes. Use localhost/127.0.0.1.
Well, none of my boxes have 192.168.0.1.
And it is not specified in the config either? There is no file in /var/lib/privoxy that contains 192.168.0.1 ?
find /var/lib/privoxy -type f | xargs grep 192.168 ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor
In data venerdì 23 novembre 2018 19:30:30 CET, Per Jessen ha scritto: preset: disabled) Active: active (running) since Fri 2018-11-23 23:06:22 CET; 4min 28s ago Process: 2733 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/ SUCCESS) Process: 1851 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/ privoxy.pid --user privoxy /etc/config (code=exited, sta> Process: 1845 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/ libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exi> Process: 1840 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc> Main PID: 1856 (privoxy) Tasks: 1 (limit: 4915) CGroup: /system.slice/privoxy.service └─1856 /usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config nov 23 23:06:21 roadrunner systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... nov 23 23:06:22 roadrunner systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities. nov 23 23:07:27 roadrunner.suse systemd[1]: Reloading Privoxy Web Proxy With Advanced Filtering Capabilities. nov 23 23:07:27 roadrunner.suse systemd[1]: Reloaded Privoxy Web Proxy With Advanced Filtering Capabilities. So it appears it is running now. I eliminated the privoxy config. When restarting the system I had no internet. So I rebooted completely. The bios gave me a message "system software updated"....and now it works. Whatever this "update" was, maybe firmware / microcode of kernel? I googled but did not find anything. I did then set up privoxy as kde system proxy. But it does not work (privoxy is not used) and then I tried to set in the browser manually, but it does not work. So now it runs but still it is not used. 127.0.0.1 and 8118 as settings that is: 127.0.0.1:8118 Still puzzled. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
So it appears it [privoxy] is running now. I eliminated the privoxy config.
Haha - the question is, does it still do what you expect it to do. With no configuration, that seems unlikely.
I did then set up privoxy as kde system proxy. But it does not work (privoxy is not used) and then I tried to set in the browser manually, but it does not work. So now it runs but still it is not used. 127.0.0.1 and 8118 as settings that is: 127.0.0.1:8118
I'm not sure what a "kde system proxy" is, but I suspect it might simply mean setting the environment variable "http_proxy'. For that to take effect, you have to restart, at least the browser, maybe logout/login too. When you say "it is not used", how do you determine that? If you want to know if it's being called, but doesn't do anything, try running "tcpdump -n -i lo port 8118" (as root). That'll show you traffic going to and from privoxy. With no configuration, I expect privoxy to listen on the default address localhost:8118, but not do anything with the traffic. -- Per Jessen, Zürich (6.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data sabato 24 novembre 2018 11:30:57 CET, Per Jessen ha scritto:
stakanov wrote:
So it appears it [privoxy] is running now. I eliminated the privoxy config.
Haha - the question is, does it still do what you expect it to do. With no configuration, that seems unlikely.
I did then set up privoxy as kde system proxy. But it does not work (privoxy is not used) and then I tried to set in the browser manually, but it does not work. So now it runs but still it is not used. 127.0.0.1 and 8118 as settings that is: 127.0.0.1:8118
I'm not sure what a "kde system proxy" is, but I suspect it might simply mean setting the environment variable "http_proxy'. For that to take effect, you have to restart, at least the browser, maybe logout/login too.
When you say "it is not used", how do you determine that?
If you want to know if it's being called, but doesn't do anything, try running "tcpdump -n -i lo port 8118" (as root). That'll show you traffic going to and from privoxy.
With no configuration, I expect privoxy to listen on the default address localhost:8118, but not do anything with the traffic. O.K. I installed tcpdump (and thank you for the program, very useful).
So the system proxy in KDE is set to use privoxy. But it does not work as when I do set: use systemproxy in falcon, then the result is silence. When I do set manually http:// to 127.0.0.1 and 8118 which are the default settings of privoxy it does not open any page, but it calls it. Albeit there is something odd again, why it call on port 35234 too???? listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes 12:34:03.097964 IP 127.0.0.1.35198 > 127.0.0.1.8118: Flags [S], seq 69639707, win 43690, options [mss 65495,sackOK,TS val 2045721770 ecr 0,nop,wscale 7], length 0 12:34:03.098008 IP 127.0.0.1.8118 > 127.0.0.1.35198: Flags [S.], seq 1725862282, ack 69639708, win 43690, options [mss 65495,sackOK,TS val 2045721770 ecr 2045721770,nop,wscale 7], length 0 12:34:03.098038 IP 127.0.0.1.35198 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045721770 ecr 2045721770], length 0 12:34:03.098307 IP 127.0.0.1.35198 > 127.0.0.1.8118: Flags [P.], seq 1:248, ack 1, win 342, options [nop,nop,TS val 2045721770 ecr 2045721770], length 247 12:34:03.098325 IP 127.0.0.1.8118 > 127.0.0.1.35198: Flags [.], ack 248, win 350, options [nop,nop,TS val 2045721770 ecr 2045721770], length 0 12:34:03.098892 IP 127.0.0.1.35200 > 127.0.0.1.8118: Flags [S], seq 3178399807, win 43690, options [mss 65495,sackOK,TS val 2045721770 ecr 0,nop,wscale 7], length 0 12:34:03.098918 IP 127.0.0.1.8118 > 127.0.0.1.35200: Flags [S.], seq 283361249, ack 3178399808, win 43690, options [mss 65495,sackOK,TS val 2045721771 ecr 2045721770,nop,wscale 7], length 0 12:34:03.098939 IP 127.0.0.1.35200 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045721771 ecr 2045721771], length 0 12:34:03.106301 IP 127.0.0.1.8118 > 127.0.0.1.35198: Flags [P.], seq 1:273, ack 248, win 350, options [nop,nop,TS val 2045721778 ecr 2045721770], length 272 12:34:03.106335 IP 127.0.0.1.35198 > 127.0.0.1.8118: Flags [.], ack 273, win 350, options [nop,nop,TS val 2045721778 ecr 2045721778], length 0 12:34:03.106366 IP 127.0.0.1.8118 > 127.0.0.1.35198: Flags [P.], seq 273:274, ack 248, win 350, options [nop,nop,TS val 2045721778 ecr 2045721778], length 1 12:34:03.106381 IP 127.0.0.1.35198 > 127.0.0.1.8118: Flags [.], ack 274, win 350, options [nop,nop,TS val 2045721778 ecr 2045721778], length 0 12:34:03.106419 IP 127.0.0.1.8118 > 127.0.0.1.35198: Flags [F.], seq 274, ack 248, win 350, options [nop,nop,TS val 2045721778 ecr 2045721778], length 0 12:34:03.111583 IP 127.0.0.1.35198 > 127.0.0.1.8118: Flags [F.], seq 248, ack 275, win 350, options [nop,nop,TS val 2045721783 ecr 2045721778], length 0 12:34:03.111627 IP 127.0.0.1.8118 > 127.0.0.1.35198: Flags [.], ack 249, win 350, options [nop,nop,TS val 2045721783 ecr 2045721783], length 0 12:34:03.112019 IP 127.0.0.1.35200 > 127.0.0.1.8118: Flags [P.], seq 1:218, ack 1, win 342, options [nop,nop,TS val 2045721784 ecr 2045721771], length 217 12:34:03.112043 IP 127.0.0.1.8118 > 127.0.0.1.35200: Flags [.], ack 218, win 350, options [nop,nop,TS val 2045721784 ecr 2045721784], length 0 12:34:03.113356 IP 127.0.0.1.35202 > 127.0.0.1.8118: Flags [S], seq 2258364541, win 43690, options [mss 65495,sackOK,TS val 2045721785 ecr 0,nop,wscale 7], length 0 12:34:03.113393 IP 127.0.0.1.8118 > 127.0.0.1.35202: Flags [S.], seq 394568182, ack 2258364542, win 43690, options [mss 65495,sackOK,TS val 2045721785 ecr 2045721785,nop,wscale 7], length 0 12:34:03.113437 IP 127.0.0.1.35202 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045721785 ecr 2045721785], length 0 12:34:03.114121 IP 127.0.0.1.35204 > 127.0.0.1.8118: Flags [S], seq 3187028101, win 43690, options [mss 65495,sackOK,TS val 2045721786 ecr 0,nop,wscale 7], length 0 12:34:03.114153 IP 127.0.0.1.8118 > 127.0.0.1.35204: Flags [S.], seq 1952610656, ack 3187028102, win 43690, options [mss 65495,sackOK,TS val 2045721786 ecr 2045721786,nop,wscale 7], length 0 12:34:03.114202 IP 127.0.0.1.35204 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045721786 ecr 2045721786], length 0 12:34:03.116612 IP 127.0.0.1.35202 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045721788 ecr 2045721785], length 245 12:34:03.116640 IP 127.0.0.1.8118 > 127.0.0.1.35202: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045721788 ecr 2045721788], length 0 12:34:03.117758 IP 127.0.0.1.8118 > 127.0.0.1.35200: Flags [P.], seq 1:276, ack 218, win 350, options [nop,nop,TS val 2045721789 ecr 2045721784], length 275 12:34:03.117781 IP 127.0.0.1.35200 > 127.0.0.1.8118: Flags [.], ack 276, win 350, options [nop,nop,TS val 2045721789 ecr 2045721789], length 0 12:34:03.117822 IP 127.0.0.1.8118 > 127.0.0.1.35200: Flags [P.], seq 276:8735, ack 218, win 350, options [nop,nop,TS val 2045721789 ecr 2045721789], length 8459 12:34:03.117838 IP 127.0.0.1.35200 > 127.0.0.1.8118: Flags [.], ack 8735, win 1373, options [nop,nop,TS val 2045721789 ecr 2045721789], length 0 12:34:03.117890 IP 127.0.0.1.8118 > 127.0.0.1.35200: Flags [F.], seq 8735, ack 218, win 350, options [nop,nop,TS val 2045721789 ecr 2045721789], length 0 12:34:03.118062 IP 127.0.0.1.35200 > 127.0.0.1.8118: Flags [R.], seq 218, ack 8736, win 1373, options [nop,nop,TS val 2045721790 ecr 2045721789], length 0 12:34:03.118313 IP 127.0.0.1.35204 > 127.0.0.1.8118: Flags [P.], seq 1:248, ack 1, win 342, options [nop,nop,TS val 2045721790 ecr 2045721786], length 247 12:34:03.118332 IP 127.0.0.1.8118 > 127.0.0.1.35204: Flags [.], ack 248, win 350, options [nop,nop,TS val 2045721790 ecr 2045721790], length 0 12:34:03.124721 IP 127.0.0.1.8118 > 127.0.0.1.35204: Flags [P.], seq 1:273, ack 248, win 350, options [nop,nop,TS val 2045721796 ecr 2045721790], length 272 12:34:03.124750 IP 127.0.0.1.35204 > 127.0.0.1.8118: Flags [.], ack 273, win 350, options [nop,nop,TS val 2045721796 ecr 2045721796], length 0 12:34:03.124785 IP 127.0.0.1.8118 > 127.0.0.1.35204: Flags [P.], seq 273:274, ack 248, win 350, options [nop,nop,TS val 2045721796 ecr 2045721796], length 1 12:34:03.124801 IP 127.0.0.1.35204 > 127.0.0.1.8118: Flags [.], ack 274, win 350, options [nop,nop,TS val 2045721796 ecr 2045721796], length 0 12:34:03.124839 IP 127.0.0.1.8118 > 127.0.0.1.35204: Flags [F.], seq 274, ack 248, win 350, options [nop,nop,TS val 2045721796 ecr 2045721796], length 0 12:34:03.130242 IP 127.0.0.1.35204 > 127.0.0.1.8118: Flags [F.], seq 248, ack 275, win 350, options [nop,nop,TS val 2045721802 ecr 2045721796], length 0 12:34:03.130285 IP 127.0.0.1.8118 > 127.0.0.1.35204: Flags [.], ack 249, win 350, options [nop,nop,TS val 2045721802 ecr 2045721802], length 0 12:34:03.144609 IP 127.0.0.1.8118 > 127.0.0.1.35202: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045721816 ecr 2045721788], length 263 12:34:03.144642 IP 127.0.0.1.35202 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045721816 ecr 2045721816], length 0 12:34:03.144682 IP 127.0.0.1.8118 > 127.0.0.1.35202: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045721816 ecr 2045721816], length 6786 12:34:03.144697 IP 127.0.0.1.35202 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045721816 ecr 2045721816], length 0 12:34:03.144730 IP 127.0.0.1.8118 > 127.0.0.1.35202: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045721816 ecr 2045721816], length 0 12:34:03.154751 IP 127.0.0.1.35202 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045721826 ecr 2045721816], length 0 12:34:03.182463 IP 127.0.0.1.35206 > 127.0.0.1.8118: Flags [S], seq 72172849, win 43690, options [mss 65495,sackOK,TS val 2045721854 ecr 0,nop,wscale 7], length 0 12:34:03.182512 IP 127.0.0.1.8118 > 127.0.0.1.35206: Flags [S.], seq 3375896357, ack 72172850, win 43690, options [mss 65495,sackOK,TS val 2045721854 ecr 2045721854,nop,wscale 7], length 0 12:34:03.182543 IP 127.0.0.1.35206 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045721854 ecr 2045721854], length 0 12:34:03.182897 IP 127.0.0.1.35206 > 127.0.0.1.8118: Flags [P.], seq 1:224, ack 1, win 342, options [nop,nop,TS val 2045721854 ecr 2045721854], length 223 12:34:03.182920 IP 127.0.0.1.8118 > 127.0.0.1.35206: Flags [.], ack 224, win 350, options [nop,nop,TS val 2045721855 ecr 2045721854], length 0 12:34:03.184793 IP 127.0.0.1.8118 > 127.0.0.1.35206: Flags [P.], seq 1:264, ack 224, win 350, options [nop,nop,TS val 2045721856 ecr 2045721854], length 263 12:34:03.184824 IP 127.0.0.1.35206 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045721856 ecr 2045721856], length 0 12:34:03.184862 IP 127.0.0.1.8118 > 127.0.0.1.35206: Flags [P.], seq 264:7006, ack 224, win 350, options [nop,nop,TS val 2045721856 ecr 2045721856], length 6742 12:34:03.184877 IP 127.0.0.1.35206 > 127.0.0.1.8118: Flags [.], ack 7006, win 1373, options [nop,nop,TS val 2045721856 ecr 2045721856], length 0 12:34:03.184905 IP 127.0.0.1.8118 > 127.0.0.1.35206: Flags [F.], seq 7006, ack 224, win 350, options [nop,nop,TS val 2045721857 ecr 2045721856], length 0 12:34:03.185071 IP 127.0.0.1.35206 > 127.0.0.1.8118: Flags [R.], seq 224, ack 7007, win 1373, options [nop,nop,TS val 2045721857 ecr 2045721857], length 0 12:34:04.481333 IP 127.0.0.1.35210 > 127.0.0.1.8118: Flags [S], seq 3970089369, win 43690, options [mss 65495,sackOK,TS val 2045723153 ecr 0,nop,wscale 7], length 0 12:34:04.481371 IP 127.0.0.1.8118 > 127.0.0.1.35210: Flags [S.], seq 773351170, ack 3970089370, win 43690, options [mss 65495,sackOK,TS val 2045723153 ecr 2045723153,nop,wscale 7], length 0 12:34:04.481395 IP 127.0.0.1.35210 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045723153 ecr 2045723153], length 0 12:34:04.481793 IP 127.0.0.1.35210 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045723153 ecr 2045723153], length 245 12:34:04.481818 IP 127.0.0.1.8118 > 127.0.0.1.35210: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045723153 ecr 2045723153], length 0 12:34:04.483924 IP 127.0.0.1.8118 > 127.0.0.1.35210: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045723156 ecr 2045723153], length 263 12:34:04.483961 IP 127.0.0.1.35210 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045723156 ecr 2045723156], length 0 12:34:04.484014 IP 127.0.0.1.8118 > 127.0.0.1.35210: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045723156 ecr 2045723156], length 6786 12:34:04.484037 IP 127.0.0.1.35210 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045723156 ecr 2045723156], length 0 12:34:04.484080 IP 127.0.0.1.8118 > 127.0.0.1.35210: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045723156 ecr 2045723156], length 0 12:34:04.484145 IP 127.0.0.1.35210 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045723156 ecr 2045723156], length 0 12:34:06.164047 IP 127.0.0.1.35212 > 127.0.0.1.8118: Flags [S], seq 452258915, win 43690, options [mss 65495,sackOK,TS val 2045724836 ecr 0,nop,wscale 7], length 0 12:34:06.164090 IP 127.0.0.1.8118 > 127.0.0.1.35212: Flags [S.], seq 366019578, ack 452258916, win 43690, options [mss 65495,sackOK,TS val 2045724836 ecr 2045724836,nop,wscale 7], length 0 12:34:06.164120 IP 127.0.0.1.35212 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045724836 ecr 2045724836], length 0 12:34:06.164426 IP 127.0.0.1.35212 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045724836 ecr 2045724836], length 245 12:34:06.164449 IP 127.0.0.1.8118 > 127.0.0.1.35212: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045724836 ecr 2045724836], length 0 12:34:06.165925 IP 127.0.0.1.8118 > 127.0.0.1.35212: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045724838 ecr 2045724836], length 263 12:34:06.165950 IP 127.0.0.1.35212 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045724838 ecr 2045724838], length 0 12:34:06.165986 IP 127.0.0.1.8118 > 127.0.0.1.35212: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045724838 ecr 2045724838], length 6786 12:34:06.165999 IP 127.0.0.1.35212 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045724838 ecr 2045724838], length 0 12:34:06.166029 IP 127.0.0.1.8118 > 127.0.0.1.35212: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045724838 ecr 2045724838], length 0 12:34:06.166082 IP 127.0.0.1.35212 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045724838 ecr 2045724838], length 0 12:34:06.215354 IP 127.0.0.1.35214 > 127.0.0.1.8118: Flags [S], seq 2292146460, win 43690, options [mss 65495,sackOK,TS val 2045724887 ecr 0,nop,wscale 7], length 0 12:34:06.215391 IP 127.0.0.1.8118 > 127.0.0.1.35214: Flags [S.], seq 1158581365, ack 2292146461, win 43690, options [mss 65495,sackOK,TS val 2045724887 ecr 2045724887,nop,wscale 7], length 0 12:34:06.215418 IP 127.0.0.1.35214 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045724887 ecr 2045724887], length 0 12:34:06.215676 IP 127.0.0.1.35214 > 127.0.0.1.8118: Flags [P.], seq 1:258, ack 1, win 342, options [nop,nop,TS val 2045724887 ecr 2045724887], length 257 12:34:06.215696 IP 127.0.0.1.8118 > 127.0.0.1.35214: Flags [.], ack 258, win 350, options [nop,nop,TS val 2045724887 ecr 2045724887], length 0 12:34:06.218154 IP 127.0.0.1.8118 > 127.0.0.1.35214: Flags [P.], seq 1:264, ack 258, win 350, options [nop,nop,TS val 2045724890 ecr 2045724887], length 263 12:34:06.218180 IP 127.0.0.1.35214 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045724890 ecr 2045724890], length 0 12:34:06.218226 IP 127.0.0.1.8118 > 127.0.0.1.35214: Flags [P.], seq 264:7074, ack 258, win 350, options [nop,nop,TS val 2045724890 ecr 2045724890], length 6810 12:34:06.218241 IP 127.0.0.1.35214 > 127.0.0.1.8118: Flags [.], ack 7074, win 1373, options [nop,nop,TS val 2045724890 ecr 2045724890], length 0 12:34:06.218273 IP 127.0.0.1.8118 > 127.0.0.1.35214: Flags [F.], seq 7074, ack 258, win 350, options [nop,nop,TS val 2045724890 ecr 2045724890], length 0 12:34:06.243681 IP 127.0.0.1.35214 > 127.0.0.1.8118: Flags [R.], seq 258, ack 7075, win 1373, options [nop,nop,TS val 2045724915 ecr 2045724890], length 0 12:34:06.254155 IP 127.0.0.1.35216 > 127.0.0.1.8118: Flags [S], seq 2885712284, win 43690, options [mss 65495,sackOK,TS val 2045724926 ecr 0,nop,wscale 7], length 0 12:34:06.254207 IP 127.0.0.1.8118 > 127.0.0.1.35216: Flags [S.], seq 167798015, ack 2885712285, win 43690, options [mss 65495,sackOK,TS val 2045724926 ecr 2045724926,nop,wscale 7], length 0 12:34:06.254240 IP 127.0.0.1.35216 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045724926 ecr 2045724926], length 0 12:34:06.254862 IP 127.0.0.1.35216 > 127.0.0.1.8118: Flags [P.], seq 1:258, ack 1, win 342, options [nop,nop,TS val 2045724926 ecr 2045724926], length 257 12:34:06.254888 IP 127.0.0.1.8118 > 127.0.0.1.35216: Flags [.], ack 258, win 350, options [nop,nop,TS val 2045724926 ecr 2045724926], length 0 12:34:06.258167 IP 127.0.0.1.8118 > 127.0.0.1.35216: Flags [P.], seq 1:264, ack 258, win 350, options [nop,nop,TS val 2045724930 ecr 2045724926], length 263 12:34:06.258200 IP 127.0.0.1.35216 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045724930 ecr 2045724930], length 0 12:34:06.258354 IP 127.0.0.1.8118 > 127.0.0.1.35216: Flags [P.], seq 264:7074, ack 258, win 350, options [nop,nop,TS val 2045724930 ecr 2045724930], length 6810 12:34:06.258381 IP 127.0.0.1.35216 > 127.0.0.1.8118: Flags [.], ack 7074, win 1373, options [nop,nop,TS val 2045724930 ecr 2045724930], length 0 12:34:06.258441 IP 127.0.0.1.8118 > 127.0.0.1.35216: Flags [F.], seq 7074, ack 258, win 350, options [nop,nop,TS val 2045724930 ecr 2045724930], length 0 12:34:06.258489 IP 127.0.0.1.35216 > 127.0.0.1.8118: Flags [R.], seq 258, ack 7075, win 1373, options [nop,nop,TS val 2045724930 ecr 2045724930], length 0 12:34:06.383444 IP 127.0.0.1.35218 > 127.0.0.1.8118: Flags [S], seq 2538854387, win 43690, options [mss 65495,sackOK,TS val 2045725055 ecr 0,nop,wscale 7], length 0 12:34:06.383481 IP 127.0.0.1.8118 > 127.0.0.1.35218: Flags [S.], seq 2746134595, ack 2538854388, win 43690, options [mss 65495,sackOK,TS val 2045725055 ecr 2045725055,nop,wscale 7], length 0 12:34:06.383507 IP 127.0.0.1.35218 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725055 ecr 2045725055], length 0 12:34:06.383857 IP 127.0.0.1.35218 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725055 ecr 2045725055], length 245 12:34:06.383882 IP 127.0.0.1.8118 > 127.0.0.1.35218: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725055 ecr 2045725055], length 0 12:34:06.385555 IP 127.0.0.1.8118 > 127.0.0.1.35218: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725057 ecr 2045725055], length 263 12:34:06.385573 IP 127.0.0.1.35218 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725057 ecr 2045725057], length 0 12:34:06.385605 IP 127.0.0.1.8118 > 127.0.0.1.35218: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045725057 ecr 2045725057], length 6786 12:34:06.385617 IP 127.0.0.1.35218 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045725057 ecr 2045725057], length 0 12:34:06.385641 IP 127.0.0.1.8118 > 127.0.0.1.35218: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045725057 ecr 2045725057], length 0 12:34:06.385684 IP 127.0.0.1.35218 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045725057 ecr 2045725057], length 0 12:34:06.385941 IP 127.0.0.1.35220 > 127.0.0.1.8118: Flags [S], seq 2881812513, win 43690, options [mss 65495,sackOK,TS val 2045725058 ecr 0,nop,wscale 7], length 0 12:34:06.385963 IP 127.0.0.1.8118 > 127.0.0.1.35220: Flags [S.], seq 4024985994, ack 2881812514, win 43690, options [mss 65495,sackOK,TS val 2045725058 ecr 2045725058,nop,wscale 7], length 0 12:34:06.385983 IP 127.0.0.1.35220 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725058 ecr 2045725058], length 0 12:34:06.386279 IP 127.0.0.1.35222 > 127.0.0.1.8118: Flags [S], seq 1801906805, win 43690, options [mss 65495,sackOK,TS val 2045725058 ecr 0,nop,wscale 7], length 0 12:34:06.386300 IP 127.0.0.1.8118 > 127.0.0.1.35222: Flags [S.], seq 478772612, ack 1801906806, win 43690, options [mss 65495,sackOK,TS val 2045725058 ecr 2045725058,nop,wscale 7], length 0 12:34:06.386320 IP 127.0.0.1.35222 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725058 ecr 2045725058], length 0 12:34:06.386567 IP 127.0.0.1.35224 > 127.0.0.1.8118: Flags [S], seq 220809764, win 43690, options [mss 65495,sackOK,TS val 2045725058 ecr 0,nop,wscale 7], length 0 12:34:06.386585 IP 127.0.0.1.8118 > 127.0.0.1.35224: Flags [S.], seq 585218179, ack 220809765, win 43690, options [mss 65495,sackOK,TS val 2045725058 ecr 2045725058,nop,wscale 7], length 0 12:34:06.386603 IP 127.0.0.1.35224 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725058 ecr 2045725058], length 0 12:34:06.386774 IP 127.0.0.1.35226 > 127.0.0.1.8118: Flags [S], seq 2327002577, win 43690, options [mss 65495,sackOK,TS val 2045725058 ecr 0,nop,wscale 7], length 0 12:34:06.386793 IP 127.0.0.1.8118 > 127.0.0.1.35226: Flags [S.], seq 193228657, ack 2327002578, win 43690, options [mss 65495,sackOK,TS val 2045725058 ecr 2045725058,nop,wscale 7], length 0 12:34:06.386811 IP 127.0.0.1.35226 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725058 ecr 2045725058], length 0 12:34:06.387101 IP 127.0.0.1.35228 > 127.0.0.1.8118: Flags [S], seq 2688438696, win 43690, options [mss 65495,sackOK,TS val 2045725059 ecr 0,nop,wscale 7], length 0 12:34:06.387118 IP 127.0.0.1.8118 > 127.0.0.1.35228: Flags [S.], seq 2932357997, ack 2688438697, win 43690, options [mss 65495,sackOK,TS val 2045725059 ecr 2045725059,nop,wscale 7], length 0 12:34:06.387137 IP 127.0.0.1.35228 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725059 ecr 2045725059], length 0 12:34:06.387619 IP 127.0.0.1.35220 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725059 ecr 2045725058], length 245 12:34:06.387640 IP 127.0.0.1.8118 > 127.0.0.1.35220: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725059 ecr 2045725059], length 0 12:34:06.389393 IP 127.0.0.1.8118 > 127.0.0.1.35220: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725061 ecr 2045725059], length 263 12:34:06.389428 IP 127.0.0.1.8118 > 127.0.0.1.35220: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045725061 ecr 2045725059], length 6786 12:34:06.389467 IP 127.0.0.1.8118 > 127.0.0.1.35220: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045725061 ecr 2045725059], length 0 12:34:06.389642 IP 127.0.0.1.35220 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725061 ecr 2045725061], length 0 12:34:06.389662 IP 127.0.0.1.35220 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045725061 ecr 2045725061], length 0 12:34:06.389786 IP 127.0.0.1.35220 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045725061 ecr 2045725061], length 0 12:34:06.390069 IP 127.0.0.1.35222 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725062 ecr 2045725058], length 245 12:34:06.390094 IP 127.0.0.1.8118 > 127.0.0.1.35222: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725062 ecr 2045725062], length 0 12:34:06.391981 IP 127.0.0.1.8118 > 127.0.0.1.35222: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725064 ecr 2045725062], length 263 12:34:06.392018 IP 127.0.0.1.8118 > 127.0.0.1.35222: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045725064 ecr 2045725062], length 6786 12:34:06.392050 IP 127.0.0.1.8118 > 127.0.0.1.35222: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045725064 ecr 2045725062], length 0 12:34:06.392102 IP 127.0.0.1.35222 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725064 ecr 2045725064], length 0 12:34:06.392123 IP 127.0.0.1.35222 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045725064 ecr 2045725064], length 0 12:34:06.392234 IP 127.0.0.1.35222 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045725064 ecr 2045725064], length 0 12:34:06.392447 IP 127.0.0.1.35224 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725064 ecr 2045725058], length 245 12:34:06.392468 IP 127.0.0.1.8118 > 127.0.0.1.35224: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725064 ecr 2045725064], length 0 12:34:06.392589 IP 127.0.0.1.35226 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725064 ecr 2045725058], length 245 12:34:06.392611 IP 127.0.0.1.8118 > 127.0.0.1.35226: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725064 ecr 2045725064], length 0 12:34:06.393868 IP 127.0.0.1.8118 > 127.0.0.1.35226: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725065 ecr 2045725064], length 263 12:34:06.393899 IP 127.0.0.1.8118 > 127.0.0.1.35226: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045725065 ecr 2045725064], length 6786 12:34:06.393928 IP 127.0.0.1.8118 > 127.0.0.1.35226: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045725066 ecr 2045725064], length 0 12:34:06.393971 IP 127.0.0.1.35226 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725066 ecr 2045725065], length 0 12:34:06.393991 IP 127.0.0.1.35226 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045725066 ecr 2045725065], length 0 12:34:06.394086 IP 127.0.0.1.35226 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045725066 ecr 2045725066], length 0 12:34:06.394193 IP 127.0.0.1.8118 > 127.0.0.1.35224: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725066 ecr 2045725064], length 263 12:34:06.394208 IP 127.0.0.1.35224 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725066 ecr 2045725066], length 0 12:34:06.394234 IP 127.0.0.1.8118 > 127.0.0.1.35224: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045725066 ecr 2045725066], length 6786 12:34:06.394246 IP 127.0.0.1.35224 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045725066 ecr 2045725066], length 0 12:34:06.394269 IP 127.0.0.1.8118 > 127.0.0.1.35224: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045725066 ecr 2045725066], length 0 12:34:06.394292 IP 127.0.0.1.35224 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045725066 ecr 2045725066], length 0 12:34:06.394404 IP 127.0.0.1.35228 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725066 ecr 2045725059], length 245 12:34:06.394423 IP 127.0.0.1.8118 > 127.0.0.1.35228: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725066 ecr 2045725066], length 0 12:34:06.399068 IP 127.0.0.1.8118 > 127.0.0.1.35228: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725071 ecr 2045725066], length 263 12:34:06.399109 IP 127.0.0.1.35228 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725071 ecr 2045725071], length 0 12:34:06.399161 IP 127.0.0.1.8118 > 127.0.0.1.35228: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045725071 ecr 2045725071], length 6786 12:34:06.404416 IP 127.0.0.1.35228 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045725076 ecr 2045725071], length 0 12:34:06.437256 IP 127.0.0.1.35230 > 127.0.0.1.8118: Flags [S], seq 2990320456, win 43690, options [mss 65495,sackOK,TS val 2045725109 ecr 0,nop,wscale 7], length 0 12:34:06.437300 IP 127.0.0.1.8118 > 127.0.0.1.35230: Flags [S.], seq 487364622, ack 2990320457, win 43690, options [mss 65495,sackOK,TS val 2045725109 ecr 2045725109,nop,wscale 7], length 0 12:34:06.437331 IP 127.0.0.1.35230 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725109 ecr 2045725109], length 0 12:34:06.437877 IP 127.0.0.1.35230 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725109 ecr 2045725109], length 245 12:34:06.437900 IP 127.0.0.1.8118 > 127.0.0.1.35230: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725109 ecr 2045725109], length 0 12:34:06.439870 IP 127.0.0.1.8118 > 127.0.0.1.35230: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725111 ecr 2045725109], length 263 12:34:06.439896 IP 127.0.0.1.35230 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725111 ecr 2045725111], length 0 12:34:06.439931 IP 127.0.0.1.8118 > 127.0.0.1.35230: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045725112 ecr 2045725111], length 6786 12:34:06.441052 IP 127.0.0.1.8118 > 127.0.0.1.35234: Flags [S.], seq 4156255386, ack 1134912242, win 43690, options [mss 65495,sackOK,TS val 2045725113 ecr 2045725113,nop,wscale 7], length 0 12:34:06.441070 IP 127.0.0.1.35234 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725113 ecr 2045725113], length 0 12:34:06.441331 IP 127.0.0.1.35236 > 127.0.0.1.8118: Flags [S], seq 3583643916, win 43690, options [mss 65495,sackOK,TS val 2045725113 ecr 0,nop,wscale 7], length 0 12:34:06.441349 IP 127.0.0.1.8118 > 127.0.0.1.35236: Flags [S.], seq 3687982361, ack 3583643917, win 43690, options [mss 65495,sackOK,TS val 2045725113 ecr 2045725113,nop,wscale 7], length 0 12:34:06.441366 IP 127.0.0.1.35236 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725113 ecr 2045725113], length 0 12:34:06.441860 IP 127.0.0.1.35232 > 127.0.0.1.8118: Flags [P.], seq 937091709:937091954, ack 4169035702, win 342, options [nop,nop,TS val 2045725113 ecr 2045725112], length 245 12:34:06.441884 IP 127.0.0.1.8118 > 127.0.0.1.35232: Flags [.], ack 245, win 350, options [nop,nop,TS val 2045725113 ecr 2045725113], length 0 12:34:06.441981 IP 127.0.0.1.35234 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725114 ecr 2045725113], length 245 12:34:06.441994 IP 127.0.0.1.8118 > 127.0.0.1.35234: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725114 ecr 2045725114], length 0 12:34:06.442074 IP 127.0.0.1.35236 > 127.0.0.1.8118: Flags [P.], seq 1:246, ack 1, win 342, options [nop,nop,TS val 2045725114 ecr 2045725113], length 245 12:34:06.442091 IP 127.0.0.1.8118 > 127.0.0.1.35236: Flags [.], ack 246, win 350, options [nop,nop,TS val 2045725114 ecr 2045725114], length 0 12:34:06.443863 IP 127.0.0.1.8118 > 127.0.0.1.35232: Flags [P.], seq 1:264, ack 245, win 350, options [nop,nop,TS val 2045725115 ecr 2045725113], length 263 12:34:06.443888 IP 127.0.0.1.35232 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725115 ecr 2045725115], length 0 12:34:06.443996 IP 127.0.0.1.8118 > 127.0.0.1.35232: Flags [P.], seq 264:7050, ack 245, win 350, options [nop,nop,TS val 2045725116 ecr 2045725115], length 6786 12:34:06.444011 IP 127.0.0.1.35232 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045725116 ecr 2045725116], length 0 12:34:06.444086 IP 127.0.0.1.8118 > 127.0.0.1.35232: Flags [F.], seq 7050, ack 245, win 350, options [nop,nop,TS val 2045725116 ecr 2045725116], length 0 12:34:06.449206 IP 127.0.0.1.8118 > 127.0.0.1.35234: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725121 ecr 2045725114], length 263 12:34:06.449232 IP 127.0.0.1.35234 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725121 ecr 2045725121], length 0 12:34:06.449277 IP 127.0.0.1.8118 > 127.0.0.1.35234: Flags [P.], seq 264:7050, ack 246, win 350, options [nop,nop,TS val 2045725121 ecr 2045725121], length 6786 12:34:06.449292 IP 127.0.0.1.35234 > 127.0.0.1.8118: Flags [.], ack 7050, win 1373, options [nop,nop,TS val 2045725121 ecr 2045725121], length 0 12:34:06.449319 IP 127.0.0.1.8118 > 127.0.0.1.35234: Flags [F.], seq 7050, ack 246, win 350, options [nop,nop,TS val 2045725121 ecr 2045725121], length 0 12:34:06.449395 IP 127.0.0.1.35232 > 127.0.0.1.8118: Flags [R.], seq 245, ack 7051, win 1373, options [nop,nop,TS val 2045725121 ecr 2045725116], length 0 12:34:06.449624 IP 127.0.0.1.35234 > 127.0.0.1.8118: Flags [R.], seq 246, ack 7051, win 1373, options [nop,nop,TS val 2045725121 ecr 2045725121], length 0 12:34:06.450348 IP 127.0.0.1.8118 > 127.0.0.1.35236: Flags [P.], seq 1:264, ack 246, win 350, options [nop,nop,TS val 2045725122 ecr 2045725114], length 263 12:34:06.586853 IP 127.0.0.1.35238 > 127.0.0.1.8118: Flags [S], seq 592326796, win 43690, options [mss 65495,sackOK,TS val 2045725258 ecr 0,nop,wscale 7], length 0 12:34:06.586891 IP 127.0.0.1.8118 > 127.0.0.1.35238: Flags [S.], seq 2113459585, ack 592326797, win 43690, options [mss 65495,sackOK,TS val 2045725258 ecr 2045725258,nop,wscale 7], length 0 12:34:06.586919 IP 127.0.0.1.35238 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725259 ecr 2045725258], length 0 12:34:06.587382 IP 127.0.0.1.35238 > 127.0.0.1.8118: Flags [P.], seq 1:224, ack 1, win 342, options [nop,nop,TS val 2045725259 ecr 2045725258], length 223 12:34:06.587414 IP 127.0.0.1.8118 > 127.0.0.1.35238: Flags [.], ack 224, win 350, options [nop,nop,TS val 2045725259 ecr 2045725259], length 0 12:34:06.587791 IP 127.0.0.1.35240 > 127.0.0.1.8118: Flags [S], seq 4177873420, win 43690, options [mss 65495,sackOK,TS val 2045725259 ecr 0,nop,wscale 7], length 0 12:34:06.587818 IP 127.0.0.1.8118 > 127.0.0.1.35240: Flags [S.], seq 673182586, ack 4177873421, win 43690, options [mss 65495,sackOK,TS val 2045725259 ecr 2045725259,nop,wscale 7], length 0 12:34:06.587839 IP 127.0.0.1.35240 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045725259 ecr 2045725259], length 0 12:34:06.588514 IP 127.0.0.1.35240 > 127.0.0.1.8118: Flags [P.], seq 1:224, ack 1, win 342, options [nop,nop,TS val 2045725260 ecr 2045725259], length 223 12:34:06.588536 IP 127.0.0.1.8118 > 127.0.0.1.35240: Flags [.], ack 224, win 350, options [nop,nop,TS val 2045725260 ecr 2045725260], length 0 12:34:06.590677 IP 127.0.0.1.8118 > 127.0.0.1.35240: Flags [P.], seq 1:264, ack 224, win 350, options [nop,nop,TS val 2045725262 ecr 2045725260], length 263 12:34:06.590712 IP 127.0.0.1.35240 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725262 ecr 2045725262], length 0 12:34:06.590756 IP 127.0.0.1.8118 > 127.0.0.1.35240: Flags [P.], seq 264:7006, ack 224, win 350, options [nop,nop,TS val 2045725262 ecr 2045725262], length 6742 12:34:06.590780 IP 127.0.0.1.35240 > 127.0.0.1.8118: Flags [.], ack 7006, win 1373, options [nop,nop,TS val 2045725262 ecr 2045725262], length 0 12:34:06.590813 IP 127.0.0.1.8118 > 127.0.0.1.35240: Flags [F.], seq 7006, ack 224, win 350, options [nop,nop,TS val 2045725262 ecr 2045725262], length 0 12:34:06.591253 IP 127.0.0.1.35240 > 127.0.0.1.8118: Flags [R.], seq 224, ack 7007, win 1373, options [nop,nop,TS val 2045725263 ecr 2045725262], length 0 12:34:06.591398 IP 127.0.0.1.8118 > 127.0.0.1.35238: Flags [P.], seq 1:264, ack 224, win 350, options [nop,nop,TS val 2045725263 ecr 2045725259], length 263 12:34:06.591416 IP 127.0.0.1.35238 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045725263 ecr 2045725263], length 0 12:34:06.591450 IP 127.0.0.1.8118 > 127.0.0.1.35238: Flags [P.], seq 264:7006, ack 224, win 350, options [nop,nop,TS val 2045725263 ecr 2045725263], length 6742 12:34:06.591465 IP 127.0.0.1.35238 > 127.0.0.1.8118: Flags [.], ack 7006, win 1373, options [nop,nop,TS val 2045725263 ecr 2045725263], length 0 12:34:06.591494 IP 127.0.0.1.8118 > 127.0.0.1.35238: Flags [F.], seq 7006, ack 224, win 350, options [nop,nop,TS val 2045725263 ecr 2045725263], length 0 12:34:06.591527 IP 127.0.0.1.35238 > 127.0.0.1.8118: Flags [R.], seq 224, ack 7007, win 1373, options [nop,nop,TS val 2045725263 ecr 2045725263], length 0 12:34:07.368652 IP 127.0.0.1.35242 > 127.0.0.1.8118: Flags [S], seq 1176741888, win 43690, options [mss 65495,sackOK,TS val 2045726040 ecr 0,nop,wscale 7], length 0 12:34:07.368717 IP 127.0.0.1.8118 > 127.0.0.1.35242: Flags [S.], seq 3407348833, ack 1176741889, win 43690, options [mss 65495,sackOK,TS val 2045726040 ecr 2045726040,nop,wscale 7], length 0 12:34:07.368760 IP 127.0.0.1.35242 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045726040 ecr 2045726040], length 0 12:34:07.369306 IP 127.0.0.1.35242 > 127.0.0.1.8118: Flags [P.], seq 1:228, ack 1, win 342, options [nop,nop,TS val 2045726041 ecr 2045726040], length 227 12:34:07.369333 IP 127.0.0.1.8118 > 127.0.0.1.35242: Flags [.], ack 228, win 350, options [nop,nop,TS val 2045726041 ecr 2045726041], length 0 12:34:07.371142 IP 127.0.0.1.8118 > 127.0.0.1.35242: Flags [P.], seq 1:264, ack 228, win 350, options [nop,nop,TS val 2045726043 ecr 2045726041], length 263 12:34:07.371168 IP 127.0.0.1.35242 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045726043 ecr 2045726043], length 0 12:34:07.371216 IP 127.0.0.1.8118 > 127.0.0.1.35242: Flags [P.], seq 264:7014, ack 228, win 350, options [nop,nop,TS val 2045726043 ecr 2045726043], length 6750 12:34:07.371233 IP 127.0.0.1.35242 > 127.0.0.1.8118: Flags [.], ack 7014, win 1373, options [nop,nop,TS val 2045726043 ecr 2045726043], length 0 12:34:07.371271 IP 127.0.0.1.8118 > 127.0.0.1.35242: Flags [F.], seq 7014, ack 228, win 350, options [nop,nop,TS val 2045726043 ecr 2045726043], length 0 12:34:07.371334 IP 127.0.0.1.35242 > 127.0.0.1.8118: Flags [R.], seq 228, ack 7015, win 1373, options [nop,nop,TS val 2045726043 ecr 2045726043], length 0 12:34:07.389494 IP 127.0.0.1.35244 > 127.0.0.1.8118: Flags [S], seq 277694261, win 43690, options [mss 65495,sackOK,TS val 2045726061 ecr 0,nop,wscale 7], length 0 12:34:07.389541 IP 127.0.0.1.8118 > 127.0.0.1.35244: Flags [S.], seq 2596598257, ack 277694262, win 43690, options [mss 65495,sackOK,TS val 2045726061 ecr 2045726061,nop,wscale 7], length 0 12:34:07.389577 IP 127.0.0.1.35244 > 127.0.0.1.8118: Flags [.], ack 1, win 342, options [nop,nop,TS val 2045726061 ecr 2045726061], length 0 12:34:07.390101 IP 127.0.0.1.35244 > 127.0.0.1.8118: Flags [P.], seq 1:230, ack 1, win 342, options [nop,nop,TS val 2045726062 ecr 2045726061], length 229 12:34:07.390128 IP 127.0.0.1.8118 > 127.0.0.1.35244: Flags [.], ack 230, win 350, options [nop,nop,TS val 2045726062 ecr 2045726062], length 0 12:34:07.392039 IP 127.0.0.1.8118 > 127.0.0.1.35244: Flags [P.], seq 1:264, ack 230, win 350, options [nop,nop,TS val 2045726064 ecr 2045726062], length 263 12:34:07.392067 IP 127.0.0.1.35244 > 127.0.0.1.8118: Flags [.], ack 264, win 350, options [nop,nop,TS val 2045726064 ecr 2045726064], length 0 12:34:07.392109 IP 127.0.0.1.8118 > 127.0.0.1.35244: Flags [P.], seq 264:7018, ack 230, win 350, options [nop,nop,TS val 2045726064 ecr 2045726064], length 6754 12:34:07.392125 IP 127.0.0.1.35244 > 127.0.0.1.8118: Flags [.], ack 7018, win 1373, options [nop,nop,TS val 2045726064 ecr 2045726064], length 0 12:34:07.392155 IP 127.0.0.1.8118 > 127.0.0.1.35244: Flags [F.], seq 7018, ack 230, win 350, options [nop,nop,TS val 2045726064 ecr 2045726064], length 0 12:34:07.392304 IP 127.0.0.1.35244 > 127.0.0.1.8118: Flags [R.], seq 230, ack 7019, win 1373, options [nop,nop,TS val 2045726064 ecr 2045726064], length 0 To be honest, I do not really understand the output. It is not functional but for some reasons it interacts. I would be thankful for some educational advice here. Page opened was weathercom. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
O.K. I installed tcpdump (and thank you for the program, very useful).
tcpdump is probably my favourite utility :-)
So the system proxy in KDE is set to use privoxy. But it does not work as when I do set: use systemproxy in falcon, then the result is silence.
Okay, it sounds like it should work, but at least it's a different issue.
When I do set manually http:// to 127.0.0.1 and 8118 which are the default settings of privoxy it does not open any page, but it calls it. Albeit there is something odd again, why it call on port 35234 too????
[snip tcpdump] This looks good - your browser is talking to privoxy, the first two lines show a connection between port 35198 to 8118 being requested and acknowledged. A little later, there is new connection from 35200, looks good. To really know what is being exchanged, wireshark is useful, but this is good enough for now.
To be honest, I do not really understand the output. It is not functional but for some reasons it interacts.
Yes, you need a decent understanding of tcp/ip to read the output in detail, but like you say, your browser is at least interacting with privoxy interacts. I would suggest another tcpdump - tcpdump -n -i eth0 host 23.50.104.180 Replace 'eth0' with whatever is your main interface, maybe wlan0. 23.50.104.180 is weather.com. This will hopefully show traffic to and from 23.50.104.180, from your 192.168 address. -- Per Jessen, Zürich (8.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
O.K. I installed tcpdump (and thank you for the program, very useful).
tcpdump is probably my favourite utility :-)
So the system proxy in KDE is set to use privoxy. But it does not work as when I do set: use systemproxy in falcon, then the result is silence.
Okay, it sounds like it should work, but at least it's a different issue.
When I do set manually http:// to 127.0.0.1 and 8118 which are the default settings of privoxy it does not open any page, but it calls it. Albeit there is something odd again, why it call on port 35234 too????
[snip tcpdump]
This looks good - your browser is talking to privoxy, the first two lines show a connection between port 35198 to 8118 being requested and acknowledged. A little later, there is new connection from 35200, looks good. To really know what is being exchanged, wireshark is useful, but this is good enough for now.
To be honest, I do not really understand the output. It is not functional but for some reasons it interacts.
Yes, you need a decent understanding of tcp/ip to read the output in detail, but like you say, your browser is at least interacting with privoxy interacts.
I would suggest another tcpdump -
tcpdump -n -i eth0 host 23.50.104.180
Replace 'eth0' with whatever is your main interface, maybe wlan0. 23.50.104.180 is weather.com.
This will hopefully show traffic to and from 23.50.104.180, from your 192.168 address. And that fails: tcpdump -n -i wlan1 host 23.50.104.180 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
In data sabato 24 novembre 2018 13:32:28 CET, Per Jessen ha scritto: listening on wlan1, link-type EN10MB (Ethernet), capture size 262144 bytes The browser shows ERR_TUNNEL_CONNECTION_FAILED _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data sabato 24 novembre 2018 13:32:28 CET, Per Jessen ha scritto:
stakanov wrote:
O.K. I installed tcpdump (and thank you for the program, very useful).
tcpdump is probably my favourite utility :-)
So the system proxy in KDE is set to use privoxy. But it does not work as when I do set: use systemproxy in falcon, then the result is silence.
Okay, it sounds like it should work, but at least it's a different issue.
When I do set manually http:// to 127.0.0.1 and 8118 which are the default settings of privoxy it does not open any page, but it calls it. Albeit there is something odd again, why it call on port 35234 too????
[snip tcpdump]
This looks good - your browser is talking to privoxy, the first two lines show a connection between port 35198 to 8118 being requested and acknowledged. A little later, there is new connection from 35200, looks good. To really know what is being exchanged, wireshark is useful, but this is good enough for now.
To be honest, I do not really understand the output. It is not functional but for some reasons it interacts.
Yes, you need a decent understanding of tcp/ip to read the output in detail, but like you say, your browser is at least interacting with privoxy interacts.
I would suggest another tcpdump -
tcpdump -n -i eth0 host 23.50.104.180
Replace 'eth0' with whatever is your main interface, maybe wlan0. 23.50.104.180 is weather.com.
This will hopefully show traffic to and from 23.50.104.180, from your 192.168 address.
And that fails: tcpdump -n -i wlan1 host 23.50.104.180 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on wlan1, link-type EN10MB (Ethernet), capture size 262144 bytes
You went to weather.com and wlan1 is your default route - 'ip route show' ?
The browser shows ERR_TUNNEL_CONNECTION_FAILED
Try some other websites maybe. https://www.dns24.ch/ (185.85.251.249). -- Per Jessen, Zürich (8.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data sabato 24 novembre 2018 13:49:22 CET, Per Jessen ha scritto:
stakanov wrote:
In data sabato 24 novembre 2018 13:32:28 CET, Per Jessen ha scritto:
stakanov wrote:
O.K. I installed tcpdump (and thank you for the program, very useful).
tcpdump is probably my favourite utility :-)
So the system proxy in KDE is set to use privoxy. But it does not work as when I do set: use systemproxy in falcon, then the result is silence.
Okay, it sounds like it should work, but at least it's a different issue.
When I do set manually http:// to 127.0.0.1 and 8118 which are the default settings of privoxy it does not open any page, but it calls it. Albeit there is something odd again, why it call on port 35234 too????
[snip tcpdump]
This looks good - your browser is talking to privoxy, the first two lines show a connection between port 35198 to 8118 being requested and acknowledged. A little later, there is new connection from 35200, looks good. To really know what is being exchanged, wireshark is useful, but this is good enough for now.
To be honest, I do not really understand the output. It is not functional but for some reasons it interacts.
Yes, you need a decent understanding of tcp/ip to read the output in detail, but like you say, your browser is at least interacting with privoxy interacts.
I would suggest another tcpdump -
tcpdump -n -i eth0 host 23.50.104.180
Replace 'eth0' with whatever is your main interface, maybe wlan0. 23.50.104.180 is weather.com.
This will hopefully show traffic to and from 23.50.104.180, from your 192.168 address.
And that fails: tcpdump -n -i wlan1 host 23.50.104.180 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on wlan1, link-type EN10MB (Ethernet), capture size 262144 bytes
You went to weather.com and wlan1 is your default route - 'ip route show' ?
The browser shows ERR_TUNNEL_CONNECTION_FAILED
Try some other websites maybe. https://www.dns24.ch/ (185.85.251.249).
ip route show default via 192.168.50.1 dev wlan1 proto dhcp metric 600 192.168.50.0/24 dev wlan1 proto kernel scope link src 192.168.50.37 metric 600 the command gives: tcpdump -n -i wlan1 host 185.85.251.249 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on wlan1, link-type EN10MB (Ethernet), capture size 262144 bytes And that is what is it all about. In the browser: Impossibile raggiungere il sito La pagina web all'indirizzo https://www.dns24.ch/ potrebbe essere temporaneamente non disponibile oppure è stata permanentemente spostata a un nuovo indirizzo web. ERR_TUNNEL_CONNECTION_FAILED still from privoxy all should be O.K.: sudo systemctl status privoxy.service privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2018-11-24 09:09:30 CET; 5h 26min ago Process: 2778 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/ SUCCESS) Process: 1834 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/ privoxy.pid --user privoxy /etc/config (code=exited, sta> Process: 1830 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/ libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exi> Process: 1824 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc> Main PID: 1840 (privoxy) Tasks: 1 (limit: 4915) CGroup: /system.slice/privoxy.service └─1840 /usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config nov 24 09:09:29 roadrunner systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... nov 24 09:09:30 roadrunner systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities. nov 24 09:10:31 roadrunner.suse systemd[1]: Reloading Privoxy Web Proxy With Advanced Filtering Capabilities. nov 24 09:10:31 roadrunner.suse systemd[1]: Reloaded Privoxy Web Proxy With Advanced Filtering Capabilities. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
ip route show default via 192.168.50.1 dev wlan1 proto dhcp metric 600 192.168.50.0/24 dev wlan1 proto kernel scope link src 192.168.50.37 metric 600
Okay, all good.
the command gives: tcpdump -n -i wlan1 host 185.85.251.249 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on wlan1, link-type EN10MB (Ethernet), capture size 262144 bytes
And that is what is it all about. In the browser:
So no outgoing traffic. I'm guessing there is some config missing after all.
Impossibile raggiungere il sito
La pagina web all'indirizzo https://www.dns24.ch/ potrebbe essere temporaneamente non disponibile oppure è stata permanentemente spostata a un nuovo indirizzo web. ERR_TUNNEL_CONNECTION_FAILED
Yes, I saw that - I googled it and it essentially says the browser cannot connect to the proxy. Apparently, you can connect to the proxy using: http://config.privoxy.org http://config.privoxy.org/show-status My guess is you need a rule that say "allow all" or something like that. -- Per Jessen, Zürich (5.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 11/24/2018 07:32 AM, Per Jessen wrote:
tcpdump is probably my favourite utility :-)
I prefer Wireshark.
Difficult to run when you don't have X. :-) But sure, wireshark is great for browsing a packet capture. -- Per Jessen, Zürich (6.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/24/2018 12:47 PM, Per Jessen wrote:
I prefer Wireshark. Difficult to run when you don't have X. :-)
But sure, wireshark is great for browsing a packet capture.
I bought a cheap managed Gb switch, which I configured for port mirroring. I can then insert the switch between the devices and use my notebook computer to monitor the traffic. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/11/2018 15.34, stakanov wrote:
In data venerdì 23 novembre 2018 12:38:16 CET, Per Jessen ha scritto:
stakanov wrote:
In data venerdì 23 novembre 2018 11:51:50 CET, Carlos E. R. ha
scritto:
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile.
I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it.
That is weird. Privoxy should write to var/log/privoxy when nothing set, and this is mandatory. But in /var/log there is not log. So probably diverted to journalctl but journalctl does not report errors.... sudo dmesg clean, just a lot of martians from multicast... nothing else.
Maybe it doesn't get far enough to be able to start logging. Try starting it from the command line, non-forking and/or in debug mode, with the appropriate arguments. roadrunner:~ # sudo privoxy --no-daemon 2018-11-23 15:30:07.480 7fea5458ff00 Info: Privoxy version 3.0.26 2018-11-23 15:30:07.480 7fea5458ff00 Info: Program name: privoxy 2018-11-23 15:30:07.480 7fea5458ff00 Fatal error: can't check configuration file '/root/config': No such file or directory
Notice that you do not need "sudo" here, you are already root. Try without.
With sudo this is worse
sudo privoxy --no-daemon 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Privoxy version 3.0.26 2018-11-23 15:29:16.102 7fb7a4624f00 Info: Program name: privoxy 2018-11-23 15:29:16.102 7fb7a4624f00 Fatal error: can't check configuration file '/home/entropia/config': No such file or directory
So I tried:
sudo systemctl status privoxy.service
Just make yourself root, and get rid of sudo. One less interference. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 23/11/2018 12.02, stakanov wrote:
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile. I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it. That is weird. Privoxy should write to var/log/privoxy when nothing set, and
In data venerdì 23 novembre 2018 11:51:50 CET, Carlos E. R. ha scritto: this is mandatory. But in /var/log there is not log. So probably diverted to journalctl but journalctl does not report errors.... sudo dmesg clean, just a lot of martians from multicast... nothing else.
No, that means that it doesn't even start. You could explicitly specify writing to /var/log/privoxy just in case, though. Run "aa-logprof" to check that apparmor does not interfere. It is running in a chroot. You might disable that temporarily to investigate. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
In data venerdì 23 novembre 2018 12:43:15 CET, Carlos E. R. ha scritto:
aa-logprof Thanks for the heads up.
sudo aa-logprof [sudo] password di root: Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. /var/log/apparmor is empty I will try to read through the necessary arguments to start privoxy in debug. Have to install the packages and get cultured. @Per Jessen: thank you for the input. Will try _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
James Knott -
Patrick Shanahan -
Per Jessen -
stakanov