Re: Wget, Yum and network investigation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tim:
> And are those other services using IPv6, too?  *And* if they do, and 
> they work, do they also go through the proxy?

antonio montagnani:
> sorry for the HTML, but I am  new to Gmail, so I am not sure where to
> switch off HTML (I hope now it is not HMTL!!!

It was still HTML, and I don't know the trick to stopping Gmail from
doing that.

> How do I know if other services go through IPv6???

Using "netstat -tu" to show current TCP and UDP connections might be all
you need to do.  You can use additional options with netstat for more
information (such as showing what process/program is using the port).

e.g. netstat -ntu
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 192.168.1.2:57310           192.168.1.2:143             ESTABLISHED
tcp        0      0 192.168.1.2:57311           192.168.1.2:143             ESTABLISHED
tcp        0      0 ::ffff:192.168.1.2:143      ::ffff:192.168.1.2:57310    ESTABLISHED
tcp        0      0 ::ffff:192.168.1.2:143      ::ffff:192.168.1.2:57311    ESTABLISHED

The first two are IPv4, the latter two are IPv6.  Note the much longer
IP address, with colons between digits.  Ignore the last colon-prefixed
ones (57310, 143, etc.), they're the port numbers being used with those
addresses.

> and why on the other network PC everything is o.k, wget, curl yum
> are o.k???

Chances are, that if other things are working, that they're not using
IPv6 addresses at that time.  I only mention IPv6 because your prior
comments about explictly telling wget to use it, or not, and the
differing results.  To be able to use it, the entire network path
between you and it would need to support it.

I've seen the following about disabling ipv6 in a prior message on this
mailing list (a different topic).  Maybe you might want to try it.

  Add "alias net-pf-10 off" to /etc/modprobe.conf and reboot

When debugging DNS issues, you probably want to try playing with the
"dig" command, rather than other commands.  You'll get more specific
information about the name resolution.

e.g. dig download.fedora.redhat.com

; <<>> DiG 9.3.1 <<>> download.fedora.redhat.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54899
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;download.fedora.redhat.com.    IN      A

;; ANSWER SECTION:
download.fedora.redhat.com. 246 IN      A       209.132.176.221
download.fedora.redhat.com. 246 IN      A       66.187.224.20
download.fedora.redhat.com. 246 IN      A       209.132.176.20
download.fedora.redhat.com. 246 IN      A       209.132.176.220

;; AUTHORITY SECTION:
redhat.com.             546     IN      NS      ns3.redhat.com.
redhat.com.             546     IN      NS      ns1.redhat.com.
redhat.com.             546     IN      NS      ns2.redhat.com.

;; Query time: 70 msec
;; SERVER: 192.168.1.2#53(192.168.1.2)
;; WHEN: Thu Feb 23 23:19:51 2006
;; MSG SIZE  rcvd: 162

-- 
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux