2.1 RC2 can't get WAN IP by DHCP ?

timthetortoise

Why spoof your MAC? Keep your modem unplugged for about a minute, plug it back in, and you should get an IP on your pfSense box.

Guldil

Hi,

log from dhcpd :

[2.1-RC2][admin@pfSense.localdomain]/root(2): clog /var/log/dhcpd.log | grep dhclient
Sep 13 09:10:26 pfSense dhclient: PREINIT
Sep 13 09:10:26 pfSense dhclient: Starting delete_old_states()
Sep 13 09:10:26 pfSense dhclient[17546]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 2
Sep 13 09:10:28 pfSense dhclient[17546]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 5
Sep 13 09:10:33 pfSense dhclient[17546]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 8
Sep 13 09:10:41 pfSense dhclient[17546]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 12
Sep 13 09:10:53 pfSense dhclient[17546]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 9
Sep 13 09:11:02 pfSense dhclient[17546]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 9
Sep 13 09:11:11 pfSense dhclient[17546]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 11
Sep 13 09:11:22 pfSense dhclient[17546]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 5
Sep 13 09:11:27 pfSense dhclient[17546]: No DHCPOFFERS received.
Sep 13 09:11:27 pfSense dhclient[17546]: No working leases in persistent database - sleeping.
Sep 13 09:11:27 pfSense dhclient: FAIL
Sep 13 09:11:27 pfSense dhclient: Starting delete_old_states()
Sep 13 09:11:42 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 1
Sep 13 09:11:43 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 2
Sep 13 09:11:45 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 4
Sep 13 09:11:49 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 5
Sep 13 09:11:54 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 5
Sep 13 09:11:59 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 14
Sep 13 09:12:13 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 17
Sep 13 09:12:30 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 7
Sep 13 09:12:37 pfSense dhclient[68018]: DHCPDISCOVER on re1 to 255.255.255.255 port 67 interval 6
Sep 13 09:12:43 pfSense dhclient[68018]: No DHCPOFFERS received.
Sep 13 09:12:43 pfSense dhclient[68018]: No working leases in persistent database - sleeping.
Sep 13 09:12:43 pfSense dhclient: FAIL
Sep 13 09:12:43 pfSense dhclient: Starting delete_old_states()

log from syslog when plugging the cable :

Sep 13 09:10:23 pfSense kernel: re1: link state changed to UP
Sep 13 09:10:23 pfSense check_reload_status: Linkup starting re1
Sep 13 09:10:26 pfSense php: rc.linkup: DEVD Ethernet attached event for wan
Sep 13 09:10:26 pfSense php: rc.linkup: HOTPLUG: Configuring interface wan
Sep 13 09:10:26 pfSense php: rc.linkup: The command '/sbin/ifconfig 're1' inet  delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
Sep 13 09:11:04 pfSense php: /index.php: Successful login for user 'admin' from: 192.168.10.77
Sep 13 09:11:04 pfSense php: /index.php: Successful login for user 'admin' from: 192.168.10.77
Sep 13 09:11:15 pfSense check_reload_status: Syncing firewall
Sep 13 09:11:15 pfSense check_reload_status: Reloading filter

I spoof my mac address because we have some rumors that our ISP doesn't like to see multiple mac adress behind modem.
Anyway i tried with and without spoofing, i cant get an ip.

i tried to stop modem, plug it to pfsense, start, same result, no ip.

Guldil

here the dump of wiresharck when sniffing my WAN.

pfsense-dhcp-numericable.png_thumb

wallabybob

There is no evidence of the mode responding.

Lets go back to basics: What sort of Internet service do you have? What is the brand and model of the modem? What s the modem configured to do?

IF you had ADSL service and the modem was configured in bridge mode then I wouldn't expect it to respond to DHCP requests.

Guldil

it's a cable modem Netgear CBVG834G, ISP in France : Numericable.
The modem is in bridge mode.

I used DHCP for configuration because it's working perfectly with DHCP on a Draytek 2910V or Zywall 2.

One time i get a public IP with Pfsense but no traffic, it's when i restart the netgear after the pfsense.

Wowawi33

Great to hear you.

wallabybob

@Guldil:

One time i get a public IP with Pfsense but no traffic, it's when i restart the netgear after the pfsense.

I suggest you:

Upgrade to the released version of pfSense 2.1; then
Restart the netgear after the pfSense; repeat if necessary a few times until you get a public IP on pfSense WAN interface, then
Post the output of pfSense shell command: /etc/rc.banner ; netstat -r -n ; ping -c 5 8.8.8.8
Post an extract from the pfSense DHCP log showing the dhclient output around the time the public IP address was acquired.

Guest

Issue I had with a fiber company here (Verizon Fios) is I had to release the IP. They give us a free Actionet router that's branded with their name, I had to log into it, and release the IP from that interface before pfsense could get an IP. Even when I spoofed the MAC address, it would not give me an IP.

kejianshi

After following all the directions to put the actioncrap router into bridged mode, and even after cloning the MAC I STILL had to go to that little box on the wall on the inside that is opposite the ONT on the outside of the house, pull the power cord, pull the battery backup harness, wait a few seconds, replug it all - Then run over to the actiontech router, unplug/replug it and the switches also and reboot pfsense.

PITA courtesy FIOS + MOCA.

Guldil

ok it was a driver problem.

i just tried the module from NeverSimple posted here http://forum.pfsense.org/index.php/topic,65355.msg366244.html#msg366244 and now it's working :)

After plugging my wan i have an IP, no need to reboot nothing.