@firestorm_v1: Now, if I statically assign the test machine an IP address, it is able to connect to the Internet and browse with no issue so I know that it's not a connectivity issue to the pfSense OPT1 interface. I can not ping the pfSense router at all, I would expect a ping response from the OPT1 IP address but not from the LAN IP address. I'd try connecting a system directly to OPT1 (bypassing the switch) to see if it gets an IP address by DHCP in that configuration.\

Hi, I'm sorry for the late reply. I just tested it again. This time it worked perfectly straight through the web interface (selecting type string, which wasn't possible back then). I entered in the following: number: 33, type: string, value: C0:A8:70:01:C0:A8:00:1E This resulted in the following host route: dst:192.168.112.1  mask:255.255.255.255     gw:192.168.0.30 Did you already succeed with your option 121 issue? Greets, Max

What is your configured DHCP range, and what is your LAN IP configured as?

Many thanks. @jimp: It's in /var/dhcpd/var/db/dhcpd.leases

Yes, that can work, as long as the d-link adapter shows itself to the system as four separate network cards, then it can be used for four (or more with vlan) separate networks, each with their own DHCP, etc. Don't use auto assign and re0 might work, it probably doesn't properly report its link state. If you assign, and actually type in re0, then it will probably work fine.

I'd start with checking what line 1 of /usr/local/etc/dnsmasq.blacklist.conf contains. (Though on my installs that file doesn't exist…)

There is an option that tells the network connection to 'Automatically obtain DNS information from provider', this option is not what you would expect, it is not the DNS server IP information. Using network manager (Gnome Desktop), select Network Manager (called just Network on the administration menu), double click the target connection and then leave a machine name in the 'hostname' box but uncheck the 'obtain DNS information' option then it works, the problem now is that it doesn't set any DNS server IP addresses at all. The fix is to leave the option selected and then add a line DHCP_HOSTNAME=whateverhostnameis into the ifcfg-eth*.conf file located in the etc/sysconfig/network_scripts folder (af least on Fedora Core) and restart the machine. Very intuitive !!

I was under the impression tinyDNS is a real dns server, querying root servers for all external dns entries… that's what I need. If I wanted to rely on dns queries being forwarded to other dns servers, I'd just stick to the dns forwarder (which I am doing now because I currently have no other dns server around...).

Hello all, Good news, i've just solve my problems: At switch, on port that pfsense is plugued, i set all vlan's ids, and this port must be tagged, and the others untagged. Thanks for all

I prefer using Bind to be fair though. Feel its a much more professional DNS, but obviously does not have a failover, though I don't actually need that anyways so cannot see much point. Ah ok that's fair enough, but I shall keep going with bind to be fair.

I can confirm that RFC 2136 DDNS updates in the latest 2.0 beta don't work either. I see nothing in the log file either. I am able to manually update when I SSH and do a manual " nsupdate -d" to update the record.

@SeventhSon: If your pfSense is behind NAT, this is still valid solution though. No because it will then just register your private IP, you'll need a different dyndns client in that case.

nslookup centosservervirtual.myradon.net Server: 192.168.1.129 Address: 192.168.1.129#53 Name: centosservervirtual.myradon.net Address:   192.168.1.136 dscacheutil -q host -a name centosservervirtual.myradon.net name: pfsense.myradon.net alias: centosservervirtual.myradon.net ip_address: 192.168.1.129 It's an OSX-thing! http://discussions.apple.com/thread.jspa?threadID=2140119&start=45&tstart=0 Is a discussion about DNS and internal name resolution. I'm going to dive into that and hopefully post the sollution here.

Hi cmb Thanks for your reply. A friend of mine emailed me a couple of hours just the same. In fact, logically - Actually, I should have noticed it by myself.  ::)

use its IP or setup a DNS server like BIND or tinyDNS , or use a DNS service that lets you make queries against it such as OpenDNS and create a shortcut.

ctrl-p

I was about to say that….in 1.2.3 this causes no issues on port 80. It is also solved in the jan 18 snapshot if I recall correctly.

Problem solved looks like, there was problem with cisco Catalyst 2960G switch, which was got from black market :) Thanks all for helping!