Compaq Deskpro won't reboot
Hi, I have a number of compaq deskpro 350mhz P2 boxes which run FreeBSD very happily. I have recently started using FreeBSD 4.8 but have run into a snag. It seems that these Compaq boxes will nor warm boot under FreeBSD4.8. Using either reboot or shutdown -r now, they shut down cleanly but then never come back up again. Any ideas? Thanks Matthew Ryan [EMAIL PROTECTED] Matt Ryan Director Loose Connection Ltd. --- [EMAIL PROTECTED] http://looseconnection.com Telephone/Fax 01273 777300 --- Wireless Networking Internet Services ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
redirect_port
Hi there, Using nat on my gateway to forward traffic on many ports the same internal machine, what is the correct syntax? redirect_port x.x.x.x zz zz redirect_port x.x.x.x yy yy redirect_port x x x x nn nn or redirect_port x.x.x.x zz,yy,nn zz,yy,nn or with some other separator or what? Thanks - this is driving me up the wall, the only way I can find is to redirect a whole range, redirect_port xx-nn xx-nn but some of the ports in the range are insecure so that means I have to secure the internal machine which kind of defeats the object of having a firewall on my external machine in the first place. Thanks again Matthew Ryan [EMAIL PROTECTED] Matt Ryan Director, Loose Connection Ltd --- [EMAIL PROTECTED] http://looseconnection.com Office/Fax 07092 013375 Mobile 07977 237476 --- Wireless Networking Internet Services ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
redirect_port
Hi there, Using nat on my gateway to forward traffic on many ports the same internal machine, what is the correct syntax? redirect_port x.x.x.x zz zz redirect_port x.x.x.x yy yy redirect_port x x x x nn nn or redirect_port x.x.x.x zz,yy,nn zz,yy,nn or with some other separator or what? Thanks - this is driving me up the wall, the only way I can find is to redirect a whole range, redirect_port xx-nn xx-nn but some of the ports in the range are insecure so that means I have to secure the internal machine which kind of defeats the object of having a firewall on my external machine in the first place. Thanks again Matthew Ryan [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Silly KDE question
Hi there, I recently installed XWindows and KDE. In a fit of enthusiasm I set about playing with, and heavily customising my new desktop environment whilst still logged on as Root (DOH!) In order to save personalising KDE again: - Can I copy the .kderc and .kde files from one home directory to another? Are there any other files I will need to copy. Or do I have to start over. Thanks Matthew Ryan [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsdforums?
Hi Stacey, On Saturday, June 28, 2003, at 07:44 PM, Stacey Roberts wrote: Hello, I've been offline for the last two weeks whilst moving house / switching ISP's, now that I'm able to access the Internet, I now find that one of my favourite FreeBSD sites www.freebsdforums.org is unavailable. Does anyone know if they're temporarily off-line, or completely gone? Just checked - the site is all up and running. Matthew Ryan [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Limiting closed port RST response
Hi there, I'm getting a lot of these in my security output. Limiting closed port RST response from 220 to 200 packets per second They are always on ports between 200- 300. Could this be a DOS atttack? Where do I find a more detailed log? I'm running FreeBSD 4.8 Release - the box is basically just a gateway router running natd and dhcpd. Any ideas. Thanks Matthew Ryan [EMAIL PROTECTED] PS Please say if this question should be on a different list :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie wirless install question
Hi Scot, On Tuesday, June 10, 2003, at 03:13 PM, Scott Miller wrote: I am still trying to get my wireless card working. What am I doing wrong? It should get an address via DHCP. (I did not see where this was indicated in ifconfig.) ifconfig won't tell you how it got it's address. Can you post the full output of ifconfig wi0 and also /etc/rc.conf? Have you used pccard_ifconfig=DHCP in /etc/rc.conf? Matthew Ryan [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
booteasy / syslog
Hi there, Does anybody know how i can configure booteasy not to remember the last choice i made. I would like it to default to one particular boot (XP in fact), so that my 5 year old does not occasionally find himself looking at a FreeBSD login prompt. Failing that, can anyone recommend an alternative boot manager. Completely unrelated i know, but I am having problems finding how to setup sysogd to accept logs from a remote host, in this case a gateway router at another site. Just a link to a good how-to would help. I have googled but to no avail. Thanks Matthew Ryan [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: supported USB ADSL modems
Hi there, The speed touch modem is supported and last time I used it the pppoA port was good for the job. I seem to remember having some useful stuff kicking around, how to's etc. I'll have a look when I get home later. The Modem it's self however is petty unreliable over time and I found that I needed a cron job to disconnect and reconnect every night. Although Kernel PPP (user PPP does not do pppoA to my knowledge) does allow for a persistant connection, it seems that the modem just crashes sometimes and the only solution is to power down the USB port or restart the host machine. Hope this helps. On Sunday, March 23, 2003, at 06:33 pm, Andrew Boothman wrote: taxman wrote: On Sunday 23 March 2003 11:00 am, DJ Boris wrote: hi there, where can I find out what USB ADSL modems are supported by freeBSD. I am using 5.0-release and thinking of getting ADSL. Can anyone help? Well if they were supported, they would most likely be listed in the hardware page for your release listed on the FreeBSD homepage. I don't think any USB ADSL modems are supported but I could be wrong. Try to get them to give you an ethernet version. Most anything that connects by ethernet would be supported. They may tell you they can't, but if you press them, they almost always have some ethernet hardware available. I believe there is support for Alcatel SpeedTouch modems using net/pppoa from ports. I've no experience with it however. If you ask me an ethernet interface is always better for networking tasks. You may also be interested to know that Bruce Simpson [EMAIL PROTECTED] is working on a driver for the Efficent Networks SpeedStream 3060 line of xDSL PCI Cards. The driver isn't working yet but you can contact him for details about helping him test it. Cheers. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message Matthew Ryan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
OS X clients - Samba Arrrrggg!!
Hi all, I'm running a Samba server under FreeBSD Release 4.8, so far everything has been just spanky but I added a new share yesterday and now I have an odd problem with my OS X clients. Actually I only tried to copy files to the server from an OS X machine for the first time yesterday so I don't actually know how long the problem has been around. I do remember having some trouble organising files on the server from an OS X client a week or so again. In fact, shortly after the server crashed No more mbufs? I restarted and it's been fine since. The problem is this: When I try to copy files from the OS X clients (and I have tried 2 to be sure), I see a Could not complete the operation because you don't have enough privileges error. Of corse, I am sure that the user I am logged on to the server as has full read write access to the directory concerned. To be sure I have logged on as different users. I find this problem in the Home Directories as well! Just to further confuse things - I am able to create a new folder and delete it again, although I am never permitted to put a file in it. And even stranger - when the copy fails it leaves a 0k file at the destination with name of the file I try to copy. All this works perfectly on Win XP, Win 200 or Win 98 clients. We also run a Win 200AS file server and the OS X clients seem to have no problem coping files to shares on that machine. Confused? - I am! Chances are that I'm doing something daft - usually the way but I can't see what. Any ideas anyone? Thanks Matthew Ryan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: OS X clients - Samba Arrrrggg!!
On Monday, March 17, 2003, at 01:10 pm, Jon Reynolds wrote: On Mon, 2003-03-17 at 04:05, Bill Moran wrote: Matthew Ryan wrote: Hi all, I'm running a Samba server under FreeBSD Release 4.8, so far everything has been just spanky but I added a new share yesterday and now I have an odd problem with my OS X clients. Actually I only tried to copy files to the server from an OS X machine for the first time yesterday so I don't actually know how long the problem has been around. I do remember having some trouble organising files on the server from an OS X client a week or so again. Well, I just tested here with my IMac vs. FreeBSD/Samba server and I could not repeat the problem. I'm using Mac OS 10.2.4, FreeBSD 4.8-RC (from March 3) and Samba 2.2.4_1 from ports ... looks like it's time to update that. Actually, I seem to remember some documented problems with certain versions of Mac OS and SMB shares. Is your version of Mac OS up to date? In fact, shortly after the server crashed No more mbufs? I restarted and it's been fine since. You may want to raise the number of mbufs available on this server. The problem is this: When I try to copy files from the OS X clients (and I have tried 2 to be sure), I see a Could not complete the operation because you don't have enough privileges error. I tried copy and create with both files and folders with no problems. Of corse, I am sure that the user I am logged on to the server as has full read write access to the directory concerned. To be sure I have logged on as different users. I find this problem in the Home Directories as well! Just to further confuse things - I am able to create a new folder and delete it again, although I am never permitted to put a file in it. And even stranger - when the copy fails it leaves a 0k file at the destination with name of the file I try to copy. This sounds vaguely familiar. I can't remember details, but I seem to recall installing a server a one point where files would be created, and when the client actually tried to write to the file, they had no permissions. The error was somewhere in the permissions and create ownership settings in Samba. Basically, Samba was being told to create all files as another user, with somewhat strict permissions, but then the permissions were too strict to access the file. Check the unix permissions on the 0 byte file that gets created. If they would prevent writing to that file, check your file creation options in samba. All this works perfectly on Win XP, Win 200 or Win 98 clients. Are the Win machines logging in differently than the Macs? We also run a Win 200AS file server and the OS X clients seem to have no problem coping files to shares on that machine. Confused? - I am! Yeah, so was I ... assuming that you're having the same problem I was. Chances are that I'm doing something daft - usually the way but I can't see what. Check the perms and the samba options. I may be wrong, but that's what it sounds like. I just got over this problem about a month ago. What I believe the problem was is that on the samba server in the shared folder I found some .(dot) files like FBCFolderLock and .DStore. When I deleted all these dot files that the Macs had created I no longer got the permissions problem. As always, back up before trying anything. Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message Well the problem was with the .(dot) files! I had veto'd all files with a dot before them: veto files = /.*/ This worked a treat for all the windows clients (who's users tend to like to see hidden files - but have no need to see all that annoying Mac stuff or the unix .(dot) files) However, it seems that the OS X clients need to place a small file in the directory to which they are copying before they copy the actual file. Don't know why - ??? Anyhow, the veto makes the small ._(dot underscore) files unaccessible, so then the copy can't complete and the user sees a permissions error. At least I think that's how it works - or doesn't. For now I have specifically veto'd all the unix .(dot) files and the common Mac ones (.DS_Store etc.) but that still leaves me with ._(dot underscore ) files which the macs create when they copy files to the server. This is not ideal cos there are hundreds of them so any better ideas would be apreciated. Thanks again Matthew Ryan [EMAIL PROTECTED]
Re: Port Forwarding FreeBSD 4.7_Release
On Saturday, March 15, 2003, at 03:06 am, Bill Moran wrote: Matthew Ryan wrote: On Saturday, March 15, 2003, at 12:13 am, Lowell Gilbert wrote: Fact is, natd _only_ redirects from the interface is was told to bind to. I'm not exactly sure why the packets don't route out and back in when you try it from inside, but they don't ;( so you always need to test it from the external interface. The reason they don't route out is that they are addressed to the router, so it doesn't bother to forward them outside. Ok, I understand, this does present me with a bit of a problem however, accessing my mail server from home for example. Can you think of a workaround? I don't fully understand the question. What exactly do you mean by from home? Is the mail server behind the firewall? You can port forward/reroute just about anything to anywhere, with enough time and patience. But there's not enough information in the statement you just made for anyone to help you much. sorry, i'll try to be more explicit. I have a number of services on ports forwarded from my external IP address to an internal IP address via NAT as we have discussed. The problem is that I can not access these services from inside nat. Example - My mail server address resolves to my external IP number. It's primarily a mobility issue. From inside NAT I can't collect my mail unless I specifically point my browser at the internal IP number of my mail server. Yes I can get around this with some sort of client location manager or by connecting to the internet via a route other than my LAN, but none of these options are ideal. I am hoping for a routing solution, and I am pleased to read your comforting words: You can port forward/reroute just about anything to anywhere, with enough time and patience. Lowell Gilbert suggests running local DNS (thanks) but I have no experience of DNS and I had other areas of learning in mind for the moment. Can anyone think of another solution? Thanks again Matthew Ryan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Port Forwarding FreeBSD 4.7_Release
Hi there, I've been trying to route packets received on port via the external interface (used by NAT) of my FreeBSD gateway to the same port on a local machine. The manual would seem to make this simple stuff - I have added the following line to /etc/rc.conf: natd_flags=-redirect_port tcp 192.168.1.241: accessing this service on the local machine via the local address is fine but a port scan from the outside, reveals that the relevant ports appear closed still. Needless to say - the service is unavailable. I have tried entering the following on the command line (with and without the /etc/rc.conf flag): natd -redirect_port tcp 192.168.1.241: but here's what i get: natd: aliasing address not given I have tried adding the external address as follows but to no avail: natd -redirect_port tcp 192.168.1.241: XXX.XXX.XXX.XXX: To avoid confusion I am running with an open firewall - rules below: gatewayb# ipfw list 00050 divert 8668 ip from any to any via ep0 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65000 allow ip from any to any 65535 deny ip from any to any I have read quite a few mails from people finding the same problem but not yet found an answer. My guess is that I am missing something simple but i've been banging away at this for a while now and no joy. Any advice would be appreciated. Thanks Matthew Ryan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Port Forwarding FreeBSD 4.7_Release
Thanks Dan Unfortunately that doesn't seem to work either. I get this when I enter on the command line: natd -n ep0 -redirect_port tcp 192.168.1.241: natd: Unable to create divert socket.: Operation not permitted and no results using the following in /etc/rc.conf: natd_flags=-n ep0 -redirect_port tcp 192.168.1.241: By the way, the interface is specified already in /etc/rc.conf as follows?: natd_interface=ep0 any other ideas? Ta Matthew Ryan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Port Forwarding FreeBSD 4.7_Release
Bill and Dan, Thanks for your help guys it's sort of working now but for the record here's the story. All attempts to start port forwarding from the command line were failing because NATD was already running (enabled at boot time) DOH! b) natd isn't already running with different options when you try to start it on the command line? Well spotted Bill! The /etc/rc.conf entry: natd_flags=-redirect_port tcp 192.168.1.241: was fine since: natd_interface=ep0 specified the interface. All in all I just should have posted the whole of my /etc/rc.conf in the first place. Sorry about that. The real irony is that it was working all along!! I just didn't know because i was trying to access the service on the external IP address of my router from an internal IP address. When I tried to access it via. my other connection (in effect from outside) everything worked fine. I'm sure that there is some reasonable explanation for this to do with the way that NAT operates but I can't figure it out. Any clues? Thanks Again Matthew Ryan [EMAIL PROTECTED] Daniel Bye wrote: On Fri, Mar 14, 2003 at 01:07:42PM +, Matthew Ryan wrote: Thanks Dan Unfortunately that doesn't seem to work either. Rats! I get this when I enter on the command line: natd -n ep0 -redirect_port tcp 192.168.1.241: natd: Unable to create divert socket.: Operation not permitted Silly question, I'm almost blushing to ask - you are running the command as root, yes? Also ... are you sure that: a) You have your kernel configured with IPDIVERT? The GENERIC kernel does _not_. b) natd isn't already running with different options when you try to start it on the command line? and no results using the following in /etc/rc.conf: natd_flags=-n ep0 -redirect_port tcp 192.168.1.241: By the way, the interface is specified already in /etc/rc.conf as follows?: natd_interface=ep0 This is redundant. You can remove the -n ep0 from natd_flags. any other ideas? I don't know _whats_ wrong. But I've got this running in two places with no problems. It works just fine, and as far as I can see, the syntax you're using is correct, so I wouldn't focus on that. Let us know what you find when you check the suggestions I made ... I have other suggestions if those don't help. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message Matthew Ryan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Port Forwarding FreeBSD 4.7_Release
On Saturday, March 15, 2003, at 12:13 am, Lowell Gilbert wrote: Fact is, natd _only_ redirects from the interface is was told to bind to. I'm not exactly sure why the packets don't route out and back in when you try it from inside, but they don't ;( so you always need to test it from the external interface. The reason they don't route out is that they are addressed to the router, so it doesn't bother to forward them outside. Ok, I understand, this does present me with a bit of a problem however, accessing my mail server from home for example. Can you think of a workaround? Ta Matthew Ryan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
