Virtual ethernet and ispcp_network daemon

[adriangam]

Hi all,

This posts is a google translation of a spanish forum post. If any doubt, ask and I try to solve it.

adriangaam Wrote:I saw that the ispcp_network daemon create devices eth0:x for each IP you have configured the panel and even though that IP is already set in another virtual device eth0:y, ie you are creating a virtual device (from my point of externally to the panel) unnecessary.

What is the goal of doubling this IP? The question is given because the device is putting some broadcasts and incorrect netmasks, which opens a server on the network to other computers, whether they arrive by broadcast to mine.

It is possible to modify the panel, by adding an IP broadcast address and netmask can be set manually? Failure to specify these addresses, to maintain the current approach would not be bad. In reality, the broadcast could be calculated based on the netmask, so this would not be necessary.

I see this as a rather important bug in the panel and, perhaps, should be updated urgently in the next minor version of the panel.

adriangaam Wrote:The truth seems to me a very good idea that the IPs can be managed from the panel, but not the way it is done (with the ispcp_network daemon), but would be much more effective than directly on the configuration file on operating system, ie if debian (for example), a process which parses the data from the DB and the write in / etc / network / interfaces but ... So yes, keeping the settings made manually, by, for example, a start tag and an ending from which the process can change and outside are not.

What do you think about this? I think that opening the broadcast can be one important issue and a possibly backdoor on the server.

Thanks for reading.

Regards.