Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Does anyone have working Icehouse 3 Node setup with Neutron Networking: ML2 OVS GRE?

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox and ping the web.... ping does not work by any VBOX Node and therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Gr8 Thx to your support

best regards n7rx!

Does anyone have working Icehouse 3 Node setup with Neutron Networking: ML2 OVS GRE?

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox and ping the web.... ping does not work by any VBOX Node and therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Update1:

neutron server log at controller:

2014-09-05 12:07:59.190 1319 WARNING neutron.plugins.ml2.drivers.type_gre [req-4a03971c-1995-4ba3-992e-be9dd61e9cac None] Gre endpoint with ip 10.20.20.53 already exists
2014-09-05 12:08:01.381 1319 WARNING neutron.scheduler.dhcp_agent_scheduler [req-ac8356be-8e3c-4fa3-84c6-81c91cca2136 None] DHCP agent 418d37e1-4e93-4075-9b59-0725cfd46144 is not active
2014-09-05 12:08:02.567 1319 WARNING neutron.plugins.ml2.drivers.type_gre [req-f82f2995-a2fc-49f8-b027-cc2544c4c701 None] Gre endpoint with ip 10.20.20.52 already exists
2014-09-05 12:08:03.017 1319 WARNING neutron.scheduler.l3_agent_scheduler [req-67bd7a80-56e1-4652-90e1-4830023ee5cc None] L3 agent cac088e6-9244-4083-86f4-5ce6223bd108 is not active
Gr8 Thx to your support

support

best regards n7rx!

Does anyone have working Icehouse 3 Node setup with Neutron Networking: ML2 OVS GRE?

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox and ping the web.... ping does not work by any VBOX Node and therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Update1:

neutron server log at controller:

2014-09-05 12:07:59.190 1319 WARNING neutron.plugins.ml2.drivers.type_gre [req-4a03971c-1995-4ba3-992e-be9dd61e9cac None] Gre endpoint with ip 10.20.20.53 already exists
2014-09-05 12:08:01.381 1319 WARNING neutron.scheduler.dhcp_agent_scheduler [req-ac8356be-8e3c-4fa3-84c6-81c91cca2136 None] DHCP agent 418d37e1-4e93-4075-9b59-0725cfd46144 is not active
2014-09-05 12:08:02.567 1319 WARNING neutron.plugins.ml2.drivers.type_gre [req-f82f2995-a2fc-49f8-b027-cc2544c4c701 None] Gre endpoint with ip 10.20.20.52 already exists
2014-09-05 12:08:03.017 1319 WARNING neutron.scheduler.l3_agent_scheduler [req-67bd7a80-56e1-4652-90e1-4830023ee5cc None] L3 agent cac088e6-9244-4083-86f4-5ce6223bd108 is not active
Gr8 Thx to Thanks for your support
responses!

best regards n7rx!

Does anyone have working Icehouse 3 Node setup with Neutron Networking: ML2 OVS GRE?GRE? (NATed web-package fails from router to instance!)

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox and ping the web.... ping does not work by any VBOX Node and therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

best regards n7rx!

Does anyone have working Icehouse 3 Node setup with Neutron Networking: ML2 OVS GRE? (NATed web-package fails from router to instance!)

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox and ping the web.... ping does not work by any VBOX Node and therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

best regards n7rx!

Does anyone have working Icehouse 3 Node setup with Neutron Networking: ML2 OVS GRE? (NATed web-package fails from router to instance!)

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox or the local pool and ping the web.... ping does not work by any VBOX Node and the host itself therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

best regards n7rx!

Does anyone have working Icehouse 3 Node setup with Neutron Networking: ML2 OVS GRE? GRE (NATed web-package fails from router to instance!)

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox or the local pool and ping the web.... ping does not work by any VBOX Node and the host itself therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

Acces to metadata by instance is always good, and all does work but not the last step to get back by the web.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

best regards n7rx!

3 Node setup with Neutron Networking: ML2 OVS GRE (NATed web-package fails from router to instance!)

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox or the local pool and ping the web.... ping does not work by any VBOX Node and the host itself therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

Acces to metadata by instance is always good, and all does work but not the last step to get back by the web.web. Forward ipv4 is always enabled on any node of my setup.

It seems as all does work but this.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

best regards n7rx!

3 Node setup with Neutron Networking: ML2 OVS GRE (NATed web-package fails from router to instance!)

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox or the local pool and ping the web.... ping does not work by any VBOX Node and the host itself therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

Acces to metadata by instance is always good, and all does work but not the last step to get back by the web. Forward ipv4 is always enabled on any node of my setup.

It seems as all does work but this.

Moreover the metadata log of my virtual router is completely empty, in an older router log i can see something, but nothing in this which belongs to my net now.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

best regards n7rx!

3 Node setup with Neutron Networking: ML2 OVS GRE (NATed NATed web-package fails from router to instance!)instance!

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox or the local pool and ping the web.... ping does not work by any VBOX Node and the host itself therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

Acces to metadata by instance is always good, and all does work but not the last step to get back by the web. Forward ipv4 is always enabled on any node of my setup.

It seems as all does work but this.

Moreover the metadata log of my virtual router is completely empty, in an older router log i can see something, but nothing in this which belongs to my net now.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

best regards n7rx!

