Hi Folks,
I am stuck on a strange problem and need some hints on how to go.
Short Version:
Webpage from a CT is reachable from the internet for some hours/days but then stop working.
As soon as i ping the Host (10.0.0.2) from inside the CT (10.0.0.3) or restart the Container, the Apache is reachable from the internet again.
So it seams Host<->CT ip routing will go to sleep after some time and needs a wakeup call in form of a ping from CT to host in order to establish ip forwarding..
Long Version:
I had a Proxmox Server (2.x) running for a year or so with 5-10 OpenVZ Containers.
On one of them i had an Apache2 Server serving Webpages on Port 80 everything went well for years.
Since i transfered the Server into my new flat, the problems have started:
After a random time, the Apache of the CT did not respond to requests from the internet any more (local requests were fine).
I had no glue what had happend and saw there is a new proxmox version available, so i updated to version 3.1 (very straightforward and painless by the way - respect!)
But my initial problem still exists.
I also created a new Container (stock debian-7.0 template), installed apache2 and copy the (static) html files over to the new CT. And disabled all other CT´s
Still the same - Webpage is reachable from the internet for some hours/days but then stop working.
I have tried via http://canyouseeme.org/ to connect to publicIP at Port 80 and it gets a timeout, wireshark sends a SYN packet but does not get anything in return.
My Setup is as following:
Internet <---> 84.114.118.x Cablemodem/Router (firewall is off atm) 10.0.0.1 <---> Proxmox Host 10.0.0.2 <---> Container 103 10.0.0.3
Container:
Host:
Iptables are empty in both Host and CT.
What i have found out so far is: As soon as i ping the Host (10.0.0.2) from inside the CT (10.0.0.3) or restart the Container, the Apache is reachable from the internet again.
So it seams Host<->CT ip routing will go to sleep after some time and needs a wakeup call in form of a ping from CT to host in order to establish ip forwarding..
Any Ideas?
I am stuck on a strange problem and need some hints on how to go.
Short Version:
Webpage from a CT is reachable from the internet for some hours/days but then stop working.
As soon as i ping the Host (10.0.0.2) from inside the CT (10.0.0.3) or restart the Container, the Apache is reachable from the internet again.
So it seams Host<->CT ip routing will go to sleep after some time and needs a wakeup call in form of a ping from CT to host in order to establish ip forwarding..
Long Version:
I had a Proxmox Server (2.x) running for a year or so with 5-10 OpenVZ Containers.
On one of them i had an Apache2 Server serving Webpages on Port 80 everything went well for years.
Since i transfered the Server into my new flat, the problems have started:
After a random time, the Apache of the CT did not respond to requests from the internet any more (local requests were fine).
I had no glue what had happend and saw there is a new proxmox version available, so i updated to version 3.1 (very straightforward and painless by the way - respect!)
But my initial problem still exists.
I also created a new Container (stock debian-7.0 template), installed apache2 and copy the (static) html files over to the new CT. And disabled all other CT´s
Still the same - Webpage is reachable from the internet for some hours/days but then stop working.
I have tried via http://canyouseeme.org/ to connect to publicIP at Port 80 and it gets a timeout, wireshark sends a SYN packet but does not get anything in return.
My Setup is as following:
Internet <---> 84.114.118.x Cablemodem/Router (firewall is off atm) 10.0.0.1 <---> Proxmox Host 10.0.0.2 <---> Container 103 10.0.0.3
Container:
Code:
root@maderas:/# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:7380 errors:0 dropped:0 overruns:0 frame:0
TX packets:6881 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1023175 (999.1 KiB) TX bytes:1443088 (1.3 MiB)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.0.0.3 P-t-P:10.0.0.3 Bcast:10.0.0.3 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1Code:
root@conception:~# ifconfig
eth0 Link encap:Ethernet Hardware Adresse 40:61:86:96:e3:e3
inet6-Adresse: fe80::4261:86ff:fe96:e3e3/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:1465919 errors:0 dropped:0 overruns:0 frame:0
TX packets:3351335 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:361050316 (344.3 MiB) TX bytes:3724675577 (3.4 GiB)
lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metrik:1
RX packets:134407 errors:0 dropped:0 overruns:0 frame:0
TX packets:134407 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:97978444 (93.4 MiB) TX bytes:97978444 (93.4 MiB)
venet0 Link encap:UNSPEC Hardware Adresse 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6-Adresse: fe80::1/128 Gültigkeitsbereich:Verbindung
UP BROADCAST PUNKTZUPUNKT RUNNING NOARP MTU:1500 Metrik:1
RX packets:2535273 errors:0 dropped:0 overruns:0 frame:0
TX packets:547470 errors:0 dropped:5 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:3499811758 (3.2 GiB) TX bytes:114610056 (109.3 MiB)
vmbr0 Link encap:Ethernet Hardware Adresse 40:61:86:96:e3:e3
inet Adresse:10.0.0.2 Bcast:10.0.0.255 Maske:255.255.255.0
inet6-Adresse: fe80::4261:86ff:fe96:e3e3/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:1417317 errors:0 dropped:0 overruns:0 frame:0
TX packets:3345335 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:335175066 (319.6 MiB) TX bytes:3724160182 (3.4 GiB)Code:
root@conception:~# route -n
Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
10.0.0.3 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
10.0.0.10 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 vmbr0
0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 vmbr0What i have found out so far is: As soon as i ping the Host (10.0.0.2) from inside the CT (10.0.0.3) or restart the Container, the Apache is reachable from the internet again.
So it seams Host<->CT ip routing will go to sleep after some time and needs a wakeup call in form of a ping from CT to host in order to establish ip forwarding..
Any Ideas?