unable to ping Jail from network

[docthomas]

Hi everyone,
I am running FreeNAS 8.3.1-BETA2 and have setup a jail for sickbeard, sab etc.
The jail starts and I am able to ping from the Freenas box to the jail ip and from the jail to the freenas IP. However I can not ping from the lan or to the lan from the Jail. This Freenas box is running on a HP Micro Server n40l and is not running on a hypervisor like esx or hyperv. I have attached netstat, ifconfig, ps, outputs as suggested by other threads.

View attachment inconfig.txt View attachment jailifconfig.txt View attachment jailps.txt View attachment netstat.txt

Any help you could provide would be great!

 

[Sarkazm]

I think I am having somewhat the same problem. Except it seems the Jail is unable to reach the the FreeNAS box??? It was working fine... Right now I do not know enough about FreeNAS to rule out my Network .. but I haven't altered my VERY simple network.

Feb 24 17:04:52 freenas kernel: re0: link state changed to UP
Feb 24 17:04:55 freenas notifier: security.jail.allow_raw_sockets: 1 -> 1
Feb 24 17:04:55 freenas notifier: Configuring jails:.
Feb 24 17:04:56 freenas notifier: Starting jails: jail1.
Feb 24 17:04:56 freenas notifier: add net default: gateway 192.168.200.1
Feb 24 17:04:56 freenas kernel: bridge0: Ethernet address: 02:9e:de:26:c8:00
Feb 24 17:04:56 freenas kernel: epair0a: Ethernet address: 02:80:44:00:09:0a
Feb 24 17:04:56 freenas kernel: epair0b: Ethernet address: 02:80:44:00:0a:0b
Feb 24 17:04:56 freenas kernel: epair0a: link state changed to UP
Feb 24 17:04:56 freenas kernel: epair0b: link state changed to UP
Feb 24 17:04:56 freenas kernel: epair0a: promiscuous mode enabled
Feb 24 17:04:56 freenas kernel: re0: promiscuous mode enabled
Feb 24 17:04:56 freenas kernel: re0: link state changed to DOWN
Feb 24 17:04:56 freenas notifier: stty: stdin isn't a terminal
Feb 24 17:04:56 freenas notifier: /etc/rc: WARNING: $hostname is not set -- see rc.conf(5).
Feb 24 17:04:56 freenas notifier: ELF ldconfig path: /lib /usr/lib /usr/local/lib
Feb 24 17:04:56 freenas notifier: ldconfig: /lib: ignoring directory not owned by root
Feb 24 17:04:56 freenas notifier: ldconfig: /usr/lib: ignoring directory not owned by root
Feb 24 17:04:56 freenas notifier: ldconfig: /usr/local/lib: ignoring directory not owned by root
Feb 24 17:04:56 freenas notifier: a.out ldconfig path: /usr/lib/aout
Feb 24 17:04:56 freenas notifier: ldconfig: /usr/lib/aout: No such file or directory
Feb 24 17:04:56 freenas notifier: Creating and/or trimming log files.
Feb 24 17:04:56 freenas notifier: Starting syslogd.
Feb 24 17:04:56 freenas notifier: Clearing /tmp (X related).
Feb 24 17:04:57 freenas notifier: grep: /usr/pbi/sabnzbd-i386/data/config.ini: No such file or directory
Feb 24 17:04:57 freenas notifier: Updating motd:.
Feb 24 17:04:57 freenas notifier: Starting minidlna.
Feb 24 17:04:57 freenas notifier: Starting cron.
Feb 24 17:04:57 freenas notifier:
Feb 24 17:04:57 freenas notifier: Sun Feb 24 17:04:57 PST 2013
Feb 24 17:04:58 freenas kernel: re0: link state changed to UP
Feb 24 17:05:04 freenas manage.py: [freeadmin.navtree:416] Couldn't retrieve http://192.168.200.46/plugins/transmission/_s/treemenu: timed out
Feb 24 17:05:04 freenas manage.py: [freeadmin.navtree:416] Couldn't retrieve http://192.168.200.46/plugins/minidlna/_s/treemenu: timed out
Feb 24 17:05:04 freenas manage.py: [freeadmin.navtree:416] Couldn't retrieve http://192.168.200.46/plugins/sabnzbd/_s/treemenu: timed out

 

[William Grzybowski]

What about the command outputs like the first post? We do not have crystal balls?