[opensuse] cannot get network to run new hd
Howdy, I cloned the root drive in my opensuse leap system with the following command: rsync -auxzHAXS --delete --progress --exclude=/proc --exclude=/sys --exclude=/mounters --exclude=/var/run/media/george --exclude=/media --exclude=/home --exclude=/windows --exclude=/mounters/homemnt --exclude=/mounters/virtmnt / /mounters/rootmnt/ What I am trying to do is run opensuse in a new hard drive on Laptop #1, an ASUS GL551. I have done this before on other machines, but something has gone awry with this one. After cloning, I swapped out the new drive with the old drive and booted up. I had to restore grub and all that with a rescue system, and I was able to boot up into opensuse Leap 42.1 on my new hard drive. So, after booting up, I cannot get the network card to do what it is supposed to do. Part of the problem is my own ignorance of how to configure networks. I am connected by wifi to my router, and have a local ip given by dhcp, but when I try to browse anything, I get the error: This site can't be reached. www.cnn.com's server DNS address could not be found. Whether it is cnn or any other website, I get that error (it has the web address for what I am trying instead of cnn in the browser error message). So I tried to plug in an ethernet cable, and connect it to the router, and it won't even get an ip address for eth0. At least wlan0 has an ip address. I tried to reset the router, and nothing changed. Everything worked on the original drive, just not on the new drive. Here are the results of ifconfig, hwinfo, iwconfig, and resolv.conf, and route -n Any help would be great! I still have a lot to learn about networks Notice below that the resolv.conf file in particular doesn't show anything. --------------------------------- tribetrekGlap:/home/george # ifconfig eth0 Link encap:Ethernet HWaddr 78:24:AF:C9:7A:23 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:5615 errors:0 dropped:0 overruns:0 frame:0 TX packets:5615 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:418996 (409.1 Kb) TX bytes:418996 (409.1 Kb) wlan0 Link encap:Ethernet HWaddr 80:19:34:BD:EB:88 inet addr:192.168.1.125 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::8219:34ff:febd:eb88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1240 errors:0 dropped:0 overruns:0 frame:0 TX packets:641 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:597127 (583.1 Kb) TX bytes:89616 (87.5 Kb) tribetrekGlap:/home/george # hwinfo --network 33: None 00.0: 10700 Loopback [Created at net.125] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 34: None 00.0: 10701 Ethernet [Created at net.125] Unique ID: usDW.ndpeucax6V1 Parent ID: rBUF.7YbuYtgtrd1 SysFS ID: /class/net/eth0 SysFS Device Link: /devices/pci0000:00/0000:00:1c.3/0000:05:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "r8169" Driver Modules: "r8169" Device File: eth0 HW Address: 78:24:af:c9:7a:23 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #20 (Ethernet controller) 35: None 00.0: 1070a WLAN [Created at net.125] Unique ID: AYEt.QXn1l67RSa1 Parent ID: y9sn.FdArGEKy_S4 SysFS ID: /class/net/wlan0 SysFS Device Link: /devices/pci0000:00/0000:00:1c.2/0000:04:00.0 Hardware Class: network interface Model: "WLAN network interface" Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlan0 HW Address: 80:19:34:bd:eb:88 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #18 (Network controller) tribetrekGlap:/home/george # iwconfig eth0 no wireless extensions. wlan0 IEEE 802.11abgn ESSID:"CiscoTX" Mode:Managed Frequency:2.437 GHz Access Point: 20:AA:4B:1F:05:F8 Bit Rate=12 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=70/70 Signal level=-26 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:1 Invalid misc:13 Missed beacon:0 lo no wireless extensions. tribetrekGlap:/home/george # cat /etc/resolv.conf # Generated by NetworkManager search site tribetrekGlap:/home/george # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 08:19 PM, tech@reachthetribes.org wrote: I would like to start with the wifi troubleshooting and ignore the ethernet problem for now, as I might just have a bad ethernet cable. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 08:27 AM, tech@reachthetribes.org wrote:
On 06/23/2016 08:19 PM, tech@reachthetribes.org wrote:
I would like to start with the wifi troubleshooting and ignore the ethernet problem for now, as I might just have a bad ethernet cable.
If you suspect a bad cable then just get rid of it. However, if both interfaces have problems, you have to look elsewhere. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2016-06-23 at 20:19 +0800, tech@reachthetribes.org wrote:
So, after booting up, I cannot get the network card to do what it is supposed to do. Part of the problem is my own ignorance of how to configure networks. I am connected by wifi to my router, and have a local ip given by dhcp, but when I try to browse anything, I get the error:
This site can't be reached. www.cnn.com's server DNS address could not be found.
Means there is probably no DNS defined. I would simply delete the network connection and create it again. You have not said if you are using yast (wicked) or network manager. If it is a laptop, probably the later.
tribetrekGlap:/home/george # cat /etc/resolv.conf # Generated by NetworkManager search site
That is the problem. No DNS. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAldr3mwACgkQtTMYHG2NR9WuCQCfRN7R+kJ7WAjC6NaWYZWvsuY9 mLEAn1LNTCzQgwR3703omcrGRCbbhjcV =xnlj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 09:04 AM, Carlos E. R. wrote:
This site can't be reached. www.cnn.com's server DNS address could not be found. Means there is probably no DNS defined.
A simple test is to ping the Google DNS server at 8.8.8.8. That will work even without DNS. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/24/2016 12:24 AM, James Knott wrote:
On 06/23/2016 09:04 AM, Carlos E. R. wrote:
This site can't be reached. www.cnn.com's server DNS address could not be found. Means there is probably no DNS defined. A simple test is to ping the Google DNS server at 8.8.8.8. That will work even without DNS.
Ok, I was able to ping 8.8.8.8 and get a response, but I can't go to google.com in my browser. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 12:36 PM, tech@reachthetribes.org wrote:
On 06/24/2016 12:24 AM, James Knott wrote:
On 06/23/2016 09:04 AM, Carlos E. R. wrote:
This site can't be reached. www.cnn.com's server DNS address could not be found. Means there is probably no DNS defined. A simple test is to ping the Google DNS server at 8.8.8.8. That will work even without DNS.
Ok, I was able to ping 8.8.8.8 and get a response, but I can't go to google.com in my browser.
That confirms a DNS problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 01:04 PM, James Knott wrote:
On 06/23/2016 12:36 PM, tech@reachthetribes.org wrote:
On 06/24/2016 12:24 AM, James Knott wrote:
On 06/23/2016 09:04 AM, Carlos E. R. wrote:
This site can't be reached. www.cnn.com's server DNS address could not be found. Means there is probably no DNS defined. A simple test is to ping the Google DNS server at 8.8.8.8. That will work even without DNS.
Ok, I was able to ping 8.8.8.8 and get a response, but I can't go to google.com in my browser.
That confirms a DNS problem.
He's already pointed out that his /etc/resolv.conf is blank. If he put 8.8.8.8 in there manually he might get some DNS functionality. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 09:04 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2016-06-23 at 20:19 +0800, tech@reachthetribes.org wrote:
So, after booting up, I cannot get the network card to do what it is supposed to do. Part of the problem is my own ignorance of how to configure networks. I am connected by wifi to my router, and have a local ip given by dhcp, but when I try to browse anything, I get the error:
This site can't be reached. www.cnn.com's server DNS address could not be found.
Means there is probably no DNS defined.
I would simply delete the network connection and create it again. You have not said if you are using yast (wicked) or network manager. If it is a laptop, probably the later. Ok, I tried that, and it still would not connect to my router. After deleting that connection in network manager, I then found it again, and it will try to connect, and using network manager, it won't get an ip address.
So I switched to wicked service, and it gets an ip address, but it still doesn't get any dns, and so I can't use the internet still.
tribetrekGlap:/home/george # cat /etc/resolv.conf # Generated by NetworkManager search site
That is the problem. No DNS.
Yes, no DNS is definitely the problem. How do I fix that? It must mean that my computer is not able to find the DNS addresses for anything on the internet. But why and how to make it work? This other computer that I am using for email doesn't have any problem at all, and neither did the original root partition that I copied this one from. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 12:34 PM, tech@reachthetribes.org wrote:
Yes, no DNS is definitely the problem. How do I fix that? It must mean that my computer is not able to find the DNS addresses for anything on the internet. But why and how to make it work?
make a manual entry in your /etc/resolv.conf Also, in /etc/sysconfig/network/config there is # List of DNS nameserver IP addresses to use for host-name lookup. # When the NETCONFIG_DNS_FORWARDER variable is set to "resolver", # the name servers are written directly to /etc/resolv.conf. # Otherwise, the nameserver are written into a forwarder specific # configuration file and the /etc/resolv.conf does not contain any # nameservers causing the glibc to use the name server on the local # machine (the forwarder). See also netconfig(8) manual page. # NETCONFIG_DNS_STATIC_SERVERS="127.0.0.1 192.168.2.1 8.8.8.8" That basically says "check local cache, then the gateway and its cacne, and finally the Google DNS server. The config of the gateway makes use of the DNS supplied by the ISP, so that resolves most addresses. OBTW: I use dnsmasq bot bind. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-23 18:34, tech@reachthetribes.org wrote:
On 06/23/2016 09:04 PM, Carlos E. R. wrote:
I would simply delete the network connection and create it again. You have not said if you are using yast (wicked) or network manager. If it is a laptop, probably the later. Ok, I tried that, and it still would not connect to my router.
What do you mean, "still"? It was connecting to your router before. New problem? Notice that in another post you say you can ping 8.8.8.8, which means that indeed you can connect to your router and to internet.
After deleting that connection in network manager, I then found it again, and it will try to connect, and using network manager, it won't get an ip address.
No IP at all? Or no DNS? It is not the same.
So I switched to wicked service, and it gets an ip address, but it still doesn't get any dns, and so I can't use the internet still.
tribetrekGlap:/home/george # cat /etc/resolv.conf # Generated by NetworkManager search site
That is the problem. No DNS.
As you copied all your files, it is possible that the network setup find that file and refuse to touch it because they think it is a manual setting of yours (there is probably a message about this in the log). I think that the trick was to delete it and restart network, but I'm not sure. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/23/2016 04:24 PM, Carlos E. R. wrote:
t is possible that the network setup find that file and refuse to touch it because they think it is a manual setting of yours
Yes, that is the case. My /etc/resolv/conf contains the following header before the auto-generated IP addresses # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # # Note: Manual change of this file disables netconfig too, but # may get lost when this file contains comments or empty lines # only, the netconfig settings are same with settings in this # file and in case of a "netconfig update -f" call. The addresses that follow this are a result of my setting those values in /etc/sysconfig/network/config as I mentioned in a previous post. Please do RTFM the netconfig(8) man page. PLEASE! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/24/2016 06:45 AM, Anton Aylward wrote:
On 06/23/2016 04:24 PM, Carlos E. R. wrote:
t is possible that the network setup find that file and refuse to touch it because they think it is a manual setting of yours Yes, that is the case.
My /etc/resolv/conf contains the following header before the auto-generated IP addresses
# # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # # Note: Manual change of this file disables netconfig too, but # may get lost when this file contains comments or empty lines # only, the netconfig settings are same with settings in this # file and in case of a "netconfig update -f" call.
The addresses that follow this are a result of my setting those values in /etc/sysconfig/network/config as I mentioned in a previous post.
Please do RTFM the netconfig(8) man page. PLEASE!
Let me say first of all to you guys, I very much appreciate your help. I know it is difficult to help someone slug through something that they have quite limited knowledge of, like my knowledge of how networking things work. Now I did as you suggested. First, reading the netconfig(8) man page. To be honest, so much of it just doesn't make any sense to me. Sorry about that - I get by pretty well on a lot of other topics, but I seem to not be able to conceptualize the whole big picture when it comes to networking. If there were a good on-line tutorial or something about what all these things are supposed to mean, like how the computer uses the different variables in the /etc/sysconfig/network/config file to make the network work. For example, I don't know what the differences are between bind, dnsmasq, and resolver, or why changing those variables would make a difference in the NETCONFIG_DNS_FORWARDER= variable. The man page doesn't tell you any of that. The man page assumes that you have a certain level of knowledge before you open it, and if you do, it is really helpful. All that is to say, I did my best at reading the man page, and I did get some stuff out of it, but not a lot. Here is what I did, and it did solve the problem. First, after reading the man page, I went into /etc/sysconfig/network/config and changed the variable NETCONFIG_DNS_STATIC_SERVERS="127.0.0.1 192.168.2.1 8.8.8.8" as you suggested. Then it still would pick up an ip address from my router, and kept kicking me off of it when I tried to connect. I reset my router, and it still would not get an ip address. I tried to reset my router, and no change. The difference this time with my original problem is that in the original problem I did get an ip, but there was no dns. Now I was neither getting an ip or dns. I might also add that in the original problem I was able to only get an ip by using wicked, not network manager. This time I was using network manager, and could not get ip and still had no dns. So I ran the command netconfig -v update, and it did a bunch of stuff (I will post below). Yet my pc still would not get an ip address from my router when it connected, and it kept kicking me off. After that I reset my router one more time, powering it off and back on again, and this time it connected and got an ip address and I finally had dns, and I was able to connect to the internet. So that is the final resolution of the problem. It worked, but I still don't understand why. It seems like if you just keep shaking things and keep trying, eventually it decides to do what it is supposed to do. Now, here is the output of my command: tribetrekGlap:/home/george # netconfig -v update netconfig: Executing '-v update' for pid 3976 debug: lockfile created (/var/run/netconfig.pid) for PID 4988 debug: lockfile created debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime debug: dns-resolver module called debug: Resolved dns-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK NetworkManager' debug: Static Fallback debug: Use NetworkManager policy merged settings debug: exec get_dns_settings: /var/run/netconfig/NetworkManager.netconfig debug: get_dns_settings: service 'NetworkManager' => rank '1' debug: get_dns_settings: DNS_SEARCHLIST_1='site' debug: get_dns_settings: DNS_SERVERS_1='' debug: exit get_dns_settings: /var/run/netconfig/NetworkManager.netconfig debug: write_resolv_conf: ' site ' ' 127.0.0.1 192.168.2.1 8.8.8.8' dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... dns-resolver: You can find my version in /etc/resolv.conf.netconfig ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... You can find my version in /etc/resolv.conf.netconfig ... debug: dns-bind Module called debug: dns-dnsmasq Module called debug: nis Module called debug: Resolved nis-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK NetworkManager' debug: Static Fallback debug: Use NetworkManager policy merged settings debug: exec get_nis_settings: /var/run/netconfig/NetworkManager.netconfig debug: exit get_nis_settings: /var/run/netconfig/NetworkManager.netconfig debug: set_nisdomainname: NetworkManager 26 debug: set_nisdomainname: => yes debug: set_nisdomainname: old[]=, new[26]= debug: format_yp_conf called with : debug: Using static fallback debug: format_static[0] called debug: No changes for /etc/yp.conf debug: nis domainname '' is up to date debug: ntp-runtime Module called debug: Resolved ntp-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK NetworkManager' debug: Static Fallback debug: Use NetworkManager policy merged settings debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig debug: get_ntp_settings: NTP_SERVER_LIST='' debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig And now I also get this, as I think I should from this network (which connects to another router to go outside) tribetrekGlap:/home/george # cat /etc/resolv.conf # Generated by NetworkManager search domain.name site nameserver 192.168.254.254 nameserver 192.168.1.1 I think that resolves the problem. Thanks again for the help. I would welcome any further comments to try and explain why it wasn't working, and changing these things (which are not changed on the original drive that still works) did the trick. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
tech@reachthetribes.org composed on 2016-06-24 16:27 (UTC+0800):
...127.0.0.1 192.168.2.1 8.8.8.8'...
When Anton wrote that, he should have explained that the middle IP is specific to his own router, and you were supposed to substitute the IP of your own router in following his instruction. It would have saved you a bunch of time lost getting "kicked off" if you had known.
And now I also get this, as I think I should from this network (which connects to another router to go outside) tribetrekGlap:/home/george # cat /etc/resolv.conf # Generated by NetworkManager search domain.name site
FWIW, "domain.name" and "site" are there because you never assigned a domain name to your LAN (or PC if you have no LAN) either during installation or after. It is prudent to do this personalization (in YaST networking), even if you provide only arbitrary nonsense.
nameserver 192.168.254.254 nameserver 192.168.1.1
I think that resolves the problem. Thanks again for the help. I would welcome any further comments to try and explain why it wasn't working, and changing these things (which are not changed on the original drive that still works) did the trick.
Network performance will probably suffer if you don't adjust /etc/sysconfig/network/config with a proper IP set, or do the equivalent in YaST networking. I don't know why it put 192.168.254.254 in there. It should be removed unless something on your LAN provides DNS using that IP. You don't want Anton's 192.168.2.1 in there either, unless it is also your own router's IP. Apparently your router's address is 192.168.1.1, so that can be left alone, and 8.8.8.8 can be restored if you want to maintain it as primary fallback for anything missing from your router's DNS service. You can probably confirm your router's IP is 192.168.1.1 by typing it in the urlbar of your web browser. That will probably result in a login screen for configuring your router. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-24 10:27, tech@reachthetribes.org wrote:
First, after reading the man page, I went into /etc/sysconfig/network/config and changed the variable NETCONFIG_DNS_STATIC_SERVERS="127.0.0.1 192.168.2.1 8.8.8.8" as you suggested.
Is your router on 192.168.2.1? That line is correct for Anton, not for you. I believe your's is "192.168.1.1". Then, unless you have configured dnsmasq or bind, that "127.0.0.1" should be removed, too. Leave it at "192.168.1.1 8.8.8.8"
debug: write_resolv_conf: ' site ' ' 127.0.0.1 192.168.2.1 8.8.8.8' dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... dns-resolver: You can find my version in /etc/resolv.conf.netconfig ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... You can find my version in /etc/resolv.conf.netconfig ...
This is what I said that was your problem. You have to delete the /etc/resolv.conf file and run the command again.
And now I also get this, as I think I should from this network (which connects to another router to go outside) tribetrekGlap:/home/george # cat /etc/resolv.conf # Generated by NetworkManager search domain.name site nameserver 192.168.254.254 nameserver 192.168.1.1
Strange. But if it works...
I think that resolves the problem. Thanks again for the help. I would welcome any further comments to try and explain why it wasn't working, and changing these things (which are not changed on the original drive that still works) did the trick.
-- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/24/2016 06:54 PM, Carlos E. R. wrote:
On 2016-06-24 10:27, tech@reachthetribes.org wrote:
First, after reading the man page, I went into /etc/sysconfig/network/config and changed the variable NETCONFIG_DNS_STATIC_SERVERS="127.0.0.1 192.168.2.1 8.8.8.8" as you suggested. Is your router on 192.168.2.1?
That line is correct for Anton, not for you. I believe your's is "192.168.1.1".
Then, unless you have configured dnsmasq or bind, that "127.0.0.1" should be removed, too.
Leave it at "192.168.1.1 8.8.8.8"
debug: write_resolv_conf: ' site ' ' 127.0.0.1 192.168.2.1 8.8.8.8' dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... dns-resolver: You can find my version in /etc/resolv.conf.netconfig ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... You can find my version in /etc/resolv.conf.netconfig ...
This is what I said that was your problem. You have to delete the /etc/resolv.conf file and run the command again.
And now I also get this, as I think I should from this network (which connects to another router to go outside) tribetrekGlap:/home/george # cat /etc/resolv.conf # Generated by NetworkManager search domain.name site nameserver 192.168.254.254 nameserver 192.168.1.1 Strange. But if it works...
I think I can explain where the 192.168.254.254 comes from. The router that I connect to inside my bedroom is necessary for my home network, but it connects to another combination router/modem provided by my isp where the service comes in. It is necessary because in the house we rent, the walls are made of concrete and steel, and the isp's router/modem isn't strong enough to penetrate the entire house without significant degradation of signal, making the performance in some parts of the house useless without the 2nd router. It is this 2nd router that I was connecting to which has the ip address 192.168.1.1. The router/modem provided by the isp has the ip address for it's network 192.168.254.254. When I originally set it up, I tried to just make the internal modem just use the dhcp settings of the original router, but I couldn't make it work for some reason. Part of it was that the isp's router only has 1 ethernet port, and I have to use that to connect to my 2nd router. I haven't studied it any further from this point, because I had a system that at least sort of works. Thanks again for everyone's help. I have now changed my network configuration file again, removing 127.0.0.1 and substituting the other ip for my router's ip, and I will now run the command netconfig -f update. //I will also look for that book in order to read up on it. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/24/2016 04:27 AM, tech@reachthetribes.org wrote:
I get by pretty well on a lot of other topics, but I seem to not be able to conceptualize the whole big picture when it comes to networking. If there were a good on-line tutorial or something about what all these things are supposed to mean,
I learnt about networking by reading Douglas Comer's excellent book[1]. A print copy is nice to have but there are ebook and PDF versions available. There are many others on how TCP works around. When you understand how networking works, what goes into /etc/resolv.conf, what the output of standard tools like "route", "ip", "ifconfig" mean, then the issue of the settings in /etc/sysconfig/networking/config will be. along with the explanatory comments therein, self apparent. https://i-technet.sec.s-msft.com/dynimg/IC213263.gif Trying to explain those variable as a starting point, if you don't know what the resulting effect in, say, /etc/resolv.conf actually means will be laborious and frustrating, both for you and for the person trying to explain. And that knowledge will not be portable to other systems such as RedHat or Ubuntu or - !shock! !horror! - Microsoft Windows. What I mean by this is that each vendor has their own 'added value' approach. Yes there are efforts to standardize, but they most often meat with resistance one way or another. Certainly Suse and openSuse make it clear that they modify the upstream version of many core packages, and in some cases lag way behind other distributions. But if you know the generic principles rather than the specifics about one distribution, you can easily accommodate. Many of the people here are professionals in their day jobs and use AIX, HP/UX, Sun/Solaris or other versions of Linux and move backwards and forwards between them because they understand the principles and how to apply then rather than treating each one 'sui generis'. See this debate, for example: http://www.zdnet.com/blog/murphy/why-many-mcses-wont-learn-linux/1137 Compared to Microsoft (or even IBM's SNA) TCP is both simple and regular. But there is a lot of it. Do not confuse volume for complexity. TCP/IP is not inherently complex. [1] My ex- destroyed my signed first edition along with many other first editions and collectables -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/24/2016 08:16 AM, Anton Aylward wrote:
I get by pretty well on a lot of other topics, but I seem to not be able
to conceptualize the whole big picture when it comes to networking. If there were a good on-line tutorial or something about what all these things are supposed to mean, I learnt about networking by reading Douglas Comer's excellent book[1]. A print copy is nice to have but there are ebook and PDF versions available. There are many others on how TCP works around.
https://www.redbooks.ibm.com/abstracts/gg243376.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/24/2016 04:27 AM, tech@reachthetribes.org wrote:
Now, here is the output of my command: tribetrekGlap:/home/george # netconfig -v update
!OUCH! !NO! This is why I said to read the man page. The "-v" option is "verbose", which, yes, is useful in debugging, if you understand the output. What you need is the "-f", "force replace", option.
After that I reset my router one more time, powering it off and back on again, and this time it connected and got an ip address and I finally had dns, and I was able to connect to the internet. So that is the final resolution of the problem. It worked, but I still don't understand why. It seems like if you just keep shaking things and keep trying, eventually it decides to do what it is supposed to do.
No, when you rebooted the network startup ran the "netconfig -f update" behind the scenes, as it should. This isn't a result of random shaking. This is correct procedure. Yes you could have done it manually without the need to reboot, using the "-f". -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Anton Aylward
-
Carlos E. R.
-
Felix Miata
-
James Knott
-
tech@reachthetribes.org