Op woensdag 13 april 2016 17:24:55 CEST schreef sdm:
On 04/13/2016 05:15 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2016-04-14 02:07, sdm wrote:
On 04/13/2016 03:57 PM, James Knott wrote:
On 04/13/2016 06:31 PM, Freek de Kruijf wrote:
This is the culprit. You have to provide an IP address for the DNS also. With DHCP, you get also the value for the DNS. With a static address you do not get this address, so you have to provide that address with the other static values.
DNS only maps a name to an IP address. You don't even need it, if you just use IP addresses. So, it shouldn't cause an interface to lose a configured static address.
It's looking like a DNS issue, because I can't access i.e. www.google.com, but if I type in: 192.168.1.1 the router GUI comes up, after a router power loss using a static IP. So the static route doesn't work after a router power loss, DHCP does, so I'm stumped. I can only get the static route going again if I switch to DHCP and then back to static. ifdown and ifup don't work.
What Freek de Kruijf said is correct. That is the cause.
And, if what sdm said, that the DNS config written in YaST doesn't catch is true (a bug that should be reported in bugzilla), then you need to apply his workaround (write the appropriate line in resolv.conf file yourself).
- -- Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlcO4QUACgkQja8UbcUWM1xckQD/fzO6oWOcPibkzGEKjGpbogW0 bRofF+idGGhABYcqZKABAJUsoUdAQBxreKH6DHU2mVzGO+Hig8ZNdnab6+O3n6IC =MKUE -----END PGP SIGNATURE-----
Static IP is set to 192.168.1.5. Subnetmask is set, 255.255.255.0. On Hostname/DNS, under Name Server 1, I set it to 192.168.1.1. And tried "Use Default Policy", "Only Manually", and "Use Custom Policy" with Custom Policy Rule set to auto or static. I've also the entire time had the name sever of 192.168.1.1 in the /etc/resolv.conf file. The Gateway I set to 192.168.1.1.
Once again, if I unplug the router and plug it back in, with the above settings DNS does not work until switching to DHCP, then back to static. If I leave it on static with the above settings, unplug the router, and then plug it back in, DNS does not work. I can access the router at 192.168.1.1, but can't go to any web address.
Use Google's DNS's instead: 8.8.8.8 and 8.8.4.4 But there's more: IIRC there was talk about a client-bridge-router. Is this a router or an access point? . A router would have an IP address in one range on the outside ( in your case 192.168.1.? ) and one on the "inside" ( 192.168.?.?). To be honest, I've been struggling with > 1 router networks in the past, and have found it's worth the time to read until you understand how networking ( not just on linux ) is structured on this level. I'm not talking about all the network layers etc, simply about IP addresses, net masks, DNS, gateways and their logic in networks. I've done so, and, like in many other "small private studies", it has brought me more than I was looking for: a network with a lot of staticly configured devices ( server, TV, STB, 2 x RPi, AP's ), own DNS- server ( which caches Google's and does local DNS, bleeding fast on my Gbit wired network ), own DHCP server, where any client can access any machine by hostname. In my case DNS and DHCP server are on an RPi. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org