June 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Where to report bad mirrors?
by Carlos E. R. 12 Jun '19

12 Jun '19

This mirror is too slow: --2019-06-10 19:17:10-- http://download.opensuse.org/update/leap/15.1/oss/x86_64/kernel-default-dev… Connecting to download.opensuse.org (download.opensuse.org)|195.135.221.134|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://ftp.rnl.tecnico.ulisboa.pt/pub/opensuse/update/leap/15.1/oss/x86_64/… [following] --2019-06-10 19:17:11-- http://ftp.rnl.tecnico.ulisboa.pt/pub/opensuse/update/leap/15.1/oss/x86_64/… Connecting to ftp.rnl.tecnico.ulisboa.pt (ftp.rnl.tecnico.ulisboa.pt)|193.136.164.6|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 8314408 (7,9M) [application/x-redhat-package-manager] Saving to: ‘kernel-default-devel-4.12.14-lp151.28.4.1.x86_64.rpm’ kernel-default-devel-4.12.14-lp151.28.4.1.x86_64.r 98%[==========================================================================================================> ] 7,78M 325KB/s eta 1s Whom do I report it to, admin(a)o.o? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

5 38

[opensuse] Trying to create a new virtual 15.1 machine under virtualbox hangs
by Carlos E. R. 12 Jun '19

12 Jun '19

Hi, Trying to create a new virtual 15.1 machine under vmware hangs when it gets to the phase "System Role". I selected "Generic Desktop" and it hangs with 100% CPU load (seen on the host) on its single core. Remote repos were enabled. The machine has 1GB ram assigned (the default), I'll try 2 GB. [...] Yes, it works. So Leap 15.1 doesn't install with the default 1 GB RAM. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

3 4

[opensuse] Trying to use aria2c instead of wget to download a pattern of files from a site
by Carlos E. R. 11 Jun '19

11 Jun '19

Ok, the goal is to download these patterns: "kernel*rpm" "nfs-kernel*rpm" "virtualbox*rpm" from "http://download.opensuse.org/update/leap/15.1/oss/x86_64/" The advantage with aria2c is that it talks to the MirrorBrain and downloads from several severs at max speed. The problem is that aria2c doesn't do recursive or pattern listing of the site. I mean, that I would have to download the index.html file and parse it to obtain the exact names to then feed aria2c. That is too much for me. Somebody has done this before? -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))

4 7

[opensuse] How can I deactivate Polari and pidgin?
by Carlos E. R. 11 Jun '19

11 Jun '19

Hi, One day I tried Polari, did not like it, and exited. But the system tries to start it it continuously: <3.6> 2019-06-11 00:29:30 Telcontar dbus-daemon 4312 - - [session uid=1000 pid=4312] Activating service name='org.freedesktop.Telepathy.Client.Polari' requested by ':1.84' (uid=1000 pid=5224 comm="/usr/lib/mission-control-5 ") <3.6> 2019-06-11 00:29:30 Telcontar dbus-daemon 4312 - - [session uid=1000 pid=4312] Activated service 'org.freedesktop.Telepathy.Client.Polari' failed: Failed to execute program org.freedesktop.Telepathy.Client.Polari: No such file or directory I had to do: mv /usr/bin/polari /usr/bin/polari.no to stop it running, but as you see something tries to start it again for days and days. Not finding it, the system tried to run /usr/bin/pidgin, which I also had to rename as /usr/bin/pidgin.no. Or the other way round, I do not remember which order I tried them, and now they refuse to cease starting. Unless I rename them to *.no, they start and impede empathy from connecting, because they register my nick first. I use XFCE on Leap 15.0. As IRC client I'm using empathy. cer@Telcontar:~> killall mission-control-5 cer@Telcontar:~> killall mission-control-5 cer@Telcontar:~> killall mission-control-5 cer@Telcontar:~> killall -9 mission-control-5 cer@Telcontar:~> killall -9 mission-control-5 cer@Telcontar:~> killall -9 mission-control-5 cer@Telcontar:~> Can't be killed! Seems to belong to "telepathy-mission-control-5.16.3-lp150.3.1.x86_64" Mission Control, or MC, is a Telepathy component providing a way for "end-user" applications to abstract some of the details of connection managers, to provide a simple way to manipulate a bunch of connection managers at once, to remove the need to have in each program the account definitions and credentials, to manage channel handling/request and to manage presence statuses. Distribution: openSUSE Leap 15.0 cer@Telcontar:~> rpm --erase telepathy-mission-control-5.16.3-lp150.3.1.x86_64 error: Failed dependencies: telepathy-mission-control is needed by (installed) polari-3.26.2-lp150.1.6.x86_64 telepathy-mission-control is needed by (installed) empathy-3.12.14-lp150.6.1.x86_64 telepathy-mission-control is needed by (installed) telepathy-mission-control-plugin-goa-3.12.14-lp150.6.1.x86_64 cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

