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


Groups > linux.debian.user > #173407

ifconfig question (recovered from hijacked thread )

From Anthony Baldwin <baldwinlinguas@gmx.com>
Newsgroups linux.debian.user
Subject ifconfig question (recovered from hijacked thread )
Date 2016-10-10 19:30 +0200
Message-ID <sqMyK-412-19@gated-at.bofh.it> (permalink)
References <spHKP-49t-47@gated-at.bofh.it> <sqoG5-66q-21@gated-at.bofh.it> <sqrDX-89N-3@gated-at.bofh.it> <sqsTo-mZ-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw



On 10/09/2016 04:23 PM, rhkramer@gmail.com wrote:
> 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?

Don't hijack another thread, send a new mail with an appropriate subject 
line like the one on this message. That way you're more likely to get 
the help you need, and it's just proper list edicate.

Good luck
tony (OP of the thread you tried to hijack)


-- 
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT

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