Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #173361

Re: url redirected in chrome/chromium, but working fine, according to ping/traceroute, lynx, w3m, iceweasel.

Show all headers | View raw

I'm not the OP, and I'm sort of piggybacking and going somewhat (or a lot?) 
OT, but I am curious about how old inet4 (right term?) and the new inet6 
addresses interact.

When I do ifconfig, I see that eth0 has both a 32 bit (e.g., 192.168.1.19) and 
an inet6 address assigned.

Can anybody point me to a fairly short document that explains things like 
which gets used under what circumstances, does one have precedence over the 
other, do they both use DNS, and similar things which might let me make sense 
of the situation?

On Sunday, October 09, 2016 03:02:25 PM Tony Baldwin wrote:
> On 10/09/2016 11:54 AM, claude juif wrote:
> > Are you logged in with a google account on that chrome/chromium ? By
> > the way, how did you install them ?
>

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Tony Baldwin <tonybaldwin@gmx.com> - 2016-10-07 20:10 +0200
  Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Anthony Baldwin <baldwinlinguas@gmx.com> - 2016-10-07 20:30 +0200
    Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. claude juif <claude.juif@gmail.com> - 2016-10-07 20:40 +0200
      Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Anthony Baldwin <baldwinlinguas@gmx.com> - 2016-10-07 21:50 +0200
  Re: url redirected in chrome/chromium, but working fine, according  to ping/traceroute, lynx, w3m, iceweasel. davidson@freevolt.org - 2016-10-08 00:50 +0200
    Re: url redirected in chrome/chromium, but working fine, according  to ping/traceroute, lynx, w3m, iceweasel. davidson@freevolt.org - 2016-10-08 01:00 +0200
    Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Anthony Baldwin <baldwinlinguas@gmx.com> - 2016-10-08 04:10 +0200
      Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. claude juif <claude.juif@gmail.com> - 2016-10-08 17:30 +0200
        Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Tony Baldwin <tonybaldwin@gmx.com> - 2016-10-08 17:40 +0200
        Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Tony Baldwin <tonybaldwin@gmx.com> - 2016-10-08 17:40 +0200
          Re: url redirected in chrome/chromium, but working fine, according  to ping/traceroute, lynx, w3m, iceweasel. <tomas@tuxteam.de> - 2016-10-08 20:10 +0200
  Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Richard Hector <richard@walnut.gen.nz> - 2016-10-09 13:20 +0200
    Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Tony Baldwin <tonybaldwin@gmx.com> - 2016-10-09 13:30 +0200
      Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Lars Noodén <lars.nooden@gmail.com> - 2016-10-09 13:40 +0200
      Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Richard Hector <richard@walnut.gen.nz> - 2016-10-09 13:40 +0200
        Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Tony Baldwin <tonybaldwin@gmx.com> - 2016-10-09 15:10 +0200
          Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. claude juif <claude.juif@gmail.com> - 2016-10-09 18:00 +0200
            Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Tony Baldwin <tonybaldwin@gmx.com> - 2016-10-09 21:10 +0200
              Re: url redirected in chrome/chromium, but working fine, according to ping/traceroute, lynx, w3m, iceweasel. rhkramer@gmail.com - 2016-10-09 22:30 +0200
                ifconfig question (recovered from hijacked thread ) Anthony Baldwin <baldwinlinguas@gmx.com> - 2016-10-10 19:30 +0200
                Linux source address selection (Was Re: url redirected in  chrome/chromium, but working fine, according to ping/traceroute, lynx,  w3m, iceweasel.) Andy Smith <andy@strugglers.net> - 2016-10-12 04:40 +0200
                Re: Linux source address selection (Was Re: url redirected in chrome/chromium, but working fine, according to ping/traceroute, lynx, w3m, iceweasel.) rhkramer@gmail.com - 2016-10-12 11:40 +0200
        Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2016-10-09 18:20 +0200
      Re: url redirected in chrome/chromium, but working fine, according to ping/traceroute, lynx, w3m, iceweasel. Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-26 18:00 +0200
    Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Tony Baldwin <tonybaldwin@gmx.com> - 2016-10-09 13:30 +0200
      Re: url redirected in chrome/chromium, but working fine, according to  ping/traceroute, lynx, w3m, iceweasel. Richard Hector <richard@walnut.gen.nz> - 2016-10-09 13:30 +0200
  Re: url redirected in chrome/chromium, but working fine, according to ping/traceroute, lynx, w3m, iceweasel. Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-26 18:00 +0200

csiph-web