DHCP wont connect

[onesillyhatch]

I changed my router and I used to have my f16v2r using a static ip address but I did not know my mac address so I tried switching it back to dhcp to optain an ip address so I can get the mac address but the screen keeps reading 0.0.0.0.  It will not obtain an ip address.  I'm at a loss.  Please help.

Thanks
Rob

[dreiman]

Plug it into your network, and on your PC do IP scan looking for open port 80.  Download Nmap. It's a powerful free port scanner.

What ever the network ID is, which are the first 3 octets of your IP address... Probably 192.168.0 then scan all of the client ID which is the last number of the IP address.  If your on Windows, open a command prompt and run ipconfig /a and you should see your IP. the last number in your IP represents your PC. everything on your router will have the same first 3 sets of numbers in the ip.

0 - 255.... hopefully it will find your controller. Just check any address that come up with open port 80.

[jdawgp04]

I had a similar issue getting wifi working after upgrading to a new version a few months ago.  I don't remember the specific error message but I struggled to get the wifi adapter to get an IP from my router.  I had to connect via ethernet cable and then disable the Tethering mode in network configuration.  The tethering was conflicting with my wifi adapter and it was on by default after the update.  If you are trying to connect over wifi, see if you can get DHCP to work over ethernet so you can access the network settings tab, then disable tethering if it's on.  If tethering is working properly, you may also be able to connect to the FPP network from your phone or computer, the default pass may be "falcon" or "Christmas".

[Poporacer]

I had a similar issue getting wifi working after upgrading to a new version a few months ago.  I don't remember the specific error message but I struggled to get the wifi adapter to get an IP from my router.

The OP was posting about an F16V2R and not FPP. It sounds like you are talking about FPP?

and then disable the Tethering mode in network configuration.

Was it enabled? The recommended setting is "If no connection"

The tethering was conflicting with my wifi adapter and it was on by default after the update.

I have done close to a thousand updates of just about every update since ver 1.8 through the years and have never had the Tethering Enabled after an update

then disable tethering if it's on. 

NO!!!! That is bad advice. Set it to If No Connection

the default pass may be "falcon" or "Christmas".

It is Christmas

[onesillyhatch]

for those wondering it is hard wired to my router but through a hub.  The FPP is going through the same connection and it connects no problem.  The f16v2 wont even talk to the router.  If I can get a static IP setup I can probably get everything to connect but I need to know the mac address, which I'm not sure how to get without finding it on the network.

[breese]

Have you tried changing out the network cable?

[k6ccc]

I'm confused.  If your F16v2 was set for a static address, changing your router would not have any effect on that.  The only real issue would be if the new router was set up to use a different subnet - example 192.168.0.xxx vs 192.168.1.xxx.

[JonD]

I'm confused.  If your F16v2 was set for a static address, changing your router would not have any effect on that.  The only real issue would be if the new router was set up to use a different subnet - example 192.168.0.xxx vs 192.168.1.xxx.

They might have had a "Sticky" IP address.  (When DHCP assigns a static to a specific MAC address)  If that was the case changing the router could impact that.  If that was the case, should just be able to look at the present router's DHCP service to find which new address was assigned to the Falcon, or scan the network for all devices that respond to port 80 and try them one by one.

[onesillyhatch]

I tried posting last night but this site went down for maintenance.  I went to change the ethernet cable and when I grabbed the plug to unplug it the light on the ethernet port on the f16 lit up!!!  All this nonsense and it was just a bad connection.  Hence why the router wouldn't assign it an IP.  As soon as the light went on I was able to switch to dhcp and the falcon was assigned an IP address.  I immediately grabbed the MAC address and set up a static using IP reservation and switched the f16 back to static and boom it's working!!!  Thank you so much for those that tried to troubleshoot my stupidity.  It seems the simplest solution is usually the most difficult.

[djmc2002]

So I have a similar but somewhat different problem. I had to do a factory reset on my v2 blue and my OLED has gone bad. Do the F-16 have a default ip address? will it be in the 192 range?  

[JonD]

Manual suggests the following...

If DHCP is selected and there is a network
connection but no DHCP server, then the IP
address defaults to 192.168.1.50.

OLED replacement link
https://pixelcontroller.com/store/main/66-oled.html

[djmc2002]

Thanks for the tip, still trying to sort this out. Hope to have it fixed before the shows are suppose to start or it will be a big dark spot - lol.  Would the OLED work on a F16 V2 Blue? its not listed but looks the same.  Is it soldered in or do you know?

[JonD]

Would the OLED work on a F16 V2 Blue? its not listed but looks the same.

Sorry... the directions I gave you were for the blue V4 series.  The OLED works for the V3 and V4 series as I have replaced several.  Never owned a V2 and can't confirm.   It is a pin connector and no soldering for the V3 and V4 series at least.

[djmc2002]

Would the OLED work on a F16 V2 Blue? its not listed but looks the same.

Sorry... the directions I gave you were for the blue V4 series.  The OLED works for the V3 and V4 series as I have replaced several.  Never owned a V2 and can't confirm.  It is a pin connector and no soldering for the V3 and V4 series at least.

Checked it closely and appears to be soldered in - Darn.  And I still cant find this dam controller.  Not super smart on network so not sure if 192.168.1.50 will show up as my main network runs in 192.168.5.x. Wished I was sharper about the network side of this world

[jnealand]

I've also wondered about replacing the screen on my F16v2b.  I was thinking about trying to get the matching pin mating connector and soldering that on the board which would help long term.  I put off trying to work on that until I get a show running and that still has not happened.