autoneighxy | Automatic Neighbor Proxy , for ARP and NDP
kandi X-RAY | autoneighxy Summary
kandi X-RAY | autoneighxy Summary
autoneighxy is a Python library typically used in Telecommunications, Media, Telecom applications. autoneighxy has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.
My CPE forces me to use addresses from its LAN address range (192.168.1.0/24 and 2001:db8::/64) in my room and my PC prevents me to bridge wireless and wired networks. In 2006 IETF published `RFC 4389 `. Scenario 1 (section `1.1 `) describes exactly my situation! So there are some people who have thought about this and created NDP proxies. Basically my PC tells that the printer and the NetDisk are itself on the CPE LAN, and tells things in my room that it owns the IP addresses of the CPE, PC1 and PC2. Linux kernel of NDP proxies implementation was not really useful before 2012 because there were no way to list configured NDP proxies. Recent kernel (version >=3.3) implements what was needed for “ip neigh show proxy” command to work. With that, it’s quite easy to write a program which listens to NDP messages other the network and configures automatically the proxies. Several projects exist to do that but none take into account routing issues. Nevertheless most of these projects use two different address spaces at the two sides of the routers. Here I need to have the same prefix (2001:db8::/64) everywhere. So on my PC, both wired and wireless interface use in 2001:db8::/64 and I need to add specific routes to the addresses of my printer and my NetDisk or this to work. Therefore routes are automatically added when a new neighbor appears on the network. The software I’ve created is written in Python 2 and uses Scapy to sniff and send packets over the network. It makes call to the `ip` command to set up neighbor proxies and routes and maintains an internal state of the whole home network. That’s not scalable to big homes (or castles) but in such cases, routing several network prefixes is far more efficient.
My CPE forces me to use addresses from its LAN address range (192.168.1.0/24 and 2001:db8::/64) in my room and my PC prevents me to bridge wireless and wired networks. In 2006 IETF published `RFC 4389 `. Scenario 1 (section `1.1 `) describes exactly my situation! So there are some people who have thought about this and created NDP proxies. Basically my PC tells that the printer and the NetDisk are itself on the CPE LAN, and tells things in my room that it owns the IP addresses of the CPE, PC1 and PC2. Linux kernel of NDP proxies implementation was not really useful before 2012 because there were no way to list configured NDP proxies. Recent kernel (version >=3.3) implements what was needed for “ip neigh show proxy” command to work. With that, it’s quite easy to write a program which listens to NDP messages other the network and configures automatically the proxies. Several projects exist to do that but none take into account routing issues. Nevertheless most of these projects use two different address spaces at the two sides of the routers. Here I need to have the same prefix (2001:db8::/64) everywhere. So on my PC, both wired and wireless interface use in 2001:db8::/64 and I need to add specific routes to the addresses of my printer and my NetDisk or this to work. Therefore routes are automatically added when a new neighbor appears on the network. The software I’ve created is written in Python 2 and uses Scapy to sniff and send packets over the network. It makes call to the `ip` command to set up neighbor proxies and routes and maintains an internal state of the whole home network. That’s not scalable to big homes (or castles) but in such cases, routing several network prefixes is far more efficient.
Support
Quality
Security
License
Reuse
Support
autoneighxy has a low active ecosystem.
It has 13 star(s) with 3 fork(s). There are 2 watchers for this library.
It had no major release in the last 6 months.
autoneighxy has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of autoneighxy is current.
Quality
autoneighxy has no bugs reported.
Security
autoneighxy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
autoneighxy is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
autoneighxy releases are not available. You will need to build from source code and install.
Build file is available. You can build the component from source.
Installation instructions are not available. Examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi has reviewed autoneighxy and discovered the below as its top functions. This is intended to give you an instant insight into autoneighxy implemented functionality, and help decide if they suit your requirements.
- Update an existing address
- Check if proxies between interfaces
- Add a host route
- Format a record
- Run the loop
- Send ICMP6 packet
- Process an ARP packet
- Process ICMPv6 packet
- Activate only iface
- Read an integer value from an entry
- Write an integer to a sysctl integer
- Activate the IP address
- Update an existing neighbor
- Delete neighbor proxy
- Add a neighbor proxy
- Get the version of a package
- Return information about an interface
- Yields a list of IP addresses
- Sets up neighbor neighbors
Get all kandi verified functions for this library.
autoneighxy Key Features
No Key Features are available at this moment for autoneighxy.
autoneighxy Examples and Code Snippets
No Code Snippets are available at this moment for autoneighxy.
Community Discussions
No Community Discussions are available at this moment for autoneighxy.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install autoneighxy
You can download it from GitHub.
You can use autoneighxy like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.
You can use autoneighxy like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page