LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Upgraded two laptops to Fedora 26 - now cannot connect to remote PostgreSQL (https://www.linuxquestions.org/questions/linux-software-2/upgraded-two-laptops-to-fedora-26-now-cannot-connect-to-remote-postgresql-4175610935/)

Doug Hutcheson 07-30-2017 08:12 PM
Upgraded two laptops to Fedora 26 - now cannot connect to remote PostgreSQL
 
As the subject says, I have upgraded our home network from F25 to F26. I have managed to get local connections to PostgreSQL working, but neither machine can connect to the other's instance.

I can ssh between one machine and the other. I can rsync from one machine to the other. This makes me suspect it is not a network issue.

To test this, I did the following:

Code:
[root@womble data]# telnet ketchup
Trying 192.168.0.101...
telnet: connect to address 192.168.0.101: No route to host
[root@womble data]# route
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
default        gateway        0.0.0.0        UG    600    0        0 wlp3s0
192.168.0.0    0.0.0.0        255.255.255.0  U    600    0        0 wlp3s0
192.168.122.0  0.0.0.0        255.255.255.0  U    0      0        0 virbr0
I am reasonably competent with Linux, but not with networking, so I am not sure if the above is meaningful. The message "no route to host" has me baffled considering my success with ssh and rsync.

While you are scratching your head, can you guide me into setting up IPv6 on one machine so pgModeler can connect from the other? This is the first time I have had to look at IPv6 and I know less than nothing about it. I looked at some Google hits on IPv6 addressing and my brain exploded. "8-[

Anyone willing to talk me through fixing these issues will be awarded a virtual beer (or other beverage of choice).

Kind regards,
Doug

Doug Hutcheson 07-30-2017 08:29 PM
Doh! telnet doesn't work because I have it disabled in the firewalls. (Slaps forehead). Is it going to be something that simple which is blocking postgresql? I have postgresql enabled in both firewalls.

Hmmm ... I will keep digging.

Doug Hutcheson 07-30-2017 08:47 PM
Double Doh! postgresql.conf needed to be told to listen on all addresses '*'. I hope my conversation with myself has been entertaining if not instructive.

I will now have my beverage (virtually, of course).


All times are GMT -5. The time now is 02:08 AM.