i can ping the jail, but the port is unreachable

[RandyJC]

I have a problem my FreeNAS is on a dedicated server running through Proxmox (server virtualization management) and i've added FreeNAS as a Virtual Machine.

Everythings works fine i can reach FreeNAS outside his own network. I even can reach the internet withing my Jails if i ping google and i can even reach my Freenas through ping.

but when i point my browser (in the same network domain) to my jail for ex. http://192.168.1.101 (owncloud port 80) the website is unreachable?! (yes i've tried to configure my jail and then start stop start the jail :) )

so i'm getting a bit tired because i don't know what to google anymore with different prhashes to find my problem.

FreeNAS:

[root@freenas ~]# ping google.nl
PING google.nl (173.194.40.191): 56 data bytes
64 bytes from 173.194.40.191: icmp_seq=0 ttl=57 time=1.156 ms
64 bytes from 173.194.40.191: icmp_seq=1 ttl=57 time=1.206 ms
64 bytes from 173.194.40.191: icmp_seq=2 ttl=57 time=1.163 ms
^C
--- google.nl ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.156/1.175/1.206/0.022 ms
[root@freenas ~]# ifconfig
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether 36:cd:da:0a:1d:d8
inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255
inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
ipfw0: flags=8800<SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:58:da:70:6f:00
nd6 options=1<PERFORMNUD>
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 6 priority 128 path cost 2000
member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 2 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:aa:6e:00:06:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair0b: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:22:e1:00:08:0b
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

[root@freenas ~]# jls
JID IP Address Hostname Path
13 - owncloud_1 /mnt/DATA/owncloud_1
14 - sickbeard_1 /mnt/DATA/sickbeard_1
[root@freenas ~]#



Desktop on the same network:
C:\Users\RandyJC>ping 192.168.1.101

Pinging 192.168.1.101 with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\RandyJC>

SSH from Proxmox:

root@sd-xxxx:/home/randyjc# ifconfig
eth0 Link encap:Ethernet HWaddr d4:ae:xxxxxx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3351884 errors:0 dropped:834 overruns:0 frame:0
TX packets:3049986 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3298426782 (3.0 GiB) TX bytes:2445654226 (2.2 GiB)

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:65536 Metric:1
RX packets:187059 errors:0 dropped:0 overruns:0 frame:0
TX packets:187059 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:128146709 (122.2 MiB) TX bytes:128146709 (122.2 MiB)

tap100i0 Link encap:Ethernet HWaddr f6:4xxxxxx
inet6 addr: fe80::f449:7aff:fe97:3e0d/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1676729 errors:0 dropped:0 overruns:0 frame:0
TX packets:1859780 errors:0 dropped:1461 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1871087692 (1.7 GiB) TX bytes:1921135881 (1.7 GiB)

tap102i0 Link encap:Ethernet HWaddr 9a:5xxxx
inet6 addr: fe80::9856:6ff:fec7:605a/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:10758 errors:0 dropped:0 overruns:0 frame:0
TX packets:40599 errors:0 dropped:887 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:5779542 (5.5 MiB) TX bytes:5994967 (5.7 MiB)

vmbr0 Link encap:Ethernet HWaddr d4:aexxxx
inet addr:62.21xxxx Bcast:62.xxxx Mask:255.255.255.0
inet6 addr: fe80::dxxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4878355 errors:0 dropped:0 overruns:0 frame:0
TX packets:4662124 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5094423073 (4.7 GiB) TX bytes:5392060739 (5.0 GiB)

vmbr0:0 Link encap:Ethernet HWaddr d4:ae:52:d0:67:13
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

root@sd-xxxx:/home/randyjc#


To much info now :p

last pid: 62109; load averages: 0.04, 0.06, 0.02 up 0+01:05:16 16:27:19
31 processes: 1 running, 30 sleeping

Mem: 212M Active, 101M Inact, 234M Wired, 1736K Cache, 185M Buf, 3389M Free
Swap: 2048M Total, 2048M Free


PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
2395 root 6 20 0 299M 116M usem 0 0:28 0.00% python2.7
2904 root 12 20 0 152M 15956K uwait 3 0:03 0.00% collectd
6115 root 1 52 0 158M 46592K ttyin 2 0:00 0.00% python2.7
60470 root 2 52 0 160M 45776K select 2 0:00 0.00% python2.7
60806 root 6 20 0 148M 28324K usem 2 0:00 0.00% python2.7
2858 nobody 1 20 0 9908K 2192K select 3 0:00 0.00% mdnsd
1989 root 1 20 0 22220K 3912K select 2 0:00 0.00% ntpd
1808 root 1 20 0 12036K 1736K select 0 0:00 0.00% syslogd
58138 root 6 52 0 106M 18868K usem 0 0:00 0.00% python2.7
62060 root 2 20 0 102M 20684K select 3 0:00 0.00% python2.7
59863 www 1 20 0 26044K 5748K kqread 0 0:00 0.00% nginx
2271 root 1 32 10 18592K 3252K wait 1 0:00 0.00% sh
7893 root 1 20 0 26044K 5224K pause 2 0:00 0.00% nginx
1495 root 1 20 0 6276K 736K select 3 0:00 0.00% devd
5976 root 1 20 0 14136K 1828K nanslp 3 0:00 0.00% cron
2252 root 1 20 0 28212K 3884K nanslp 1 0:00 0.00% smartd
2909 root 1 20 0 12044K 1584K sigwai 2 0:00 0.00% daemon
57882 root 1 20 0 12084K 1808K select 2 0:00 0.00% syslogd



SORRY FOR MY REALLY BAD ENGLISH!

 

[Whattteva]

From your jail, run

Code:

netstat -an|grep LISTEN

and check if you have anything listening on port 80.

Note: Your English is perfectly fine. I've seen a lot worse from actual native English speakers.

 

[RandyJC]

Wow, quick reply :) and thanks for the note! haha :)

Output:
root@owncloud_1:/ # netstat -an | grep LISTEN
tcp4 0 0 192.168.1.101.12347 *.* LISTEN

 

[RandyJC]

from another jail that i haven't tampered with:

Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 192.168.1.100.12346 192.168.1.5.42456 TIME_WAIT
tcp4 0 0 192.168.1.100.12346 *.* LISTEN

 

[Whattteva]

Wow, quick reply :) and thanks for the note! haha :)

Output:
root@owncloud_1:/ # netstat -an | grep LISTEN
tcp4 0 0 192.168.1.101.12347 *.* LISTEN

That tells me you have nothing listening on port 80. Hence, the "unreachable" error.
Something IS running at port 12347 though. Not sure what it is, but you can try to point your browser there http://192.168.1.101:12347 and see where it leads you.

 

[Neme]

I'm sure someone will be along shortly to warn you (quite rightly) of the perils of running FreeNAS as a virtual machine.

That aside I know from experience that on ESXi you have to set your virtual switch, network and FreeNAS NIC to allow promiscuous mode to allow it to pass the traffic for jails properly (without this I have had results from no traffic at all, to strange results like yours). I can see from the info you have posted above that "PROMISC" is being advertised by NIC em0, I would check that this is true of the other network layers. This may or may not be related to your problem as I have ZERO experience with Proxmox (hadn't even heard of it).

Would also be good if you could give us an idea of the hardware this is running on, there is some good information in the Forums Rules section about the sorts of things that might be useful to know: http://forums.freenas.org/index.php?threads/forum-rules.22553/

If you do chose to continue down the virtual route please make sure you read and understand the following information at a minimum:
http://forums.freenas.org/index.php...nas-in-production-as-a-virtual-machine.12484/

EDIT: The above being said (and still worth checking) Whattteva raises a valid point ;), I was busy typing at the time.

Good Luck

 

[RandyJC]

That tells me you have nothing listening on port 80. Hence, the "unreachable" error.
Something IS running at port 12347 though. Not sure what it is, but you can try to point your browser there http://192.168.1.101:12347 and see where it leads you.

The paige is still loading if i point my browser to that adress.

I'm sure someone will be along shortly to warn you (quite rightly) of the perils of running FreeNAS as a virtual machine.

That aside I know from experience that on ESXi you have to set your virtual switch, network and FreeNAS NIC to allow promiscuous mode to allow it to pass the traffic for jails properly (without this I have had results from no traffic at all, to strange results like yours). I can see from the info you have posted above that "PROMISC" is being advertised by NIC em0, I would check that this is true of the other network layers. This may or may not be related to your problem as I have ZERO experience with Proxmox (hadn't even heard of it).

Would also be good if you could give us an idea of the hardware this is running on, there is some good information in the Forums Rules section about the sorts of things that might be useful to know: http://forums.freenas.org/index.php?threads/forum-rules.22553/

If you do chose to continue down the virtual route please make sure you read and understand the following information at a minimum:
http://forums.freenas.org/index.php...nas-in-production-as-a-virtual-machine.12484/

EDIT: The above being said (and still worth checking) Whattteva raises a valid point ;), I was busy typing at the time.

Good Luck

Wow, ok i've read the topic and thats something i really did not think about! so oke i'm gonna reorder some things.. and pull my old pc out of the attic and start FreeNAS on that :)

Im gladly you came across and my point me to this. if i only knew this 11 hours straight earlier :P ( just being silly ;) )

Thanks again and pointing me to the rules before posting any question ! :)