Page 1 of 1

M6 installation will only ping and connect to 192.168.0.1

PostPosted: Dec 5th, '17, 21:33
by DiBosco
Folks,

I have a laptop that was running Mageia 5. It worked fine and could connect to anything else on my subnet. I have done a fresh install (not an upgrade) to Mageia 6 and now I can only "talk to" 192.168.0.1 Said address is the DHCP server and ADSL router - I can get Internet just fine as well. It's just no other device on the 192.168.0 subnet that I can talk to.

My firewall is switched off, the previous install worked fine, so I don't think it's either of those things. I don't know what to try or what information to post. So, if anyone can suggest anything that I can do/info I can give I'd be most grateful.

Many thanks.

Re: M6 installation will only ping and connect to 192.168.0.

PostPosted: Dec 6th, '17, 11:35
by wintpe
when you say you can talk to 192.168.0.1 do you mean ping or http

check your subnet mask is not set to something odd by mistake, as its possible that could restrict your view down to just a small number of hosts. for example 255.255.255.255 could reduce you down to one host.

for that range its usually 255.255.255.0, unless you are using superneting to boost the default range from 255 addresses per network.

ens192: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255

check that your default router is getting set:

if that does not work show us the output of netstat -rn

should be something like:

Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 ens192

and ifconfig -a

regards peter

Re: M6 installation will only ping and connect to 192.168.0.

PostPosted: Dec 6th, '17, 11:51
by DiBosco
Hi Peter,

I mean both ping and http. My banana pi has a web server and Mercurial interface, neither of which I can connect to. Can't even ping it or indeed anything else.

Am in work at the moment; I just tried pinging the work laptop and it works fine, which is making me think there must be some issue with the router at home. I'll be back tomorrow, try again and report back.

Many thanks. :)