Skip to Content.

rare-users - Re: [RARE-users] [freertr] Wireless connection with RARE/freeRtr

Subject: RARE user and assistance email list

List archive


Re: [RARE-users] [freertr] Wireless connection with RARE/freeRtr


Chronological Thread 
  • From: Frederic LOUI <>
  • To: Edgard da Cunha Pontes <>
  • Cc:
  • Subject: Re: [RARE-users] [freertr] Wireless connection with RARE/freeRtr
  • Date: Mon, 26 Sep 2022 21:46:30 +0200
  • Dkim-filter: OpenDKIM Filter v2.10.3 zmtaauth03.partage.renater.fr 0AC28806E3
  • Importance: Normal
  • List-id: <freertr.groups.io>
  • Mailing-list: list ; contact

So basically want i wanted to show you is that whether wlan0 is shut then nothing changes from freertr point of view... (Interface are always UP ... ) Try to shut manually veth1b what is happening?

Le 26 sept. 2022 21:20, Edgard da Cunha Pontes <> a écrit :
Hi Frédéric, thank you for answering me.

I tried to decrease the amount of information in the previous email.

I might be wrong but you bound wireless to veth1a (belonging linux)
But veth1b (belonging to linux) is bound to freeRTr with rawInt socket.
A: Yes, I tried to do this. I don't know if I was right.

What is the status on linux of veth1a?
A: # ip addr show dev veth1a
5: veth1a@veth1b: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether d2:4c:37:72:86:21 brd ff:ff:ff:ff:ff:ff

What is the status on linux and freeRtr of veth1b when you shut wlan0?
A: Before shutting down wlan0
# ip addr show dev veth1b
4: veth1b@veth1a: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:00:11:11:22:22 brd ff:ff:ff:ff:ff:ff

After shutting down
# ip link set dev wlan0 down
# ip addr show dev veth1b
4: veth1b@veth1a: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:00:11:11:22:22 brd ff:ff:ff:ff:ff:ff

On freeRtr
ethernet2 is up
 description: wifi connection
 state changed 3 times, last at 2022-09-26 20:23:39, 00:32:44 ago
 last packet input 00:03:06 ago, output never ago, drop 00:03:06 ago
 type is ethernet, hwaddr=0000.1111.2222, mtu=1500, bw=100mbps, vrf=inet
 received 4177 packets (383572 bytes) dropped 4177 packets (383572 bytes)
 transmitted 0 packets (0 bytes) macsec=false sgt=false

freertr#traceroute 8.8.8.8 source eth2 vrf inet                                                    
tracing 8.8.8.8, src="null," vrf=inet, prt=0/33440, tim=1000, tos=0, flow=0, len=64
via 0.0.0.0/0 0/2 ethernet1 192.168.25.1 00:35:30
[...]

The ethernet1 interface is always chosen. I must have put some wrong config in the interface definitions (rtr-hw, hwdet-al).

I will follow the debug options you indicated. Again, thanks for answering me.

Em seg., 26 de set. de 2022 às 15:06, Frédéric LOUI <> escreveu:
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 (#754) | | | Mute This Topic | New Topic
Your Subscription | | Unsubscribe []

_._,_._,_



Archive powered by MHonArc 2.6.19.

Top of Page