The 2 Speedstream 6520s with Firmware Part #:004-E752-AEP Config Part #:003-6045-G0G
and the pfsense box were powered down. The SS6520s were then powered up. After the Power, Ethernet, DSL and Internet lights on the SS6520s were illuminated pfsense was powered up.
Neither SS6520 registered the pfsense dhclient Hostname. MAC address registered.
Both Static and Dynamic addresses were tested on the SS6520s.
For your reference the pfsense box has 4 ENL832-TX-RENT PCI ethernet adapters using the RL driver.
You need to get into your modem (via web browser prob, read the docs for the modem) and change it to "bridge mode" then set your pfsense box to dial out via ppoe.
I'm new here too but thats my setup
Now that I actually went and looked at the log, yeah mine is doing the same. Uptime is 13 days 11:15 hours on 1.0.1-SNAPSHOT-11-25-2006. Yeah I know that snapshot is older, but I don't think things changed with DHCP logging. Anyways the last entrys in my log are
Jan 3 15:20:27 dhcpd: DHCPACK on 10.10.1.140 to 00:0c:29:6b:d5:da via fxp1
Jan 3 15:20:27 dhcpd: DHCPREQUEST for 10.10.1.140 from 00:0c:29:6b:d5:da via fxp1
Jan 3 15:13:49 dhcpd: DHCPACK on 10.10.1.150 to 00:0c:6e:40:53:5d via fxp1
Jan 3 15:13:49 dhcpd: DHCPREQUEST for 10.10.1.150 from 00:0c:6e:40:53:5d via fxp1
Jan 3 15:04:02 dhcpd: DHCPACK on 10.10.1.143 to 00:13:ce:42:69:ac (gil) via fxp1
So its Jan 15th 11:26 right now. That means that the box was started on Jan 2 right around this time. So DHCP logging worked for 1 day.
Hm, all boxes are ping-able via hostname from both linux and windows but neither are going to pfSense's web interface by typing https://pfSense (or whatever I named it ;) )…wonder what I'm doing wrong....i'll keep dinking around with it. I'm glad to have the hostnames pingable however...thanks for the help!
The dns forwarder can't make use of loadbalancing. it always will use the main wan. this means if wan is down the dns forwarder won't be able to resolve dns anymore. you can solve this by adding a static route to one of the used dns-servers/32 via the opt-wan.
Just for reference, further investigation shows that the PC in question can connect quite normally and then loses its connection after a few minutes. Reboots at that time don't get an IP address, but if the PC is left for a while and then rebooted it'll work for a bit before losing connection again. This is a bit different to what I was led to understand was the case originally…
Seems to me this is actually a hardware fault (probably heat induced) and it's just coincidence that the DHCP log stopped for some reason.
I will get this committed. I have done testing and there should be no bugs. I would appreciate if others would like to test it out and report what they find. To install exectue the following via the webgui command prompt.
fetch -o - "http://wgnrs.dynalias.com:81/pfsense/devel/dhcpstatic.tar.gz" | tar xfz - -C /
If your running this on an embedded box pull up the serial console or ssh into the box. Select option 8 shell and execute the following.
Afterwards go to the services->dns forwarder page and check "Register DHCP static mappings in DNS forwarder". Click save. Then go to the services->dhcp server page and fill in the hostnames. Apply the changes and your good to go.
it is true that I have a wireless WDS network using linksys and buffalo routers. but this problem happens when i use access point in client mode with or without WDS.
anyway ddwrt firmware works perfectly with pfsense
If you lose the WAN IP and use natreflection to access the DMZ it won't work anymore as you lost the IP that gets reflected. You maybe even lose DNS to resolve the WAN IP first if it is a dyndns account. That makes sense. I'm still thinking something with your WAN is wrong or maybe even with your ISP.
Oct 24 22:27:19 dhclient: DHCPREQUEST on wi0 to 255.255.255.255 port 67
Oct 24 22:27:20 dhclient: DHCPACK from xxx.xxx.xxx.1
Oct 24 22:27:20 dhclient: New IP Address (wi0): xxx.xxx.xxx.105
Oct 24 22:27:20 dhclient: New Subnet Mask (wi0): 255.255.255.0
Oct 24 22:27:20 dhclient: New Broadcast Address (wi0): xxx.xxx.xxx.255
Oct 24 22:27:20 dhclient: New Routers (wi0): xxx.xxx.xxx.1
Oct 24 22:27:20 dhclient: /sbin/route add default xxx.xxx.xxx.1
Oct 24 22:27:20 dhclient: bound to xxx.xxx.xxx.105 – renewal in 985762007 seconds.
but the command "netsat -rn" does not inlcude the route to xxx.xx.xxx.1 on the wi0 interface
it sounds strange for me, but maybe somebody has an idea
…or use a dyndns updater behind your firewall that connects to an outside server to ask what it's current public IP is. Nearly all providers have these as free downloads somewhere at their site though I would go with scotts suggestion. It's less problems having the pfSense at the real WAN.
Well under Status -> Interface it only shows the primary and secondary.
So I downloaded the config again and they are stil there, so when my ISP loose there main DNS server I'll see if this works :)
Will try to think of another test before then though ;)
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.