3 6

[opensuse] glibc version
by Roger Oberholtzer 11 Jun '19

11 Jun '19

I have an openSUSE 42.3 system on which I am trying to run some libraries compiled for Ubuntu. They are for Z+F lasers (https://www.zf-laser.com/Home.91.0.html?&L=1) not that this is important. But they are starting to add Linux support for their devices. Generally, lots of things work. The only issue is that some of the libraries want a newer version of glibc. openSUSE 42.3 uses 2.22, and these libraries want 2.27. I know that glibc supports various versions at the same time. I guess it is part of the install. That is, IIUC, version 2.22 supports that release, as well as some earlier versions. One does not have different versions of the RPM installed. I think I know the answer to this, but is it possible to update glibc to version 2.27 on openSUSE 42.3? I'm okay if it is in some parallel directory that only these libraries/binaries know about. Has anyone done this kind of thing? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Question about iptables and port forward masquerading
by Marc Chamberlin 11 Jun '19

11 Jun '19

Hi - I dunno if this is a good group to ask this question but I will give it a shot and perhaps get pointed to a better group... I am running the Apache James email server on an OpenSuSE 15.0 x64 system and because of some other requirements I have to run the James daemon under a system user name and not under root. To accomplish that I had to change all the standard email ports that it listens on, to higher ones (I added 10000 to the standard port numbers so for example instead of having the smtp server listen on port 25 I configured it to listen on port 10025. Then using SuSEfirewall2 I configured it to do forward masquerading to route connections from port 25 to port 10025. So for example, and in particular for localhost which is shown here, I did the following - (sorry about the formatting, Thunderbird seems to be making choices that I don't want and I haven't got the time to figure out how to tell Thunderbird to knock it off!.) FW_FORWARD_MASQ=" ... \ (ext and int interface routing not shown but it is similar to what is shown below for localhost) 0/0,127.0.0.1,tcp,25,10025,127.0.0.1 \ 0/0,127.0.0.1,tcp,465,10465,127.0.0.1 \ 0/0,127.0.0.1,tcp,587,10587,127.0.0.1 \ 0/0,127.0.0.1,tcp,110,10110,127.0.0.1 \ 0/0,127.0.0.1,tcp,995,10995,127.0.0.1 \ 0/0,127.0.0.1,tcp,143,10143,127.0.0.1 \ 0/0,127.0.0.1,tcp,993,10993,127.0.0.1" The server is not protected from the internal network (this is a SOHO net) and all the external ports are opened. From either the internal network, or from the external network I can use telnet to connect to either the low number ports or the high numbered ports successfully. But from the localhost I can only connect to the high numbered ports. Connecting to the low number ports, such as 25, gets me a Connection Refused message when I try and do a 'telnet localhost 25'. ('telnet localhost 10025' works!) Using netstat shows that indeed Apache James (a java application) is listening on for example port 10025 - netstat -plnt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:10025 0.0.0.0:* LISTEN 25012/java and from a snip of the iptables I see this - iptables -t nat -vnL Chain PREROUTING (policy ACCEPT 226K packets, 15M bytes) pkts bytes target prot opt in out source destination (lots of other stuff removed, in particular the external interface as I don't want to show the IP addresses, but here is a bit showing some of the internal interface) 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 0 0 DNAT tcp -- lo * 0.0.0.0/0 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 22 1320 DNAT tcp -- p3p1 * 0.0.0.0/0 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 0 0 DNAT tcp -- tun0 * 0.0.0.0/0 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 192.168.10.100 tcp dpt:465 to:192.168.10.100:10465 0 0 DNAT tcp -- lo * 0.0.0.0/0 192.168.10.100 tcp dpt:465 to:192.168.10.100:10465 9 468 DNAT tcp -- p3p1 * 0.0.0.0/0 192.168.10.100 tcp dpt:465 to:192.168.10.100:10465 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 192.168.10.100 tcp dpt:465 to:192.168.10.100:10465 (and here is some of the things showing the localhost interface) 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 0 0 DNAT tcp -- lo * 0.0.0.0/0 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 0 0 DNAT tcp -- p3p1 * 0.0.0.0/0 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 0 0 DNAT tcp -- tun0 * 0.0.0.0/0 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 0 0 DNAT tcp -- lo * 0.0.0.0/0 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 0 0 DNAT tcp -- p3p1 * 0.0.0.0/0 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 0 0 DNAT tcp -- tun0 * 0.0.0.0/0 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 0 0 DNAT tcp -- lo * 0.0.0.0/0 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 0 0 DNAT tcp -- p3p1 * 0.0.0.0/0 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 0 0 DNAT tcp -- tun0 * 0.0.0.0/0 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 127.0.0.1 tcp dpt:110 to:127.0.0.1:10110 0 0 DNAT tcp -- lo * 0.0.0.0/0 127.0.0.1 tcp dpt:110 to:127.0.0.1:10110 0 0 DNAT tcp -- p3p1 * 0.0.0.0/0 127.0.0.1 tcp dpt:110 to:127.0.0.1:10110 yada yada yada... So what am I missing? It is important that I get localhost to accept connections on the low ports since I am using other tools, such as sendmail (in non-daemon mode) and I want it to use Apache James as it's MTA. Yet I cannot get connections to the low ports on localhost to work, but I am doing exactly the same sort of setup for the internal and external interfaces and there everything does work! Thanks in advance for any thoughts and ideas. I will be happy to provide more information, just ask! Marc.. -- --... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-. Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] A user writable directory in /run, security implications?
by Robert Hardy 11 Jun '19

11 Jun '19

For years, I have been using a user run script that globally adjusts the display for various lighting conditions (reproduced below). It writes a couple of files in the users home directory to save state, and it has always annoyed me that the globally saved state is not globally available. My thought is to write to a user writable directory in /run, perhaps /run/users, right next to /run/user, but I thought I should check with the experts as to possible security implications. I would also have to instantiate that directory on every boot, and I don't know how off the top of my head. That state is not saved across reboots is a plus. Thoughts? Perhaps such a directory should be available on every system. Here is /usr/local/bin/invert-display: #!/bin/sh if test -f ~/.altered-display; then xcalib -c; if test -f ~/.inverted-display; then rm ~/.altered-display ~/.inverted-display; #normal display else xcalib -red 0.75 0 100 -green 0.75 0 78 -blue 0.75 0 55 -i -a; mv ~/.altered-display ~/.inverted-display; #inverted display fi else if test -f ~/.inverted-display; then xcalib -co 60 -a; #nighttime away from city lights else xcalib -gc 2.2 -a; #high gamma for incident sunlight fi; touch ~/.altered-display; fi; I've used it for years on a laptop that rides around mounted in my car, where it helps deal with varying lighting such as direct sunlight and nighttime use. The idea at night is to minimize total light output so that my eyes can remain dark adapted, so it works best with light background colors. I have lightened the dark parts of the Breeze theme colors to suit, e.g., the active titlebar color matches the color for "Hover Decoration", etc. The script is run by clicking a panel button. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

Re: [opensuse] Question about iptables and port forward masquerading
by Marc Chamberlin 11 Jun '19

11 Jun '19

Aw but Jeffrey you may indeed be partially correct! My own additional research has now found that apparently localhost does not use the PREROUTING chain in the iptables and this is where SuSEfirewall2 is putting these FW_FORWARD_MASQ rules. I think what I have to do is coax SuSEFirewall2 to put the localhost port routing rules in the OUTPUT chain instead. So now the question is how do I do that? Back to Google and searching, hopefully someone here knows and/or will beat me to the answer and share it with this poor lost soul!? ;-) Marc... P.S. Jeffrey had replied privately to me so I have removed identifying information in order to respect that, but wanted to give him kudos and let him and the group see where he has lead me in my search for a solution to this problem. On 6/10/19 6:32 PM, Jeffrey ***** wrote: > My statement is incorrect. > > Sorry, > Jeffrey > > On Mon, Jun 10, 2019, 8:15 PM Jeffrey (email deleted since Jeffery > replied to me privately) wrote: > > I don't think connections to localhost go thru the firewall. > > Jeffrey > > On Mon, Jun 10, 2019, 7:49 PM Marc Chamberlin > <marc(a)marcchamberlin.com <mailto:marc@marcchamberlin.com>> wrote: > > > Hi - I dunno if this is a good group to ask this question but > I will > give it a shot and perhaps get pointed to a better group... > > I am running the Apache James email server on an OpenSuSE 15.0 x64 > system and because of some other requirements I have to run > the James > daemon under a system user name and not under root. To > accomplish that I > had to change all the standard email ports that it listens on, > to higher > ones (I added 10000 to the standard port numbers so for > example instead > of having the smtp server listen on port 25 I configured it to > listen on > port 10025. Then using SuSEfirewall2 I configured it to do forward > masquerading to route connections from port 25 to port 10025. > So for > example, and in particular for localhost which is shown here, > I did the > following - (sorry about the formatting, Thunderbird seems to > be making > choices > that I don't want and I haven't got the time to figure out how > to tell > Thunderbird to knock it off!.) > > FW_FORWARD_MASQ=" ... \ > (ext and int interface routing not shown but it is similar to > what is > shown below for localhost) > 0/0,127.0.0.1,tcp,25,10025,127.0.0.1 \ > 0/0,127.0.0.1,tcp,465,10465,127.0.0.1 \ > 0/0,127.0.0.1,tcp,587,10587,127.0.0.1 \ > 0/0,127.0.0.1,tcp,110,10110,127.0.0.1 \ > 0/0,127.0.0.1,tcp,995,10995,127.0.0.1 \ > 0/0,127.0.0.1,tcp,143,10143,127.0.0.1 \ > 0/0,127.0.0.1,tcp,993,10993,127.0.0.1" > > The server is not protected from the internal network (this is > a SOHO > net) and all the external ports are opened. From either the > internal > network, or from the external network I can use telnet to > connect to > either the low number ports or the high numbered ports > successfully. But > from the localhost I can only connect to the high numbered ports. > Connecting to the low number ports, such as 25, gets me a > Connection > Refused message when I try and do a 'telnet localhost 25'. > ('telnet > localhost 10025' works!) > > Using netstat shows that indeed Apache James (a java > application) is > listening on for example port 10025 - > > netstat -plnt > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign > Address > State PID/Program name > > tcp 0 0 0.0.0.0:10025 > <http://0.0.0.0:10025> 0.0.0.0:* > LISTEN 25012/java > > and from a snip of the iptables I see this - > > iptables -t nat -vnL > Chain PREROUTING (policy ACCEPT 226K packets, 15M bytes) > pkts bytes target prot opt in out > source > destination > > (lots of other stuff removed, in particular the external > interface as I > don't want to show the IP addresses, but here is a bit showing > some of > the internal interface) > > 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 > <http://192.168.10.100:10025> > 0 0 DNAT tcp -- lo * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 > <http://192.168.10.100:10025> > 22 1320 DNAT tcp -- p3p1 * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 > <http://192.168.10.100:10025> > 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 > <http://192.168.10.100:10025> > 0 0 DNAT tcp -- tun0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:25 to:192.168.10.100:10025 > <http://192.168.10.100:10025> > 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:465 to:192.168.10.100:10465 > <http://192.168.10.100:10465> > 0 0 DNAT tcp -- lo * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:465 to:192.168.10.100:10465 > <http://192.168.10.100:10465> > 9 468 DNAT tcp -- p3p1 * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:465 to:192.168.10.100:10465 > <http://192.168.10.100:10465> > 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 > <http://0.0.0.0/0> > 192.168.10.100 tcp dpt:465 to:192.168.10.100:10465 > <http://192.168.10.100:10465> > > (and here is some of the things showing the localhost interface) > > 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 > <http://127.0.0.1:10025> > 0 0 DNAT tcp -- lo * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 > <http://127.0.0.1:10025> > 0 0 DNAT tcp -- p3p1 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 > <http://127.0.0.1:10025> > 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 > <http://127.0.0.1:10025> > 0 0 DNAT tcp -- tun0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:25 to:127.0.0.1:10025 > <http://127.0.0.1:10025> > 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 > <http://127.0.0.1:10465> > 0 0 DNAT tcp -- lo * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 > <http://127.0.0.1:10465> > 0 0 DNAT tcp -- p3p1 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 > <http://127.0.0.1:10465> > 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 > <http://127.0.0.1:10465> > 0 0 DNAT tcp -- tun0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:465 to:127.0.0.1:10465 > <http://127.0.0.1:10465> > 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 > <http://127.0.0.1:10587> > 0 0 DNAT tcp -- lo * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 > <http://127.0.0.1:10587> > 0 0 DNAT tcp -- p3p1 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 > <http://127.0.0.1:10587> > 0 0 DNAT tcp -- p3p2 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 > <http://127.0.0.1:10587> > 0 0 DNAT tcp -- tun0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:587 to:127.0.0.1:10587 > <http://127.0.0.1:10587> > 0 0 DNAT tcp -- eth0 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:110 to:127.0.0.1:10110 > <http://127.0.0.1:10110> > 0 0 DNAT tcp -- lo * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:110 to:127.0.0.1:10110 > <http://127.0.0.1:10110> > 0 0 DNAT tcp -- p3p1 * 0.0.0.0/0 > <http://0.0.0.0/0> > 127.0.0.1 tcp dpt:110 to:127.0.0.1:10110 > <http://127.0.0.1:10110> > yada yada yada... > > So what am I missing? It is important that I get localhost to > accept > connections on the low ports since I am using other tools, such as > sendmail (in non-daemon mode) and I want it to use Apache > James as it's > MTA. Yet I cannot get connections to the low ports on > localhost to work, > but I am doing exactly the same sort of setup for the internal and > external interfaces and there everything does work! > > Thanks in advance for any thoughts and ideas. I will be happy > to provide > more information, just ask! Marc.. > > -- > > --... ...-- .----. ... -.. . .-- .- --... .--. > -..- .-- -- .- .-. -.-. > Computers: the final frontier. These are the voyages of the > user Marc. His mission: to explore strange new hardware. > To seek out new software and new applications. To boldly > go where no Marc has gone before! > > > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > <mailto:opensuse%2Bunsubscribe@opensuse.org> > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > <mailto:opensuse%2Bowner@opensuse.org> > -- --... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-. Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] How to connect two servers through an Ethernet A/B switch and not change the upstream MAC addy?
by Lew Wolfgang 10 Jun '19

