Name Picture of Glen Lalonde My alias








QuiBids Support Page

BidTracker stopped working?

Most of the time the issue is that QuiBids changed their IP address information, thus the filter in WireShark stops BidTracker from seeing anything.
For most people, a very quick fix is to just fill in the capture file part of the wireshark capture options dialog as you usually do, but
leave the capture filter part empty. This will always work, only problem is it will capture data from ALL the trafic from your computer.
This might be an issue for slower computers.

Update July 2012:

New version of wireshark does work with Quibids but you must unselect the "use pcap-ng format" in the capture Options window.
Also the filters do still exists, scroll in the interface list on the top of the capture options windows and select the filters column.

Current value I use is :src host 64.74.193 and tcp[tcpflags] & (tcp-push) != 0
(yes that is 64.74.193 since you want 64.74.193.XXX all to capture)

-----
OLD:


Also existing both BidTracker and WireShark and restarting, can some times resolve the issue.

Current as of Apr 29, 2012: (you can always just leave it blank, but that may slow down your pc and you might not be able to follow as many auctions)
(enter this string in the WireShark Capture Options, Capture filter field:

src host 64.74.193.77 or src host 64.74.193.71 and tcp[tcpflags] & (tcp-push) != 0

---
OLD:
Current Filter value, as of Jan 22, 2012:

(enter this string in the WireShark Capture Options, Capture filter field:

src host 72.52.7.161 or src host 66.114.53.27 or src host 72.52.7.167 and tcp[tcpflags] & (tcp-push) != 0