From owner-freebsd-isp Tue Sep 7 17:39:13 1999 Delivered-To: freebsd-isp@freebsd.org Received: from arutam.inch.com (ns.inch.com [207.240.140.101]) by hub.freebsd.org (Postfix) with ESMTP id 0AB1C15658; Tue, 7 Sep 1999 17:39:00 -0700 (PDT) (envelope-from freyes@inch.com) Received: from tomasa (freyes.static.inch.com [207.240.212.43]) by arutam.inch.com (8.9.3/8.9.3/UTIL-INCH-2.0.0) with SMTP id UAA11737; Tue, 7 Sep 1999 20:38:42 -0400 (EDT) Message-Id: <199909080038.UAA11737@arutam.inch.com> From: "Francisco Reyes" To: "freebsd-jobs@freebsd.org" Date: Tue, 07 Sep 1999 20:39:15 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Need remote help for misc setup issues.. possible remote part time sysadmin Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Note: I am not in the jobs list, so please reply to my email... I had enough trying to figure out how to make a gateway with FreeBSD ipfw and natd. I am looking for someone to help me and I am willing to pay. I am looking for someone with who I can build a relation and hopefully have this person help me not only with my home network, but with a box I run with Netmax (www.netmax.com). I could have gone the easy route and use Netmax at home, but I really want to see how things work under the hood.. I just don't have the time or patience to figure them out myself. The job at hand: -Configure ipfw/natd for a home network while not breaking Samba Samba was working fine before I tried setting up ipfw/natd in the kernel and changing /etc/rc.conf Prefer someone who is currently working as a sysadmin somewhere, but basically if you have the experience I will consider. A good working knowledge of security/ipfw (or by other means) a definite plus since I would eventually like someone to look at my site running netmax (I got the firewall working, but I am sure the rule order are non-optimal). Other things which I would probably need are -Help installing ports (i.e. just tried ssh and the port on my 3.2 box did not work even after installing the package to bring the ports up to date). I will be willing to consider someone with less experience with a lower rate.. but the rate will highly define the type of relation (i.e. the higher the rate the more I will try myself before going to the consultant...). If you need references I have two other remote consultants that I do work with that could answer your questions regarding my paying history.. etc.... I basically am a strong believer of offsite/remote work and before the two consultants I am using now I had used two other consultants and have been happy with hiring people over the net. Please include: - Your experience WITH FREEBSD. In particular relating to networking, security and routing (ipfw/natd), sendmail (mostly for my business site), www (Also for business site) and DNS. -Your rate -Timezone/country. I am in eastern standard time/US. It could be one person or a group of friends/hackers... as long as I have a single point of contact. I would find acceptable to have work done within a week for anything. The email I posted to questions was... ******************* I am trying to make a FreeBSD box a gateway for a windows box at home. I am using Natd with an "open" firewall. Not only the windows box can not see the internet, but now the FreeBSD box takes a very long time at bootup specially at the startup of some of the daemons such as sendmail and Samba. Ping to the box works fine, but telnet to the box takes much longer than usual to get a prompt. Pinging the FreeBSD box works but trying to ping the windows box gives an error. PING tomasa.reyes.somos.net (10.0.0.10): 56 data bytes ping: sendto: No route to host Relevant files: /etc/rc.conf hostname="sanson.reyes.somos.net" ifconfig_ed1="inet 10.1.1.10 netmask 255.255.255.0" ifconfig_ppp0="inet 207.240.212.43 netmask 255.255.255.0" network_interfaces="ppp0 ed1 lo0" firewall_enable="YES" firewall_type="open" firewall_quiet="NO" natd_enable="YES" <===== natd_interface="tun0" <===== natd_flags="" gateway_enable="YES" <===== named_enable="YES" The name server is setup just as a chaching DNS. nslookup Default Server: localhost.reyes.somos.net Address: 127.0.0.1 /etc/resolv.conf domain somos.net nameserver 127.0.0.1 nameserver 207.240.128.28 nameserver 207.240.140.102 I confirmed that natd is coming up ps -aux |grep natd root 94 0.0 1.0 428 212 ?? Is 3:04AM 0:00.00 /sbin/natd -n tun0 The Natd man page specifies to have the interface up before using it. Where would call user ppp so it gets started before natd? Is this related to not finding a route to my windows box and the slow bootup? ******************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message