PF RDR from LAN to LAN
Hi folks, I've little questions about RDR using Packet Filter (PF), I used IPF (IPFILTER) before and success with this scenario. extif = outside interface intif = internal interface public_ip = 202.xxx.xxx.xxx client_create = 192.168.1.1, port = 6112 client_join = 192.168.1.2 for outside/internet rdr pass on $extif proto tcp from any to $public_ip port 6112 - $client_create port 6112 That's rule success can forward from from internet to $client_create, now other plan how to forward $client_join to $client_create. I use this rule: rdr pass on $intif proto tcp from $client_join to $public_ip port 6112 - $client_create port 6112 As far i know if $client_create created game host with port 6112 will be translate to $public_ip with port 6112 too. so I need to forward from LAN to $public_ip/6112 to actually who create game ($client_create/6112) pfctl -s state resulting: client_create 6112 - public_ip 6112 - client_join SYS-CLOSED Anyone help for this issue - Thank you -- budsz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
re: /root/bin and /usr/local/i386-portbld-freebsd9.0
I've found the two directories below on my system. I don't remember creating them. So I'd like to be able to find out what package(s) has/have created them, if possible. # ls -ld /root/bin/ drwxr-xr-x 2 root wheel 512 Aug 29 22:52 /root/bin/ # ls -Rl /root/bin/ total 0 # ls -dl /usr/local/i386-portbld-freebsd9.0 drwxr-xr-x 4 root wheel 512 Jul 8 22:32 /usr/local/i386-portbld-freebsd9.0 # ls -Rl /usr/local/i386-portbld-freebsd9.0 total 8 drwxr-xr-x 2 root wheel 512 Jul 8 22:32 bin drwxr-xr-x 3 root wheel 512 Jul 8 22:32 lib /usr/local/i386-portbld-freebsd9.0/bin: total 10816 -r-xr-xr-x 2 root wheel 604172 Jul 8 22:32 ar -r-xr-xr-x 2 root wheel 1036440 Jul 8 22:32 as -r-xr-xr-x 4 root wheel 879860 Jul 8 22:32 ld -r-xr-xr-x 4 root wheel 879860 Jul 8 22:32 ld.bfd -r-xr-xr-x 2 root wheel 3463684 Jul 8 22:32 ld.gold -r-xr-xr-x 2 root wheel 587808 Jul 8 22:32 nm -r-xr-xr-x 2 root wheel 733004 Jul 8 22:32 objcopy -r-xr-xr-x 2 root wheel 1098644 Jul 8 22:32 objdump -r-xr-xr-x 2 root wheel 604172 Jul 8 22:32 ranlib -r-xr-xr-x 2 root wheel 733004 Jul 8 22:32 strip /usr/local/i386-portbld-freebsd9.0/lib: total 4 drwxr-xr-x 2 root wheel 1024 Jul 8 22:32 ldscripts /usr/local/i386-portbld-freebsd9.0/lib/ldscripts: total 228 -r--r--r-- 1 root wheel 7375 Jul 8 22:32 elf_i386.x -r--r--r-- 1 root wheel 7158 Jul 8 22:32 elf_i386.xbn -r--r--r-- 1 root wheel 7188 Jul 8 22:32 elf_i386.xc -r--r--r-- 1 root wheel 7303 Jul 8 22:32 elf_i386.xd -r--r--r-- 1 root wheel 7133 Jul 8 22:32 elf_i386.xdc -r--r--r-- 1 root wheel 7123 Jul 8 22:32 elf_i386.xdw -r--r--r-- 1 root wheel 7375 Jul 8 22:32 elf_i386.xn -r--r--r-- 1 root wheel 4658 Jul 8 22:32 elf_i386.xr -r--r--r-- 1 root wheel 6897 Jul 8 22:32 elf_i386.xs -r--r--r-- 1 root wheel 6727 Jul 8 22:32 elf_i386.xsc -r--r--r-- 1 root wheel 6717 Jul 8 22:32 elf_i386.xsw -r--r--r-- 1 root wheel 4704 Jul 8 22:32 elf_i386.xu -r--r--r-- 1 root wheel 7178 Jul 8 22:32 elf_i386.xw -r--r--r-- 1 root wheel 7476 Jul 8 22:32 elf_i386_fbsd.x -r--r--r-- 1 root wheel 7259 Jul 8 22:32 elf_i386_fbsd.xbn -r--r--r-- 1 root wheel 7289 Jul 8 22:32 elf_i386_fbsd.xc -r--r--r-- 1 root wheel 7404 Jul 8 22:32 elf_i386_fbsd.xd -r--r--r-- 1 root wheel 7234 Jul 8 22:32 elf_i386_fbsd.xdc -r--r--r-- 1 root wheel 7224 Jul 8 22:32 elf_i386_fbsd.xdw -r--r--r-- 1 root wheel 7476 Jul 8 22:32 elf_i386_fbsd.xn -r--r--r-- 1 root wheel 4682 Jul 8 22:32 elf_i386_fbsd.xr -r--r--r-- 1 root wheel 6998 Jul 8 22:32 elf_i386_fbsd.xs -r--r--r-- 1 root wheel 6828 Jul 8 22:32 elf_i386_fbsd.xsc -r--r--r-- 1 root wheel 6818 Jul 8 22:32 elf_i386_fbsd.xsw -r--r--r-- 1 root wheel 4728 Jul 8 22:32 elf_i386_fbsd.xu -r--r--r-- 1 root wheel 7279 Jul 8 22:32 elf_i386_fbsd.xw -r--r--r-- 1 root wheel 838 Jul 8 22:32 i386bsd.x -r--r--r-- 1 root wheel 849 Jul 8 22:32 i386bsd.xbn -r--r--r-- 1 root wheel 843 Jul 8 22:32 i386bsd.xn -r--r--r-- 1 root wheel 642 Jul 8 22:32 i386bsd.xr -r--r--r-- 1 root wheel 682 Jul 8 22:32 i386bsd.xu Any pointers would be much appreciated. Alexander Kapshuk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NFSv4 ACL permissions setting
Wiadomość napisana przez Doug Sampson w dniu 31 sie 2012, o godz. 01:42: [..] group:DSP-production:rwxpDdaARWcCos:fd:allow - group:DSP-production:rwxpDdaARWcCos:fd:allow - This itself looks like a bug in setfacl(1). I'll look into it. However... [..] #!/bin/sh # run this script where you wish to effect the changes # reset perms to default find . -type d -print0 | xargs -0 setfacl -b * Why the asterisk? Also, using -m with NFSv4 ACLs is not a very good idea - it's supposed to work, but with NFSv4 ACLs the ordering does matter, and -m simply modifies the ACL entry in place, while the effect of the entry might depend e.g. on deny entries before it. Use -a instead. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading 9.1-BETA1 - 9.1-RC1
On 08/31/12 01:17, warchild wrote: Hi That is wrong, this worked for me on one of my servers since I did it straight away (as soon as I saw the release for rc1. FreeBSD warsol 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 that was beta1, and I used freebsd-update to upgrade it! Now, on another server i would like to do I have the same error as the OP. Go to: http://update3.freebsd.org/ Simple put, someone has deleted the whole BETA1 directory/brach!? WHY!? is there another way we can accept the key. or is that data needed.. Can we get the branch restored? It does work. Rebuilding world is so painful. thanks -- View this message in context: http://freebsd.1045724.n5.nabble.com/Upgrading-9-1-BETA1-9-1-RC1-tp5737452p5739453.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org There is a stupid way to upgrade FreeBSD: http://forums.freebsd.org/archive/index.php/t-1280.html % su # env UNAME_r=7.1-PRERELEASE freebsd-update upgrade -r 7.1 i use # env UNAME_r=8.2 freebsd-update upgrade -r 9.1-RC1 But it doesn't help me with tool [, so i can't update with csup. :( Greetings ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 support for RealTek NIC - re0 driver
On 08/29/12 18:14, d...@safeport.com wrote: This card is on a Dell Inspiron. It works perfectly on 8.x. Dmesg on 8.2 reports it as: re0: RealTek 8101E/8102E/8102EL/8103E PCIe 10/100baseTX pciconf: re0@pci0:4:0:0: class=0x02 card=0x04341028 chip=0x813610ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Realtek 10/100/1000 PCI-E NIC Family all in one NDIS Driver v5.728.0604.2009 06/04/2009 (Rtl8023)' class = network subclass = ethernet On 9.0 I got it to work once or twice out of a couple of dozen tries. 9.0 dmesg reports: re0: RealTek 8139C+/8169/8169S/8110S PCI ... The release docs imply the card is supported. I did not see a PR. Anyone else with similiar issues? Is the MAC changing? Give dmesg some message about it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 20:23, Alexander Kapshuk wrote: I've found the two directories below on my system. I don't remember creating them. So I'd like to be able to find out what package(s) has/have created them, if possible. # ls -ld /root/bin/ drwxr-xr-x 2 root wheel 512 Aug 29 22:52 /root/bin/ # ls -Rl /root/bin/ total 0 # ls -dl /usr/local/i386-portbld-freebsd9.0 drwxr-xr-x 4 root wheel 512 Jul 8 22:32 /usr/local/i386-portbld-freebsd9.0 # ls -Rl /usr/local/i386-portbld-freebsd9.0 total 8 Which program do you use to upgrade/ build ports? http://forums.freebsd.org/showthread.php?t=21088 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 22:26, lokada...@gmx.de wrote: Which program do you use to upgrade/ build ports? portupgrade. I had a look at the link you'd included in your previous email. I'm still unclear as to where the two directories came from. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 21:32, Alexander Kapshuk wrote: On 08/31/12 22:26, lokada...@gmx.de wrote: Which program do you use to upgrade/ build ports? portupgrade. I had a look at the link you'd included in your previous email. I'm still unclear as to where the two directories came from. Thanks. I think it comes from portupgrade. I use portmaster, but when i look at google, i found some thinks with portupgrade and portbld. I think, portbld is building for some ports, but on different places. Kick it (or rename it), look that all ok and make a upgrade, if available. If one port need it, it will create it. greetings ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 22:41, lokada...@gmx.de wrote: I think it comes from portupgrade. I use portmaster, but when i look at google, i found some thinks with portupgrade and portbld. I think, portbld is building for some ports, but on different places. Kick it (or rename it), look that all ok and make a upgrade, if available. If one port need it, it will create it. Understood. Thanks. Any ideas about /root/bin? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 21:43, Alexander Kapshuk wrote: On 08/31/12 22:41, lokada...@gmx.de wrote: I think it comes from portupgrade. I use portmaster, but when i look at google, i found some thinks with portupgrade and portbld. I think, portbld is building for some ports, but on different places. Kick it (or rename it), look that all ok and make a upgrade, if available. If one port need it, it will create it. Understood. Thanks. Any ideas about /root/bin? Not really. It looks like an error like my tool [. I get this after i would go to head (in february?) and get back this linking. No chance to get of it. Every new buildworld will look for it. :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/2012 11:10 PM, lokada...@gmx.de wrote: Not really. It looks like an error like my tool [. I get this after i would go to head (in february?) and get back this linking. No chance to get of it. Every new buildworld will look for it. :( No worries. I didn't think it was there when I first installed the system. So I thought I'd ask. /root/bin/ does seem to be defined in the $PATH environment variable for the root user account in both .cshrc and .profile. Thanks for your prompt response. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 support for RealTek NIC - re0 driver
On Fri, 31 Aug 2012, lokada...@gmx.de wrote: On 08/29/12 18:14, d...@safeport.com wrote: This card is on a Dell Inspiron. It works perfectly on 8.x. Dmesg on 8.2 reports it as: re0: RealTek 8101E/8102E/8102EL/8103E PCIe 10/100baseTX pciconf: re0@pci0:4:0:0: class=0x02 card=0x04341028 chip=0x813610ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Realtek 10/100/1000 PCI-E NIC Family all in one NDIS Driver v5.728.0604.2009 06/04/2009 (Rtl8023)' class = network subclass = ethernet On 9.0 I got it to work once or twice out of a couple of dozen tries. 9.0 dmesg reports: re0: RealTek 8139C+/8169/8169S/8110S PCI ... The release docs imply the card is supported. I did not see a PR. Anyone else with similiar issues? Is the MAC changing? Give dmesg some message about it? Not currently in the same city as my Dell. I installed 8.2 to make sure I did not have a hardware issue. I will [re]install 9.0 Sunday and report back. _ Douglas Denault http://www.safeport.com d...@safeport.com Voice: 301-217-9220 Fax: 301-217-9277 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Root password not working on console
I recently *accidentally* removed myself from the wheel group, so I was no longer able to use su to root. To fix it, I hooked up a monitor and keyboard to my FreeBSD 8.2 box so I could login as root, but it kept rejecting my password. I restarted the machine in single-user mode, did the following: mount -u / mount -a passwd exit So it booted back in to multi-user mode. Once again, I tried to login as root, but got the same Login incorrect message. Puzzled, I repeated the previous steps using the password pass this time. However, I went ahead and added my user account to the wheel group while in single-user mode. Once in multi-user mode again, I still got Login incorrect (specifically, pam_acct_mgmt(): authentication error) when logging in as root. I SSH'd to the machine as my regular user, typed su, and entered pass which worked just fine. So, I have absolutely no clue why I am unable to login to my machine, on the console, as root with pass, but it works when using su from a regular user account. I tried searching around but almost all of the hits are about resetting the root password in single-user mode. Does any one know what I'm doing incorrectly? Thanks for any help in advance, -Walt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Root password not working on console
On 08/31/2012 03:37 PM, Walt Elam wrote: I recently *accidentally* removed myself from the wheel group, so I was no longer able to use su to root. To fix it, I hooked up a monitor and keyboard to my FreeBSD 8.2 box so I could login as root, but it kept rejecting my password. I restarted the machine in single-user mode, did the following: mount -u / mount -a passwd exit So it booted back in to multi-user mode. Once again, I tried to login as root, but got the same Login incorrect message. Puzzled, I repeated the previous steps using the password pass this time. However, I went ahead and added my user account to the wheel group while in single-user mode. Once in multi-user mode again, I still got Login incorrect (specifically, pam_acct_mgmt(): authentication error) when logging in as root. I SSH'd to the machine as my regular user, typed su, and entered pass which worked just fine. So, I have absolutely no clue why I am unable to login to my machine, on the console, as root with pass, but it works when using su from a regular user account. I tried searching around but almost all of the hits are about resetting the root password in single-user mode. Does any one know what I'm doing incorrectly? Thanks for any help in advance, -Walt The only thing that comes to mind would be to check /etc/ttys and see if the console ttys are set to insecure, which would prevent root login. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Root password not working on console
Jeremy, Nailed it on the head. I had forgotten that a few weeks ago I was messing around with that file. I changed this line: ttyv0 /usr/libexec/getty Pc cons25 on insecure to this: ttyv0 /usr/libexec/getty Pc cons25 on secure And now I am able to login to root from the console. Thanks for the quick help! I should've remembered that. -Walt On Fri, Aug 31, 2012 at 6:51 PM, Jeremy Johnston jer...@stormy.smart-serv.net wrote: On 08/31/2012 03:37 PM, Walt Elam wrote: I recently *accidentally* removed myself from the wheel group, so I was no longer able to use su to root. To fix it, I hooked up a monitor and keyboard to my FreeBSD 8.2 box so I could login as root, but it kept rejecting my password. I restarted the machine in single-user mode, did the following: mount -u / mount -a passwd exit So it booted back in to multi-user mode. Once again, I tried to login as root, but got the same Login incorrect message. Puzzled, I repeated the previous steps using the password pass this time. However, I went ahead and added my user account to the wheel group while in single-user mode. Once in multi-user mode again, I still got Login incorrect (specifically, pam_acct_mgmt(): authentication error) when logging in as root. I SSH'd to the machine as my regular user, typed su, and entered pass which worked just fine. So, I have absolutely no clue why I am unable to login to my machine, on the console, as root with pass, but it works when using su from a regular user account. I tried searching around but almost all of the hits are about resetting the root password in single-user mode. Does any one know what I'm doing incorrectly? Thanks for any help in advance, -Walt The only thing that comes to mind would be to check /etc/ttys and see if the console ttys are set to insecure, which would prevent root login. __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
