On 08/28/2013 02:12 PM, Abigail Walthall wrote:
I haven't ever used netsukuku but the first thing you should look at
is if it is setting a default route or default gateway when the
netsukuku link it established. If it does this after the internet
interface is connected it may be overriding the the default route that
was set which was enabling the packets to flow correctly out of the
network to the internet. Just something I learned from adventuring in
network administration.
I love your excitement! Don't stop being awesome.
On Wed, Aug 28, 2013 at 11:31 AM, Miss Valeska <[email protected]
<mailto:[email protected]>> wrote:
I just tested out my two virtual machines with my new knowledge of
netsukuku, And I was able to get them both to communicate and ping
each other! One had eth0 and another had eth1, They are Ubuntu
clones of each other, Running in Virtual Box.
I wasn't able to get IGS working on the virtual machines either
though, It seems, When ever netsukuku is running on an interface,
It is impossible to use that interface for internet. These virtual
machines are connected through their virtual ethernet interface,
So they cannot be connected to the internet if they are using it
for netsukuku. Which is interesting, But makes sense I suppose.
I added another ethernet interface to one of the virtual machines,
And set IGS to SHARE on it, And USE on the other. However, As soon
as I started netsukuku, I couldn't connect to the internet. And
when I told the network manager to disconnect the ethernet
interface I was connected to the other node with (in this case
eth1 because I added another) in hopes it'd just disconnect it
from the internet, And possibly work.
It just disconnected it from the other node, And I had to stop
netsukuku, And run it again to fix it. It seems netsukuku
disconnects the user from the internet throughout all interfaces
of the same type it is using. So running netsukuku on an ethernet
interface, Seems to disable all internet connections on all
ethernet interfaces.
I tried running netsukuku from both eth1 and eth0, And it worked,
However, It seemed to be the same node still. I half expected it
to recognise three nodes, Itself, My other VM, And the eth1
netsukuku instance. But it didn't, Only the other VM, Which was
mutually pingable.
I know that, At least, Running netsukuku on ethernet allows you to
be connected to the internet through wifi, And visa versa. I'll
have to see if this is true on any other interfaces, or not. I
need to test netsukuku through bluetooth, And other means. Though,
That sounds more difficult, I see no reason why it cannot be done.
If anyone can help me with any part of any of this, Please email
me or join the netsukuku IRC. Remember, You don't have to be a
programmer, Or know how to fix everything. Even if you only know
one thing, Just emailing me an explanation would be MASSIVELY
helpful to me!
Anyway! Thank you all for reading!
_______________________________________________
Netsukuku mailing list
[email protected] <mailto:[email protected]>
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
_______________________________________________
Netsukuku mailing list
[email protected]
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
*nods* I set the route to ethernet, because I used ntkd -i eth0 That
means netsukuku will run on the ethernet interface, Though, I might be
missing something.
_______________________________________________
Netsukuku mailing list
[email protected]
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