10 Jun '19

Hi Folks, I've got an interesting network configuration problem that I'd like to run by you all. At this time I've got a server that connects to a switch at 1GbE over Cat-6 copper with RJ-45 connections. I don't have admin rights on the switch and it uses MAC address authentication to turn on the port. The server is rather important and contains about 400-TB of data in multiple RAID-6 arrays. I've received authorization to purchase a second "mirror" server to act as a warm spare. They will have a private 192.168 subnet via second Ethernet ports, maybe 10GbE, to synchronize the data on a regular basis between the servers. What's the best way to hook these up? I'm thinking of something like an RJ-45 A/B switch to manually connect one or the other server to the upstream switch. But then, it looks like simple switches just pass through the two back MAC addresses, and I need the A/B switch to present the same MAC to upstream at all times. Could I use macchanger on each of the servers to keep the same MAC presented through the switch? Or is there a better way? Thanks, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 22

[opensuse] About tail -f
by Carlos E. R. 10 Jun '19

10 Jun '19

Hi, I have a bunch of terminals running "tail -f /some/logfile" (directly from the terminal without bash). The problem is that when the logfile is rotated, it does not catch the "new" log. I have to terminate that tail and start another. How could I automate this, another tail program? (on some tail -f terminals I have, rotate works automatically) To be exact, I use this: xfce4-terminal \ --tab --command="/home/cer/bin/terminales_one /var/log/warn" --title="* Warn *" \ --tab --command="/home/cer/bin/terminales_one /var/log/messages" --title=messages \ Where terminales_one is: while true ; do tail -f -n 1000 $1 ; sleep 5 ; done Maybe this is the trick: -f, --follow[={name|descriptor}] output appended data as the file grows; an absent option argument means 'descriptor' -F same as --follow=name --retry So use -F instead? I'm going to try that, but it may take days till I notice if it works or not. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

2 1