You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by sandeep khandekar <cl...@gmail.com> on 2014/08/18 11:36:02 UTC
New error iptables
Dear Cloudstackers,
[root@hypervisor ~]# service iptables restart
iptables: Setting chains to policy ACCEPT: filter mangle na[ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: iptables-restore v1.4.7: Set i-2-3-VM
doesn't exist.
Error occurred at line: 83
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[FAILED]
vi /etc/sysconfig/iptables
80 -A i-2-3-def -m state --state RELATED,ESTABLISHED -j ACCEPT
81 -A i-2-3-def -p udp -m physdev --physdev-in vnet9
--physdev-is-bridged -m udp --sport 68 --dport 67 -j ACCEPT
82 -A i-2-3-def -p udp -m physdev --physdev-out vnet9
--physdev-is-bridged -m udp --sport 67 --dport 68 -j ACCEPT
83 -A i-2-3-def -p udp -m physdev --physdev-in vnet9
--physdev-is-bridged -m set --match-set i-2-3-VM src -m udp --dport 53 -j
RETURN
84 -A i-2-3-def -m physdev --physdev-in vnet9 --physdev-is-bridged -m
set --match-set i-2-3-VM src -j i-2-3-VM-eg
85 -A i-2-3-def -m physdev --physdev-out vnet9 --physdev-is-bridged -j
i-2-3-VM
86 -A r-4-VM -m physdev --physdev-in vnet7 --physdev-is-bridged -j
RETURN
87 -A r-4-VM -j ACCEPT
88 COMMIT
How to solve these error
--
SANDEEP KHANDEKAR
Assistant Professor
Department of Computer science and engineering
Sreenidhi Institute of science and Technology
Hyderabad
Re: New error iptables
Posted by Jayapal Reddy Uradi <ja...@citrix.com>.
Hi Sandeep,
upset for the vm i-2-3-VM is not found.
Try ipset -L command on the host to check the ipset names.
For help search ipset in http://jayapalu.blogspot.in/2013/09/security-groups-in-cloudstack.html
Why do you want to restart the iptables on the host?
When you reboot the host all the rules from the MS get reconfigured.
Thanks,
Jayapal
On 18-Aug-2014, at 3:06 PM, sandeep khandekar <cl...@gmail.com>
wrote:
> Dear Cloudstackers,
>
> [root@hypervisor ~]# service iptables restart
> iptables: Setting chains to policy ACCEPT: filter mangle na[ OK ]
> iptables: Flushing firewall rules: [ OK ]
> iptables: Unloading modules: [ OK ]
> iptables: Applying firewall rules: iptables-restore v1.4.7: Set i-2-3-VM
> doesn't exist.
>
> Error occurred at line: 83
> Try `iptables-restore -h' or 'iptables-restore --help' for more information.
> [FAILED]
> vi /etc/sysconfig/iptables
> 80 -A i-2-3-def -m state --state RELATED,ESTABLISHED -j ACCEPT
> 81 -A i-2-3-def -p udp -m physdev --physdev-in vnet9
> --physdev-is-bridged -m udp --sport 68 --dport 67 -j ACCEPT
> 82 -A i-2-3-def -p udp -m physdev --physdev-out vnet9
> --physdev-is-bridged -m udp --sport 67 --dport 68 -j ACCEPT
> 83 -A i-2-3-def -p udp -m physdev --physdev-in vnet9
> --physdev-is-bridged -m set --match-set i-2-3-VM src -m udp --dport 53 -j
> RETURN
> 84 -A i-2-3-def -m physdev --physdev-in vnet9 --physdev-is-bridged -m
> set --match-set i-2-3-VM src -j i-2-3-VM-eg
> 85 -A i-2-3-def -m physdev --physdev-out vnet9 --physdev-is-bridged -j
> i-2-3-VM
> 86 -A r-4-VM -m physdev --physdev-in vnet7 --physdev-is-bridged -j
> RETURN
> 87 -A r-4-VM -j ACCEPT
> 88 COMMIT
>
> How to solve these error
> --
> SANDEEP KHANDEKAR
> Assistant Professor
> Department of Computer science and engineering
> Sreenidhi Institute of science and Technology
> Hyderabad