Welcome Guest. Please Login or Register  


You are here: Index > Virtualizor - Virtual Server Control Panel > General Support > Topic : Rebuild Xen IPtables Without Restarting



Normal Mode | Print  

Rebuild Xen IPtables Without Restarting
bitronictechnologies
Group: Member
Post Group: Newbie
Posts: 3
Status:
By the way the whole reason that I had to reset the IP tables was because I could not traceroute any of my servers. Now I see why. The Virtulizor strikes again.

I guess after the latest update when you rebuild a VM with multiple IPs you end up with iptables like this:

Code
Chain FORWARD (policy ACCEPT)
target    prot opt source              destination
ACCEPT    all  --  anywhere            anywhere            PHYSDEV match --physdev-in eth0 ! --physdev-out eth0
ACCEPT    all  --  anywhere            anywhere            PHYSDEV match ! --physdev-in eth0 --physdev-out eth0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  powerhub.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  cloudone.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    all  --  powerhub.bitronictech.net  anywhere            PHYSDEV match --physdev-in vif1101.0
ACCEPT    udp  --  anywhere            anywhere            PHYSDEV match --physdev-in vif1101.0 udp spt:bootpc dpt:bootps


Obviously a problem. It is getting the hostname instead of the IP, which is screwing the hell out of all the packet routing.

I'll be opening a ticket and referencing this forum. This needs to be patched immediately.
IP: --   


Threads
 bitronictechnologies   Rebuild Xen IPtables Without Restarting, How does one Rebuild Xen IPtables Without Restarting (1 Replies, Read 3577 times)
    |--  bitronictechnologies   By the way...   on January 25, 2014, 7:43 am

« Previous    Next »

Normal Mode | Print  



Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is May 1, 2025, 12:19 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 10  |  Page Created In:0.072