If this is a managed VPN Service AT&T should be able to decipher this issue,
Also are they using a hardware VPN concentrator at work?
Gianluca Varenni <[EMAIL PROTECTED]> wrote: This is definitely a WinPcap
issue and not a wireshark one (wireshark receives packets from WinPcap).
I wou
> From: [EMAIL PROTECTED]
>
> This may be a bit more difficult than it needs to be. Is your linksys
> router actually your internet gateway? You said your internet
> connection is wireless, and your drawing lists your pc as the wifi hub.
> So is your outgoing internet connection your computer v
would rpcap help?
On Nov 13, 2007 7:21 AM, Gary Fritz <[EMAIL PROTECTED]> wrote:
> On 13 Nov 2007 at 12:00, Andreas Fink <[EMAIL PROTECTED]> wrote:
> > the two switches are not forwarding packets to your PC as the
> > destination of the packets are not meant to receive it
> > You need to do the t
Joe,
unfortunately, there is no easy solution to the problem. Several VPN clients
use a mix of layers to tunnel the traffic (a lot of them use a virtual network
miniport and an intermediate driver). WinPcap sits on top of this stack, and
quite frequently cannot capture all the traffic going on
Is wireshark running on the same pc that you did the ping from? If so
you're only going to see internal packets (before the frame hits the
wire), and thus smaller packets not including the padding are going to be
valid. 43 is a valid size for a packet that didn't actually hit the wire.
Kevin.
This may be a bit more difficult than it needs to be. Is your linksys
router actually your internet gateway? You said your internet connection
is wireless, and your drawing lists your pc as the wifi hub. So is your
outgoing internet connection your computer via the wifi, or the linksys
via somet
I've started to experiment recently with Version 0.99.6a (SVN Rev 22276) and
WinPcap version 4.0.1 which was the recommended version when I installed
Wireshark. As far as I'm aware, ethernet frames should be between 64 and 1518
bytes long and, if the data section is less than 46 bytes, padding
On Nov 13, 2007 3:21 PM, Gary Fritz <[EMAIL PROTECTED]> wrote:
>
> If none of those tricks work, then I guess the only way to do this is to run
> Wireshark on my son's laptop. Not the greatest solution. Ohwell
>
Have you looked at linklogger or wallwatcher etc?
http://www.linklogger.com/
ht
On 13 Nov 2007 at 12:00, Andreas Fink <[EMAIL PROTECTED]> wrote:
> the two switches are not forwarding packets to your PC as the
> destination of the packets are not meant to receive it
> You need to do the tracing on the WRTG54G itself (if it runs some
> linux for example) or it should forward
You're definitely right about it being WinPCap... I get the same result
when simply running windump on that interface.. My situation is a
little different than the gentleman's that started this thread..
1) I have NO software firewall running
2) I am using AT&T AGN client 6.3
When attempting to
the two switches are not forwarding packets to your PC as the
destination of the packets are not meant to receive it
You need to do the tracing on the WRTG54G itself (if it runs some
linux for example) or it should forward packets.
I dont think even without the two switches you will see the pac
11 matches
Mail list logo
