Strange network/firefox-related observations; any pointer to tool or page or google search term


#1

So I installed TrueOS on my system very recently. …

The strange observations I made today were related to network and firefox. I started firefox and then tried to go to a news site and it gave an error “could not connect”. Then, I wondered if I could connect to this forum and I got just blank white, yet I hit “view source” and saw plenty of source! I opened a terminal and typed “curl https://discourse.trueos.org/” and saw source too. For the news article (https://hbr.org/2018/07/when-generalists-are-better-than-specialists-and-vice-versa) that gave me the “Could not connect” error, I hit “ping hbr.org” at a terminal and it said “no route to host”, but I tried to “ping” google.com and www.google.com and got the same “no route to host” errors so I’m not sure if the ping output is trustworthy! What’s particularly strange is that other websites such as youtube I was able to visit without any issue! it’s strange when one site works and not another. I used my smartphone to visit the sites my computer wouldn’t to verify they sites weren’t down. I also had my phone be connected to the wifi network that the computer is connected to the same router (but via wired not wifi like my phone).

I wonder can anybody offer any pointer/guidance as to what tool or tools or links I can try or read up on to try to debug this and/or try to understand why the behaviour is not as desired and is not as expected? The desired and expected behaviour is of course to be able to load the sites!

Has anyone made similar observations?

edit: it has been a long time since I’ve done any networking debug …

thanks!

PS, using the “appcafe” (thanks @RJules3) I was able to install virtualbox and boot virutal TrueOS (guest) from TrueOS host and in the virtual TrueOS, I was not able to view any site I tried (not google!). something about the networking doesn’t seem right.


#2

Wired or WiFi

DHCP or Static?

Can you ping anything else on your LAN?

Can you ping yourself, and not 127.0.0.1?


#3

thank you for your reply @RodMyers !

my computer is connected wired.

everything is dynamic/DHCP. The router gets a dynamic IP from the ISP (comcast) and all my devices get assigned an IP from the cable modem/router

next time I boot into TrueOS (I type via ubuntu at the moment), I can see if I can ping myself (127.0.0.1 and “localhost”) and also my other computer and see the result.

it seems quite stragne to me that some sites I could visit and others not…in my experience, it’s usually an all-or-none things except in the rare cases where a remote site is actually “down” !

-eddie

PS
I should’ve thought of those two (ping self, ping others on the LAN) I guess I am tired after a long day…I did some TrueOS stuff this morning, caffeinated…but bedtime is coming soon tonight, so I’m not caffeinated…


#4

I just booted into/outof TrueOS and now am in ubuntu…

I was able to ssh to my other computer but darn it after I was able to ssh to it, I sort of forgot to ping it. … thinking that if I can ssh to it, presumably the ping would be okay, but I should have pinged my other machine!

edit: I do confirm that I was able to ping myself (both localhost and 127.0.0.1)

I was also able to ssh to myself (localhost and 127.0.0.1).

I tried curl to this site and got data, but it’s strange that firefox in TrueOS wouldn’t display the site

I was able to use curl with this site…

[esalina@trueos-7709] ~% curl https://discourse.trueos.org/ | head
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>TrueOS Community</title>
    <meta name="description" content="Conversation and discussion around the TrueOS operating system">
    <meta name="author" content="">
<meta name="generator" content="Discourse 2.1.0.beta2 - https://github.com/discourse/discourse version 202b839208d4127b73d2206dc1a96efe408b7bd8">
<link rel="icon" type="image/png" href="/uploads/trueos/original/1X/fe1842117baf87ac3f15bbb493924865d64cfd6a.png">
<link rel="apple-touch-icon" type="image/png" href="/uploads/trueos/original/1X/6a7abd0e493a0b1aa6ac39dd4da4f88fe0597c1f.png">
100 15676    0 15676    0     0  21832      0 --:--:-- --:--:-- --:--:-- 21863
curl: (23) Failed writing body (0 != 8192)

…but not ping…

[esalina@trueos-7709] ~% ping discourse.trueos.org
PING trueos.hosted-by-discourse.com (216.218.240.90): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host

but not with the hbr.org site

[esalina@trueos-7709] /.autofs/ada0s2/TrueOS_share% curl https://hbr.org/2018/07/when-generalists-are-better-than-specialists-and-vice-versa
curl: (7) Couldn't connect to server


#5

Try to disable ipv6 support first.


#6

Also, use the about command and paste the results here as well


#7

