Displaying 3 results from an estimated 3 matches for "ee6".
Did you mean:
e6
2008 Oct 03
1
Problem with glm.nb estimation
...today, R gave me an error message when estimating one of my usual
models:
> depEsf.nb <- glm.nb(depE ~ manuf00E + corps00E + lngdp00E + lngdp00sqE +
> lnpop00E + indshE + scishE + mechshE + elecshE + chemshE + drugshE +
> urban_dummyE + aggl_dummyE
+ + eE1 + eE2 + eE3 + eE4 + eE5 + eE6 + eE7 + eE8 + eE9 + eE10 + eE11 + eE12
+ eE13 + eE14 + eE15 + eE16 + eE17, maxit = 100000)
Warning messages:
1: In sqrt(1/i) : NaNs produced
2: In sqrt(1/i) : NaNs produced
What does it mean to receive such a message? And, most of all, can I fix
this problem?
The only problem I could think of i...
2020 Apr 30
2
Diagnosing IPv6 routing
...ost to Linode host:
[root at saruman ~]# traceroute6 2600:3c01::f03c:91ff:febc:e22d
traceroute to 2600:3c01::f03c:91ff:febc:e22d
(2600:3c01::f03c:91ff:febc:e22d), 30 hops max, 80 byte packets
1 2001:1890:1837:5b00::1 (2001:1890:1837:5b00::1) 3.230 ms 3.181 ms
3.137 ms
2 2001:1890:c05:2f3a::ee6e:61cd (2001:1890:c05:2f3a::ee6e:61cd) 6.906 ms
6.901 ms 6.870 ms
3 ok3ca81crs.ipv6.att.net (2001:1890:ff:ffff:12:123:6:98) 8.305 ms
8.254 ms 8.258 ms
4 sffca21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:110:65) 14.199 ms
14.164 ms 14.153 ms
5 sffca401igs.ipv6.att.net (2001:1890:ff:fff...
2020 Apr 28
3
Diagnosing IPv6 routing
On 4/28/2020 3:17 PM, Chris Adams wrote:
> - gateway sends a router solicitation and gets a router advertisement
> with "stateful config" set, which tells gateway to do DHCPv6 (but
> default route comes from RA)
I'm not seeing any outbound IPv6 traffic from my CentOS 7 box on the WAN
interface. I do see RA's emitting from the LAN interface, from radvd. Is
there