5.2 /usr/libexec/ld-elf.so.1 upgrade problem in make installworld
Hello everyone, I have a problem during make installworld while upgrading from 5.1-p11 to 5.2-RELEASE. I cvsup'ed my source tree this morning, did make buildworld, make buildkernel and make installkernel, reboot, everything was fine. While running make installworld, I bump into an error in libexec/rtld-elf, output is below. I can see this is to do with the move from /usr/libexec to /libexec, but I can't work out how to get round it. The permission denied must be coming from a schg flag... Any help would be appreciated. I apologize if this question has already come up but googling hasn't revealed anything. Thanks in advance! Jonathan Output from make installworld: [...] === libexec/rtld-elf chflags noschg /usr/libexec/ld-elf.so.1 install -s -o root -g wheel -m 555 -fschg -C -b ld-elf.so.1 /libexec install -o root -g wheel -m 444 rtld.1.gz /usr/share/man/man1 /usr/share/man/man1/ld-elf.so.1.1.gz - /usr/share/man/man1/rtld.1.gz /usr/share/man/man1/ld.so.1.gz - /usr/share/man/man1/rtld.1.gz /usr/libexec/ld-elf.so.1 - /libexec/ld-elf.so.1 ln: /usr/libexec/ld-elf.so.1: Operation not permitted *** Error code 1 Stop in /usr/src/libexec/rtld-elf. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bluetooth support
Anyone happen to know if bluetooth is supported in BSD? I was thinking of getting a little USB Bluetooth adapter:) I have just looked into this myself, so here is a brief summary of my findings. Bluetooth is supported via the netgraph framework, though only in 5.1 and 5-CURRENT. The USB adapters supported seem quite varied, from what I've read, although 5.1's hardware notes only mentions a few : http://www.freebsd.org/releases/5.1R/hardware-i386.html#BLUETOOTH According to a message ( http://unix.derkeiler.com/Mailing-Lists/FreeBSD/net/2003-08/0130.html ) from Maksim Yevmenkin, the guy who wrote the bluetooth stack, a lot more adapters will work, based on their Linux support, see the link in the message. Finally, here are some instructions on setting up bluetooth on FreeBSD : http://www.oook.cz/bsd/bluetooth.html Good luck, Jonathan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interest in diskless booting?
I was at a local installfext yesterday (http://installfest.auug.org.au/), and a number of people were interested in doing diskless booting, either for reasons of economy or reliability. I'm currently about to finish the manuscript of the fourth edition of The Complete FreeBSD, and I was wondering if there was enough interest in this topic for me to include it in the book. If *you* are interested, please let me know. I'll make a decision depending on the amount of feedback I get. This is another definite YES ! :) Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NAT and Firewall Configuration ?
I am in the process of configuring NAT and a firewall on FreeBSD 4.7 Stable. I have configured the external interface with 2 class C addresses 192.x.x.1 and 192.x.x.2. and the internal interface with 192.168.x.1 ( gateway ) I have also configured natd_flags=-redirect_address 192.168.x.3 192.x.x.2 which if I'm correct will redirect all traffic destined for 192.x.x.2 to 192.168.x.3 ? That's right in the idea. To be finicky, I'd say that natd doesn't *redirect* traffic, it just *rewrites* packet headers, so they can be redirected. My question is have I done everything correct so far and what rule would I use for my firewall so that natd will work the way I want it ? You need to add the following rule as the first rule in your firewall (or pretty much so): add 00100 divert natd ip from any to any via rl0 (considering rl0 is the interface connected to the exterior) This passes all packets coming in or going out through rl0 to natd, who will decide whether they need aliasing or not, and do so. It then passes them back into the firewall list, and the following rule number. See man ipfw. SNIP firewall rules My rc.conf is as follows: SNIP ifconfig_rl0=inet 192.x.x.1 netmask 255.255.255.0 ifconfig_rl0_alias0=inet 192.x.x.2 netmask 255.255.255.255 ifconfig_rl1=inet 192.168.x.1 netmask 255.255.255.0 SNIP natd_enable=YES natd_interface=rl0 natd_flags=-redirect_address 192.168.x.3 192.x.x.x2 SNIP The line 'natd_interface=rl0' tells natd to do it's aliasing to and from the IP address used by rl0. This may or may not be what you want, since you have two IPs on this interface. I expect that natd gets the primary IP for the interface rather than the alias. In this case your setup would send all traffic for 192.x.x.2 to 192.168.x.3 and share the connection to all other hosts on the 192.168.x.x network via 192.x.x.1. ## Required for ipfw support firewall_enable=YES #firewall_script=/etc/rc.firewall #firewall_type=OPEN firewall_type=/etc/ipfw.rules firewall_quiet=YES firewall_logging_enable=YES Er, I know this isn't your question, but shouldn't 'firewall_type=/etc/ipfw.rules' be 'firewall_script=/etc/ipfw.rules'? SNIP kernel options Look good to me. Hope this helps, Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: IPFW + NATD with redirect_port
I want to redirect incoming ssh packet to another box internally. I have
got the following as my /etc/natd.conf
dynamic yes
log_denied yes
use_sockets yes
same_ports yes
unregistered_only
redirect_port tcp 192.168.0.200:22 4455
When I try to ssh to port 4455 I get nothing - I have ipfw running - do I
need any specific rules to get this working. I have tried ${fwcmd} add
pass log tcp from any to any 22 in via ${oif} setup but it doesn't seem
to
work.
Gordon,
Your natd setup looks OK to me. I'm wondering whether your ipfw isn't
blocking connection attempts. Do you have a rule that allows tcp connections
to port 4455? And another to allow connections from NAT box to ssh box on
port 22?
And when you try to connect to port 4455 on your NAT box, you do it from the
exterior, right?
Hope this helps,
Jonathan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: routing problem
today i tried to setup 4.7 gateway. It hastwo NICs (rl0 and rl1) on different subnets (rl0 = 192.168.0.66, rl1 = 192.168.1.2). The rl0 is connected to a cable-modem and gets an other IP (213.209.66.214) after booting. After playing with routes, i can ping outside, can ping rl0 and rl1 and 192.168.1.18 (a windows-box). The 192.168.1.18 can ping the 192.168.1.2 and 213.209.66.214 (the other NIC in the server), but not any outside IP (wich should be routed over 213.209.66.214 i think) gateway_enable=YES in /etc/rc.config and for testing router_enable=YES and natd_enable=YES Thomas, The problem is to do with setting up natd. You don't need router_enable=YES. Firstly, natd listens on a divert socket for packets to 'translate' from the internet to your LAN. Therefore, you need to make sure that the IP packets going to and coming from your modem get sent to natd. The way to do this is using ipfw, the kernel firewall. If you're not already using it (which I would recommend doing anyhow), you'll need to recompile your kernel with options IPFIREWALL and options IPDIVERT (checkout man ipfw). Then simply do : ipfw add divert natd ip from any to any via rl0 Assuming rl0 is the interface that has your 213.209.66.214 address, this will pass all ip packets through natd, which will rewrite them transparently. Secondly, you need to tell natd which interface (IP address actually) to operate on. To do this just add 'natd_interface=rl0' to you /etc/rc.conf , if rl0 is your internet interface. If you have a dynamic IP address, you may want to add 'natd_flags=-dynamic' aswell. See man natd for details. Then it should all work fine! A couple of points to check for : make sure you add a default route for your ISP's IP (the one the modem connects to) and be careful the connection with the public IP address is indeed on rl0 (if you use PPPOE for example, another interface is used...) Hope this helps, Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
