Can you give the output of:
route -n
or
ip route
as root from the client?
JCLVanier,
Iâve included LC_ALL=C in both commands as not to have to translate the messages. Today the client is 192.168.0.103 and the server is 192.168.0.100.
# LC_ALL=C route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 600 0 0 wlp0s29u1u3
192.168.0.0 0.0.0.0 255.255.255.0 U 600 0 0 wlp0s29u1u3
# LC_ALL=C ip route
default via 192.168.0.1 dev wlp0s29u1u3 proto static metric 600
192.168.0.0/24 dev wlp0s29u1u3 proto kernel scope link src 192.168.0.103 metric 600I see nothing wrong here.
Can you access the routerâs settings as suggested before?
This might be done via a web interface from your browser. The url might be simply:
http://192.168.0.1
Yes. And I couldnât find anything about client to client or client to
server configuration on routerâs 192.168.0.1 page.
I donât mean to keep saying the same thing over and over, but you have not confirmed that you have turned off the firewall on both machines and tried to connect. Have you done this? If so and it did not work, check iptables -L and see if it looks like this:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
1 Like
Isnât there anything to do with firewall as suggested by CLB? I opened om-control-center=>Network=>Add-network-hosts and found that only 127.0.1.1 was there as localhost. I add the address 192.168.0.101 (todayâs address of the other computer) but it did not help. Again at om-cc=>Network-sharing some options are not available for configuration (file or directory not found).
From the command prompt, what does the command iptables -L give you?
iptable -L is attached.iptables-L.txt (2,4 KB)
I checked /var/log/firewalld file. This are two messages that repeats ânâ times in this file:
WARNING: INVALID_HELPER: ânf_conntrack_netbios_nsâ not available in kernel
ERROR: UNKNOWN_INTERFACE: âwlp0s29u1u2â is not in any zone
the first one appears at another forum (see 1394573 â firewall-config missing kernel feature nf_conntrack_netbios_ns) also related with sambaâs configuration and I saw errorâs during boot about samba. The second message seems to say that some configuration of zone is necessary in firewalld at om-control-center âŠ
So the output of iptables tells me that a firewall is running. So just for testing purposes, run âsystemctl stop firewalldâ on both machines and try sshing to see if it works.
CLB,
Yes, after stopping firewalld ssh works again. So what can I change in firewall so that ssh works without disabling firewalld? I guess some network or network sharing configuration at om-cc could help but which one?
Many thanks
Sorry, for not answering in the first place, this happened because I was my cell phone to see the messages and this limits the amount of messages shownâŠ
I currently get these errors when I look at the firewall status.
Jun 15 14:00:03 gizmo firewalld[6812]: WARNING: â/sbin/ebtables-restore --noflushâ failed:
Jun 15 14:00:03 gizmo firewalld[6812]: ERROR: COMMAND_FAILED
Jun 15 14:00:03 gizmo firewalld[6812]: WARNING: â/sbin/ip6tables-restore -nâ failed:
Jun 15 14:00:03 gizmo firewalld[6812]: WARNING: â/sbin/iptables-restore -nâ failed:
Jun 15 14:00:03 gizmo firewalld[6812]: ERROR: COMMAND_FAILED
I have not had time to try and figure out what is wrong to my just have things open right now.
Is it mine a different problem of yours? Iâm planning to try some definitions on firewall. First I would choose the firewall area between the following options:
block, dmz, drop, external, home, internal, public, trusted, work
then I would set at om-control-center=>network the ssh for the connection and area.
The point is which option should I use? I guess home or internal, but Iâm not sure and what are the consequences.
Anyway, it seems that if this is a recent feature of Openmandriva this distro is getting far from the initial goal of being a beginner friendly distro.
Unsuccessful trials:
configure zone as home for both computers <no help
then, in om-control-center=>network=>add networks I added each other IP address (192.168.0.xxx) <no help as well.
Looking a little deeper, at,
How To Set Up a Firewall Using FirewallD on CentOS 7 | DigitalOcean
I see an example of a âsurveyâ command that in CENTOS 7, for zone home, returns
$ firewall-cmd --zone=home --list-all
output
home
interfaces:
sources:
services: dhcpv6-client ipp-client mdns samba-client ssh
ports:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
However, here with OMV LX 3.0X, the same command returns two other parameters (target and icmp-block-inversion) and no settings for services at all
$ firewall-cmd --zone=home --list-all
home
target: default
icmp-block-inversion: no
interfaces:
sources:
services:
ports:
protocols:
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
As for a beginner friendly distro, wouldnât it be that some default configurations are left?
Ok! Now ssh is working. I did in both computers,
$ om-control-center=>security=>configure firewall
Then I set the connections to zone = home and allow for the following services:
dhcpv6-client ipp-client mdns samba-client ssh
I wonât mark this as âsolving the issueâ until Iâm sure this is the best solution.
I insist, some update have changed settings here because I did not have this problem a few days ago.
Also, as a beginner friendly distro, this type of configuration (or a better/recomended one) should be the default.
Thanks
1 Like
Thanks for investigation, if you consider this should be default option, is it possible to open a ticket in bugzilla?
Iâm afraid I will not be able to say âthis is the defaultâ since I donât have much experience with this. I really know very few about it. What I did was to look for configurations in the internet but I will try to figure out if this is adequate at least to my needs/opinion.
I really know very little about everything in this field. Yesterday, Iâve reset everything with the option âpermanentâ as to guarantee that the working configuration for zone home would hold for every boot. It did not, the command,
$ firewall-cmd --zone=home --list-all
doesnât reflect the configuration I want.
But what is weird about this is that the ssh is still working.