milosgajdos/tenus

Linux networking in Go

tenus's Issues

What happened to the master branch?

It seems to be overwritten by something completely different? Where all previous history lost

Enable Sourcegraph

I want to use Sourcegraph for tenus code search, browsing, and usage examples. Can an admin enable Sourcegraph for this repository? Just go to https://sourcegraph.com/github.com/milosgajdos83/tenus. (It should only take 30 seconds.)

Thank you!

Possible to create tuntap links?

There doesn't currently seem to be any way to create tuntap interfaces. Is this likely to be supported (i.e. just a matter of adapting the code) or was there a fundamental limitation to doing it?

everything is gone after reboot.

How to persistent data after reboot?

Persist configuration on reboot

Hello.I have recently started using Golang.What I want is the following,I want to be able to edit an existing interface(e.g. eth0).I want to change the IP from dhcp to static and set a custom gateway IP and subnet mask.If I do that using tenus will the changes persist after a system reboot ?

Avoid libcontainer fork

The Cloud Foundry project is considering using tenus to simplify its usage of netlink. However, we need to avoid being on a fork of libcontainer. We are currently planning to fork tenus, re-base it on vanilla libcontainer, and offer the re-basing as a pull request to tenus. We are also planning some functional extensions to tenus and libcontainer/netlink which we will most likely also offer back via pull requests.

For more details, please see the CF Garden tracker and search for tenus.

This issue is essentially a heads up. We acknowledge that tenus may not need to avoid being on a fork of libcontainer for its own purposes, but we wanted to make you aware of our plans.

veth_linux does not build

Attempting to test tenus produces the following build errors.

$ go test .
# github.com/milosgajdos83/tenus
/home/vagrant/go/src/github.com/milosgajdos83/tenus/veth_linux.go:62: too many arguments in call to netlink.NetworkCreateVethPair
/home/vagrant/go/src/github.com/milosgajdos83/tenus/veth_linux.go:119: too many arguments in call to netlink.NetworkCreateVethPair
FAIL    github.com/milosgajdos83/tenus [build failed]

Please use valid hostname in DockerPidByName when using unix sockets

Currently when docker API is served via UNIX sockets a http request is constructed with used as hostname. This gives (with golang 1.6) following error:

Fail to create http request: parse http:// /containers/e41fcca44e18c5275/json: invalid character " " in host name

Please use a valid hostname instead 'example.com' might be good :-)

Interact with wifi interfaces

This is not exactly an issue. However, I want to know whether this library is able to create virtual wifi interfaces and bridge them with networks. Thanks in adavance.

Sniffing network traffic

Could this be used to sniff network traffic? I am trying to create a utility that watches SIP (voip) network traffic and greps it. An easier version of ngrep. Thought it would be cool to do it in go if possible.

Is it Possible to add ipTables rules programmatically (without exec :) ) ?

Hi
I'm now writing some low level application with Netfilter interaction, and some part of it written in GO

Is it possible to add/remove some ipTables rules using your library ?

Without using iptables command line tool !


Thanks.

Proposal: Please start using Semantic Versioning

I found that this project already supports Go modules. But sadly, the tags doesn't follow Semantic Versioning, which means that all tags of this project will be ignored by Go modules and replaced by pseudo-versions, go get acts weirdly when tags are not in that form. It would be great to have the tagged release be named in the format vX.X.X format so that go mod can read it.

	github.com/milosgajdos/tenus v0.0.0-20200730100109-997445a7a4dd

Else the mod file shows something like github.com/milosgajdos/tenus v0.0.0-20200730100109-997445a7a4dd which is not very readable and difficult to upgrade. It’s hard to verify which version is in use. This is not conducive to version control

So, I propose this project to follow Semantic Versioning in future versions. For example, v1.0.1, v2.0.0, v3.1.0-alpha, v3.1.0-beta.2etc.

No Way To Manipulate Existing Links

There is no way to take an existing interface and manipulate it.