Search results

  1. A

    Site Load Time Utility?

    I always use a site called Pingdom for it. They also give tips on how to improve stuff, etc..
  2. A

    Network traffic logging

    You can do that with TCPDUMP(1). If i'm not mistaken you'd want something like tcpdump -A 'gateway x.x.x.x and (dst port http)' Where x.x.x.x is your server's IP. Look at PCAP-FILTER(7) for the syntax of the expression / filter.
  3. A

    Trouble with Sendmail

    You don't have to. For name-based virtual hosts a forward DNS is all you need. In your case... if 199.102.76.2 resolves to rmg4.x.rootbsd.net, you simply define that as the MX-host for your domains: zone-file for indyuru.net : @ IN MX 10 rmg4.x.rootbsd.net. @ IN TXT "v=spf1 a mx -all"...
  4. A

    Trouble with Sendmail

    Personally I don't think it's your sendmail that is the problem; it looks fine to me. If gmail accepted the e-mail, then your sendmail is working properly. I think your problem might be the DNS settings of your domain. If your forward and reverse DNS don't match, some spamfilters will complain...
  5. A

    IPFW and NTP

    The simplest way would be to allow UDP port 123 through; both incoming and outgoing. ipfw add pass udp from any to any 123
  6. A

    FreeBSD 9.0-RELEASE : saslauthd 2.1.25 coredumps at Sendmail TSL/AUTH

    I've filed a problem report for the issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=165422 If there's any development or news on the problem report, I'll update this forum post.
  7. A

    IPFW firewall and maybe ng0 problem

    You say you have two network interfaces: em0, which is connected your internal network. em1, which is connected to your internet connection (via the modem). Why in Bob's name are you using a netgraph interface for your network address translation ?The way I see it, the correct way to get...
  8. A

    FreeBSD 9.0-RELEASE : saslauthd 2.1.25 coredumps at Sendmail TSL/AUTH

    So, I had hoped to solve this problem by reverting to FreeBSD 8.2-RELEASE. Here's where it gets funny: I have the exact same problem on FreeBSD 8.2-RELEASE! I've followed the steps described in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/smtp-auth.html 1-on-1 to install and...
  9. A

    Fresh FreeBSD 8.2 install fails "make" on sendmail.

    Fixed! I think... I removed the whole /usr/src tree and reinstalled the sources distribution. It compiles just fine now, even after freebsd-update.
  10. A

    /dev/ad4 becomes /dev/ada0?

    If you look carefully, then you will see that /dev/ad4 is now actually a symbolic link to /dev/ada0. If you just change your configuration to match the new device name, it should work out just fine. Also, don't forget to add the following in your kernel configuration, or smartmontools won't be...
  11. A

    Fresh FreeBSD 8.2 install fails "make" on sendmail.

    I'm trying to set up SMTH authentication for sendmail on a fresh FreeBSD 8.2-RELEASE install. After the installation I've run freebsd-update, which is the only change that was made to the system. Following the following document...
  12. A

    smartmontools after upgrade to FreeBSD 9.0-RELEASE

    Unfortunately, setting kern.securelevel to -1, and/or specifying "atacam" as device type doesn't make a difference :(
  13. A

    smartmontools after upgrade to FreeBSD 9.0-RELEASE

    Unfortunately, on my 9.0-RELASE it doesn't. Allthough currently I'm getting a different message from when I first started the thread: /dev/ada0: Operation not permitted At first I thought it had something to do with the kernel security being too high, but lowering my kern.securelevel to...
  14. A

    smartmontools after upgrade to FreeBSD 9.0-RELEASE

    I never install binary packages. I updated the ports with portsnap and then recompiled all the ports with portmanager. After it broke again, I recompiled the kernel to make absolutely 100% sure that device pass was enabled. I've also recompiled smartmontools from scratch, but all to no avail. :(
  15. A

    smartmontools after upgrade to FreeBSD 9.0-RELEASE

    After updating the ports, I'm back to square one. device pass Is enabled in the kernel configuration, just as before. Yet, using smartctl 5.42, the error messages return. Does this mean the port is bugged, or am I just missing something?
  16. A

    Upgrade to FreeBSD 9.0-RELEASE broke my ichwd?

    Problem solved! Adding nooption NEW_PCIB to my kernel config solved the problem.
  17. A

    smartmontools after upgrade to FreeBSD 9.0-RELEASE

    I managed to solve it myself. In my kernel I forgot to include device pass I must have overlooked it in the documentation. So this thread may be closed and flagged as "solved" :)
  18. A

    FreeBSD 9.0-RELEASE : saslauthd 2.1.25 coredumps at Sendmail TSL/AUTH

    While trying to set up SMTP AUTH with Sendmail on my freshly installed FreeBSD 9.0-RELEASE, I'm running into a problem: saslauthd 2.1.25 seems to core dump as soon as I try to authenticate using SMTP AUTH via Sendmail. Sendmail has been recompiled with the following flags, to facilitate SMTP...
  19. A

    Upgrade to FreeBSD 9.0-RELEASE broke my ichwd?

    Ok, So after upgrading to FreeBSD 9.0-RELEASE, suddenly my watchdog can't be patted anymore. The culprit seems to be that ichwd isn't working anymore: ichwd0: <Intel ICH9R watchdog timer> on isa0 ichwd0: unable to reserve GCS registers device_attach: ichwd0 attach returned 6 ichwd0: <Intel...
  20. A

    smartmontools after upgrade to FreeBSD 9.0-RELEASE

    Ok, So after upgrading to FreeBSD 9.0-RELEASE, suddenly my disks aren't recognized by Smartmontools anymore. /dev/ada0: No such file or directory Smartctl: please specify device type with the -d option. Yet, after specifying the device with: /usr/local/sbin/smartctl -d ata -i /dev/ada0...
Back
Top