Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #3832 > unrolled thread
| Started by | F Volker <here@home.net> |
|---|---|
| First post | 2016-09-06 06:32 +0700 |
| Last post | 2016-09-07 03:29 +0000 |
| Articles | 18 on this page of 58 — 10 participants |
Back to article view | Back to comp.os.linux.networking
What should I change my DNS to? F Volker <here@home.net> - 2016-09-06 06:32 +0700
Re: What should I change my DNS to? Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-06 03:35 +0000
Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-06 13:48 +0700
Re: What should I change my DNS to? William Unruh <unruh@invalid.ca> - 2016-09-06 07:25 +0000
Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-06 14:53 +0700
Re: What should I change my DNS to? Dan Purgert <dan@djph.net> - 2016-09-06 09:40 +0000
Re: What should I change my DNS to? William Unruh <unruh@invalid.ca> - 2016-09-06 10:35 +0000
Re: What should I change my DNS to? Dan Purgert <dan@djph.net> - 2016-09-06 11:09 +0000
Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-07 08:53 +0700
Re: What should I change my DNS to? William Unruh <unruh@invalid.ca> - 2016-09-07 08:24 +0000
Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:02 +0200
Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-08 06:42 +0700
Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-08 03:10 +0200
Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-08 09:43 +0700
Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-06 21:36 +0000
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 00:48 +0200
Re: What should I change my DNS to? (combined response) William Unruh <unruh@invalid.ca> - 2016-09-07 08:18 +0000
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:08 +0200
Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 21:52 +0000
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-08 00:52 +0200
Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-07 09:13 +0700
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 04:26 +0200
Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-07 09:41 +0700
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:11 +0200
Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-07 10:59 +0700
Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 06:53 +0000
Re: What should I change my DNS to? (combined response) Dan Purgert <dan@djph.net> - 2016-09-07 11:02 +0000
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:21 +0200
Re: What should I change my DNS to? (combined response) Dan Purgert <dan@djph.net> - 2016-09-07 14:09 +0000
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 21:53 +0200
Re: What should I change my DNS to? (combined response) Dan Purgert <dan@djph.net> - 2016-09-08 11:06 +0000
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-08 15:22 +0200
Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 06:55 +0000
Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-07 14:27 +0700
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:28 +0200
Re: What should I change my DNS to? (combined response) Stefan Monnier <monnier@iro.umontreal.ca> - 2016-09-07 09:32 -0400
Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 21:50 +0000
Re: What should I change my DNS to? (combined response) William Unruh <unruh@invalid.ca> - 2016-09-07 08:29 +0000
Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-08 10:15 +0700
Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-08 19:34 +0000
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-09 03:56 +0200
Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-09 20:55 +0000
Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-10 02:47 +0200
Re: What should I change my DNS to? (combined response) Bit Twister <BitTwister@mouse-potato.com> - 2016-09-10 08:27 +0000
Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-10 22:53 +0000
Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-06 13:35 +0200
Re: What should I change my DNS to? Aragorn <thorongil@telenet.be.invalid> - 2016-09-06 14:06 +0200
Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-06 14:27 +0200
Re: What should I change my DNS to? Dan Purgert <dan@djph.net> - 2016-09-06 13:03 +0000
Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-06 17:01 +0200
Re: What should I change my DNS to? Dan Purgert <dan@djph.net> - 2016-09-06 16:25 +0000
Re: What should I change my DNS to? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-09-06 21:37 +0300
Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-06 23:42 +0200
Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-07 09:26 +0700
Re: What should I change my DNS to? Roger Blake <rogblake@iname.invalid> - 2016-09-06 12:54 +0000
Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-07 09:28 +0700
Re: What should I change my DNS to? William Unruh <unruh@invalid.ca> - 2016-09-07 08:25 +0000
Re: What should I change my DNS to? Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 03:29 +0000
Page 3 of 3 — ← Prev page 1 2 [3]
| From | "Carlos E. R." <robin_listas@invalid.es> |
|---|---|
| Date | 2016-09-09 03:56 +0200 |
| Subject | Re: What should I change my DNS to? (combined response) |
| Message-ID | <meh9ad-arv.ln1@minas-tirith.valinor> |
| In reply to | #3884 |
On 2016-09-08 21:34, Moe Trin wrote:
> A problem is finding a host out on the Internet that will respond (ping
> has been abused so much that many Internet hosts disable the responder).
> Lessee, www.ibiblio.org is a host in the Eastern USA, and it has an IP
> address of 152.19.134.40. I choose it because from experience I know it
> will _usually_ respond to pings.
I use google.com. They can afford many pings, they don't care :-)
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Moe Trin <ibuprofin@painkiller.example.tld.invalid> |
|---|---|
| Date | 2016-09-09 20:55 +0000 |
| Subject | Re: What should I change my DNS to? (combined response) |
| Message-ID | <slrnnt68e9.4vr.ibuprofin@planck.phx.az.us> |
| In reply to | #3885 |
On Fri, 9 Sep 2016, in the Usenet newsgroup comp.os.linux.networking, in article
<meh9ad-arv.ln1@minas-tirith.valinor>, Carlos E. R. wrote:
>Moe Trin wrote:
>> A problem is finding a host out on the Internet that will respond
>> (ping has been abused so much that many Internet hosts disable the
>> responder). Lessee, www.ibiblio.org is a host in the Eastern USA,
>> and it has an IP address of 152.19.134.40. I choose it because from
>> experience I know it will _usually_ respond to pings.
>I use google.com. They can afford many pings, they don't care :-)
That's because "google.com" isn't a single host. It's many individual
hosts for load sharing. If you ask a DNS server for the IP address of
google.com, you'll get an answer with short TTL, and the answer will
vary from DNS server to DNS server and (often) from response to
response. I asked a dozen different DNS servers that respond to
non-customer queries using "host -a google.com $IP.ADDR.OF.DNS", and the
answers were:
[ingenio ~]$ grep -w A google.com.IPs
google.com. 285 IN A 216.58.199.14
google.com. 283 IN A 216.58.199.14
google.com. 258 IN A 216.58.203.14
google.com. 158 IN A 216.58.199.110
google.com. 276 IN A 216.58.199.14
google.com. 251 IN A 216.58.203.14
google.com. 299 IN A 216.58.218.174
google.com. 299 IN A 216.58.218.174
google.com. 293 IN A 216.58.217.206
google.com. 72 IN A 216.58.217.206
google.com. 21 IN A 216.58.199.110
google.com. 71 IN A 216.58.217.206
[ingenio ~]$
If you prefer IPv6 instead, the DNS servers gave me six different IPv6
addresses (interestingly, 3 in .au and 3 in .us, even though I'm in the
US and using US based nameservers). The reason for the variety of
answers is because that is what the Google authoritative name servers
are telling everyone who asks. If you were running your own recursive
DNS server, or if you asked one of the authoritative name servers (such
as ns1.google.com.) directly, you probably will get a different answer -
I just did, and got
google.com. 300 IN A 216.58.194.78
The A and AAAA record TTLs are 300 (seconds), and even the MX (mail
exchange) servers are only 600 (seconds). This "low" TTL allows rapid
switching of hostname <-> IP address values. Google (and other
high-bandwidth providers such as Akamai) try to give you the IP of the
"fastest" (closest by hop-count, or least loaded) server at any given
moment. As you are in Europe, you will likely see a different range of
addresses from what I see in the US or the O/P sees in Southeast Asia.
Thus, you may attempt to ping an IP (such as 216.58.199.14) and get no
response - because that particular host is on coffee break at the moment
and the hostname 'google.com' doesn't (AT THIS MOMENT) resolve to that
IP because of that fact. What can I say? ;-)
Old guy
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@invalid.es> |
|---|---|
| Date | 2016-09-10 02:47 +0200 |
| Subject | Re: What should I change my DNS to? (combined response) |
| Message-ID | <op1cad-kdi.ln1@minas-tirith.valinor> |
| In reply to | #3886 |
On 2016-09-09 22:55, Moe Trin wrote:
>> I use google.com. They can afford many pings, they don't care :-)
>
> That's because "google.com" isn't a single host. It's many individual
> hosts for load sharing.
Yes, I know, but that doesn't matter (for the current issue) :-)
The main thing is that they respond to ping, they leave it open.
> Thus, you may attempt to ping an IP (such as 216.58.199.14) and get no
> response - because that particular host is on coffee break at the moment
> and the hostname 'google.com' doesn't (AT THIS MOMENT) resolve to that
> IP because of that fact. What can I say? ;-)
I just typically do "ping google.es". If it fails, chances are it is me,
not google.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2016-09-10 08:27 +0000 |
| Subject | Re: What should I change my DNS to? (combined response) |
| Message-ID | <slrnnt7guv.rk3.BitTwister@wb.home.test> |
| In reply to | #3887 |
On Sat, 10 Sep 2016 02:47:20 +0200, Carlos E. R. wrote: > I just typically do "ping google.es". I ping yahoo.com one time for my "Internet" connectivity test. > If it fails, chances are it is me, not google. If you were to draw a picture of you internet connections with ip address at each nic connection, you might figure out you can write a script to ping each point along the way to see where the connection breaks down. You can look around in the modem for some IP addresses and use traceroute for your nodes ISP gateway. Depending on your setup and what you test, the testing results could look something like the following: $ network_ck 1 Testing that ping "127.0.0.1" and networking is working on wb 2 Testing that wb resolver reads /etc/hosts by "localhost" 3 Testing wb nic (enp3s0) access by ip address "192.168.13.122" 4 Testing that wb resolver reads /etc/hosts by "wb.home.test" 5 Testing that wb resolver reads /etc/hosts by "wb" 6 Testing that your ISP router's ethernet "192.168.13.1" nic is alive 7 Testing that ISP modem talks to ONT's fiber nic "71.172.145.40" 8 Testing that ONT fiber nic talks to ISP gateway "71.172.145.1" 9 Testing if DNS nameserver "127.0.0.1" is alive 10 Testing that ISP can route to "98.139.183.24" (yahoo.com) 11 Testing ISP can get a DNS result to "yahoo.com" 12 Testing that /etc/resolv.conf nameserver "127.0.0.1" is alive 13 Testing that /etc/resolv.conf nameserver "8.8.8.8" is alive Basic network connectivity is working to yahoo.com
[toc] | [prev] | [next] | [standalone]
| From | Moe Trin <ibuprofin@painkiller.example.tld.invalid> |
|---|---|
| Date | 2016-09-10 22:53 +0000 |
| Subject | Re: What should I change my DNS to? (combined response) |
| Message-ID | <slrnnt93o5.3o9.ibuprofin@planck.phx.az.us> |
| In reply to | #3888 |
On Sat, 10 Sep 2016, in the Usenet newsgroup comp.os.linux.networking, in
article <slrnnt7guv.rk3.BitTwister@wb.home.test>, Bit Twister wrote:
>Carlos E. R. wrote:
>> I just typically do "ping google.es".
>I ping yahoo.com one time for my "Internet" connectivity test.
"one time" makes you a good network neighbor. (Many people don't bother
to read the man-page and are unaware of the ping count option.) There
are other hosts out on the Internet that will usually respond, such as:
8.8.4.4 google-public-dns-b.google.com
8.8.8.8 google-public-dns-a.google.com
129.82.138.44 pinger6.netsec.colostate.edu.
152.19.134.40 www.ibiblio.org
195.251.255.69 zff45.unnamed.aueb.gr
203.178.148.19 pinger-j2.ant.isi.edu.
206.117.25.90 pinger-w4.ant.isi.edu.
varies google.com (a.k.a www.google.com)
varies yahoo.com
>If you were to draw a picture of you internet connections with ip
>address at each nic connection, you might figure out you can write a
>script to ping each point along the way to see where the connection
>breaks down. You can look around in the modem for some IP addresses
>and use traceroute for your nodes ISP gateway.
In my case, the Ethernet switch is on top of a file-cabinet where I can
see the lights blink when the LAN is in use. 'ping' (ICMP Echo) may
not work well - on Linux, see
[dawn ~]$ whatis ICMP
ICMP (7) - Linux IPv4 ICMP kernel module.
[dawn ~]$ cat /proc/sys/net/ipv4/icmp_echo_ignore_all
1
[dawn ~]$
Mentioned, many systems on the Internet are set to ignore pings, and
some [selectively] filter ICMP at the perimeter firewall. Other systems
may ignore/drop unexpected UDP packets, and that can break traceroute.
(UDP source addresses can be forged, and this is often used in Denial-
Of-Service attacks - see RFC2827 and RFC3704). This is why I prefer
"tcptraceroute" (or "traceroute -T" in some distros). For me, one or
two tcptraceroutes to systems (such as those ping-ables mentioned above)
will nearly always provide enough clues to explain why things aren't
working.
A good reason for knowing how to make simple tests is that the resulting
information can HELP the ISP. A thousand customers calling to say "The
Internet is down" is less useful than one who calls to say "the next-hop
router from 203.0.113.X to Genuity Net is not reachable" (but that
assumes a familiarity when the routes used by your ISP) or "the DNS
server on 198.51.100.56 is very slow". (Of course, some staff on the
hell-desk can't even _spell_ DNS, much less know what it is, and they
usually won't listen to you until you tell that that you have rebooted
your computer, and the router, and the refrigerator, and...)
Old guy
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@invalid.es> |
|---|---|
| Date | 2016-09-06 13:35 +0200 |
| Message-ID | <c8m2ad-jms.ln1@minas-tirith.valinor> |
| In reply to | #3834 |
On 2016-09-06 08:48, F Volker wrote:
...
> Well, this is the part which concerns me - my Gateway password was
> rejected, I tried several times but without success. So, instead of
> entering my specific username/password I used 'admin' for both Gateway
> user name and Gateway password and at this very instant was able to
> access my router details. However, all my specific router configurations
> were gone (as someone or something had re-set the router) and I had
> start all over again.
> I have no explanation for this occurrence and am sure my ISP would not
> want to comment on this issue.
> Could it be that my router got hacked by my ISP? What can I do to avoid
> this from happening again? I am on Linux Mint 17.3 KDE.
I doubt it would be a hack attempt, as the hackers would surely change
the login/pass to one of their own to deny you access. Or, not change it
at all from the one you set, so that you do not notice anything.
This looks rather like a chance reset. Like, a single bit flops, the
router notices the checksum does not match, and resets it all for
safety. Same thing the BIOS of a PC does to its own configuration stored
in CMOS.
You could google to find out if other people complain of random resets
of this same router model.
Like others, I do not think this is at all related to your DNS
choice(1). If you are paranoid about privacy, then run your own DNS.
Otherwise, it depends on whether you trust more your ISP or Google or
openDNS (or other), or which is faster.
(1) Unless the memory location where the DNS is stored happens to be
faulty :-P
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Aragorn <thorongil@telenet.be.invalid> |
|---|---|
| Date | 2016-09-06 14:06 +0200 |
| Message-ID | <nqmbh1$vim$1@dont-email.me> |
| In reply to | #3840 |
On Tuesday 06 Sep 2016 13:35, Carlos E. R. conveyed the following to
comp.os.linux.networking...
> On 2016-09-06 08:48, F Volker wrote:
>
>> Well, this is the part which concerns me - my Gateway password was
>> rejected, I tried several times but without success. So, instead of
>> entering my specific username/password I used 'admin' for both
>> Gateway user name and Gateway password and at this very instant was
>> able to access my router details. However, all my specific router
>> configurations were gone (as someone or something had re-set the
>> router) and I had start all over again.
>> I have no explanation for this occurrence and am sure my ISP would
>> not want to comment on this issue.
>> Could it be that my router got hacked by my ISP? What can I do to
>> avoid this from happening again? I am on Linux Mint 17.3 KDE.
>
> I doubt it would be a hack attempt, as the hackers would surely change
> the login/pass to one of their own to deny you access. Or, not change
> it at all from the one you set, so that you do not notice anything.
>
> This looks rather like a chance reset. Like, a single bit flops, the
> router notices the checksum does not match, and resets it all for
> safety. Same thing the BIOS of a PC does to its own configuration
> stored in CMOS.
>
> You could google to find out if other people complain of random resets
> of this same router model.
I've already had that happen a couple of times with a Linksys WRT54GL.
It's usually due to atmospheric conditions ─ high plasma content in the
air, cosmic rays, et al. These things don't have ECC memory and they're
poorly shielded.
In my own experience, there were two levels of severity to this kind of
disruption:
1. Only the wireless settings were botched, and my WiFi network was
wide open, but the LAN settings were unaffected.
2. Everything was botched, and even the IP range for my LAN was reset
back to the default range of 192.168.x.x, while my workstation
expects it to be in the 10.0.x.x range.
--
= Aragorn =
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@invalid.es> |
|---|---|
| Date | 2016-09-06 14:27 +0200 |
| Message-ID | <l9p2ad-m8u.ln1@minas-tirith.valinor> |
| In reply to | #3841 |
On 2016-09-06 14:06, Aragorn wrote:
> I've already had that happen a couple of times with a Linksys WRT54GL.
> It's usually due to atmospheric conditions ─ high plasma content in the
> air, cosmic rays, et al. These things don't have ECC memory and they're
> poorly shielded.
Ah, ECC memory. Well, errors in the config memory can be detected by a
simple checksum byte(s). I assume it is a flash chip of some kind. Or a
partition in the main flash memory, perhaps.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2016-09-06 13:03 +0000 |
| Message-ID | <slrnnstfie.mg7.dan@xps-linux.djph.net> |
| In reply to | #3842 |
Carlos E. R. wrote: > On 2016-09-06 14:06, Aragorn wrote: > >> I've already had that happen a couple of times with a Linksys WRT54GL. >> It's usually due to atmospheric conditions ─ high plasma content in the >> air, cosmic rays, et al. These things don't have ECC memory and they're >> poorly shielded. > > Ah, ECC memory. Well, errors in the config memory can be detected by a > simple checksum byte(s). I assume it is a flash chip of some kind. Or a > partition in the main flash memory, perhaps. > Doesn't help when the botched config is the running config though ;) -- |_|O|_| Registered Linux user #585947 |_|_|O| Github: https://github.com/dpurgert |O|O|O|
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@invalid.es> |
|---|---|
| Date | 2016-09-06 17:01 +0200 |
| Message-ID | <ka23ad-i53.ln1@minas-tirith.valinor> |
| In reply to | #3844 |
On 2016-09-06 15:03, Dan Purgert wrote:
> Carlos E. R. wrote:
>> On 2016-09-06 14:06, Aragorn wrote:
>>
>>> I've already had that happen a couple of times with a Linksys WRT54GL.
>>> It's usually due to atmospheric conditions ─ high plasma content in the
>>> air, cosmic rays, et al. These things don't have ECC memory and they're
>>> poorly shielded.
>>
>> Ah, ECC memory. Well, errors in the config memory can be detected by a
>> simple checksum byte(s). I assume it is a flash chip of some kind. Or a
>> partition in the main flash memory, perhaps.
>>
> Doesn't help when the botched config is the running config though ;)
Right, but normally the device should check that the checksum matches
when booting, and if it doesn't, reset to factory defaults, which is
what happened to the OP, IMO: he got factory defaults, including the
password.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2016-09-06 16:25 +0000 |
| Message-ID | <slrnnstrcn.mg7.dan@xps-linux.djph.net> |
| In reply to | #3845 |
Carlos E. R. wrote: > On 2016-09-06 15:03, Dan Purgert wrote: >> [snip] >> Doesn't help when the botched config is the running config though ;) > > Right, but normally the device should check that the checksum matches > when booting, and if it doesn't, reset to factory defaults, which is > what happened to the OP, IMO: he got factory defaults, including the > password. > Ah, I was taking it in the context of Aragorn's comments about devices just going stupid (and ecc ram maybe helping), rather than "broke on reboot". Broke on reboot should absolutely have some form of checksumming. Not that we're ever likely to see it. -- |_|O|_| Registered Linux user #585947 |_|_|O| Github: https://github.com/dpurgert |O|O|O|
[toc] | [prev] | [next] | [standalone]
| From | Tauno Voipio <tauno.voipio@notused.fi.invalid> |
|---|---|
| Date | 2016-09-06 21:37 +0300 |
| Message-ID | <nqn2d6$of4$1@dont-email.me> |
| In reply to | #3846 |
On 6.9.16 19:25, Dan Purgert wrote: > Carlos E. R. wrote: >> On 2016-09-06 15:03, Dan Purgert wrote: >>> [snip] >>> Doesn't help when the botched config is the running config though ;) >> >> Right, but normally the device should check that the checksum matches >> when booting, and if it doesn't, reset to factory defaults, which is >> what happened to the OP, IMO: he got factory defaults, including the >> password. >> > > Ah, I was taking it in the context of Aragorn's comments about devices > just going stupid (and ecc ram maybe helping), rather than "broke on > reboot". > > Broke on reboot should absolutely have some form of checksumming. Not > that we're ever likely to see it. > Could it be as simple as forgetting to save the changed parameters before reboot? -- -TV
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@invalid.es> |
|---|---|
| Date | 2016-09-06 23:42 +0200 |
| Message-ID | <aqp3ad-7va.ln1@minas-tirith.valinor> |
| In reply to | #3847 |
On 2016-09-06 20:37, Tauno Voipio wrote:
> Could it be as simple as forgetting to save the changed parameters
> before reboot?
In that case it would retain the previous settings, which should be
consistent. The checksum would match the contents. Not the contents you
expected, but as far as the firmware is concerned, correct. So no reset
to defaults.
Something that might happen is the firmware forgetting to recalculate
the checksum after writing the changed config. But such a tremendous bug
I don't see them doing, unless very bad programmers. Or insufficiently paid.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | F Volker <here@home.net> |
|---|---|
| Date | 2016-09-07 09:26 +0700 |
| Message-ID | <nqntso$1f39$1@gioia.aioe.org> |
| In reply to | #3840 |
On 09/06/2016 06:35 PM, Carlos E. R. wrote: [cut] > I doubt it would be a hack attempt, as the hackers would surely change > the login/pass to one of their own to deny you access. Or, not change it > at all from the one you set, so that you do not notice anything. This is comforting to know! > This looks rather like a chance reset. Like, a single bit flops, the > router notices the checksum does not match, and resets it all for > safety. Same thing the BIOS of a PC does to its own configuration stored > in CMOS. This could well be the case considering the age of computer, motherboard and router. > You could google to find out if other people complain of random resets > of this same router model. Lots of search results, need to do some serious reading... [cut] > (1) Unless the memory location where the DNS is stored happens to be > faulty :-P Maybe you could elaborate on this please, because some time ago I indeed experienced some problems related to the 'memory' sticks installed to the motherboard. My desktop is about 9 years old and the RAM was upgraded from 2GiB to 4GiB a couple of years ago or so. Motherboard details: American Megatrends Inc. ASUSTeK Computer INC. P5GC-MX/1333 Version: 0310 ASUS UPDATE: V7.10.05 Release date: 24 December 2007 Long story short, a recent memtest failed miserably and unbeknownst to me this particular motherboard apparently does not like to be upgraded in terms of RAM because when I inserting the old (original) RAM sticks the memtest passed with flying colours. The old BIOS most probably is for whatever reason rejecting the modules with higher RAM. Maybe 'old age' of equipment, insufficient RAM is the cause for all this and it's time to purchase both a new machine and router.
[toc] | [prev] | [next] | [standalone]
| From | Roger Blake <rogblake@iname.invalid> |
|---|---|
| Date | 2016-09-06 12:54 +0000 |
| Message-ID | <20160906084938@news.eternal-september.org> |
| In reply to | #3834 |
On 2016-09-06, F Volker <here@home.net> wrote: > I am not a technical person and wouldn't want to attempt running my own > DNS server. Though I am using a paid VPN service mainly for p2p > downloads am considering utilising the VPN service much more frequently. Check with your VPN provider. Some provide their own DNS server(s) as part of the service. > Well, this is the part which concerns me - my Gateway password was > rejected, I tried several times but without success. So, instead of > entering my specific username/password I used 'admin' for both Gateway > user name and Gateway password and at this very instant was able to > access my router details. However, all my specific router configurations > were gone (as someone or something had re-set the router) and I had > start all over again. It's not that unusual. I've seen this happen with power surges, sometimes for no apparent reason other than buggy firmware. -- ----------------------------------------------------------------------------- Roger Blake (Posts from Google Groups killfiled due to excess spam.) NSA sedition and treason -- http://www.DeathToNSAthugs.com Don't talk to cops! -- http://www.DontTalkToCops.com Badges don't grant extra rights -- http://www.CopBlock.org -----------------------------------------------------------------------------
[toc] | [prev] | [next] | [standalone]
| From | F Volker <here@home.net> |
|---|---|
| Date | 2016-09-07 09:28 +0700 |
| Message-ID | <nqntvh$1f39$2@gioia.aioe.org> |
| In reply to | #3843 |
On 09/06/2016 07:54 PM, Roger Blake wrote: [cut] > It's not that unusual. I've seen this happen with power surges, sometimes > for no apparent reason other than buggy firmware. I feel comforted that the consent here is that this glitch is not related to any hacking attempts to access my computer networks.
[toc] | [prev] | [next] | [standalone]
| From | William Unruh <unruh@invalid.ca> |
|---|---|
| Date | 2016-09-07 08:25 +0000 |
| Message-ID | <nqoiul$2e3$3@dont-email.me> |
| In reply to | #3855 |
On 2016-09-07, F Volker <here@home.net> wrote: > On 09/06/2016 07:54 PM, Roger Blake wrote: > > [cut] > >> It's not that unusual. I've seen this happen with power surges, sometimes >> for no apparent reason other than buggy firmware. > > I feel comforted that the consent here is that this glitch is not > related to any hacking attempts to access my computer networks. Noone here as any idea why YOUR machine reset. All we have done is list some other possibilities. Whether they, or a hacking attempt, are the explanation for your system none of us has any idea.
[toc] | [prev] | [next] | [standalone]
| From | Moe Trin <ibuprofin@painkiller.example.tld.invalid> |
|---|---|
| Date | 2016-09-07 03:29 +0000 |
| Message-ID | <slrnnsv2dk.fdi.ibuprofin@planck.phx.az.us> |
| In reply to | #3843 |
On Tue, 6 Sep 2016, in the Usenet newsgroup comp.os.linux.networking, in article
<20160906084938@news.eternal-september.org>, Roger Blake wrote:
]On Tue, 6 Sep 2016, F Volker wrote:
]I reside in a third world country within the SE Asia region. Power
]outages are regular events. An UPS is essential and it's working as
]expected. Connected to the UPS is a desktop computer, monitor and
]router.
>> However, all my specific router configurations were gone (as someone
>> or something had re-set the router) and I had start all over again.
>It's not that unusual. I've seen this happen with power surges,
>sometimes for no apparent reason other than buggy firmware.
He's got an unidentified UPS for power, and that _should_ reduce the
chance of power-surges, etc. I'm more concerned that the router may
be being reset to factory default, because every skript-kiddie in the
world knows it reverts to the admin:admin password pair.
Mind you, back in the mid 1970s, I was supporting some (US) FAA
experimental electronics at an airfield in California's Central Valley
about 75 miles / 120 km Southeast of San Francisco. This was prime
farming country because it was/is irrigated from canals or deep wells.
This means honking BIG electrically powered pumps (100 HP = 75 KVA)
and when they were turned on, I swear you could see the power poles
vibrating from the surges. Our equipment had "overkill" (for the
time) surge protection, LC filters, Metal Oxide Varistors, and such,
but I was still loosing one or two power supplies a month due to
surges. We eventually added a set of Control Concepts "Isolatrols"
which were an active tracking power-line filter. They weren't cheap
(US$275 in 1975 for a 115 VAC 15 Amp unit), but they completely
eliminated the surge problems. In 1978, I bought two units for the
house (protecting the home entertainment stuff). When we got our
first home computer in 1981, I added another unit for that. When we
bought additional computers in the mid-80s, we also added UPS units,
but I'm still using those Isolatrols to protect the UPSs.
Old guy
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | comp.os.linux.networking
csiph-web