Topic: coova chilli, no ip on eth2

[tropicalview]

Dear all,

I installed a virtual machine with the SME server to have a lab test for installing coova chilli before installing on a production machine.

i installed the OS when i had already 3 ethernet cards, and finished up with external ip 192.168.9.25 (on my network with internet) and 192.168.203.1 as internal ip.

Now the server worked, and all functions where functional.
but up to that moment i had only ETH0, ETH1, LO as network interfaces.

Because in the installation instructions i saw this:

you should have a new 'eth2' card not configured (it's ok, you do not need to configure it).

on: http://wiki.contribs.org/CoovaChilli

i did continue to install, everything was successfull.
the ETH2 indeed appeared and also the tun0.

but the eth2 did not get an ip address.
I decided to reboot the server, but still.
I checked out the config files in /etc/coovachilli and there i saw the config of 10.1.0.1.

to be sure i uninstalled coovachilli again, and the eth2 was still available.
now i reinstalled again, but again without an ip address.

I updated the ethernet card with ifconfig and gave it the ip address, now i was able to see the mac address in the table of my pc, but couldn't ping it or access anything.

does anybody know where i did go wrong?

[Daniel B.]

There's nothing wrong. eth2 will never have an IP, as chilli will mask incoming traffic on eth2, and the kernel will see this traffic as comming from tun0 instead. tun0 should have the IP 10.1.0.1

[tropicalview]

This is more than great.

you're right, it works indeed out of the box.

i was to fast in searching for the IP!

perhaps it's nice to put a little side note on the page to prevent other people getting into this problem.

Thanks a lot,