Modify

Opened 4 years ago

Last modified 21 months ago

#13581 new defect

no WAN DHCP lease in Attitude Adjustment (against Verizon FIOS)

Reported by: j295@… Owned by: developers
Priority: high Milestone: Barrier Breaker 14.07
Component: base system Version: Trunk
Keywords: Cc:

Description

Summary: no WAN DHCP lease in Attitude Adjustment (against Verizon FIOS)

Problem: new install of Attitude Adjustment won't connect to the WAN
because it doesn't get a DHCP lease.

Things worked fine with backfire 10.03.1

Steps to reproduce:

  1. install AA
  2. connect to provider like Verizon FIOS that wants a MAC address
  3. by default, clientid is not set, so udhcp runs with -C
  4. total rejection from Verizon

Problem frequency: Happens every time with AA.

Expected behavior: dhcp gets a lease.

Observed behavior: infinite dhcp retries with no response from the ISP.

With Backfire, if clientid was not set, there was no -C
and all works well.

Fix: remove the -C in /lib/netifd/proto/dhcp.sh
(I will attach a patch.)

Presumably someone actually WANTS the -C option,
so restoring that would require another configuration option in LuCI.

Attachments (5)

dhcp.sh.patch (442 bytes) - added by j295@… 4 years ago.
patch to dhcp.sh to remove -C
dhcp.sh-none.patch (697 bytes) - added by j295@… 4 years ago.
dhcp.sh-none.2.patch (691 bytes) - added by j295@… 4 years ago.
patch correction
func.php (2.8 KB) - added by Slavon 3 years ago.
http://graco-duoglider-stroller.com
dhcp.sh-150411.patch (963 bytes) - added by johnh295 2 years ago.
patch /lib/netifd/proto/dhcp.sh to support "noc" option for FIOS

Download all attachments as: .zip

Change History (25)

Changed 4 years ago by j295@…

patch to dhcp.sh to remove -C

comment:1 in reply to: ↑ description Changed 4 years ago by hnyman <hannu.nyman@…>

Replying to j295@…:

Presumably someone actually WANTS the -C option,


See bug #12426 and changeset r34089 & r34090

comment:2 Changed 4 years ago by anonymous

Yes, #12426 had an ISP that didn't want it.
But mine insists upon it.
Interpreting an empty clientid as -C breaks my configuration.
Rather than changing the default from backfire, IMHO there should be a new option to enable -C.
A simple way to do this is to interpret "none" as -C.

I'll attach a patch that does this, although the LuCI UI needs to announce this change.

Changed 4 years ago by j295@…

comment:3 Changed 4 years ago by hnyman <hannu.nyman@…>

Isn't that patch buggy?

x*) clientid="-x 0x3d:${clientid:/}";;

should be

x*) clientid_opt="-x 0x3d:${clientid:/}";;

right?

Changed 4 years ago by j295@…

patch correction

comment:4 Changed 4 years ago by anonymous

This patch fixes issues with users unable to get DHCP leases from Verizon FIOS as well as Canadian cable providers such as my situation, Hopefully this does not get overlooked.

comment:5 Changed 4 years ago by anonymous

I added these lines and I still can't get an WAN ip address from Verizon. Do I also need to make this change:

config (/etc/config/network):

config 'interface' 'wan'

option 'ifname' 'eth0'
option 'proto' 'dhcp'
option 'clientid' '01:mm:aa:cc:aa:dd:rr'

Note, the client ID needs to start with 01, followed by the MAC address of the interface.

comment:6 Changed 4 years ago by anonymous

Thanks, 'dhcp.sh-none.2.patch'​ fixed my problem.

The problem I had was that I could not access the router when the wan was plugged into my cable tv provider. I had to disconnect the wan, apply the patch, then restart the router and then everything was ok.

comment:7 Changed 4 years ago by anonymous

Can we look at back porting this fix to AA final? The release version of the product doesn't work due to the -C option.

comment:8 Changed 4 years ago by tschmelcher

Telus in Canada demands the default clientid too. Had a terrible time upgrading to AA because of this bug. Please include the fix in 12.09.1.

comment:9 Changed 4 years ago by anonymous

