DHCP doesn't work

[dsimboss]

Hello there,

my setup:
A WLAN router I don't have access to, my own WLAN router and several devices that need to connect to it.

what I want:
Because some of my devices only have a LAN port, I wanted to use my router to connect wirelessly to the other one. Now my router should create a new subnetwork, i.e. create a WLAN AP and provide the network via LAN.

The problem:
It doesn't work. I tried to use the gateway settings within the gargoyle router firmware.
Here my different tries to solve the setup:

1. Since the main router supports DHCP, I tried 'Connect Via: DHCP (Wireless)'. Here the problem occurs that my gargoyle router doesn't get an IP address via DHCP (the WAN IP on the status page is empty and the internet doesn't work).
2. Then I used 'Connect Via: Static IP (Wireless)'. Here the following problem occurs: My gargoyle router does in fact connect to the main network, but it doesn't have the right DNS server (I set the main router IP as gateway).
3. Now, I changed the DNS settings from Default to Custom and added the main router. This seems to work for now.

During all those tries, I didn't change the settings how to connect to the main router (WPA PSK, SSID, password etc.) and how to create the new AP.

Another strange issue that seems to be fixed with the 1.5.4 version: When using the 1.5.3 version, the LAN clients directly connected to my gargoyle router didn't get an IP address via DHCP. The router logs said that it had been broadcasted, but it didn't.

Perhaps someone has an idea? Thanks in advance!
If any information is missing, please ask and I will provide it as soon as possible!

Greetings

David

[pbix]

Perhaps it will not help you much but I have tried this with my WRT54GL running v1.5.4. It takes a few moments but my router obtains a WAN IP address from my main router when I set WAN access to DHCP (Wireless).

So I cannot reproduce your problem.

When I have had problems in the past it has been because I did not have the password set correctly to access the main router. It seems this may not be your problem since you indicated that you checked it.

You did not mention what router you are using.

[dsimboss]

Good idea. I will try this later and give it hopefully enough time to connect.

You did not mention what router you are using.

I'm using a TP-LINK TL-WR1043ND.

I will post the result as soon as I'm done.

[dsimboss]

Now, after one hour of waiting, it clearly doesn't connect via DHCP (wireless).

What it says:

Code: Select all

WAN IP Address:
WAN Netmask:
WAN MAC Address: F6:EC:38:CB:5B:DF
WAN Gateway IP:
WAN DNS Server(s): 192.168.1.1

So, it doesn't work and I don't have any idea why (and I do not know how this wrong DNS server is set, too...).

I also attached a screenshot of my current configuration (that DOES work) and explained some of the settings.

[pbix]

So how do you know that your main router supports DHCP?

I do not have the TL-1043D routers so I cannot test myself on your exact hardware. But if you have another router that can connect to the WAN you can design an experiment to determine if the problem is on the Gargoyle side or the WAN router side of the equation.

[dsimboss]

So how do you know that your main router supports DHCP?

My notebook and my smartphone can connect to the main router without any problems. They both get their IP address via DHCP, so I guess the main router's DHCP works fine.

[DoesItMatter]

You need to connect that TP-Link to the main router via LAN cable
and verify that it will get issued a DHCP IP through wired connect.

If it won't get a DHCP IP wired, try flashing back to stock firmware
then do another test.

Some routers and/or firmwares are incompatible - just happens.

By the way - is that a valid MAC address?

WAN MAC Address: F6:EC:38:CB:5B:DF

http://hwaddress.com/?q=%09TP-LINK+TECH ... CO.%2C+LTD

[dsimboss]

You need to connect that TP-Link to the main router via LAN cable
and verify that it will get issued a DHCP IP through wired connect.

If it won't get a DHCP IP wired, try flashing back to stock firmware
then do another test.

I will test this later.

By the way - is that a valid MAC address?

WAN MAC Address: F6:EC:38:CB:5B:DF

Good question. It doesn't appear to be a valid MAC address.
How can this happen?

[lippmannmax]

Yes, some people know, that I have the same problem.


for comparison, here is my WAN MAC Adress: 74-EA-3A-D1-30-C7

I also can't find the mac on the link from 'DoesItMatter'.

[dsimboss]

Strange behaviour: If I use the Wireless Bridge/Repeater Option, it DOES connect to the main router via DHCP.

That doesn't help me, because I need to have the setup described in my first post. But it is clearly strange...