ISPconfig3 support on Hyper-V

Discussion in 'Installation/Configuration' started by Polk, Aug 10, 2010.

  1. Polk

    Polk New Member

    Is ISPconfig3 supported on Hyper-V with synthetic drivers on Centos/SUSE?
    Integration Services create a seth0, seth1 network cards rather than eth0, eth1. Will ISPconfig work with seth* ?

    I have installed everything, but it doesn't seem to control much of the server. Firewall goes crazy sometimes and I keep losing connections.
    I did a change in
    /etc/Bastille/bastille-firewall.cfg

    PUBLIC_IFCES="eth+ ppp+ slip+ venet+"
    to:
    PUBLIC_IFCES="seth+ ppp+ slip+ venet+"

    but it doesnt seem to help.

    So is there support with seth network cards? If not, what is work around? How can I rename seth back to eth cards and still using hyper-v synthetic adapters.
     

Share This Page