Jeffrey P. Toth wrote:

Thank you for your response Ion-Mihai,

On the router question, no, the router is a separate device, a D-Link 504H but is a loaner while my D-Link 804HV is in the shop. After changing them out is when I discovered I had problems. Apparently the DL804 handled whatever the problem was without a complaint.

Yes I have been through setup a few times. So far all I have been able to do is take the server off-line.

I have also looked up setup for NATD and I think I can enable it but would not be able to write the firewall rules for it to read yet, as I understand needs to be done. I also had a little help with setup originally and I know there is something of a firewall setup but without know what exactly I would be afraid of interfering with what is there and making a mess of it.

Sorry I am such a non-user.



I've been reading this thread and I think you need to start from the beginning. I am going to make a broad assumption that your D-Link is set up correctly and that it *is* a sort of broadband router that does NAT and has DHCP services. This means that the D-Link should be somehow connected to your DSL modem and/or Cable modem (unless you are using some other sort of connection - I couldn't find the 504H on D-Link's site, but was able to find the 804HV and am *again* assuming that it is similar).

So here is the assumption list:
- Your D-Link is capable of doing NAT and DHCP
- You can ping the D-Link from your FreeBSD box (Win box, etc.) - if you can't STOP - this is your first problem.
- Your router's internal address is with a netmask of
- You have chosen to statically assign your inside machines with addy's (although you could also get the addy assignment via DHCP from the D-Link, you may have chosen to go the static route for other reasons).

On the FreeBSD box:
in rc.conf you should keep:

ifconfig_xl0="inet netmask" # <-- no other machine on the network should have this address

Assigning an address to rl0 is irrelevant - also, make sure that that interface is unplugged from your network. Make sure the xl0 interface is plugged in correctly.
For now, also make sure the following is true:


Save rc.conf
Now, take a look at resolv.conf.
It should show something like:


or the address of a nameserver you know is valid. Get rid of any other lines for now - you can simply comment them out by beginning the line with #.
Save resolv.conf

Although there are ways around this, reboot the machine.

Once back up and running, you should be able to ping the router and ping an address like If you can't ping a website outside your internal network - i.e. Yahoo's - then there is a problem probably related to the D-Link.

On every machine, you should (basically) have the following configuration:

IP: 192.168.0.x (NOT 1 or any address that you have used with another machine)
DNS: (or other valid DNS cache server).

Since you are not doing NAT or firewalling on the FreeBSD machine, there is no need to enable them. If you eventually want to do firewalling directly on the FreeBSD box, then you can enable it and configure it after you have solved your networking problems.
I would recommend simply allowing the IP addy's to be assigned via DHCP, though. On FreeBSD, you simply put:


in rc.conf and get rid of the other config info. Also, leave the firewall and nat off.
In resolv.conf you can comment everything out with # as it will be assigned dynamically by the dhcp server.

This *should* get you going...

[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to