Did Freebsd 7.4 supports HMAC-SHA-256-128
Hi, Following interoperability is failing:- IPv6 Ready Logo, Phase-2 Interoperability Test Scenario Ipsec -Test cases 5.2.12 is failing with FreeBSD. Observation:-Freebsd 7.4 uses HMAC-SHA-256-96 Algorithm and SGW1 are using HMAC-SHA-256-128 Algorithm due to this interoperability is failing. Did Freebsd 7.4 supports HMAC-SHA-256-128 ? Purpose: Interoperability:-Tunnel mode between two SGWs, ESP=3DES-CBC HMAC-SHA-256 Setup:- H1---net0---SGW1---net1--Router---net2---SGW2(freebsd)---net3---H2 Net0 (2001::/64) Net1 (2004::/64) Net2 (2002::/64) Net3 (2003::/64) Please find the attached zip folder. Regards, Rohit ___ 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
PHP 5.3 + ZendGuard Support
Hello, I found a couple of threads on the web about this but no solution. Am I the only one of few people who needs to run PHP scripts on FreeBSD machine that were encoded with Zend Guard technology? trying to run linux version of PHP, which has a ZendGuard loader made for it, or worse linux version of Apache which loads linux PHP module on FreeBSD is the last thing I want to do. It would be easier to switch to linux altogether, which I'm trying to avoid at all costs. Has anyone found a solution less of switching to linux for the purpose described above? Is there anything FreeBSD community can do to influence Zend Guard developers to release Zend Guard loader for FreeBSD? The company I work for has already at least a few clients who are forcing me to switch them to Linux due to lack of Zend Guard support under FreeBSD. Any thoughts, comments, would be appreciated. Thank you! Simon ___ 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: PHP 5.3 + ZendGuard Support
Am I the only one of few people who needs to run PHP scripts on FreeBSD machine that were encoded with Zend Guard technology? trying to run linux version of probably not, no idea EXACTLY what zend guard is but i've seen other such standards of encoding==obfuscating PHP sources. I don't provide services like hosting for anyone, while i do support businesses and run their servers, and if anyone offer his/her software in such form i (which happened) i just say NO at least, preferably kicking ass. Don't believe in i use it because i don't my code i worked hard on it to be copied by others which actually mean I am simple thief and i copied almost everything and not even modified it much as i don't understand it at all, so i use encoder/obfuscator to hide it. Allowing any software without proper source and preferably documentation in any business always ends badly. So really - if you provide hosting service just run linux for that case, on VM, and probably charge a bit more for that, or leave such case to competition to handle. in every other case just say no. ___ 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: FW: 5.2.11. Tunnel Mode Fragmentation.zip
On 16/05/2012 07:53, Agarwal Rohit-B39617 wrote: Trying to execute IPv6 Ready Logo Phase-2 Interoperability Test Scenario Ipsec test cases 5.2.11 Issue:- FreeBSD 7.4 not sending icmpv6 too big message Please check the updated setup pcap. Your attachments aren't making it through to the list -- the vast majority of non-text attachments are stripped by mailman. Best thing to do is stick your debug output on a site like pastebin and post a link. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: file permission template
I need a sort of file permission template. Under some particular directory (like ~/secret), I need all those files (including newly creating one) mode 700. Is there any template-trick? Or chmod -R 700 every time? umask when creating files there. ___ 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: file permission template
Thanks. But I need specific directory only. umask way seems to set mode not only under ~/secret but other directories like ~/public. Is there any elegant way? elegant way is just to chmod 700 ~/secret and do not do anything more, as files under ~/secret are already inaccessible too for others and group. ___ 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: Building FreeBSD to install or update in two DESTDIRs
Better to make buildkernel and make installkernel as two separate steps, rather than make kernel? Yes. You only need to make buildkernel once, then make installkernel for both $DESTDIRs. The idea was to make buildkernel once and make buildworld once and install to two different DESTDIRs. After rebooting single-user, do mergemaster -p, then mergemaster -p -D /mnt, and then make installworld and immediately following that, make installworld DESTDIR=/mnt ? Refer to the commend header in /usr/src/Makefile for the correct procedure. Without having it tested, the following commands in SUM (after you have successfully installed the new kernels) should work as intended: # merpemaster -p # make installworld # make delete-old # mergemaster # merpemaster -p -D /mnt # make installworld DESTDIR=/mnt # make delete-old DESTDIR=/mnt # mergemaster -D /mnt # reboot Also see the comment regarding make delete-old-libs to be applied after reboot correspondingly. I assume your merpemaster is a typo for mergemaster? I would have done each step for main installation and then for USB stick (DESTDIR=/mnt) before going to the next step, or maybe that doesn't really matter? I think the second mergemaster was supposed to be done before make delete-old, or maybe that doesn't really matter either? I installed to USB stick only after fully upgrading on main installation, finally copied /boot/kernel directory, and that USB stick is now bootable. So now I know how to make a USB stick bootable with GPT. Maybe kernel modules for GPT have been missing? Check /etc/src.conf for any strange settings, see man 3 src.conf for details. You can use this file to customize and tweak your builds. I think I must have all GPT modules there; I have no trouble accessing hard-disk partitions, and USB stick when partitioned GPT. I might want to prevent building ulpt module because of hplip and HP 1212nf MFP printer idiosyncrasies, though that may or may not make any difference. I could also prevent building other modules that would not be used. Tom ___ 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
disable console messages
hi all. how I can disbale console messages and clear screen on boot? 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
IPv6 flow id hash calculation
Folks, This question is related to the hash calculation done as part of selecting the transmit queue for IPv6 traffic. I observed that no matter how many queues you use in the driver, the tx traffic is always coming on queue 0. Did anybody else observed this behaviour? and is that how it is in freebsd? Note: IPv4 traffic is coming on all the tx queues. Please clarify. /Venkat ___ 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
(no subject)
I bought server HP ProLiant BL460c G7. I couldn't find Ethernet driver for the FreeBSD. Does anyone know where can I get driver for my OpenBSD(or freeBSD) server ? Best regards Shahin Hasanov ___ 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: (no subject)
On Wed, May 16, 2012 at 1:56 PM, hasanhasanli Hasan hasanhasa...@mail.ruwrote: I bought server HP ProLiant BL460c G7. I couldn't find Ethernet driver for the FreeBSD. Does anyone know where can I get driver for my OpenBSD(or freeBSD) server ? Best regards Shahin Hasanov Which version of FreeBSD did you install? What is the output of the command `ifconfig` ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email. ___ 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
Ethernet driver HP ProLiant BL460c G7
I bought server HP ProLiant BL460c G7. I couldn't find Ethernet driver for the FreeBSD. Does anyone know where can I get driver for my OpenBSD(or freeBSD) server ? Best regards Shahin Hasanov ___ 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: Ethernet driver HP ProLiant BL460c G7
On Wed, 16 May 2012 15:29:05 +0400, hasanhasanli Hasan wrote: I bought server HP ProLiant BL460c G7. I couldn't find Ethernet driver for the FreeBSD. Does anyone know where can I get driver for my OpenBSD(or freeBSD) server ? You shouldn't need to get a driver because it's the operating system's job to provide the drivers. FreeBSD comes with lots of drivers for Ethernet cards. After booting the machine with a FreeBSD system (or even after installing it), try # ifconfig -a and look for which Ethernet interfaces have been success- fully created. Missing something? Compare to the hardware specification which lists the kinds of installed network hardware (should be in your documentation provided with the server). Check those lists: http://www.freebsd.org/releases/8.0R/hardware.html#ETHERNET http://www.freebsd.org/relnotes/CURRENT/hardware/support.html#ETHERNET You can always use man driver to find out more about drivers on an installed system, or you can use the hyperlinks in that lists to access the online documentation of the drivers. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: disable console messages
On Wed, 16 May 2012 00:27:07 -0700, mahdieh salamat wrote: hi all. how I can disbale console messages and clear screen on boot? Thanks The console messages can be suppressed by commenting out the line *.err;kern.warning;auth.notice;mail.crit/dev/console in /etc/syslog.conf; if you want the messages redirected to a file (instead of the screen), just provide a different target, such as *.err;kern.*;auth.notice;mail.crit;console.info/var/log/console.log Make sure /var/log/console.log does exist: run # touch /var/log/console.log There are more useful examples in that file. See man 5 syslog.conf for details. To also silence the kernel, you could add boot_mute=YES or (and?) consolse=nullconsole to /boot/loader.conf. See man 8 loader and man 5 loader.conf and less /boot/defaults/loader.conf for details. Finally: Add the command clear or /usr/bin/tput clear at the end of the /etc/rc script (not very clean, but works). A quick web search brings up some inspiration: http://lists.freebsd.org/pipermail/freebsd-questions/2003-October/022911.html http://forums.freebsd.org/showthread.php?t=10341 http://forums.freebsd.org/showthread.php?p=58256#post58256 You'll find a suggestion there on how to avoid fiddling with the /etc/rc boot script (which should stay untouched due to many reasons). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Ethernet driver HP ProLiant BL460c G7
On 05/16/2012 02:38 PM, Polytropon wrote: HP ProLiant BL460c G7 Maybe this helps http://forums.freebsd.org/showthread.php?t=24769 Disclaimer: http://www.ose.nl/email ___ 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
(mutt +) msmtp problem?
I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes smoothly, but every once in a while I lose network connectivity when sending email (I don't recall whether there is a correlation between this problem and my trying to send not-so-big but yet around 1mb files). Basically, what happens in trying to send an email is: May 16 10:01:17 wpa_supplicant[662]: CTRL-EVENT-DISCONNECTED bssid=**:**:**:**:**:** reason=0 ... May 16 10:02:27 wpa_supplicant[662]: CTRL-EVENT-CONNECTED - Connection to **:**:**:**:**:** completed (reauth) [id=0 id_str=] ... Then I try again, and the same thing happens. All msmtp's log shows is: errormsg='cannot write to TLS connection: Pipe Broken' exitcode=EX_IOERR Any ideas? Best, Ramiro ___ 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: (mutt +) msmtp problem?
I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes smoothly, but every once in a while I lose network connectivity when sending email (I don't recall whether there is a correlation between this problem and my trying to send not-so-big but yet around 1mb files). Basically, what happens in trying to send an email is: May 16 10:01:17 wpa_supplicant[662]: CTRL-EVENT-DISCONNECTED bssid=**:**:**:**:**:** reason=0 ... May 16 10:02:27 wpa_supplicant[662]: CTRL-EVENT-CONNECTED - Connection to **:**:**:**:**:** completed (reauth) [id=0 id_str=] ... Then I try again, and the same thing happens. All msmtp's log shows is: errormsg='cannot write to TLS connection: Pipe Broken' exitcode=EX_IOERR Any ideas? Best, Ramiro Based on above, mutt and msmpt *appear* to be fine, but this seems to be a problem with the wireless driver, card, or router - you are being disconnected from the network, which in turn is causing the 'broken pipe'. You could feasibly work around it by using a wired connection, or take a look at what is going on with your wireless. -- Regards, James Edwards ___ 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: Building FreeBSD to install or update in two DESTDIRs
On Wed, 16 May 2012 03:13:10 -0400, Thomas Mueller wrote: Better to make buildkernel and make installkernel as two separate steps, rather than make kernel? Yes. You only need to make buildkernel once, then make installkernel for both $DESTDIRs. The idea was to make buildkernel once and make buildworld once and install to two different DESTDIRs. I'm not sure I understand: The two install* targets (make installkernel and make installworld) are only able to install to _one_ location, which is the _default_ location *or* the location pointed to by DESTDIR. It is not possible to perform _one_ install step which will cause results in _two_ locations (without any means of hidden duplication, e. g. by using a mirroring technique). After rebooting single-user, do mergemaster -p, then mergemaster -p -D /mnt, and then make installworld and immediately following that, make installworld DESTDIR=/mnt ? Refer to the commend header in /usr/src/Makefile for the correct procedure. Without having it tested, the following commands in SUM (after you have successfully installed the new kernels) should work as intended: # merpemaster -p # make installworld # make delete-old # mergemaster # merpemaster -p -D /mnt # make installworld DESTDIR=/mnt # make delete-old DESTDIR=/mnt # mergemaster -D /mnt # reboot Also see the comment regarding make delete-old-libs to be applied after reboot correspondingly. I assume your merpemaster is a typo for mergemaster? Ah yes, the well-known P next to G typing error, procreated by copy paste. :-) I would have done each step for main installation and then for USB stick (DESTDIR=/mnt) before going to the next step, or maybe that doesn't really matter? The order of targets does not matter. However, the order of steps _per_ target does matter (e. g. make installkernel first, _then_ installworld - it matters as soon as you boot). I think the second mergemaster was supposed to be done before make delete-old, or maybe that doesn't really matter either? I'm refering to the instructions presented in /usr/src/Makefile: # For individuals wanting to upgrade their sources (even if only a # delta of a few days): # # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) That means: mergemaster -p before installing world, mergemaster (maybe with additional options) after installing world. I think the delete-old and delete-old-libs steps can also be performed at the end of the whole process. But doing what the instructions say has always been the most comfortable way of avoiding trouble. :-) I installed to USB stick only after fully upgrading on main installation, finally copied /boot/kernel directory, and that USB stick is now bootable. So now I know how to make a USB stick bootable with GPT. Maybe kernel modules for GPT have been missing? Check /etc/src.conf for any strange settings, see man 3 src.conf for details. You can use this file to customize and tweak your builds. I think I must have all GPT modules there; I have no trouble accessing hard-disk partitions, and USB stick when partitioned GPT. I might want to prevent building ulpt module because of hplip and HP 1212nf MFP printer idiosyncrasies, though that may or may not make any difference. I could also prevent building other modules that would not be used. There are several means you can use for this: a custom kernel configuration, settings in /etc/src.conf, settings in /boot/loader.conf. It should not _require_ you to deal with a custom kernel if you want to avoid that. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: (mutt +) msmtp problem?
On 16/05/2012 11:04, James Edwards wrote: I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes smoothly, but every once in a while I lose network connectivity when sending email (I don't recall whether there is a correlation between this problem and my trying to send not-so-big but yet around 1mb files). Basically, what happens in trying to send an email is: May 16 10:01:17 wpa_supplicant[662]: CTRL-EVENT-DISCONNECTED bssid=**:**:**:**:**:** reason=0 ... May 16 10:02:27 wpa_supplicant[662]: CTRL-EVENT-CONNECTED - Connection to **:**:**:**:**:** completed (reauth) [id=0 id_str=] ... Then I try again, and the same thing happens. All msmtp's log shows is: errormsg='cannot write to TLS connection: Pipe Broken' exitcode=EX_IOERR Any ideas? Best, Ramiro Based on above, mutt and msmpt *appear* to be fine, but this seems to be a problem with the wireless driver, card, or router - you are being disconnected from the network, which in turn is causing the 'broken pipe'. Indeed, mutt + msmtp appear to be fine... My bad for not being clearer... However, there is a correlation that goes beyond credible coincidence: the disconnection happens when (and, as far as I can recall, only when) I use mutt + msmtp to send sizeable files. In particular, no disconnection occurs when I'm not using mutt + msmtp, or when I use mutt + msmtp but I send emails without sizeable attachments. Also, the disconnection happens within seconds of attempting to send the sizeable emails. I guess it is a problem with the wireless card, but it seems to be somehow closely linked to the event of trying to send sizeable emails using mutt + msmtp (when I use thunderbird to send the files, everything works as expected, no disconnection). You could feasibly work around it by using a wired connection, or take a look at what is going on with your wireless. My work around, for now, is to use thunderbird for sending large emails, so there's no hurry. But I'm a bit puzzled about what's happening. ___ 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 8.3 support for LSI SAS 2208 based controllers/Dell PERC 710
Hi All, I have a Dell R620 which utilizes the PERC H710 controller based on the LSI SAS 2208 chip. According to the hardware notes for 8.3-RELEASE, this chip is supported by the mps driver. Unfortunately, when I attempt to install 8.3-RELEASE via DVD, it does not recognize the controller and no disks are found and the install exits. The manpage indicates the driver was introduced in 9.0-RELEASE suggesting it was backported to 8.3? Would this be correct? A search for related bug reports did not return anything useful. Would anyone else out there have any experience with installing FreeBSD on the R620 and be able to provide any tips for troubleshooting? -- Take care Rick Miller ___ 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: Running OS tftp vs. pxeboot tftp
Thanks for your feedback. I agree that separating the networks and isolating the build network thus eliminating the need for VLAN tagging is the ideal scenario. Unfortunately, influencing those changes are beyond my sphere of influence in this particular case. At the end of the day, our solution was to replace pxeboot.bs with Grub2pxe. I have a blog post detailing the scenario at https://hostileadmin.wordpress.com/2012/05/04/pxe-booting-into-a-freebsd-installation/ On Wed, Mar 14, 2012 at 9:30 AM, Erik Nørgaard norga...@locolomo.org wrote: Hi On 14/03/2012 11:44, Rick Miller wrote: I thought I would follow up on this as a couple individuals expressed an interest in it... We have isolated the configuration in which this occurs under. It occurs during the execution of pxeboot.bs on brocade switches with vlan tagging enabled. You might save yourself time and money buying a cheap switch and doing your jumpstart install on a separate closed network completely isolated from the rest of your networks, without VLAN tagging required. If you have lots of nodes to install it makes sense to maintain your own repository of freebsd and packages, and it's good practice to keep your preproduction systems separate from production, so there is no need for network access. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ 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 -- Take care Rick Miller ___ 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: FreeBSD 8.3 support for LSI SAS 2208 based controllers/Dell PERC 710
On Wed, 16 May 2012 13:04:25 -0500, Rick Miller vmil...@hostileadmin.com wrote: Would anyone else out there have any experience with installing FreeBSD on the R620 and be able to provide any tips for troubleshooting? Does 9.0 install on that hardware? It's possible your controller chip has a slightly different revision that isn't listed in the driver. I'd expect it to not work on 9.0 either in that case. ___ 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
Newsyslog | Cronjob faulty?
At midnight (00.00) I run this cronjob from my crontab: Crontab: 00 * * * * rootnewsyslog For some reason this goes wrong; (if I run 'newsyslog' on any other time, there is no error message). bzip2: Can't open input file /var/log/maillog.0: No such file or directory. newsyslog: `bzip2 -f /var/log/maillog.0' terminated with a non-zero status (1) /var/log: -rw-r- 1 rootwheel 63162 May 16 21:20 maillog -rw-r- 1 rootwheel 109 May 16 00:00 maillog.0.bz2 -rw-r- 1 rootwheel 73674 May 16 00:00 maillog.1 -rw-r- 1 rootwheel 111 May 15 00:00 maillog.2.bz2 -rw-r- 1 rootwheel 73050 May 15 00:00 maillog.3 -rw-r- 1 rootwheel 109 May 14 00:00 maillog.4.bz2 -rw-r- 1 rootwheel184042 May 14 00:00 maillog.5 Can somebody tell me what goes wrong here? On my other FreeBSD server the same cronjob goes ok... thanks, Jos Chrispijn ___ 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
problems with networking and route command
I am having a problem getting users who get their dhcp from my system to be able to connect to the internet. On one network interface my server can connect to the internet no problem - that's device vr0. On another, rl0 - I have a connection to the local network - no problem connecting to local machines from the server. The problem is that the local machines cannot access the internet through the FreeBSD server. Here is the output of ifconfig; fwe0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 02:11:d8:b3:0e:43 ch 1 dma -1 vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 64.40.244.36 netmask 0xfff0 broadcast 64.40.244.47 inet6 fe80::16d6:4dff:fe47:88ae%vr0 prefixlen 64 scopeid 0x2 ether 14:d6:4d:47:88:ae media: Ethernet autoselect (100baseTX full-duplex) status: active rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::211:95ff:fe66:7162%rl0 prefixlen 64 scopeid 0x3 ether 00:11:95:66:71:62 media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 And here is the ipv4 part output of netstat -nr # netstat -nr Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default64.40.244.33 UGSc8 2365vr0 64.40.244.32/28link#2 UC 10vr0 64.40.244.33 00:0c:42:07:26:35 UHLW90vr0 1187 127.0.0.1 127.0.0.1 UH 761626lo0 192.168.1 link#3 UC 40rl0 192.168.1.16 link#3 UHLW2 2032rl0 192.168.1.40 00:1b:78:e6:c3:cc UHLW0 31rl0 1189 192.168.1.101 00:07:e9:b9:50:98 UHLW412526rl0 1193 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 3 330rl0 It is machines that connect and receive via DHCP 192.168.1.2 and above that can't connect to the internet though the server. I don't know a whole lot about route - I have been attempting a variation of route commands without success. If anyone by looking at my information can suggest a route command, or suggest a way to dig for more information on this it would be greatly appreciated. lot about this ___ 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: problems with networking and route command
Hi-- On May 16, 2012, at 1:08 PM, David Banning wrote: [ ... ] It is machines that connect and receive via DHCP 192.168.1.2 and above that can't connect to the internet though the server. I don't know a whole lot about route - I have been attempting a variation of route commands without success. You need to implement NAT on this box, since 192.168.0.0/16 is an RFC-1918 unrouteable private network range. Regards, -- -Chuck ___ 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: AFS install
On Tue, May 15, 2012 at 12:51:04AM -0400, Benjamin Kaduk wrote: Hello Ben, Thank you for your response. I cleaned and then copied the 82 file to 83 and then edited it to replace all 82-s with 83 or added it where there seemed to be a list of versions. It got a lot further, but now dies not finding another file. ../rpc/types.h:77:27: error: rpc/netconfig.h: No such file or directory I will send along another message with the build script attached. Hi Jerry, On Mon, 14 May 2012, Jerry McAllister wrote: Hi, I installed AMD64 FreeBSD 8.3 on a new machine a couple of days ago. It seems fine so far. This afternoon I tried to install OpenAFS 1.6.0 on it from /usr/ports/net/openafs The configure ran happily and I didn't notice any errors. But, the make died soon after starting with the following complaints. make: don't know how to make ./param.amd64_fbsd_83.h. stop *** Error code 2 Stop in /usr/ports/net/openafs/work/openafs-1.6.0. ** Error code 1 I presume that means that it does not know about FreeBSD 8.3 yet. That's right; the OpenAFS build system has lots of history behind it, which means that it is not particularly elegant at handling this sort of thing. A lot of history. We have used it at MSU for a long time. It was never my project to build or maintain, but I used it a lot. I rummaged around in the README it left in the ../work directory and saw a bunch of AMD64 versions up to 8.1 (and even 9.0) but not 8.2 or 8.3. I noticed in the Makefile where it says: IGNORE= Supports FreeBSD 8.0 and later I am not sure how that plays in it. I am definitely not a make hacker. Anyway, is there a good tinker to get past this or do I have to wait until something gets updated in the port? Or, did I just do something stupid? No fault on your end; I need to push in updates for 8.3 and 10.0 support but have been busy with schoolwork. I can sure relate to that. For now, if you're up for a little bit of tinkering, you could go in to /usr/ports/net/openafs and 'make clean make extract', then: cd work/openafs-1.6.0/src/config cp param.amd64_fbsd_82.h param.amd64_fbsd_83.h and continue with the usual make install, etc., in /usr/ports/net/openafs/. If that still does not compile/run, please send me the build log (or dmesg -a output if a runtime failure) and I will look at it. Thanks for the report, and sorry to have been so slow at catching up to 8.3/10.0. -Ben Kaduk Thanks for your help, jerry ___ 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: Building FreeBSD to install or update in two DESTDIRs
The idea was to make buildkernel once and make buildworld once and install to two different DESTDIRs. I'm not sure I understand: The two install* targets (make installkernel and make installworld) are only able to install to _one_ location, which is the _default_ location *or* the location pointed to by DESTDIR. It is not possible to perform _one_ install step which will cause results in _two_ locations (without any means of hidden duplication, e. g. by using a mirroring technique). The idea was to make buildkernel once and make buildworld once, but make installkernel and make installworld would each have to be done once for each DESTDIR, meaning twice each. Building takes much more computer resources than installing, so I try to avoid building the same thing twice. I'm refering to the instructions presented in /usr/src/Makefile: # For individuals wanting to upgrade their sources (even if only a # delta of a few days): # # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) I checked /usr/src/UPDATING, and the sequence was ... reboot in single user mode mergemaster -p make installworld mergemaster -i (one may wish also -U) make delete-old reboot I checked /usr/src/Makefile , and found you quoted correctly, see 'make delete-old' and the second 'mergemaster' are transposed relative to what I saw in /usr/src/UPDATING Sort of confusing; make either way works? Subsequently I would also want to build for i386, but this would be after the amd64 build and installation/update. It would be nice if bsdinstall had an option for update as well as fresh install. For i386, I would follow advice on http://wiki.freebsd.org/Wine but would want a full installation capable of running independently of amd64, would need the kernel, would install on 16 GB USB stick which could be mounted on /compat/i386. I would want to use hard-drive PORTSDIR, would need to so adjust /etc/make.conf . I don't really want to think of building big ports on a USB stick, especially on the older computer with 256 MB RAM and USB 1.1 on motherboard. Tom ___ 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: Building FreeBSD to install or update in two DESTDIRs
On Wed, 16 May 2012 18:46:28 -0400, Thomas Mueller wrote: The idea was to make buildkernel once and make buildworld once and install to two different DESTDIRs. I'm not sure I understand: The two install* targets (make installkernel and make installworld) are only able to install to _one_ location, which is the _default_ location *or* the location pointed to by DESTDIR. It is not possible to perform _one_ install step which will cause results in _two_ locations (without any means of hidden duplication, e. g. by using a mirroring technique). The idea was to make buildkernel once and make buildworld once, but make installkernel and make installworld would each have to be done once for each DESTDIR, meaning twice each. Building takes much more computer resources than installing, so I try to avoid building the same thing twice. Yes, _that_ is the correct approach. In case you need to do more than one additional installation, you should consider creating a tar archive of the fully installed system and then use tar --unlink to the mounted target. If you need to create many bootable systems from scratch, a script performing the disklabel, newfs, mount and tar steps should be easy to write. I'm refering to the instructions presented in /usr/src/Makefile: # For individuals wanting to upgrade their sources (even if only a # delta of a few days): # # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) I checked /usr/src/UPDATING, and the sequence was ... reboot in single user mode mergemaster -p make installworld mergemaster -i (one may wish also -U) make delete-old reboot I checked /usr/src/Makefile , and found you quoted correctly, see 'make delete-old' and the second 'mergemaster' are transposed relative to what I saw in /usr/src/UPDATING Sort of confusing; make either way works? It should not be much difference if you consider what the steps in permutation do: mergemaster modifies files, make delete-old removes stuff that isn't needed anymore. Both steps don't seem to affect each other. a + b = b + a. :-) Subsequently I would also want to build for i386, but this would be after the amd64 build and installation/update. In case you're creating different TARGET= architectures, the fun doubles. :-) It would be nice if bsdinstall had an option for update as well as fresh install. This step can easily be performed manually using freebsd-update right after installation. If you understand update == overwrite, just don't format the partitions that are already present on the target media. For i386, I would follow advice on http://wiki.freebsd.org/Wine but would want a full installation capable of running independently of amd64, would need the kernel, would install on 16 GB USB stick which could be mounted on /compat/i386. I would want to use hard-drive PORTSDIR, would need to so adjust /etc/make.conf . I don't really want to think of building big ports on a USB stick, especially on the older computer with 256 MB RAM and USB 1.1 on motherboard. Also note that USB sticks are not real R/W media, they suffer more from using than hard disks do, and they're slower of course. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: (mutt +) msmtp problem?
On 16/05/2012 11:04, James Edwards wrote: I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes smoothly, but every once in a while I lose network connectivity when sending email (I don't recall whether there is a correlation between this problem and my trying to send not-so-big but yet around 1mb files). Basically, what happens in trying to send an email is: May 16 10:01:17 wpa_supplicant[662]: CTRL-EVENT-DISCONNECTED bssid=**:**:**:**:**:** reason=0 ... May 16 10:02:27 wpa_supplicant[662]: CTRL-EVENT-CONNECTED - Connection to **:**:**:**:**:** completed (reauth) [id=0 id_str=] ... Then I try again, and the same thing happens. All msmtp's log shows is: errormsg='cannot write to TLS connection: Pipe Broken' exitcode=EX_IOERR Any ideas? Best, Ramiro Based on above, mutt and msmpt *appear* to be fine, but this seems to be a problem with the wireless driver, card, or router - you are being disconnected from the network, which in turn is causing the 'broken pipe'. Indeed, mutt + msmtp appear to be fine... My bad for not being clearer... However, there is a correlation that goes beyond credible coincidence: the disconnection happens when (and, as far as I can recall, only when) I use mutt + msmtp to send sizeable files. In particular, no disconnection occurs when I'm not using mutt + msmtp, or when I use mutt + msmtp but I send emails without sizeable attachments. Also, the disconnection happens within seconds of attempting to send the sizeable emails. I guess it is a problem with the wireless card, but it seems to be somehow closely linked to the event of trying to send sizeable emails using mutt + msmtp (when I use thunderbird to send the files, everything works as expected, no disconnection). You could feasibly work around it by using a wired connection, or take a look at what is going on with your wireless. My work around, for now, is to use thunderbird for sending large emails, so there's no hurry. But I'm a bit puzzled about what's happening. ___ 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
VPN client for MSCHAP
Hello list, I am having a horrible time trying to connect to a PPTP VPN with MSCHAP and MSCHAPv2 and MPPE. I have tried pptpclient and mpd5 and both fail on many counts. I assume there is no gui client at this time, but can I get some sample config file for ANY vpn client on FreeBSD... I need user/pass auth with MPPE and login method MSCHAP MSCHAPv2, connecting to URL not an IP. Cheers. -- bgalakazam ___ 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: FreeBSD on the ASUS P8H67-M LGA1155 H67 motherboard
On 16/05/2012 13:52, Victor Sudakov wrote: Colleagues, Do you have success stories running FreeBSD on an ASUS P8H67-M LGA1155 H67 motherboard? This will be mostly a desktop system on 9.0-RELEASE. I am worried especially about the Sandy Bridge video, shall I be able to use it with xorg at least in VESA modes? Do also the sound/NIC/etc drivers work well with this motherboard? I am running 9.0-RELEASE on an ASUS P8H61-M LE/USB3 with a corei5 Having the same audio and LAN chips I can say they work. Had some trouble getting the audio working to start with, vaguely recall it was something with the generic sound detection didn't pick the right driver, once I enabled one specific sound device I haven't had trouble (also that was back in rc3). Only using stereo speakers so can't vouch for any surround features. Add snd_hda_load=YES to /boot/loader.conf Using an Nvidia PCIe card - haven't tried the on-board video. ___ 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: FreeBSD on the ASUS P8H67-M LGA1155 H67 motherboard
Shane Ambler wrote: Do you have success stories running FreeBSD on an ASUS P8H67-M LGA1155 H67 motherboard? This will be mostly a desktop system on 9.0-RELEASE. I am worried especially about the Sandy Bridge video, shall I be able to use it with xorg at least in VESA modes? Do also the sound/NIC/etc drivers work well with this motherboard? I am running 9.0-RELEASE on an ASUS P8H61-M LE/USB3 with a corei5 Having the same audio and LAN chips I can say they work. Had some trouble getting the audio working to start with, vaguely recall it was something with the generic sound detection didn't pick the right driver, once I enabled one specific sound device I haven't had trouble (also that was back in rc3). Only using stereo speakers so can't vouch for any surround features. Add snd_hda_load=YES to /boot/loader.conf Thanks for the good news. Can you please show 'cat /dev/sndstat' and what the kernel thinks about the NIC (is it the re(4) driver?) Using an Nvidia PCIe card - haven't tried the on-board video. I have tried PC-BSD 9.0 on a similar motherboard with a Sandy Bridge video, it seems to work in VESA mode. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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
Wine for Diablo 3 on FreeBSD 9.0R amd64
Can anybody play diablo 3 with wine on FreeBSD 9R amd64? Wine 1.5.4,1 64bit can't running Diablo III perhaps because of Agent.exe. see http://appdb.winehq.org/objectManager.php?sClass=versioniId=25953. 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: Wine for Diablo 3 on FreeBSD 9.0R amd64
We have to wait, unfortunately. I am using a Linux partition with Wine meanwhile. As long as it's not mainstream, it will be hard to do. Not to mention port is at 1.4. 2012/5/16 alphachi alpha...@mediaspirit.org Can anybody play diablo 3 with wine on FreeBSD 9R amd64? Wine 1.5.4,1 64bit can't running Diablo III perhaps because of Agent.exe. see http://appdb.winehq.org/objectManager.php?sClass=versioniId=25953. 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 -- Lyubomir Grigorov (bgalakazam) ___ 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
