ContributionsMost RecentMost LikesSolutionsAnyone else having IPv6 trouble in the Wichita area? My router picks up the /128 for its external interface okay: FastEthernet4 [up/up] FE80::B6DE:31FF:FEA2:4BEC 2600:8803:7F11:300:54BF:ED91:45A5:7F07 ...but never receives the /56 prefix; the DHCPv6 client stays in SOLICIT: FastEthernet4 is in client mode Prefix State is SOLICIT (1) Information refresh timer expires in 23:43:58 Address State is OPEN Renew for address will be sent in 11:43:58 List of known servers: Reachable via address: FE80::EE1D:8BFF:FE08:6419 DUID: 00010001561BCA61F8BC123D6028 Preference: 0 Configuration parameters: IA NA: IA ID 0x00080001, T1 43200, T2 69120 Address: 2600:8803:7F11:300:54BF:ED91:45A5:7F07/128 preferred lifetime 86400, valid lifetime 86400 expires at Apr 21 2018 12:35 PM (85439 seconds) DNS server: 2001:578:3F::30 DNS server: 2001:578:3F:1::30 Information refresh time: 0 Prefix name: prefix-from-provider Prefix Rapid-Commit: enabled Address Rapid-Commit: enabled Prefixes sent as hint: ::/56 Anyone else seeing the like? -c Re: Dynamic port blocking - what the heck? ..sorry, please ignore this. Found a local problem upstream of the router. -c Re: Dynamic port blocking - what the heck? I should note that this port appears closed (i.e., connection refused) rather than giving no response, unlike the ports listed here:https://www.cox.com/residential/support/internet-ports-blocked-or-restricted-by-cox.html . -c Dynamic port blocking - what the heck? I'm having a peculiar issue with inbound TCP connections (to my local smart home services and Plex server). Basically, after a period of successful operation, I can no longer receive inbound connections on a given TCP port (it shows as connection refused), and have to change the port mapping to be able to access it again; then, after another period, the new port becomes closed/connection refused, and I have to change it again - although usually the old one works again by this time. It's definitely upstream of me (I have tested with a laptop on the outside of my router), so any thoughts on what's exactly going on, and how it can be stopped? -c SolvedRe: Have you guys started blocking port 443 (https) inbound in the last couple of days? Hrm. It's very odd, then. I suspected something was up because I can see the other blocked ports on a quick scan (most ports show up as closed, but the ones Cox blocks generate no response at all to a connection attempt), whereas what I see with this is that 443 is showing up as closed. (Suddenly, after months of successful operation.) Fiddling with the static NAT mappings on my router, though, other ports work just fine when mapped to the same home-automation endpoint: 442, open and responsive, 444, open and responsive, but 443, nothing. Thanks, -c Have you guys started blocking port 443 (https) inbound in the last couple of days? Because it's started showing as closed/unconnectable for me from outside, and I'm not showing any changes or issues at my end. (Not trying to run a web server from home here in any but the most technical sense; it's for smart home integration, and Alexa skills have to run on the standard https port...) -c IPv6 prefix changing Is it normal for, or are there circumstances under which you can expect, the IPv6 prefix delegated to you by Cox to change? (I had been under the impression that, unlike IPv4 addresses, these were not dynamically assigned.) I ask in this case because my /56 just has afterbouncing the external interface onmy borderrouter, which I would not have thought should cause that. (I had expected that it might change, on the other hand, after upgrading my modem some months ago, which did not appear to cause it; although, on thinking back, this is the first time the external interface has beenadministratively downsince the modem was swapped out.) In any case, is there any word on when and why this can be expected to happen? While the router picks up the change of prefix just fine interface address-wise, it does force me to manually rejig the neighbor discovery config on the internal interface, the firewall rules, andmy external DNS, in order to restore connectivity which is something of a pain in the neck, belike. -c