Jeff | 6 May 2010 12:19
Picon
Favicon

Printer won't work

I had a Canon i550 working fine in PCBSD 7.1 but it fails to work in 8.0.

Used the CUPS facility to find this USB printer but it didn't find it.  Manually installed it using the BJC-8200 Gutenprint driver I've used before. 

Then trying to print via OO resulted in CUPS reporting a permission error: "Unable to open device file: /dev/ulpt0 Permission denied":

Permissions are: crw-r--r--.  What does the 'c' mean? User is 'root', group is 'operator'.

Tried using the PCBSD printer facility and got nowhere. Can't print test page either.

Any idea how to troubleshoot this?

...Jeff

_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Kris Moore | 6 May 2010 10:33
Gravatar

Re: Printer won't work

On 05/06/2010 10:19, Jeff wrote:
I had a Canon i550 working fine in PCBSD 7.1 but it fails to work in 8.0.

Used the CUPS facility to find this USB printer but it didn't find it.  Manually installed it using the BJC-8200 Gutenprint driver I've used before. 

Then trying to print via OO resulted in CUPS reporting a permission error: "Unable to open device file: /dev/ulpt0 Permission denied":

Permissions are: crw-r--r--.  What does the 'c' mean? User is 'root', group is 'operator'.

Tried using the PCBSD printer facility and got nowhere. Can't print test page either.

Any idea how to troubleshoot this?

...Jeff

_______________________________________________ Testing mailing list Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org http://lists.pcbsd.org/mailman/listinfo/testing


The "c" means character device. You can try running "chmod 666" /dev/utlp0, and check the perms again, should be writable now.

If that works, we'll need to check /etc/devfs.rules, utlp0 is already supposed to be setperm "666", but it may be failing :(

-- Kris Moore PC-BSD Software iXsystems
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Jeff | 6 May 2010 16:57
Picon
Favicon

Re: Printer won't work

I forgot to mention I had changed the perms to crw-rw-r-- but it just does nothing and CUPS reports the job is pending.  The file /dev/ulpt0 BTW, is empty.

Printer works fine on Windoze.

CUPS error log didn't show anything egregious.

CUPS reports printer status: Paused - "Finished page 2..."


--- On Thu, 5/6/10, Kris Moore <kris-E1R8x85rdljYtjvyW6yDsg@public.gmane.org> wrote:

From: Kris Moore <kris-E1R8x85rdljYtjvyW6yDsg@public.gmane.org>
Subject: Re: [PC-BSD Testing] Printer won't work
To: testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
Date: Thursday, May 6, 2010, 4:33 AM

On 05/06/2010 10:19, Jeff wrote:
I had a Canon i550 working fine in PCBSD 7.1 but it fails to work in 8.0.

Used the CUPS facility to find this USB printer but it didn't find it.  Manually installed it using the BJC-8200 Gutenprint driver I've used before. 

Then trying to print via OO resulted in CUPS reporting a permission error: "Unable to open device file: /dev/ulpt0 Permission denied":

Permissions are: crw-r--r--.  What does the 'c' mean? User is 'root', group is 'operator'.

Tried using the PCBSD printer facility and got nowhere. Can't print test page either.

Any idea how to troubleshoot this?

...Jeff


_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing


The "c" means character device. You can try running "chmod 666" /dev/utlp0, and check the perms again, should be writable now.

If that works, we'll need to check /etc/devfs.rules, utlp0 is already supposed to be setperm "666", but it may be failing :(

--
Kris Moore
PC-BSD Software
iXsystems

-----Inline Attachment Follows-----

_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing

_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Jeff | 6 May 2010 17:20
Picon
Favicon

1TB external usb drive shows smaller size in Dolphin

Using PCBSD-8.0 - 64bit Dolphin mounts my Western Digital 1TB USB drive ok but reports this for disk usage with 2.4 GiB of files on it:

16,777,216.0 TiB free of 15.5 GiB (-2,147,483,548 % used)

Total gibberish.  So I can't put more than a few GiB on this drive before it reports the disk is full.

Konqueror reports the same krap.

