discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] TUN/TAP PDU not working


From: Cinaed Simson
Subject: Re: [Discuss-gnuradio] TUN/TAP PDU not working
Date: Thu, 22 Jun 2017 12:28:53 -0700
User-agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.2.0

On 06/22/2017 05:24 AM, Derek Kozel wrote:
> Hello Cinaed,
> 
> I have no experience with the TUN/TAP code or setup, but the B210 is an
> SDR which can only be connected to the host using USB.

Did you try it?

>There is no IP
> address associated with it.

Probably because you haven't given it one.

I connect my Beagle Bone to my laptop over a USB cable with 2 IP
addresses - on IP for my laptop and one IP for the Beagle Bone.

The USB cable also provides power for the Beagle Bone.

Then I use ssh to connect to the Beagle Bone.

A single tap IP address is a bridge to nowhere.

-- Cinaed



> https://www.ettus.com/product/details/UB210-KIT
> 
> Regards,
> Derek
> 
> On Thu, Jun 22, 2017 at 10:29 AM, Cinaed Simson <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     On 06/17/2017 04:26 AM, address@hidden
>     <mailto:address@hidden> wrote:
>     > Hi Cinaed,
>     >
>     > Sorry to miss the previous email.
>     >
>     > I need to clarify that B210 USRP is connected to the PC though USB 
> cable. That's why my Ethernet cards are disabled.
>     >
>     > Meanwhile I have been trying different things and I noticed the 
> followings:
>     >
>     > 1- Packet Encoder/Decoder blocks work fine with GMSK modulation scheme. 
> But with other modulation like QAM and PSK, it seems to be less efficient.
>     >
>     > 2- I can receive any packet delivered to the virtual IP address I 
> create using GNURadio. I also can print them to the console in GNURadio.
>     >
>     > 3- I can easily send/receive any form of information using GMSK Scheme 
> along with packet encoder/decoder from one USRP to another>
>     > 4- but whatever I do I can't put the received packets from virtual IP 
> address though GMSK and packet en/decoder.
> 
>     Try setting the IP address of your USRP in the properties by replacing
> 
>       Device Address="name=USRP_1"
> 
>     with
> 
>       Device Address="addr=192.168.200.1"
> 
>     -- Cinaed
> 
>     >
>     > Sincerely,
>     > Mansour.
>     >
>     >> On 17 Jun 2017, at 02:46, Cinaed Simson <address@hidden
>     <mailto:address@hidden>> wrote:
>     >>
>     >> Incidentally, all you need is a $20-$30 Ethernet switch with 5-8
>     ports,
>     >> and 3 CAT-6 Ethernet cables - twice as long as you think might need.
>     >>
>     >> Then plug 1 one cable into each of the 3 device and plug the
>     other end
>     >> the of all the cables into the switch.
>     >>
>     >> Configure them as below and you should be able to ping all the
>     devices
>     >> from either the desktop or the laptop.
>     >>
>     >> -- Cinaed
>     >>
>     >>
>     >>> On 06/15/2017 02:49 PM, Cinaed Simson wrote:
>     >>>
>     >>> I'll assume they're connected correctly.
>     >>>
>     >>> On the both PC1 and PC2, type
>     >>>
>     >>>  ip tuntap del dev tap0 mode tap
>     >>>
>     >>> On PC1, type
>     >>>
>     >>>  ifconfig enp0s31f6 inet 192.168.200.1 netmask 255.255.255.0
>     >>>  ifconfig enp0s31f6 up
>     >>>
>     >>> On PC2, type
>     >>>
>     >>>  ifconfig enp0s31f6 inet 192.168.200.3 netmask 255.255.255.0
>     >>>  ifconfig enp0s31f6 up
>     >>>
>     >>> Then on either PC, ping the other one. Try pinging the USRP. The
>     pinging
>     >>> shoud work - unless you have more than one Ethernet card and you
>     plugged
>     >>> the cable into the wrong card.
>     >>>
>     >>> The idea is a tap relies on the existing Ethernet framing (and hence
>     >>> routing) so if the machines are connected correctly then configuring
>     >>> their Ethernet cards should provide the necessary infrastructure.
>     >>>
>     >>> Also, you need to go the USRP mailing list and ask them how to
>     change
>     >>> the IP address of the B210 - it's something you should know how
>     to do.
>     >>>
>     >>> In general, the tap address on the B210 should have the same network
>     >>> address as your PC.
>     >>>
>     >>> The network address of PC1 is 192.168.200.0 and the host address
>     >>> 192.168.200.1.
>     >>>
>     >>> -- Cinaed
>     >>>
>     >>>> _______________________________________________
>     >>>> Discuss-gnuradio mailing list
>     >>>> address@hidden <mailto:address@hidden>
>     >>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>     >>>>
>     >>>
>     >>
>     >>
>     >> _______________________________________________
>     >> Discuss-gnuradio mailing list
>     >> address@hidden <mailto:address@hidden>
>     >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>     >
>     > _______________________________________________
>     > Discuss-gnuradio mailing list
>     > address@hidden <mailto:address@hidden>
>     > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>     >
> 
> 
>     _______________________________________________
>     Discuss-gnuradio mailing list
>     address@hidden <mailto:address@hidden>
>     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]