Hello all,
I've tried all of the suggestions above to fix the DHCP issue with Verizon Fios to no avail. What are the specific changes that need to be made to fix this issue? If I wanted to issue the udchpc command from the CLI, what would it look like? I’ve tried different variations. The dhcp.sh-none.2.patch didn’t fix the issue. In the changes listed, I didn’t see the ‘clientid_opt’ variable declared. I’ve tried running the dhcp.sh script by itself and am getting an error. For testing should we be able to run the dhcp.sh script to get an address from Verizon? Honestly, I’ve been looking on the wiki daily to see if a new update is coming or announced.
Thanks

comment:10 Changed 3 years ago by anonymous

I don't think this is just a config issue. I have two routers with the same version of OpenWrt Attitude Adjustment 12.09 with identical /lib/netifd/proto/dhcp.sh file (unchanged from the original). One router (Buffalo WHR-HP-G300N) gets DHCP lease from the cable modem (in bridged mode), but the other router (TP-LINK TL-WDR4300) gets nothing.

comment:11 follow-up: Changed 3 years ago by g00dy

I agree, this is not a configuration problem. I've tried all of the suggested fixes above to no avail. I'm using a DIR-825 with Verizon's FIOS network. It will work just find running 10.0.3.1. When I load 10.0.9 it doesn't. I've tried the command line:

udhcpc -p /var/run/udhcpc-eth1.pid -s /lib/netifd/dhcp.script -f -t 0 -i eth1 -x 0x3d:01AABBCCDDEEFF

Not working. I could plug in a sniffer and to capture some packets, but I'm hoping that somebody could show a command line that work.

comment:12 in reply to: ↑ 11 Changed 3 years ago by g00dy

Replying to g00dy:

I agree, this is not a configuration problem. I've tried all of the suggested fixes above to no avail. I'm using a DIR-825 with Verizon's FIOS network. It will work just find running 10.0.3.1. When I load 10.0.9 it doesn't. I've tried the command line:

udhcpc -p /var/run/udhcpc-eth1.pid -s /lib/netifd/dhcp.script -f -t 0 -i eth1 -x 0x3d:01AABBCCDDEEFF

Not working. I could plug in a sniffer and to capture some packets, but I'm hoping that somebody could show a command line that work.

Sorry, I meant to say: Does anybody know that the command line should be for
"udhcpc" on Verizon fios? I would like to rule out a configuration file issue if possible, before starting look to look at pcap files of dhcp requests. If this is not a configuration issue, then it is a protocol problem with udhcpc.

Thanks

comment:13 Changed 3 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:14 Changed 2 years ago by johnh295

This problem persists with Barrier Breaker, for users of Verizon FIOS.
Any chance of getting the fix added?

comment:15 Changed 2 years ago by austin@…

I'd like this fixed as well, I have FIOS. I tried applying the patch but the first chunk failed.

Changed 2 years ago by johnh295

patch /lib/netifd/proto/dhcp.sh to support "noc" option for FIOS

comment:16 Changed 2 years ago by johnh295

Wrt comment:15: You might try dhcp.sh-150411.patch, against BB.

It differs from the prior patches: an empty clientid sends -C (same as AA and BB). A value in clientid sends it. THe special clientid "noc" suppresses the -C and is required to make FIOS work.

comment:17 Changed 2 years ago by austin@…

Thanks for the patch! I applied it successfully. Unfortunately it still doesn't work. My /etc/config/network:

config interface 'wan'

option ifname 'eth0'
option proto 'dhcp'
option clientid 'noc'

I verified that udhcpc didn't have the -C option by using ps. I noticed it set the MAC address properly so didn't include that line. For hardware I use a TP-Link Archer C7. I hope someone can help.

comment:18 Changed 2 years ago by anonymous

I believe Verizon locks service to the MAC of the router they sent you. If you use a different router, you should clone the MAC addr of theirs. One can do that with an "option macaddr 'aa:bb:cc:dd:ee:ff'" in the config interface 'wan' section, where aa:bb:cc:dd:ee:ff is that of the Verizon router.

comment:19 Changed 2 years ago by austin@…

Wow, they don't make it easy! I didn't have to do this when I installed Tomato on my current router. I'll give it a try though.

comment:20 Changed 21 months ago by johnh295

This bug still persists in Chaos Calmer-rc3.
It would be nice to pick up the patch dhcp.sh-150411.patch
to perhaps help some other Vierzon users (although Apparently not austin).
I had to reapply it now aginst CC-rc3.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.