Kwikdisk reports this drive /dev/da0s1 as having a capacity of 1.9 GB and full.
-----------------------
Another drive I have was formatted for Windoze.  Way back in PCBSD 7 or possibly earlier, I was able to read this drive and retrieve some old Windoze files.  I cannot mount this drive anymore using various combinations of: mount_msdosfs -o large /dev/da0s1 /media/Backup

Or: mount -o large -t msdosfs /dev/da0s1 /media/Backup

camcontrol devlist reports this drive as da0.

Frustrating!



_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Ian Robinson | 6 May 2010 23:33
Picon

Mounting USB Hard Drives



On Thu, May 6, 2010 at 3:00 PM, Jeff wrote:

Another drive I have was formatted for Windoze.? Way back in PCBSD 7 or possibly earlier, I was able to read this drive and retrieve some old Windoze files.? I cannot mount this drive anymore using various combinations of: mount_msdosfs -o large /dev/da0s1 /media/Backup

Or: mount -o large -t msdosfs /dev/da0s1 /media/Backup

camcontrol devlist reports this drive as da0.

1.  Sometimes a USB device will not mount with the /dev/da0s1 argument but will mount with /dev/da0

2.  The FreeBSD handbook ( <at> http://www.freebsd.org/doc/en/books/handbook/usb-disks.html  ) adds a couple of "extras" which may be worth reviewing:

======= Begin Quote from FreeBSD Handbook ================

"To make this device mountable as a normal user, certain steps have to be taken. First, the devices that are created when a USB storage device is connected need to be accessible by the user. A solution is to make all users of these devices a member of the operator group. This is done with pw(8). Second, when the devices are created, the operator group should be able to read and write them. This is accomplished by adding these lines to /etc/devfs.rules:

[localrules=5]
add path 'da*' mode 0660 group operator

Note: If there already are SCSI disks in the system, it must be done a bit different. E.g., if the system already contains disks da0 through da2 attached to the system, change the second line as follows:

add path 'da[3-9]*' mode 0660 group operator

This will exclude the already existing disks from belonging to the operator group.

You also have to enable your devfs.rules(5) ruleset in your /etc/rc.conf file:

devfs_system_ruleset="localrules"

Next, the kernel has to be configured to allow regular users to mount file systems. The easiest way is to add the following line to /etc/sysctl.conf:

vfs.usermount=1

Note that this only takes effect after the next reboot. Alternatively, one can also use sysctl(8) to set this variable.

The final step is to create a directory where the file system is to be mounted. This directory needs to be owned by the user that is to mount the file system. One way to do that is for root to create a subdirectory owned by that user as /mnt/username (replace username by the login name of the actual user and usergroup by the user's primary group):

# mkdir /mnt/username
# chown username:usergroup /mnt/username"

======= End Quote from FreeBSD Handbook ================

3.  The last three Western Digital external USB drives I bought with 500 Gb and larger came formatted NTFS.  Are yours formatted Fat32 or NTFS?

4.  Even then, NTFS may present mounting issues on 8.0/64 bit installations.  See " [solved] Can't mount ntfs usb hard drive" <at> 4ttp://forums.freebsd.org/showthread.php?t=11968

5.  There are reports of USB disks hanging during the boot/POST sequence with a recommendation to "disable legacy USB support" in the BIOS.  See <at> http://forums.freebsd.org/showthread.php?t=11650

Ian Robinson
Salem, Ohio




_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Mike Bybee | 6 May 2010 23:57

Re: Mounting USB Hard Drives



On Thu, May 6, 2010 at 2:33 PM, Ian Robinson <fitchkendall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:


On Thu, May 6, 2010 at 3:00 PM, Jeff wrote:

Another drive I have was formatted for Windoze.? Way back in PCBSD 7 or possibly earlier, I was able to read this drive and retrieve some old Windoze files.? I cannot mount this drive anymore using various combinations of: mount_msdosfs -o large /dev/da0s1 /media/Backup

Or: mount -o large -t msdosfs /dev/da0s1 /media/Backup

camcontrol devlist reports this drive as da0.

1.  Sometimes a USB device will not mount with the /dev/da0s1 argument but will mount with /dev/da0

2.  The FreeBSD handbook ( <at> http://www.freebsd.org/doc/en/books/handbook/usb-disks.html  ) adds a couple of "extras" which may be worth reviewing:

======= Begin Quote from FreeBSD Handbook ================

"To make this device mountable as a normal user, certain steps have to be taken. First, the devices that are created when a USB storage device is connected need to be accessible by the user. A solution is to make all users of these devices a member of the operator group. This is done with pw(8). Second, when the devices are created, the operator group should be able to read and write them. This is accomplished by adding these lines to /etc/devfs.rules:

[localrules=5]
add path 'da*' mode 0660 group operator

Note: If there already are SCSI disks in the system, it must be done a bit different. E.g., if the system already contains disks da0 through da2 attached to the system, change the second line as follows:

add path 'da[3-9]*' mode 0660 group operator

This will exclude the already existing disks from belonging to the operator group.

You also have to enable your devfs.rules(5) ruleset in your /etc/rc.conf file:

devfs_system_ruleset="localrules"

Next, the kernel has to be configured to allow regular users to mount file systems. The easiest way is to add the following line to /etc/sysctl.conf:

vfs.usermount=1

Note that this only takes effect after the next reboot. Alternatively, one can also use sysctl(8) to set this variable.

The final step is to create a directory where the file system is to be mounted. This directory needs to be owned by the user that is to mount the file system. One way to do that is for root to create a subdirectory owned by that user as /mnt/username (replace username by the login name of the actual user and usergroup by the user's primary group):

# mkdir /mnt/username
# chown username:usergroup /mnt/username"

======= End Quote from FreeBSD Handbook ================

3.  The last three Western Digital external USB drives I bought with 500 Gb and larger came formatted NTFS.  Are yours formatted Fat32 or NTFS?

4.  Even then, NTFS may present mounting issues on 8.0/64 bit installations.  See " [solved] Can't mount ntfs usb hard drive" <at> 4ttp://forums.freebsd.org/showthread.php?t=11968

5.  There are reports of USB disks hanging during the boot/POST sequence with a recommendation to "disable legacy USB support" in the BIOS.  See <at> http://forums.freebsd.org/showthread.php?t=11650

Ian Robinson
Salem, Ohio





_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing


I've had major issues with NTFS USB drives on the new PC-BSD 8 images - especially the higher capacity ones. It's almost critical to make sure you plug them in once you're logged in - I haven't gotten one to work yet if it was plugged in prior to booting.
Also worth noting is that the new extFAT that some of the new thumbdrives come with is nearly impossible to get working (I found it's far easier to just reformat them).

--
Thanks,
Mike Bybee
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Brodey Dover | 7 May 2010 00:34
Picon

Re: Printer won't work

Although "other" shouldn't need r and w from what I remember, 666 is the recommended user-level access for device in FreeBSD. Want to see if adding that w in other helps things along?

On Thu, May 6, 2010 at 10:57 AM, Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:
I forgot to mention I had changed the perms to crw-rw-r-- but it just does nothing and CUPS reports the job is pending.  The file /dev/ulpt0 BTW, is empty.

Printer works fine on Windoze.

CUPS error log didn't show anything egregious.

CUPS reports printer status: Paused - "Finished page 2..."


--- On Thu, 5/6/10, Kris Moore <kris-E1R8x85rdljYtjvyW6yDsg@public.gmane.org> wrote:

From: Kris Moore <kris-E1R8x85rdljYtjvyW6yDsg@public.gmane.org>
Subject: Re: [PC-BSD Testing] Printer won't work
To: testing <at> lists.pcbsd.org
Date: Thursday, May 6, 2010, 4:33 AM


On 05/06/2010 10:19, Jeff wrote:
I had a Canon i550 working fine in PCBSD 7.1 but it fails to work in 8.0.

Used the CUPS facility to find this USB printer but it didn't find it.  Manually installed it using the BJC-8200 Gutenprint driver I've used before. 

Then trying to print via OO resulted in CUPS reporting a permission error: "Unable to open device file: /dev/ulpt0 Permission denied":

Permissions are: crw-r--r--.  What does the 'c' mean? User is 'root', group is 'operator'.

Tried using the PCBSD printer facility and got nowhere. Can't print test page either.

Any idea how to troubleshoot this?

...Jeff


_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing


The "c" means character device. You can try running "chmod 666" /dev/utlp0, and check the perms again, should be writable now.

If that works, we'll need to check /etc/devfs.rules, utlp0 is already supposed to be setperm "666", but it may be failing :(

--
Kris Moore
PC-BSD Software
iXsystems

-----Inline Attachment Follows-----


_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing


_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing


_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Brodey Dover | 7 May 2010 00:38
Picon

Re: Mounting USB Hard Drives

Is this only with USB? Can you test FW or SATA? I think I'm actually
capable of testing this out for confirmation!

Brodey

On Thu, May 6, 2010 at 5:57 PM, Mike Bybee <mbybee@...> wrote:
>
>
> On Thu, May 6, 2010 at 2:33 PM, Ian Robinson <fitchkendall@...> wrote:
>>
>>
>> On Thu, May 6, 2010 at 3:00 PM, Jeff wrote:
>>
>>> Another drive I have was formatted for Windoze.? Way back in PCBSD 7 or
>>> possibly earlier, I was able to read this drive and retrieve some old
>>> Windoze files.? I cannot mount this drive anymore using various combinations
>>> of: mount_msdosfs -o large /dev/da0s1 /media/Backup
>>>
>>> Or: mount -o large -t msdosfs /dev/da0s1 /media/Backup
>>>
>>> camcontrol devlist reports this drive as da0.
>>
>> 1.  Sometimes a USB device will not mount with the /dev/da0s1 argument but
>> will mount with /dev/da0
>>
>> 2.  The FreeBSD handbook ( <at> 
>> http://www.freebsd.org/doc/en/books/handbook/usb-disks.html  ) adds a couple
>> of "extras" which may be worth reviewing:
>>
>> ======= Begin Quote from FreeBSD Handbook ================
>>
>> "To make this device mountable as a normal user, certain steps have to be
>> taken. First, the devices that are created when a USB storage device is
>> connected need to be accessible by the user. A solution is to make all users
>> of these devices a member of the operator group. This is done with pw(8).
>> Second, when the devices are created, the operator group should be able to
>> read and write them. This is accomplished by adding these lines to
>> /etc/devfs.rules:
>>
>> [localrules=5]
>> add path 'da*' mode 0660 group operator
>>
>> Note: If there already are SCSI disks in the system, it must be done a bit
>> different. E.g., if the system already contains disks da0 through da2
>> attached to the system, change the second line as follows:
>>
>> add path 'da[3-9]*' mode 0660 group operator
>>
>> This will exclude the already existing disks from belonging to the
>> operator group.
>>
>> You also have to enable your devfs.rules(5) ruleset in your /etc/rc.conf
>> file:
>>
>> devfs_system_ruleset="localrules"
>>
>> Next, the kernel has to be configured to allow regular users to mount file
>> systems. The easiest way is to add the following line to /etc/sysctl.conf:
>>
>> vfs.usermount=1
>>
>> Note that this only takes effect after the next reboot. Alternatively, one
>> can also use sysctl(8) to set this variable.
>>
>> The final step is to create a directory where the file system is to be
>> mounted. This directory needs to be owned by the user that is to mount the
>> file system. One way to do that is for root to create a subdirectory owned
>> by that user as /mnt/username (replace username by the login name of the
>> actual user and usergroup by the user's primary group):
>>
>> # mkdir /mnt/username
>> # chown username:usergroup /mnt/username"
>>
>>
>> ======= End Quote from FreeBSD Handbook ================
>>
>> 3.  The last three Western Digital external USB drives I bought with 500
>> Gb and larger came formatted NTFS.  Are yours formatted Fat32 or NTFS?
>>
>> 4.  Even then, NTFS may present mounting issues on 8.0/64 bit
>> installations.  See " [solved] Can't mount ntfs usb hard drive"  <at> 
>> 4ttp://forums.freebsd.org/showthread.php?t=11968
>>
>> 5.  There are reports of USB disks hanging during the boot/POST sequence
>> with a recommendation to "disable legacy USB support" in the BIOS.  See  <at> 
>> http://forums.freebsd.org/showthread.php?t=11650
>>
>> Ian Robinson
>> Salem, Ohio
>>
>>
>>
>>
>>
>> _______________________________________________
>> Testing mailing list
>> Testing@...
>> http://lists.pcbsd.org/mailman/listinfo/testing
>>
>
> I've had major issues with NTFS USB drives on the new PC-BSD 8 images -
> especially the higher capacity ones. It's almost critical to make sure you
> plug them in once you're logged in - I haven't gotten one to work yet if it
> was plugged in prior to booting.
> Also worth noting is that the new extFAT that some of the new thumbdrives
> come with is nearly impossible to get working (I found it's far easier to
> just reformat them).
>
> --
> Thanks,
> Mike Bybee
>
> _______________________________________________
> Testing mailing list
> Testing@...
> http://lists.pcbsd.org/mailman/listinfo/testing
>
>
Mike Bybee | 7 May 2010 00:55

Re: Mounting USB Hard Drives



On Thu, May 6, 2010 at 3:38 PM, Brodey Dover <doverosx <at> gmail.com> wrote:
Is this only with USB? Can you test FW or SATA? I think I'm actually
capable of testing this out for confirmation!

Brodey




I do have one laptop with firewire and PC-BSD 8, I'll give it a shot and we can compare. Not sure my firewire works on there though :)

--
Thanks,
Mike Bybee
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Jeff | 7 May 2010 16:09
Picon
Favicon

Re: BIND problem in jail

Well, this has come back to bite me again.

I was living in Thailand when it I fixed it, using a Dlink ADSL router and used DHCP for the PCBSD box.  Then I moved back to the US and set up my old network using a Linksys router and a Linksys wireless bridge to connect my PCBSD box to the router and the internet.

I'm using lagg0 for the jail but set up the box with a static IP.  So now the original problem is back - slow server response in the jail and Drupal cannot talk to the internet for updates and such.  Set it up with DHCP and same problem.

Oddly enough, when I had it setup with a static IP, Firefox was really slow accessing the server site, like 10 seconds lag, but Opera was the normal 1 or 2 seconds.  When I changed to DHCP both were slow, taking nearly 20 seconds to respond - it's all lag time - the page loads very fast after that.

I noticed at boot there is a message something to the effect of re0 busy.  Also noticed in Webmin, the network interface is reported as:

  Name    Type    IP Address    Netmask    Status   

lagg0 Unknown 192.168.1.101 255.255.255.0 Up

  lagg0:0 Unknown (Virtual) 192.168.1.12 255.255.255.255 Up
lo0 Loopback 127.0.0.1 255.0.0.0 Up

192.168.1.12 is the IP for the jail and .101 is the network interface card on DHCP.

I have had similar problems with PCBSD going way back and never resolved them.  I just keep fiddling and rebooting and somehow it magically gets fixed but I never know why.  Now however, I can't get it to work properly no matter what I try.

What in the world causes this behavior and how do I fix it?

...Jeff

--- On Sat, 3/27/10, Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:

From: Jeff <dejamuse <at> yahoo.com>
Subject: Re: [PC-BSD Testing] BIND problem in jail
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Date: Saturday, March 27, 2010, 4:28 AM

Rebooted the machine and now can access the server from the other computer as before.

Hurray!

Still confusing krap though...

--- On Sat, 3/27/10, Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:

From: Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PC-BSD Testing] BIND problem in jail
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Date: Saturday, March 27, 2010, 3:43 AM

Also should note that when the interface for the jail was set to re0, Drupal could not reach the outside world (to check for module updates) and I could not ping the IP from another computer in my local network (on a wireless port to the router).

Now using lagg0 I can ping the IP from the other computer but I cannot connect to the server as I could before.  Strange.   I suspect that has more to do with the router than PCBSD.  I had been tinkering with it before, trying to expose the server to the internet.  That normally requires port forwarding which in turn requires a static IP for the server.  But when I first set things up, the server box was using DHCP and I could access the server on port 80 from the other computer - now I can't, even after resetting the router back to where it was.

Confusing krap!

--- On Sat, 3/27/10, Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:

From: Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PC-BSD Testing] BIND problem in jail
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Date: Saturday, March 27, 2010, 3:22 AM

When I reset the jail to use re0, the response of the server in the jail was sluggish, like 15 seconds to render a page.

Then I set it to use lagg0 and it's now fast again.

I don't understand too much of this network stuff - confusing.

--- On Fri, 3/26/10, Kris Moore <kris-E1R8x85rdljYtjvyW6yDsg@public.gmane.org> wrote:

From: Kris Moore <kris-E1R8x85rdljYtjvyW6yDsg@public.gmane.org>
Subject: Re: [PC-BSD Testing] BIND problem in jail
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Date: Friday, March 26, 2010, 7:17 AM

On 03/26/2010 13:31, Jeff wrote:
Yes created with the Warden (in 7.1.1).

Output of jls:

   JID  IP Address      Hostname                      Path
     1  192.168.1.12    Drupal                        /usr/local/warden/jails/192.168.1.12
     2  10.1.1.1        pcbsd-2276                    /usr/jails/portjail

Contents of etc/pf.conf:

set skip on lo0
set block-policy return
scrub in all
nat on lagg0 from lo1:network to any -> (lagg0)
nat on re0 from lo1:network to any -> (re0)
block in log
antispoof quick for lo0 inet
block in from no-route to any
pass out keep state
table <blacklist> persist file "/etc/blacklist"
pass inet proto icmp from any to any
pass inet6 proto icmp6 from any to any
pass in proto {tcp,udp} from any to any port 49152:65535 keep state
block from <blacklist> to any
pass in on re0 proto tcp from any to (re0) port 80 keep state
pass in on re0 proto udp from any to (re0) port 138 keep state
pass in on re0 proto udp from any to (re0) port 111 keep state
pass in on re0 proto udp from any to (re0) port 1110 keep state
pass in on re0 proto udp from any to (re0) port 2049 keep state
pass in on re0 proto udp from any to (re0) port 4045 keep state
pass in on re0 proto tcp from any to (re0) port 445 keep state
pass in on re0 proto tcp from any to (re0) port 137 keep state
pass in on re0 proto tcp from any to (re0) port 139 keep state
pass in on re0 proto tcp from any to (re0) port 111 keep state
pass in on re0 proto tcp from any to (re0) port 1110 keep state
pass in on re0 proto tcp from any to (re0) port 4045 keep state
pass in on lagg0 proto udp from any to (lagg0) port 137 keep state
pass in on lagg0 proto udp from any to (lagg0) port 138 keep state
pass in on lagg0 proto udp from any to (lagg0) port 111 keep state
pass in on lagg0 proto udp from any to (lagg0) port 1110 keep state
pass in on lagg0 proto udp from any to (lagg0) port 2049 keep state
pass in on lagg0 proto udp from any to (lagg0) port 4045 keep state
pass in on lagg0 proto tcp from any to (lagg0) port 445 keep state
pass in on lagg0 proto tcp from any to (lagg0) port 137 keep state
pass in on lagg0 proto tcp from any to (lagg0) port 139 keep state
pass in on lagg0 proto tcp from any to (lagg0) port 111 keep state
pass in on lagg0 proto tcp from any to (lagg0) port 1110 keep state
pass in on lagg0 proto tcp from any to (lagg0) port 4045 keep state
pass out on re0 proto tcp from any to (re0) port 80 keep state
pass in on re0 proto tcp from any to (re0) port 8080 keep state
pass out on re0 proto tcp from any to (re0) port 8080 keep state
pass in on lagg0 proto tcp from any to (lagg0) port 80 keep state
pass out on lagg0 proto tcp from any to (lagg0) port 80 keep state

Oh another thing to check. We need to make sure the jail is getting started on the right network interface. Try this as root:

# pbreg get /PC-BSD/TheWarden/NIC

What is that set to? If you are using the lagg0 interface in ifconfig, then you'll need to set it to lagg0 with:

# pbreg set /PC-BSD/TheWarden/NIC lagg0

Otherwise, it'll need to bet set to the right device, such as re0 and restart the jail.

--
Kris Moore
PC-BSD Software
iXsystems

-----Inline Attachment Follows-----

_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing


-----Inline Attachment Follows-----

_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing


-----Inline Attachment Follows-----

_______________________________________________
Testing mailing list
Testing <at> lists.pcbsd.org
http://lists.pcbsd.org/mailman/listinfo/testing


-----Inline Attachment Follows-----

_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing

_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing

Gmane