Ok, two items of response @RodMyers and one question if you can offer any advice Rod or @vit

  1. I am in trueOS now as I type this and I’m able to get to the forum! Earlier I was not able but now I am able to get to the forum! I did not disable IPV6 support, all I did was reboot! Also, now am I not only able to visit this forum I’m able to visit the hbr link. I would suspect that such strangeness is because of my ISP, but I was in trueOS, could not access the hbr, then went to ubuntu, then could, then returned to TrueOS and then could not again…which seems to point to TrueOS or a configuration in TrueOS being the source … I suppose it’s possibly the ISP (comcast!) but it seems statistically unlikely???

  2. Here is the output of “about -a”

[esalina@trueos-7709] /.autofs/ada0s2/TrueOS_share% about -a

===================
General information
===================

boot environment now (N) … initial NR 2018-07-16
       after restart (R) … initial NR 2018-07-16
boot loader …………………………………… BSD
            type ……………………… BIOS
CPU ………………………………………………………… Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz
    number of cores ……………… 20
host ……………………………………………………… trueos-7709
memory ………………………………………………… 131072 MB available, 124900 MB free
OS git branch ……………………………………………………………………………………… trueos-stable-18.03
OS git revision ………………………………………………………………………………… fa797a5a3
OS kernel build time ………………………………………………………… Mon 2018 Mar 26 00:24:47 UTC
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… STABLE
TrueOS version …………………………… TrueOS-Desktop-201803131015
uptime ………………………………………………… 8 mins
user  …………………………………………………… esalina

More (TrueOS Desktop):

    desktop environment …… Lumina
    sound card driver ………… pcm5: <NVIDIA (0x0082) (HDMI/DP 8ch)> (play) default
    wireless driver ……………… 
    X11 drivers ………………………… nvidia_drv.so 


==========
Networking
==========

Default routing table
---------------------

   route to: default
destination: default
       mask: default
    gateway: 192.168.0.1
        fib: 0
  interface: em0
      flags: <UP,GATEWAY,DONE,STATIC>
 recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1500         1         0 

Routing table in numeric format
-------------------------------

Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
default            192.168.0.1        UGS         em0
127.0.0.0/8        127.0.0.1          UGS         lo0
127.0.0.1          link#3             UH          lo0
192.168.0.0/24     link#2             U           em0
192.168.0.14       link#2             UHS         lo0

Internet6:
Destination                       Gateway                       Flags     Netif Expire
::/96                             ::1                           UGRS        lo0
default                           fe80::c2ff:d4ff:fee9:532%em0  UGS         em0
::1                               link#3                        UH          lo0
::ffff:0.0.0.0/96                 ::1                           UGRS        lo0
2601:46:200:74b0::/64             link#2                        US          em0
2601:46:200:74b0:f5fb:8b0d:87a:d641 link#2                      UHS         lo0
fe80::/10                         ::1                           UGRS        lo0
fe80::%alc0/64                    link#1                        U          alc0
fe80::21f:bcff:fe12:8af3%alc0     link#1                        UHS         lo0
fe80::%em0/64                     link#2                        U           em0
fe80::21f:bcff:fe12:8af2%em0      link#2                        UHS         lo0
fe80::%lo0/64                     link#3                        U           lo0
fe80::1%lo0                       link#3                        UHS         lo0
ff02::/16                         ::1                           UGRS        lo0

Interface information, condensed
--------------------------------

alc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c319a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MCAST,WOL_MAGIC,VLAN_HWTSO,LINKSTATE>
        inet6 fe80::21f:bcff:fe12:8af3%alc0 prefixlen 64 scopeid 0x1 
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect (none)
        status: no carrier
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=85259b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
        inet6 fe80::21f:bcff:fe12:8af2%em0 prefixlen 64 scopeid 0x2 
        inet6 2601:46:200:74b0:f5fb:8b0d:87a:d641 prefixlen 64 
        inet 192.168.0.14 netmask 0xffffff00 broadcast 192.168.0.255 
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 
        inet 127.0.0.1 netmask 0xff000000 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo 

DNS-related
-----------

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 4445
;; flags: qr rd ra ; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13 
;; QUESTION SECTION:
;; .    IN      NS

;; ANSWER SECTION:
.       499829  IN      NS      e.root-servers.net.
.       499829  IN      NS      f.root-servers.net.
.       499829  IN      NS      g.root-servers.net.
.       499829  IN      NS      h.root-servers.net.
.       499829  IN      NS      i.root-servers.net.
.       499829  IN      NS      a.root-servers.net.
.       499829  IN      NS      j.root-servers.net.
.       499829  IN      NS      k.root-servers.net.
.       499829  IN      NS      l.root-servers.net.
.       499829  IN      NS      m.root-servers.net.
.       499829  IN      NS      b.root-servers.net.
.       499829  IN      NS      c.root-servers.net.
.       499829  IN      NS      d.root-servers.net.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:
m.root-servers.net.     599347  IN      A       202.12.27.33
m.root-servers.net.     601976  IN      AAAA    2001:dc3::35
b.root-servers.net.     172050  IN      A       199.9.14.201
b.root-servers.net.     399284  IN      AAAA    2001:500:200::b
c.root-servers.net.     318003  IN      A       192.33.4.12
c.root-servers.net.     399285  IN      AAAA    2001:500:2::c
d.root-servers.net.     392415  IN      A       199.7.91.13
d.root-servers.net.     399285  IN      AAAA    2001:500:2d::d
e.root-servers.net.     271898  IN      A       192.203.230.10
e.root-servers.net.     399285  IN      AAAA    2001:500:a8::e
f.root-servers.net.     281584  IN      A       192.5.5.241
f.root-servers.net.     399285  IN      AAAA    2001:500:2f::f
g.root-servers.net.     332207  IN      A       192.112.36.4

;; Query time: 18 msec
;; SERVER: 2001:558:feed::2
;; WHEN: Thu Jul 19 19:55:27 2018
;; MSG SIZE  rcvd: 508

----

IPv4 key points (not interface specific): 

    192.168.0.14
    127.0.0.1

IPv6 key points (not interface-specific): 

    fe80::21f:bcff:fe12:8af3%alc0
    fe80::21f:bcff:fe12:8af2%em0
    2601:46:200:74b0:f5fb:8b0d:87a:d641
    ::1
    fe80::1%lo0

Any my question now: Should I disable IPV6 if the networking issue is resolved? and apparently self-resolved at that…

THANK YOU! @RodMyers @vit

-eddie


#8

Welcome

I would still disable ipv6 in your /etc/rc.conf

ipv6_activate_all_interfaces=“NO”

add that and reboot


#9

thank you for your support @RodMyers I appreciate it!

I added the line to my /etc/rc.conf, but the about -n seems to show ipv6 isn’t disabled because there are several settings/information about it in the output? Despite the output of “about -n” is ipv6 in fact disabled?


[esalina@trueos-7709] ~% tail -1 /etc/rc.conf && about -n
ipv6_activate_all_interfaces="NO"

==========
Networking
==========

Default routing table
---------------------

   route to: default
destination: default
       mask: default
    gateway: 192.168.0.1
        fib: 0
  interface: em0
      flags: <UP,GATEWAY,DONE,STATIC>
 recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1500         1         0 

Routing table in numeric format
-------------------------------

Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
default            192.168.0.1        UGS         em0
127.0.0.0/8        127.0.0.1          UGS         lo0
127.0.0.1          link#3             UH          lo0
192.168.0.0/24     link#2             U           em0
192.168.0.14       link#2             UHS         lo0

Internet6:
Destination                       Gateway                       Flags     Netif Expire
::/96                             ::1                           UGRS        lo0
default                           fe80::c2ff:d4ff:fee9:532%em0  UGS         em0
::1                               link#3                        UH          lo0
::ffff:0.0.0.0/96                 ::1                           UGRS        lo0
2601:46:200:74b0::/64             link#2                        US          em0
2601:46:200:74b0:f5fb:8b0d:87a:d641 link#2                      UHS         lo0
fe80::/10                         ::1                           UGRS        lo0
fe80::%alc0/64                    link#1                        U          alc0
fe80::21f:bcff:fe12:8af3%alc0     link#1                        UHS         lo0
fe80::%em0/64                     link#2                        U           em0
fe80::21f:bcff:fe12:8af2%em0      link#2                        UHS         lo0
fe80::%lo0/64                     link#3                        U           lo0
fe80::1%lo0                       link#3                        UHS         lo0
ff02::/16                         ::1                           UGRS        lo0

Interface information, condensed
--------------------------------

alc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c319a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MCAST,WOL_MAGIC,VLAN_HWTSO,LINKSTATE>
        inet6 fe80::21f:bcff:fe12:8af3%alc0 prefixlen 64 scopeid 0x1 
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect (none)
        status: no carrier
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=85259b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
        inet6 fe80::21f:bcff:fe12:8af2%em0 prefixlen 64 scopeid 0x2 
        inet6 2601:46:200:74b0:f5fb:8b0d:87a:d641 prefixlen 64 
        inet 192.168.0.14 netmask 0xffffff00 broadcast 192.168.0.255 
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 
        inet 127.0.0.1 netmask 0xff000000 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo 

DNS-related
-----------

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 350
;; flags: qr rd ra ; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13 
;; QUESTION SECTION:
;; .    IN      NS

;; ANSWER SECTION:
.       495838  IN      NS      g.root-servers.net.
.       495838  IN      NS      h.root-servers.net.
.       495838  IN      NS      i.root-servers.net.
.       495838  IN      NS      j.root-servers.net.
.       495838  IN      NS      k.root-servers.net.
.       495838  IN      NS      l.root-servers.net.
.       495838  IN      NS      m.root-servers.net.
.       495838  IN      NS      a.root-servers.net.
.       495838  IN      NS      b.root-servers.net.
.       495838  IN      NS      c.root-servers.net.
.       495838  IN      NS      d.root-servers.net.
.       495838  IN      NS      e.root-servers.net.
.       495838  IN      NS      f.root-servers.net.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:
a.root-servers.net.     468873  IN      A       198.41.0.4
a.root-servers.net.     470017  IN      AAAA    2001:503:ba3e::2:30
b.root-servers.net.     492675  IN      A       199.9.14.201
c.root-servers.net.     530396  IN      A       192.33.4.12
c.root-servers.net.     582431  IN      AAAA    2001:500:2::c
d.root-servers.net.     488315  IN      A       199.7.91.13
d.root-servers.net.     521419  IN      AAAA    2001:500:2d::d
e.root-servers.net.     527417  IN      A       192.203.230.10
e.root-servers.net.     581482  IN      AAAA    2001:500:a8::e
f.root-servers.net.     509487  IN      A       192.5.5.241
f.root-servers.net.     591151  IN      AAAA    2001:500:2f::f
g.root-servers.net.     530086  IN      A       192.112.36.4
g.root-servers.net.     322794  IN      AAAA    2001:500:12::d0d

;; Query time: 12 msec
;; SERVER: 75.75.75.75
;; WHEN: Thu Jul 19 20:31:11 2018
;; MSG SIZE  rcvd: 508

----

IPv4 key points (not interface specific): 

    192.168.0.14
    127.0.0.1

IPv6 key points (not interface-specific): 

    fe80::21f:bcff:fe12:8af3%alc0
    fe80::21f:bcff:fe12:8af2%em0
    2601:46:200:74b0:f5fb:8b0d:87a:d641
    ::1
    fe80::1%lo0

[esalina@trueos-7709] ~% 


#10

Reminds me the following thread:

Which was related to the start order of net services.
If it’s working now, just leave it as is and wait for the next update.


#11

Re IPV6:

# /etc/defaults/rc.conf

### IPv6 options: ###
ipv6_network_interfaces="auto"  # List of IPv6 network interfaces
                                # (or "auto" or "none").
ipv6_activate_all_interfaces="NO"       # If NO, interfaces which have no
                                        # corresponding $ifconfig_IF_ipv6 is
                                        # marked as IFDISABLED for security
                                        # reason.

ip6addrctl_enable="YES" # Set to YES to enable default address selection
ip6addrctl_verbose="NO" # Set to YES to enable verbose configuration messages
ip6addrctl_policy="AUTO"        # A pre-defined address selection policy
                                # (ipv4_prefer, ipv6_prefer, or AUTO)

pls don’t edit /etc/defaults/rc.conf.


#12

Maybe not related to your issue, but ping is using internet control protocol (ICMP) which may be blocked by some routers. We all mainly use TCP and UDP of which neither need ICMP or the mode ping is using.

You can do a traceroute and see where it stops. It supports multiple protocols so you can test ICMP, TCP etc. (see man traceroute, which has examples of different situations.)

And ah, yes. Could be a IPv6 vs IPv4 issue.

Edit
Hehe, following up with missed subjects I thought nobody had replied.


#13

Thanks for this reminder @bsdisgood about ICMP. I can try traceroute and see if I can see where things stop


#14

Hi @vit as I interpret your post you mean that I should edit /etc/defaults/rc.conf but leave /etc/rc.conf alone


#15

This morning from trueOS I am observing that I cannot see the forum again so it seems the issue returned! :frowning:

And now I’m reviewing the /etc/defaults/rc.conf and it matches @vit the snippet you show


#16

On a contrary, put your changes into either /etc/rc.conf or /etc/rc.conf.local. Leave the defaults alone. I mentioned the defaults as a source, where one can find all the system settings and their descriptions. I’m sorry I wasn’t clear about that.
See https://www.freebsd.org/cgi/man.cgi?rc.conf(5)

According to the defaults, the ipv6_activate_all_interfaces works under some conditions and may not always switch off ipv6 support. I think the ipv6_network_interfaces and ip6addrctl_enable are “better” alternatives (depending on one’s needs). I’m suggesting:

# /etc/rc.conf

ipv6_network_interfaces="none"
ipv6_activate_all_interfaces="NO"
ip6addrctl_enable="NO"

Technically, just ip6addrctl_enable="NO" should be enough as a single global switch, but the CURRENT branch is unpredictable thing. In addition, tos/trident devs might have something undocumented in their init scripts. Some of the above may or may not work.