Bug 230228 - pkg works with ipv4 / but not ipv6
Summary: pkg works with ipv4 / but not ipv6
Status: Closed Not A Bug
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 11.2-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: ipv6
Depends on:
Blocks:
 
Reported: 2018-07-31 05:51 UTC by Gary Tivey
Modified: 2018-07-31 21:32 UTC (History)
3 users (show)

See Also:


Attachments
Output from truss cmd while gif0 active (48.17 KB, text/plain)
2018-07-31 16:39 UTC, Gary Tivey
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Tivey 2018-07-31 05:51:59 UTC
Hi 'all ---> new install 11.2-STABLE ... had problems installing packages at a certain point, and even the ports stopped downloading files while compiling.

Background: TunnelBroker protocol 41 / IPV6 over IPV4 networking. It all worked fine since last week of June with FreeBSD 11.1-RELEASE.

Named/Bind service works fine over IPV6, Firefox fine accessing ipv6.google.com...but when the gif0 interface is activated, no web access for pkg program *search *install *etc.
When I shut down the gif interface, pkg works like greased' lightning! 

This is pretty unusual. FreeBSD networking stack is amazing..but that's what I have 'right now'. Can replicate.
Will work with developers.  thanks! --G
Comment 1 Conrad Meyer freebsd_committer freebsd_triage 2018-07-31 15:58:20 UTC
Can you please run an example pkg search/install under truss(1) and attach the log?  E.g., (as root probably),

$ truss -o pkg_ipv6.log pkg install foo

If pkg doesn't do anything too crazy that may help tell us what has gone wrong.  Thanks.
Comment 2 Gary Tivey 2018-07-31 16:39:14 UTC
Created attachment 195692 [details]
Output from truss cmd while gif0 active
Comment 3 Gary Tivey 2018-07-31 21:32:18 UTC
After checking the network ipv6 chain, I discovered that the end-point ip for the ipv6 tunnel had changed in the router. (likely thunderstorm caused) Since the computer had not been rebooted, the routing tables pointing to IPV6 land were still active but the link to IPV6 was not. Thanks to all who helped ! --G