NATed web-package fails from router to instance!external Net reachable but not the internet!

I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox or the local pool and ping the web.... ping does not work by any VBOX Node and the host itself therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

Acces to metadata by instance is always good, and all does work but not the last step to get back by the web. Forward ipv4 is always enabled on any node of my setup.

It seems as all does work but this.

Moreover the metadata log of my virtual router is completely empty, in an older router log i can see something, but nothing in this which belongs to my net now.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

So it seems that the packages are going their way and gets back to the demorouter but not to the instance!

best regards n7rx!

external Net reachable but not the internet!

UPDATE:

It seems to work a little bit... I can get response with telnet command but than the ssh gets freeze or something like this... So really hope that it works for now!

ORIGINAL: I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox or the local pool and ping the web.... ping does not work by any VBOX Node and the host itself therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

Acces to metadata by instance is always good, and all does work but not the last step to get back by the web. Forward ipv4 is always enabled on any node of my setup.

It seems as all does work but this.

Moreover the metadata log of my virtual router is completely empty, in an older router log i can see something, but nothing in this which belongs to my net now.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

So it seems that the packages are going their way and gets back to the demorouter but not to the instance!

best regards n7rx!

external Net reachable but not the internet!

UPDATE:

It seems to work a little bit... I can get response with telnet command but than the ssh gets freeze or something like this... So really hope that it works for now!now! But within the telnet command it seems at there is a dns problem... telnet does only work with ip but try ping e.g. google.de resolves to correct ip!

ORIGINAL: I had used the basic installation guide for a 3 Node Icehouse Setup using ML2 with OVS as mechanism driver and GRE Tunneling.

Tutorial: http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_preface.html

Alll 3 Nodes are setup with Virtualbox and it seem to work nearly fine.

I can establish Instance, can ssh and ping it from any node in my physical net. The instance can ping real nodes in the physical net too.

My problem is the final step to Internet.

I have assigned floating_ips, setup the nova security rules and all other stuff.

There is some issue with virtualbox or the local pool and ping the web.... ping does not work by any VBOX Node and the host itself therefore not by Instance at all... but ping www.google.de does show me the right dns resolution.

Acces to metadata by instance is always good, and all does work but not the last step to get back by the web. Forward ipv4 is always enabled on any node of my setup.

It seems as all does work but this.

Moreover the metadata log of my virtual router is completely empty, in an older router log i can see something, but nothing in this which belongs to my net now.

The 3 Nodes can telnet the web but this does not work for instance with output:

From Instance:
$ telnet www.google.de 80
telnet: can't connect to remote host: Network is unreachable

So does anyone of you have a 3 Node Icehouse setup like me (maybe with Virtualbox, too) that does work and can ping the web and can share his files with me which i have to setup and also not to setup...!

Thanks for your responses!

Instance: telnet 173.194.112.120 80

demorouter tcpdump:

 root@network:~# ip netns exec qrouter-d8455b20-5a2f-4c49-9370-f0648b5ea4f5 tcpdump -nnti any not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^CIP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 3843316346:3843316394, ack 2841661934, win 255, options [nop,nop,TS val 1462078 ecr 32083], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 1:49, ack 48, win 3982, options [nop,nop,TS val 33823 ecr 1462078], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 49, win 255, options [nop,nop,TS val 1462081 ecr 33823], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [S], seq 1230737052, win 14600, options [mss 1460,sackOK,TS val 33825 ecr 0,nop,wscale 3], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [S.], seq 1104021756, ack 1230737053, win 42540, options [mss 1300,sackOK,TS val 709581795 ecr 33825,nop,wscale 6], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 1, win 1825, options [nop,nop,TS val 33829 ecr 709581795], length 0
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 48:96, ack 49, win 255, options [nop,nop,TS val 1466158 ecr 33823], length 48
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 49:209, ack 96, win 3982, options [nop,nop,TS val 37901 ecr 1466158], length 160
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 209, win 264, options [nop,nop,TS val 1466160 ecr 37901], length 0
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.138 > 172.29.34.255.138: NBT UDP PACKET(138)
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [P.], seq 96:144, ack 209, win 264, options [nop,nop,TS val 1466570 ecr 37901], length 48
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [F.], seq 1, ack 1, win 1825, options [nop,nop,TS val 38313 ecr 709581795], length 0
IP 192.168.1.4.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.98.22 > 172.29.34.90.40587: Flags [P.], seq 209:257, ack 144, win 3982, options [nop,nop,TS val 38314 ecr 1466570], length 48
IP 172.29.34.90.40587 > 172.29.34.98.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 172.29.34.90.40587 > 192.168.1.4.22: Flags [.], ack 257, win 264, options [nop,nop,TS val 1466571 ecr 38314], length 0
IP 173.194.112.120.80 > 172.29.34.98.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 173.194.112.120.80 > 192.168.1.4.58435: Flags [F.], seq 1, ack 2, win 665, options [nop,nop,TS val 709599744 ecr 38313], length 0
IP 192.168.1.4.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0
IP 172.29.34.98.58435 > 173.194.112.120.80: Flags [.], ack 2, win 1825, options [nop,nop,TS val 38318 ecr 709599744], length 0

32 packets captured
32 packets received by filter
0 packets dropped by kernel

So it seems that the packages are going their way and gets back to the demorouter but not to the instance!

best regards n7rx!