LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop
User Name
Password
Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context.

Notices


Reply
  Search this Thread
Old 10-04-2019, 08:30 AM   #1
TokTok
Member
 
Registered: Oct 2019
Posts: 230

Rep: Reputation: Disabled
Kodachi Linux cannot connect to wifi or hard wired router-web access.


I have a copy of Kodachi Linux the newest version ( i don`t have it in front of me at the monment ) it reconizes both wifi & wired connection but will not connect to the web & can`t find the reason for it, i have tried everything, changed every setting i could, reloaded several times, but still wont connect, any suggestions ?
Ps. this is both a live and install disk but it should not matter. I tried it on 2 PC a dell OptiPlex 320 never any problems running anything-A HP laptop same thing-same result.
 
Old 10-08-2019, 07:27 PM   #2
ShadowCat8
Member
 
Registered: Nov 2004
Location: San Bernardino, CA
Distribution: Gentoo, Arch, (RedHat4.x-9.x, FedoraCore 1.x-4.x, Debian Potato-Sarge, LFS 6.0, etc.)
Posts: 261

Rep: Reputation: 52
Greetings,

Well, first I would double-check my local network settings, either via ifconfig or ip and make sure that your network config is good.

Example of ifconfig:
Code:
# ifconfig 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.89  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::227:eff:fe12:69cd  prefixlen 64  scopeid 0x20<link>
        ether 00:00:00:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 249128670  bytes 95474238373 (88.9 GiB)
        RX errors 0  dropped 13322  overruns 0  frame 0
        TX packets 205801437  bytes 108139166244 (100.7 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xee200000-ee220000

...<snip>...
Next, have the system try to ping itself, both localhost as well as the IP address you get from the above command. Remember that you will have to stop the ping command yourself, hence the "^C" (READ: Ctrl+C).
Code:
$ ping 127.0.0.1 
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.029 ms
^C
--- 127.0.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 6ms
rtt min/avg/max/mdev = 0.024/0.026/0.029/0.005 ms
Now, if that works, next run a "route -n" and see what your gateway is set to. Example:
Code:
$ 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    2      0        0 eth0
127.0.0.0       127.0.0.1       255.0.0.0       UG    0      0        0 lo
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
Now, if you get a valid gateway, try to ping the gateway and make sure it is responding to you.

Given that the pings above work and the system knows it's gateway, try to ping 8.8.8.8. That is the IP address for Google's Root DNS server, so it always responds to pings. If that doesn't respond, check your gateway.

If that does respond, then check /etc/resolv.conf for where you are pointing your DNS, and make sure you can reach it and get answers.
Code:
 $ cat /etc/resolv.conf
nameserver 74.40.74.41
nameserver 208.67.222.222
nameserver 208.67.220.220
nameserver 8.8.8.8
 $ nslookup www.google.com
Server:		74.40.74.41
Address:	74.40.74.41#53

Non-authoritative answer:
Name:	www.google.com
Address: 172.217.4.68
Name:	www.google.com
Address: 2607:f8b0:4009:80f::2004
Hope that helps... Let us know.
 
Old 10-09-2019, 12:25 PM   #3
TokTok
Member
 
Registered: Oct 2019
Posts: 230

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ShadowCat8 View Post
Greetings,

Well, first I would double-check my local network settings, either via ifconfig or ip and make sure that your network config is good.

Example of ifconfig:
Code:
# ifconfig 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.89  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::227:eff:fe12:69cd  prefixlen 64  scopeid 0x20<link>
        ether 00:00:00:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 249128670  bytes 95474238373 (88.9 GiB)
        RX errors 0  dropped 13322  overruns 0  frame 0
        TX packets 205801437  bytes 108139166244 (100.7 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xee200000-ee220000

...<snip>...
Next, have the system try to ping itself, both localhost as well as the IP address you get from the above command. Remember that you will have to stop the ping command yourself, hence the "^C" (READ: Ctrl+C).
Code:
$ ping 127.0.0.1 
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.029 ms
^C
--- 127.0.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 6ms
rtt min/avg/max/mdev = 0.024/0.026/0.029/0.005 ms
Now, if that works, next run a "route -n" and see what your gateway is set to. Example:
Code:
$ 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    2      0        0 eth0
127.0.0.0       127.0.0.1       255.0.0.0       UG    0      0        0 lo
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
Now, if you get a valid gateway, try to ping the gateway and make sure it is responding to you.

Given that the pings above work and the system knows it's gateway, try to ping 8.8.8.8. That is the IP address for Google's Root DNS server, so it always responds to pings. If that doesn't respond, check your gateway.

If that does respond, then check /etc/resolv.conf for where you are pointing your DNS, and make sure you can reach it and get answers.
Code:
 $ cat /etc/resolv.conf
nameserver 74.40.74.41
nameserver 208.67.222.222
nameserver 208.67.220.220
nameserver 8.8.8.8
 $ nslookup www.google.com
Server:		74.40.74.41
Address:	74.40.74.41#53

Non-authoritative answer:
Name:	www.google.com
Address: 172.217.4.68
Name:	www.google.com
Address: 2607:f8b0:4009:80f::2004
Hope that helps... Let us know.
I`ll give it a try and let you know how it goes.
Thank`s for your time>> Also-Great Community Here very helpful to all.
 
Old 10-11-2019, 09:50 AM   #4
TokTok
Member
 
Registered: Oct 2019
Posts: 230

Original Poster
Rep: Reputation: Disabled
I figured out what it was...When i did a hard install when trying to login with PassWord it would not take the PW, i reinstalled several times with different config`s but same thing no matter what i did...Any thought`s on the matter ?
 
Old 10-17-2019, 08:53 AM   #5
TokTok
Member
 
Registered: Oct 2019
Posts: 230

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by TokTok View Post
I figured out what it was...When i did a hard install when trying to login with PassWord it would not take the PW, i reinstalled several times with different config`s but same thing no matter what i did...Any thought`s on the matter ?
I figured it out, a default password is required then when logged in it can be changed to whatever.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Kodachi Linux (PGP Key Import) (Persistence??) protoyugen Linux - Distributions 0 10-19-2016 08:57 PM
no access to config on wired access, but modem/router and wired access point work littlejoe5 Linux - Networking 1 10-22-2014 02:40 PM
ADSL WIFI ROUTER, SETTING DIFERENT IP RANGES BETWEEN WIRED and WIFI Corsari Linux - Networking 12 12-12-2012 08:27 AM
cannot ping wireless router or access router settings. wireless works, wired doesn't mattca Linux - Networking 1 06-09-2010 09:28 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop

All times are GMT -5. The time now is 07:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration