Displaying 4 results from an estimated 4 matches for "tunnes".
Did you mean:
tunnel
2006 Oct 31
0
6393049 in.ndpd[XXXXX]: phyint_init_from_k: SIOCSLIFLNKINFO (interface ip6.tunN): Invalid argument
Author: pwernau
Repository: /hg/zfs-crypto/gate
Revision: b3afdaefb7d45f88f10766a716398f06d290cfb6
Log message:
6393049 in.ndpd[XXXXX]: phyint_init_from_k: SIOCSLIFLNKINFO (interface ip6.tunN): Invalid argument
Files:
update: usr/src/cmd/cmd-inet/usr.lib/in.ndpd/tables.c
2002 Dec 18
1
problem with 'gnls'
I'm working with data measured in a tunnel to estimate the
emission factor of heavy & light vehicles.
I tried to use 'gnls' and I get the following Error:
>> Error in "coef<-.corARMA"(*tmp*, value = c(174.267493382104, 173.412740072763 :
>> Coefficient matrix not invertible
Here is my R-code:
data <- d.plabutsch.neu
# calculating the starting
2011 Feb 25
2
problem with tunnels
I use ssh tunnels extensively. recently I upgraded my linux kernel from
2.6.18 to 2.6.37 and a problem with tunnels has resulted.
prior to the upgrade use of ssh tunN devices was rock solid.
the problem manifests as the tunnel from the initiator end ceasing to
transfer data to the remote after a quantity of data is sent. it is
necessary to create a new tunnel after destroying the old to get
2002 Dec 02
1
ipip and nexthdr
After carefull reading (LARTC) and experimentation, I am in a dead
end...
I am using several IPIP tunnels (linux ipip module, IP protocol 4).
I''d like to filter packets going through these tunnes to different
classes, on the ingress device, based on source and destination IP
_INSIDE THE TUNNEL_.
First I tried the nexthdr bit. As explained in LARTC, nexthdr jumps to
the next header in the packet, so I figured if it works for TCP, it
should also work for IP in IP, but it didn''t....