n2n icon indicating copy to clipboard operation
n2n copied to clipboard

can not use brctl addif br-lan edge0

Open levin-go opened this issue 4 years ago • 15 comments
trafficstars

n2n version: 2.8 My openwrt device (edge IP 10.0.0.1) and my windows PC (edge IP 10.0.0.2) can ping each other. After windows executes the command route add 192.168.10.0 mask 255.255.0 10.0.0.1, windows can ping openwrt's intranet 192.168.10. X. Now I want to set up a LAN in another way (this way can be successful with OpenVPN)

  1. Set two IP addresses for windows edge network card (10.0.0.2 and 192.168.10.33)

  2. Openwrt uses brctl addif br-lan edge0 to bind edge0 and eth0 together.

Now, when I use brctl addif br-lan edge0 to bind edge0 and eth0 together under openwrt. my openwrt device and PC will can't communicate. Below is the log of my openwrt device

image

my openwrt device config:

image

Why can't eth0 and edge0 be bound together?

levin-go avatar Jul 21 '21 10:07 levin-go

... eth0 and edge0 be bound together ...

Bridge support has been a still pending issue up to now, please see #302 and #204.

I hope you can solve it with routing (ip route command or edge's -n command line option).

Why ...

I am not sure about the reasons, not too deep into bridging. Any help is appreciated.

Logan007 avatar Jul 21 '21 10:07 Logan007

Thanks. Is there any plan to solve it, because bridging is much more convenient than routing table.

levin-go avatar Jul 21 '21 10:07 levin-go

bridging is much more convenient than routing table.

I know...

Is there any plan to solve it

#302 is flagged Help Wanted. We still are looking for someone to sustainably solve it. Any help with it is appreciated.

Logan007 avatar Jul 21 '21 10:07 Logan007

I will continue to pay attention to this issue, and I will submit any findings to Issues in time.

levin-go avatar Jul 21 '21 10:07 levin-go

Is this issue solved now?

stardustzh avatar May 20 '22 10:05 stardustzh

I think the status is still "open". After @maxleaf had created the pull request #977, it was closed very soon then, even before we had any chance to review.

Is there anyone who has an environment available for testing it?

Logan007 avatar May 20 '22 10:05 Logan007

I think the status is still "open". After @maxleaf had created the pull request #977, it was closed very soon then, even before we had any chance to review.

Is there anyone who has an environment available for testing it?

Yes,I'm working on this issuse. And the patch should work. But since Shanghai's lockdown, there is no test environment on my hand. If someone can help test it, it would be greatly appreciated.

maxleaf avatar May 31 '22 09:05 maxleaf

Great news, I hope you will share your results with that pull request again.

Logan007 avatar May 31 '22 17:05 Logan007

I think the status is still "open". After @maxleaf had created the pull request #977, it was closed very soon then, even before we had any chance to review. Is there anyone who has an environment available for testing it?

Yes,I'm working on this issuse. And the patch should work. But since Shanghai's lockdown, there is no test environment on my hand. If someone can help test it, it would be greatly appreciated.

I tried on my openwrt router,the outside device can connect to my router with the bridge mode (the LAN ip:192.168.1.1), but all the other devices in the LAN are out of connection. btw: here the things I found that you have to do so that you can run in the bridge mode. edge -d zf100 -a 192.168.1.1 -c n100 -k n100 -p 10100 -M 1400 -l superser:superport -A -t 20260 -m aa:bb:cc:dd:ee:ff 1.it has to use 192.168.1.1 instead of dhcp:0.0.0.0 2.mac address:aa:bb:cc:dd:ee:ff, it has to use the same mac address with the br-lan

thankeyes avatar Jun 29 '22 14:06 thankeyes

Sorry, I just saw the message. If you haven't tested yet, I can help.

levin-go avatar Jul 02 '22 14:07 levin-go

I have tried to add an edge device to a bridge. When i try this, i lose the previous working connection to the other edge device. I am testing this with the git head code.

reinhard1 avatar Jul 16 '22 23:07 reinhard1

Hi @reinhard1 - there are some patches that add this feature referenced in the comments above, but none of them have been merged as yet, so it is known not to work

hamishcoleman avatar Jul 17 '22 00:07 hamishcoleman

Yes, i have seen the patch and the merge request, but, as i understand, this merge request is rejected. Will this feature added in the near future?

reinhard1 avatar Jul 17 '22 00:07 reinhard1

The merge request was not rejected, the original author closed it while he continued to work on the patch

hamishcoleman avatar Jul 17 '22 00:07 hamishcoleman

superser:superport -A -t 20260 -m aa:bb:cc:dd:ee:ff

edge -d zf100 -a 192.168.1.1 -c n100 -k n100 -p 10100 -M 1400 -l

I think the status is still "open". After @maxleaf had created the pull request #977, it was closed very soon then, even before we had any chance to review. Is there anyone who has an environment available for testing it?

Yes,I'm working on this issuse. And the patch should work. But since Shanghai's lockdown, there is no test environment on my hand. If someone can help test it, it would be greatly appreciated.

I tried on my openwrt router,the outside device can connect to my router with the bridge mode (the LAN ip:192.168.1.1), but all the other devices in the LAN are out of connection. btw: here the things I found that you have to do so that you can run in the bridge mode. edge -d zf100 -a 192.168.1.1 -c n100 -k n100 -p 10100 -M 1400 -l superser:superport -A -t 20260 -m aa:bb:cc:dd:ee:ff 1.it has to use 192.168.1.1 instead of dhcp:0.0.0.0 2.mac address:aa:bb:cc:dd:ee:ff, it has to use the same mac address with the br-lan

for edge node, -r option is needed

maxleaf avatar Aug 09 '22 15:08 maxleaf