Hello everybody, osmocom is down (sad) so I cant look for the answer there. How do I tunnel the gnu radio into wireshark? is there a sink that goes to an ip address or a usb port or something? I am stuck here without the instructions on osmo. Thanks, Matt -----------------
On Thu, Mar 21, 2013 at 05:37:10PM -0400, Matt D wrote:
Hello everybody, osmocom is down (sad) so I cant look for the answer there. How do I tunnel the gnu radio into wireshark? is there a sink that goes to an ip address or a usb port or something? I am stuck here without the instructions on osmo.
My copy of the repo isn't terribly recent, but, from what I can see, we're implementing a UDP socket in one of the op25 blocks to deliver packets to Wireshark.
There are a couple of implementations of GNU Radio blocks that send data over UDP or TCP, but we're not using them, probably because they are more suitable for sending a stream of samples rather than packets.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, Mar 21, 2013 at 05:37:10PM -0400, Matt D wrote:
Hello everybody, osmocom is down (sad) so I cant look for the answer there. How do I tunnel the gnu radio into wireshark? is there a sink that goes to an ip address or a usb port or something? I am stuck here without the instructions on osmo.
My copy of the repo isn't terribly recent, but, from what I can see, we're implementing a UDP socket in one of the op25 blocks to deliver packets to Wireshark.
There are a couple of implementations of GNU Radio blocks that send data over UDP or TCP, but we're not using them, probably because they are more suitable for sending a stream of samples rather than packets.
So I have the patched wireshark up and the flowgraph running. wireshark is telling me there are no interfaces to capture. I am not doing something here?
On Fri, Mar 22, 2013 at 11:03:55AM -0400, Matt D wrote:
wireshark is telling me there are no interfaces to capture. I am not doing something here?
The op25 code is sending UDP packets to 224.0.0.1 which probably should show up on your primary external interface.
You should be able to capture on your that interface (e.g. eth0 or wlan0) or on your loopback interface (e.g. lo) in Wireshark. If you can't, you have a Wireshark problem (maybe permissions?).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/22/2013 01:47 PM, Michael Ossmann wrote:
On Fri, Mar 22, 2013 at 11:03:55AM -0400, Matt D wrote:
wireshark is telling me there are no interfaces to capture. I am not doing something here?
The op25 code is sending UDP packets to 224.0.0.1 which probably should show up on your primary external interface.
You should be able to capture on your that interface (e.g. eth0 or wlan0) or on your loopback interface (e.g. lo) in Wireshark. If you can't, you have a Wireshark problem (maybe permissions?).
right so i run sudo wireshark and those options show up. getting the p25 CAI on eth1 192.168.0.14. Thanks a bunch, Matt - --------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/22/2013 01:47 PM, Michael Ossmann wrote:
On Fri, Mar 22, 2013 at 11:03:55AM -0400, Matt D wrote:
wireshark is telling me there are no interfaces to capture. I am not doing something here?
The op25 code is sending UDP packets to 224.0.0.1 which probably should show up on your primary external interface.
You should be able to capture on your that interface (e.g. eth0 or wlan0) or on your loopback interface (e.g. lo) in Wireshark. If you can't, you have a Wireshark problem (maybe permissions?).
Right, I ran sudo wireshark and those options show up. getting the p25 CAI from eth1 192.168.0.14 Thanks a bunch, Matt - ------
--- In op25-dev@yahoogroups.com, Michael Ossmann <mike@...> wrote:
My copy of the repo isn't terribly recent, but, from what I can see, we're implementing a UDP socket in one of the op25 blocks to deliver packets to Wireshark.
The original way that we used was in the receiver after the P25 frames were received and reassembled they were encapsulated and written to the Linux TUN/TAP interface. When properly configured, this interface (typ. 'tun0') shows up as a standard interface in ifconfig (and in the list of allowed network interfaces that wireshark can listen on).
Then later our repeater stuff added support for writing received frames to UDP, using UDP port 23456. See file repeater/src/python/usrp_rx.py.
In response to this, Mike added a UDP option to the wireshark plugin - see this message: http://tech.groups.yahoo.com/group/op25-dev/message/201
Best
Max
-
ikj1234i -
Matt D -
Michael Ossmann