Re: Problem with user-pppoe after upgrade, fixed
Hi, I said your ppp.conf was censored because you didn't attach it - you just attached an error message that said it couldn't read it :*P The right fix is to simply remove these lines. What do your logs say when you enable LCP logging and the negotiation fails ? Brian Somers wrote: Hi, I think your ppp.conf was a bit too censored. Well the only thing I censored was my password/username lines and a set log line I removed the same day. Apart from that, this is the ppp.conf that I use right now, and it works. If you're setting the MTU or MRU to 1500, this will now fail. As seen in the logs? The maximum these can be set to for PPPoE is 1492. That's the physical ethernet limitation, right? That's now enforced by the PPPoE ppp device as it knows the limitations on the physical Ethernet. Shouldn't ppp warn the user or panic instead of looping as it did for me? Just commenting out your setting of the MTU/MRU should solve your problems. Actually, putting the set mtu/mru lines solved the problems. Should I remove them altogether to remove future problems? :) Thank you very much. A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Benchmarks from SysAdmin mag
* Paul [EMAIL PROTECTED] [010712 23:23]: Once upon a time, Matt Dillon [EMAIL PROTECTED] scribed: In anycase, the results prove our point rather succinctly. Unfortunately, it proves our point to us daemonites mostly, and is probably still lost on the average sysadminmag reader... ah well :) Well, at least they know now if they badmouth BSD they're going to get mailbombed :) -- When more and more people are thrown out of work, unemployment results. -- Calvin Coolidge Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ipfilter Module Breakage (Was: IPFirewall Module Breakage)
* Andrew Boothman [EMAIL PROTECTED] [010713 00:09]: Replying to my own message, the subject of this message should have course have been _ipfilter_ Module Breakage. === ipfilter Search the archives of this mailing list, about a month ago. ipf moved oin the base system and borke stable for a little while (few hours ). I thought it was only temporary and another cvsup would fix it, but if you have a fresh /usr/src that sounds unlikely...? -- Carmel, New York, has an ordinance forbidding men to wear coats and trousers that don't match. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem with user-pppoe after upgrade, fixed
Brian Somers wrote: Hi, I said your ppp.conf was censored because you didn't attach it - you just attached an error message that said it couldn't read it :*P LOL! ok.. I see. Darn mozilla. :) Ok, here goes a url, that should be fine: http://anarcat.dyndns.org/ftp/pub/FreeBSD/local_info/ppp.conf Also check the parent dir for dmesg. The right fix is to simply remove these lines. Then a workaround is to change them to 1492. :) But ok, I'll kill the line. What do your logs say when you enable LCP logging and the negotiation fails ? I'm sorry, I forgot to check yesterday night. But we have another nice test case here that cross-posted -stable and -questions. :) I'll try to do it via remote and a nice script, but this is mad, I could really fsck up my connection here. Hmm... Let's be mad. ;) A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: $diety, I hate natd.
On Thu, 12 Jul 2001, Mike Hoskins wrote: On Thu, 12 Jul 2001, Matt Dillon wrote: My new 'firewall' manual page has an ipfw example of a natd setup. It might help. You need a relatively recent -stable to have the man page. I see the page... Thanks, btw. However, it still seems fubar. Like I said before, natd's configuration looks simple enough, but packets aren't getting through. If I add an ipfw rule to just allow traffic to the outside port (8080), I see incoming packets hitting the rule... but no connection (no real fowarding to the internal ip:port). If I run a sniffer on the outside interface, I see connection attempts to 8080... run the same sniffer on the internal interface, nothing. My first thought was 'duh, the packets have to get to natd somehow so redirect_port can actually do something...' but changing the 8080 allow to a divert doesn't fix the problem. So next I figured one piece of the conversation was dying... somewhere... I.e. inbound's fine but I'm fscking something up outbound... but no denied packets in logs. It certainly seems like natd's working and ipfw just isn't allowing packets to get 'into' natd for the redirect. Unfortuneately, I've tried about everything in ipfw and natd's man page and am still stumped. Then again, I may very well be taking the wrong approach entirely. I've opened the firewall completely (allow ip any any...), and it didn't help. I knew today would be great when it started with big brother alerts at 4AM. ;) It wouldn't be so bad if I hadn't had this working before... I hate that. Thanks, -Mike -- Eat drink and be merry, for tomorrow they may make it illegal. Would something like this in your /etc/rc.conf do the trick: natd_flags=-proxy_rule port 8080 server 1.2.3.4:my_divert_port This should divert incoming packets on port 8080 to the server 1.2.3.4 on port my_divert_port. I use this on a firewall to send web traffic to our cache server. Mine looks like this: natd_flags=-proxy_rule port 80 server 1.2.3.4:3128 RJ - Ryan J. Taylor Systems/Network Administrator NCIA [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
NMI panics
Anyone have any suggestions for what the most probable causes of the following panic are? panic: NMI indicates hardware failure Thanks. -steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: mass uninstall all ports?
It's nice, but I have had it burn my ports so bad I had to start over. Gnome seemed to confuse it. I have had this happen twice and will use portupgrade after I hear people saying nice things about it for a while. - Mike H. Date: Thu, 12 Jul 2001 15:22:05 -0700 From: Kris Kennaway [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Content-Type: multipart/signed; micalg=pgp-md5; protocol=application/pgp-signature; boundary=HcAYCG3uE/tztfnV Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: [EMAIL PROTECTED] List-ID: freebsd-stable.FreeBSD.ORG List-Archive: http://docs.freebsd.org/mail/ (Web Archive) List-Help: mailto:[EMAIL PROTECTED]?subject=help (List Instructions) List-Subscribe: mailto:[EMAIL PROTECTED]?subject=subscribe%20freebsd-stable List-Unsubscribe: mailto:[EMAIL PROTECTED]?subject=unsubscribe%20freebsd-stable X-Loop: FreeBSD.ORG Precedence: bulk --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 12, 2001 at 03:05:12PM -0700, abram olson wrote: I just updated from 4.3 release to 4.3 stable. My entire system is built via ports. I want to make some updates but I keep running into endless dependency chains. I'm doing a=20 Look into portupgrade in the ports collection, which does a superb job of upgrading ports and dependencies in the correct order. Kris --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7TiMNWry0BWjoQKURAsABAKCOs+LzqQ7Xk4HuOoqfdOHH5fh66QCfV067 H5CSDVt+nXKhZ6LwKrdmTkI= =OUsp -END PGP SIGNATURE- --HcAYCG3uE/tztfnV-- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NMI panics
Steve Price [EMAIL PROTECTED] writes: Anyone have any suggestions for what the most probable causes of the following panic are? panic: NMI indicates hardware failure It's obvious that something is generating an NMI when it shouldn't. There's a sysctl, machdep.panic_on_nmi, that controls whether that should result in a panic or not. You might want to set it to 0 and see if the machine goes haywire or not. Perhaps it'd be nice to know if the NMI was delivered if !panic_on_nmi, but that's not currently implemented. Thanks. -steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: IPFirewall Module Breakage
Andrew Boothman wrote: Hi all! I've successfully built and installed a new world (including GENERIC kernel), cvsuped a few hours ago. But I'm having trouble compiling my custom kernel. During a 'make buildkernel KERNCONF=SPATULA' I'm getting the following failure : === ipfilter make: don't know how to make /usr/src/sys/modules/ipfilter/../../netinet/mlfk_ipl.c. Stop *** Error code 2 I can't understand what the problem is, as I build the GENERIC kernel without problems. But, I thought that all the modules are built in the same way, reguardless of what's in the kernel config file. So I'm not sure how I could have effected it. I saw the same errors a few days ago when building a kernel. I'm not sure what was causing it but I fixed it by ditching the custom kernel config file I've been using and re-customizing GENERIC. basically I made all the customizations I had been using to a copy of a freshly cvsup'd GENERIC and make buildkernel worked. hope this helps... -- -- Daniel Frazier [EMAIL PROTECTED] Tel: 302-239-5900 Ext. 231 Systems AdministratorFax: 302-239-3909 MAGPAGE, We Power the Internet WWW: http://www.magpage.com/ They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin, Historical Review of Pennsylvania, 1759. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NMI panics
On Fri, 13 Jul 2001, Steve Price wrote: Anyone have any suggestions for what the most probable causes of the following panic are? panic: NMI indicates hardware failure Typically, it is a memory problem. If you use ECC or parity memory, and a memory error is detected (and unfixable with ECC), the memory subsystem deliveres a NMI. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: difficulty uninstalling ports
At 9:52 PM -0700 7/12/01, Jordan Hubbard wrote: And, as I'm sure others have pointed out by now, it's even easier to do this with the -a flag. :) Of course, since pkg_delete also supports globbing now, one assumes 'pkg_delete *' from *any* directory would also work. watch out there. you wouldn't want your shell to do it's glob- expansion before pkg_delete even sees the parameter. So, you might want: pkg_delete '*' but probably not pkg_delete * when typing that in from any directory. disclaimer: I assume that's how it would work, but I'm not going to try it myself to know for sure... :-) -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: $diety, I hate natd.
On Fri, 13 Jul 2001, Ryan Taylor wrote:
Would something like this in your /etc/rc.conf do the trick:
natd_flags=-proxy_rule port 8080 server 1.2.3.4:my_divert_port
This should divert incoming packets on port 8080 to the server 1.2.3.4 on
port my_divert_port. I use this on a firewall to send web traffic to our
cache server. Mine looks like this:
natd_flags=-proxy_rule port 80 server 1.2.3.4:3128
Thanks for the suggestion, it doesn't seem to get the packets routed
properly though. The reason I hadn't tried proxy rules in the first place
was, per the man page, 'Outgoing TCP packets with the given port going
through this host to any other host are redirected...' I'm wanting to get
_incoming_ ports to ${oip}:8080 to ${iip}:80.
From what I've found online and read in the man pages... I think my natd
arguments are OK, I'm just fudging a divert somewhere.
Later,
-Mike
--
Eat drink and be merry, for tomorrow they may make it illegal.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: difficulty uninstalling ports
Boy, life would be easier if folks would just read the man pages. :-) -G Do not try to expand shell glob patterns in the pkg-name when selecting packages to be deleted (by default pkg_delete automati- cally expands shell glob patterns in the pkg-name). From: Matthew D. Fuller [EMAIL PROTECTED] Subject: Re: difficulty uninstalling ports Date: Fri, 13 Jul 2001 00:21:51 -0500 On Thu, Jul 12, 2001 at 09:52:40PM -0700, a little birdie told me that Jordan Hubbard remarked And, as I'm sure others have pointed out by now, it's even easier to do this with the -a flag. :) Of course, since pkg_delete also supports globbing now, one assumes 'pkg_delete *' from *any* directory would also work. pkg_delete supports globbing? Last I saw (and submitted patches for, as I recall) the shell does all the globbing, pkg_delete is just smart enough to do some trimming on absolute paths to find the package name. -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: Regarding New FreeBSD BenchMark From Sysadmin Mag (left out a fiew tuning options)
:: camcontrol modepage da0 -m 0x08 -e -P 3 su-2.05# camcontrol modepage da0 -m 0x08 -e -P 3 camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da0 doesn't exist su-2.05# camcontrol devlist IBM DDYS-T36950N S93Eat scbus0 target 0 lun 0 (da0) IBM DDYS-T36950N S93Eat scbus0 target 1 lun 0 (da1) # camcontrol inquiry da0 -S camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da0 doesn't exist Am I missing some funky kernel option here? -- Juha To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Regarding New FreeBSD BenchMark From Sysadmin Mag (left out a fiew tuning options)
Some SCSI drive manufacturers ship their drives with WCE enabled. Other SCSI drive manufacturers, who are more concerned with data integrity as opposed to performance figures, will ship their drives with WCE disabled. I have 3 IBM drives, and the /root drives (U160's) are WCE enabled. The non-root drive (also happens to be U2W), does not have WCE enabled. Could WCE be a featue of U160? Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Regarding New FreeBSD BenchMark From Sysadmin Mag (left out a fiew tuning options)
In message 01f101c10c0c$73e1c000$0a01a8c0@den2, Juha Saarinen writes: ::camcontrol modepage da0 -m 0x08 -e -P 3 su-2.05# camcontrol modepage da0 -m 0x08 -e -P 3 camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da0 doesn't exist su-2.05# camcontrol devlist IBM DDYS-T36950N S93Eat scbus0 target 0 lun 0 (da0) IBM DDYS-T36950N S93Eat scbus0 target 1 lun 0 (da1) # camcontrol inquiry da0 -S camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da0 doesn't exist Am I missing some funky kernel option here? cd /dev ./MAKEDEV all or cd /dev ./MAKEDEV pass4 xpt2 I'm assuming you have the pass(4) device in your kernel, which is by default in the GENERIC kernel. Regards, Phone: (250)387-8437 Cy SchubertFax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Installing old port version
I apologize if I should already know how to do this, but I haven't figured it out and haven't seen anything in the mailing lists archives or handbook about it. The closest I've found relates just to system source. I want to install XFree86 4.0.x instead of the current release of 4.1.0. The current release causes my machine (and it appears some other peoples machines, too) to reboot when vmware is powered on. How can I cvsup an older version of the XFree86-4 port? I'd go back to XFree86 3.3.6, but the whole reason I started this upgrade process was to get better support for my Matrox G400 card. Thank you. -matthew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Regarding New FreeBSD BenchMark From Sysadmin Mag (left out a fiew tuning options)
On Fri, Jul 13, 2001 at 07:48:30PM -0700, Cy Schubert - ITSD Open Systems Group wrote: :: :: cd /dev ./MAKEDEV all :: :: or :: :: cd /dev ./MAKEDEV pass4 xpt2 :: :: I'm assuming you have the pass(4) device in your kernel, which is by :: default in the GENERIC kernel. Nope, didn't know I needed that one. Will recompile and try again. Thanks. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 My pid is Inigo Montoya. You kill -9 my parent process. Prepare to vi. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Regarding New FreeBSD BenchMark From Sysadmin Mag (left out a fiew tuning options)
OK, recompiled the kernel with the 'pass' driver, and did the camcontrol modepage thing. On this particular system, with two IBM DDYS-T36950N SCSI-3 drives, WCE is enabled on both. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 My pid is Inigo Montoya. You kill -9 my parent process. Prepare to vi. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Regarding New FreeBSD BenchMark From Sysadmin Mag (left out a fiew tuning options)
On Friday 13 July 2001 21:26, Juha Saarinen wrote: ::camcontrol modepage da0 -m 0x08 -e -P 3 su-2.05# camcontrol modepage da0 -m 0x08 -e -P 3 camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da0 doesn't exist su-2.05# camcontrol devlist IBM DDYS-T36950N S93Eat scbus0 target 0 lun 0 (da0) IBM DDYS-T36950N S93Eat scbus0 target 1 lun 0 (da1) # camcontrol inquiry da0 -S camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da0 doesn't exist Am I missing some funky kernel option here? -- Juha Well, look at what it says. You either don't have the funky pass driver in your kernel, or you don't have any SCSI drives. Josh To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Installing old port version
In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes: I apologize if I should already know how to do this, but I haven't figured it out and haven't seen anything in the mailing lists archives or handbook about it. The closest I've found relates just to system source. I want to install XFree86 4.0.x instead of the current release of 4.1.0. The current release causes my machine (and it appears some other peoples machines, too) to reboot when vmware is powered on. How can I cvsup an older version of the XFree86-4 port? I'd go back to XFree86 3.3.6, but the whole reason I started this upgrade process was to get better support for my Matrox G400 card. Put date=2001.06.04.00.00.00 into your supfile then cvsup. Regards, Phone: (250)387-8437 Cy SchubertFax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Cron still exiting signal 11.
Robert [EMAIL PROTECTED] writes: What is up with cron not working? I cvsup'd last night and its still br0ke. It works fine unless you don't specify a username in /etc/crontab. It's a bug that it crashes instead of civilly reporting the error, but it has never and will never do what you want until you fix the syntax error in your crontab. -Robert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
