opengnb: version 1.6.3 is ported to openwrt#28956
opengnb: version 1.6.3 is ported to openwrt#28956charleschan2006-alias wants to merge 1 commit intoopenwrt:masterfrom
Conversation
|
greatly support, i desperately need this feature |
|
感谢大佬的移植！以后不用自己在 OpenWrt 上编译了！ |
charleschan2006-alias
changed the title
charleschan2006-alias
changed the title
This ports opengnb version 1.6.3 to OpenWrt. Signed-off-by: charles chan <hollidgelongsun157@gmail.com>
charleschan2006-alias
force-pushed
the
master
branch
from
e829618 to
46ea109
Compare
|
charleschan2006-alias made great efforts for OpenGNB porting to OpenWRT platform |
|
Nice work! No more manual compilation from now on. |
|
Great addition! This would be a very useful tool for OpenWrt users. Hope to see it merged soon. |
BKPepe
left a comment
BKPepe
left a comment
There was a problem hiding this comment.
I noticed that you are including a lot of configuration files for Darwin, FreeBSD, and OpenBSD. However, these are not used within the OpenWrt environment, and the Makefile does not reference them at all. Is there a reason for including these redundant files in the OpenWrt package?
| define Build/Compile | ||
| $(MAKE) -C $(PKG_BUILD_DIR) \ | ||
| $(TARGET_CONFIGURE_OPTS) \ | ||
| CFLAGS="$(TARGET_CFLAGS) -I. -I./src -I./libs -I./libs/miniupnpc -I./libs/libnatpmp -I./libs/zlib -D_GNU_SOURCE -DNO_GZIP=1 -DGNB_OPENWRT_BUILD=1" \ |
There was a problem hiding this comment.
I have a question regarding the bundling of numerous libraries and applications. It seems redundant to me, especially since we already have packages like miniupnpc, zlib, and libnatpmp present in the system. Shouldn't these be treated as external dependencies instead of being bundled directly?
| PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-ver$(PKG_VERSION) | ||
|
|
||
| PKG_MAINTAINER:=OpenGNB Developer <hollidgelongsun157@gmail.com> | ||
| PKG_LICENSE:=GPL-3.0 |
There was a problem hiding this comment.
This SPDX License Identifier is deprecated.
|
|
||
| PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-ver$(PKG_VERSION) | ||
|
|
||
| PKG_MAINTAINER:=OpenGNB Developer <hollidgelongsun157@gmail.com> |
There was a problem hiding this comment.
However, we cannot accept this PR in its current state because the maintainer field ('OpenGNB Developer') does not comply with the OpenWrt Contributing Guidelines.
To move forward, please update the maintainer information and the Signed-off-by line in your commits to include a real name and a valid email address. This is a mandatory requirement for legal and maintenance reasons within the OpenWrt ecosystem.
You can find more details in our documentation regarding the Developer Certificate of Origin (DCO).
|
good jod! I love your work! |
|
oh yeah. that's meaning not need to recompile . 如果能进就太好了。 |
9 participants
📦 Package Details
PKG_MAINTAINER:= Charles Chan hollidgelongsun157@gmail.com
opengnb: version 1.6.3 is ported to openwrt
Description:
OpenGNB is an open source P2P decentralized Software Defined Virtual Network with extreme intranet penetration capability,Allows you to combine your company-home network into a direct-access LAN.
All code related to the GNB project is released as open source, and the currently released source code supports the following platforms: FreeBSD Linux OpenWRT Raspberrypi OpenBSD macOS
GNB Features
Intranet penetration P2P VPN
No public IP required
Extreme link capability
Unlimited speed effects
Data Security
Reliable authentication between GNB nodes based on elliptic curve digital signature
Multi-platform support
GNB is developed in C language. It does not need to refer to third-party library files when compiling. It can be easily ported to the current popular operating systems. Currently supported operating systems and platforms include Linux_x86_64, Windows10_x86_64, macOS, FreeBSD_AMD64, OpenBSD_AMD64, Raspberry Pi, OpenWRT; as big as server environment, desktop system, as small as OpenWRT router with only 32M memory can run GNB network very well.
🧪 Run Testing Details
✅ Formalities