[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

sniffit problems



what does this error message mean?

	# sniffit -F dave -i
	Forcing device to dave (user requested)...
	Make sure you have read the docs carefully.
	unknown physical layer type 0x30a

here, dave is a tunnel device created via
	# create new device
	$IPCMD tunnel add $DEV \
			local $OUTSIDE_HERE \
			remote $OUTSIDE_THERE \
			mode $MODE \
			ttl $TTL
	# set it up to talk between these two points (with network on far end)
	ifconfig $DEV \
			$INSIDE_HERE pointopoint $INSIDE_THERE \
			netmask $MASK

and i can use it to tunnel windows file-share services,
so it's working just fine --

	# ifconfig dave
	dave      Link encap:UNSPEC  HWaddr D0-21-5A-55-00-00-00-00-00-00-00-00-00-00-00-00
			  inet addr:192.168.1.1  P-t-P:192.168.0.1  Mask:255.255.255.0
			  UP POINTOPOINT RUNNING NOARP  MTU:1476  Metric:1
			  RX packets:4300 errors:0 dropped:0 overruns:0 frame:0
			  TX packets:4308 errors:0 dropped:0 overruns:0 carrier:0
			  collisions:0 txqueuelen:0
	# route -n
	Kernel IP routing table
	Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
	208.33.90.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
	192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
	192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 dave
	0.0.0.0         208.33.90.84    0.0.0.0         UG    0      0        0 eth1

but what's up with sniffit?

when i just
# sniffit -i
all i see are my existing login/ssh sessions, altho i
can still ping 192.168.0.2 (which is past the remote end
of the tunnel, which is 192.168.0.1; my end is 192.168.1.1).

unfortunately, when running 'sniffit -i' the only options are
to check certain ports and certain ip numbers, not specific
devices.


-- 
things are more like they used to be than they are now.

will@serensoft.com *** http://www.dontUthink.com/



Reply to: