RARE user and assistance email list

["Edgard" <>]

Hi Frédéric and Csaba,

Thanks for all your support.

Frédéric I tried several times (and in different ways) to continue with the idea of using pcap2pcap.bin with wlan0 and one of the ends of the pair of veths (veth1a/veth1b), but unfortunately it still didn't work. I will try again asap.

So I tried to take a step back and use the suggestion from the last Csaba's email, which I understood was to use rawInt.bin directly with the wlan0 interface. And it worked!

freertr#sh int eth1                                                                                                          
ethernet1 is up
 description: uplink
 state changed 5 times, last at 2022-09-27 13:43:01, 01:14:09 ago
 last packet input 00:00:00 ago, output 00:00:05 ago, drop 00:00:10 ago
 type is ethernet, hwaddr=782b.cbbb.e504, mtu=1500, bw=100mbps, vrf=inet
 ipv4 address=192.168.25.47/24, mask=255.255.255.0, ifcid=860065977
 ipv6 address=2804:1b3:9003:a0c3:7a2b:cbff:febb:e504/64, mask=ffff:ffff:ffff:ffff::, ifcid=707621491
 received 7366 packets (612706 bytes) dropped 53 packets (2738 bytes)
 transmitted 442 packets (26748 bytes) macsec=false sgt=false

ethernet2 is up
 description: wifi connection
 state changed 3 times, last at 2022-09-27 13:39:13, 01:17:37 ago
 last packet input 00:00:01 ago, output 00:00:00 ago, drop 00:01:51 ago
 type is ethernet, hwaddr=18d6.c70e.9748, mtu=1500, bw=100mbps, vrf=inet
 ipv4 address=192.168.25.10/24, mask=255.255.255.0, ifcid=860065978
 ipv6 address=2804:1b3:9003:a0c3:1ad6:c7ff:fe0e:9748/64, mask=ffff:ffff:ffff:ffff::, ifcid=707621492
 received 9835 packets (873237 bytes) dropped 76 packets (3952 bytes)
 transmitted 2100 packets (74557 bytes) macsec=false sgt=false

freertr#ping 8.8.8.8 sou eth1                                                                                                
pinging 8.8.8.8, src="192.168.25.47," vrf=inet, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
!!!!!
result=100.0%, recv/sent/lost/err=5/5/0/0, took 87, min/avg/max/dev rtt=16/17.2/19/1.3, ttl 56/56.0/56/0.0, tos 0/0.0/0/0.0

freertr#ping 8.8.8.8 sou eth2                                                                                                
pinging 8.8.8.8, src="192.168.25.10," vrf=inet, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
!!!!!
result=100.0%, recv/sent/lost/err=5/5/0/0, took 101, min/avg/max/dev rtt=19/20.0/22/1.1, ttl 56/56.0/56/0.0, tos 0/0.0/0/0.0

Remembering that I removed the IP request line, for my local network dhcp, from the hwdet-all file and transferred it to the rtr-sw file on the eth2 interface.

All I've been testing so far is internet connectivity using RARE/freeRtr with a wireless interface, but the main goal is to use an Access Point, in a way "managed" by freeRtr, for the RENaaS project. As I had not yet used freeRtr with a wireless interface, I decided to "break" the main objective into an "easier" problem that I could solve.

Again, thanks Frédéric and Csaba for their support! Sorry for the beginner's questions about wireless connection. Now I have to figure out a way to complete the RENaaS goal.

Em ter., 27 de set. de 2022 às 02:00, mc36 <> escreveu:

wireless connections usually require mac address cloning....
in your case, the physical nic's mac to freerouter should match....
br,
cs

On 9/26/22 20:06, Fr  d  ric LOUI wrote:
> Hi Edgar,
>
> In networking you have other tools besides    ping   .
>
> 1- traceroute
>      This command is available in very host. In freeRtr you would have to precise VRF
> 2- show ipv4 route <VRF_NAME>
>      In freeRtr case. This is is a powerful command that will let you see the routing table :)
>
> I might be wrong but you bound wireless to veth1a (belonging linux)
> But veth1b (belonging to linux) is bound to freeRTr with rawInt socket.
>
>
> What is the status on linux of veth1a ?
> What is the status on linux and freeRtr of veth1b when you shut wlan0 ?
>
> Then try your Linux to do a "ip route show    and check default route.
> Please also do the same with freeRtr (show ipv4 route <VRF_NAME>
>
> This will help you trace packet path.
>
> And if you are unsure use tcpdump -I (with icmp and host filter if you want)
>
> Good luck
> Frederic
>
>> Le 26 sept. 2022    19:40, Edgard <> a   crit :
>>
>> Hi all,
>>
>> I started a thread like this in the old list (), and I don't know if anyone else got this message as I got a send error return.
>> So I decided to post it here. I apologize if I repeat the content.
>>
>> After a few months, I returned to this thread.
>> The following commands worked.
>>   
>> hwdet-all.sh
>> [...]
>> ### wireless interface  ###
>> ip link set wlan0 up multicast on promisc on mtu 1500
>> ethtool -K wlan0 rx off
>> ethtool -K wlan0 tx off
>> ethtool -K wlan0 sg off
>> ethtool -K wlan0 tso off
>> ethtool -K wlan0 ufo off
>> ethtool -K wlan0 gso off
>> ethtool -K wlan0 gro off
>> ethtool -K wlan0 lro off
>> ethtool -K wlan0 rxvlan off
>> ethtool -K wlan0 txvlan off
>> ethtool -K wlan0 ntuple off
>> ethtool -K wlan0 rxhash off
>> ethtool --set-eee wlan0 eee off
>> /sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/example.conf
>> /sbin/dhclient wlan0
>> [...]
>> ### wireless connection ###
>> ip link add veth1a type veth peer name veth0
>> ip link set veth0 name veth1b
>> ip link set veth1a up multicast on promisc on mtu 1500
>> ethtool -K veth1a rx off
>> ethtool -K veth1a tx off
>> ethtool -K veth1a sg off
>> ethtool -K veth1a tso off
>> ethtool -K veth1a ufo off
>> ethtool -K veth1a gso off
>> ethtool -K veth1a gro off
>> ethtool -K veth1a lro off
>> ethtool -K veth1a rxvlan off
>> ethtool -K veth1a txvlan off
>> ethtool -K veth1a ntuple off
>> ethtool -K veth1a rxhash off
>> ethtool --set-eee veth1a eee off
>> ip link set veth1b up multicast on promisc on mtu 1500
>> ethtool -K veth1b rx off
>> ethtool -K veth1b tx off
>> ethtool -K veth1b sg off
>> ethtool -K veth1b tso off
>> ethtool -K veth1b ufo off
>> ethtool -K veth1b gso off
>> ethtool -K veth1b gro off
>> ethtool -K veth1b lro off
>> ethtool -K veth1b rxvlan off
>> ethtool -K veth1b txvlan off
>> ethtool -K veth1b ntuple off
>> ethtool -K veth1b rxhash off
>> ethtool --set-eee veth1b eee off
>> ip link set veth1a up address 00:00:11:11:22:22 mtu 1500
>> [...]
>>   
>> rtr-hw.txt
>> [...]
>> proc wifi.sh /rtr/pcap2pcap.bin wlan0 veth1a
>> proc ifc2.sh /rtr/rawInt.bin veth1b 20004 127.0.0.1 20003 127.0.0.1
>> int eth2 stat eth 00:00:11:11:22:22 127.0.0.1 20003 127.0.0.1 20004
>> [...]
>>   
>> rtr-sw.txt
>> [...]
>> interface ethernet2
>>   description wifi connection
>>   vrf forwarding inet
>>   no shutdown
>>   no log-link-change
>>   exit
>> [...]
>>   
>> But... There are still errors in this config that I couldn't understand.
>>   
>> In Debian managed interface
>> root@optiplex790:~# ping -I wlan0 8.8.8.8 -c 4
>> PING 8.8.8.8 (8.8.8.8) from 192.168.25.10 wlan0: 56(84) bytes of data.
>> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=20.6 ms
>> 64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=20.3 ms
>> 64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=18.7 ms
>> 64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=18.6 ms
>>   
>> On RARE/freeRtr even with wlan0 down
>> freertr#ping 8.8.8.8 source eth2
>> pinging 8.8.8.8, src="null," vrf=inet, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
>> !!!!!
>>   
>> It was too good to be true. I think I'm forgetting something.
>>
>> ---
>> Edgard.
>>
>
>
>
>
>
>

--

Att.

Edgard da Cunha Pontes

_._,_._,_

---

   Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#758) | | | Mute This Topic | New Topic
Your Subscription | | Unsubscribe []

_._,_._,_