I have been getting a lot of helpful suggestions and will respond to
everything here:

1) Throughout all of today's testing, I have ensured that the tx_overrun
flag is never set.
2) On all runs that I have tried, the tx_afull flag is always set prior to
issuing the tap_start command.
3) I have the ability to toggle the tx_rst and rx_rst inputs and have done
so after the tap_start command is issued.
4) When I disconnect the PPC Net cable and only have the V6 Net cable
connected, I am no longer able to ping
5) The V6 Net and PPC Net devices have been physically mapped to different
subnets.  This did not fix the issue.
6) The name for the device is now changed from Riometer0 to Rio0.
7) Issuing the ifconfig after a tap_start command results in the following
information:

Rio0      Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.5.29  P-t-P:192.168.5.29  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

On the second line, the part that says 'P-t-P:192.168.5.29' looks
suspicious to me.

8) I am using WireShark to sniff the cable that is connected to the V6
Ethernet port.  As far as I can see, the V6 port never sends anything out
to the cable.

9) The machine I am pinging from never shows up on the tap-info list.

10) MAC addresses with a 02 in the first byte do have a special meaning
(see the second paragraph in the section 'Address details' at
http://en.wikipedia.org/wiki/MAC_address ).  In any case, there are no
routers/switches in the system between my desktop and the V6 port.

11) I still get the following message in the KATCP window:

#log info 964316466836 raw
detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964316466.839293s
#log info 964316467417 raw
detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964316467.419921s
#log info 964316467997 raw
detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964316468.000567s
#log info 964316468578 raw
detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964316468.581139s
#log info 964316469158 raw
detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964316469.161788s
#log info 964316469739 raw
detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964316469.742352s
#log info 964316470320 raw
detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964316470.323013s


Does anyone have some additional suggestions?

Thanks,

-Joe Kujawski

Reply via email to