Wireshark-users: Re: [Wireshark-users] Wireshark 1.2 running and not running on thesame machine ?
Hi there,
Could you please help me how to determine "CGI=MCC+MNC+LAC+CellID" in Wireshark.
Which part should I filter to get all those info.
Thanks for your kind assistance.
Rgds
junaidi b jamaluddin
PESS
P 018 200 2040/ 012 385 9142
junaidi.jamaluddin@xxxxxxxx
-----Original Message-----
From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap Keuter
Sent: Wednesday, June 24, 2009 5:04 PM
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] Wireshark 1.2 running and not running on thesame machine ?
Hi,
There seems to be an annoying bug in Windows that causes this problem
when no Ethernet interface is connected. I've no idea what's causing
that, and hope it will be addressed soon
Thanx,
Jaap
Sent from my iPhone
On 24 jun 2009, at 10:10, "Oliver Keller"
<oliver.keller@xxxxxxxxxxxxx> wrote:
> Hi all,
>
>
> first : thanks to the developers for constant work on that awesome
> tool !
>
> I switched to Wireshark 1.2 these days and there is a strange
> problem :
> Using VMware, I can install and use Wireshark in a guest system
> (WinXP)
> with no problems at all. However, installing the program on the host
> (which
> is also XP), I can´t start it without a crash. I switched back to 1.
> 0.4
> (without changing WinPcap) and everything works fine. Reinstalling
> 1.2.0
> gives the same error again. So I guess it´s not the WinPcap library,
> but
> something else.
>
> Maybe it´s the interfaces, cause the guest has just the emulated AMD
> net NIC
> while the host features the real card (Broadcom Netlink Gigabit)
> plus 5
> MS-loopback interfaces. Disabling the loopback interfaces doesn´t he
> lp,
> plus 1.0.4 has no issues with the loopbacks.
>
> I copied the crashreport but don´t want to clog the mailinglist, I c
> an post
> it if you think it may help.
>
>
> Best regards,
>
> Oliver
>
>
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx
> >
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?
> subject=unsubscribe
>
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
-----------------------------------------
This message and any attachment are for the intended recipient’s
use only. It may contain confidential, proprietary, legally
privileged information or otherwise be protected from disclosure by
other legal rules. The information contained in this email or any
attachments may also be encrypted by U Mobile to protect its
security. If you have received an email or attachment(s) which you
are unable to open due to the encryption, please contact the sender
or visit this site(http://corporate.u.com.my/external/faq-rms.htm)
to learn how to open them. Any opinions and other statement
contained in this message and attachment are solely those of their
author and do not necessarily represent those of U Mobile. If you
are not the intended recipient, you may not use, disclose,
distribute or reproduce this message, its attachment or any part of
them, or take any action in reliance on them. Please notify the
sender immediately and delete this message and any attachment from
your system. You agree that any privilege or confidentiality
attached to this email is not waived because you have received the
email in error. Emails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses or other
malicious programs. Anyone who communicates with us by email is
deemed to have accepted these risks. U Mobile denies liability for
any damage arising from the use of email. “U Mobile” means U Mobile
Sdn Bhd (223969-U)
