173399 2007-04-04 21:14 0000 net-misc/dhcpcd-2.0.5-r1 worked, net-misc/dhcpcd-3.0.16 doesn't 2007-04-11 20:12:02 0000 1 1 1 Unclassified Gentoo Linux Applications unspecified x86 Linux RESOLVED FIXED P2 normal --- 1 kim@runholt.dk uberlord@gentoo.org kim@runholt.dk 2007-04-04 21:14:27 0000 After upgrading dhcpcd from 2.0.5-r1 to 3.0.16, I can't get an IP address from my "3COM OfficeConnect Wireless Cable/DSL Gateway". I have tried both wireless and cabled connections. Downgrading dhcpcd "solves" the problem. Using 2.0.5: # dhcpcd -N -R -d eth0 Info, MAC address = 00:14:22:fa:96:93 Debug, broadcasting DHCP_DISCOVER Debug, dhcpIPaddrLeaseTime=43200 in DHCP server response. Debug, dhcpT1value is missing in DHCP server response. Assuming 21600 sec Debug, dhcpT2value is missing in DHCP server response. Assuming 37800 sec Debug, DHCP_OFFER received from ÿ (192.168.1.1) Debug, broadcasting DHCP_REQUEST for 192.168.1.248 Debug, dhcpIPaddrLeaseTime=43200 in DHCP server response. Debug, dhcpT1value is missing in DHCP server response. Assuming 21600 sec Debug, dhcpT2value is missing in DHCP server response. Assuming 37800 sec Debug, DHCP_ACK received from ÿ (192.168.1.1) Debug, broadcasting ARPOP_REQUEST for 192.168.1.248 Info, verified 192.168.1.248 address is not in use Info, your IP address = 192.168.1.248 Debug, orig hostname = kru3 Using 3.0.16: # dhcpcd -N -R -d eth0 Info, eth0: dhcpcd 3.0.16 starting Info, eth0: hardware address = 00:14:22:fa:96:93 Info, eth0: broadcasting for a lease Debug, eth0: sending DHCP_DISCOVER with xid 1256379199 Debug, eth0: waiting on select for 20 seconds Debug, eth0: sending DHCP_DISCOVER with xid 1256379199 Debug, eth0: sending DHCP_DISCOVER with xid 1256379199 Debug, eth0: sending DHCP_DISCOVER with xid 1256379199 Debug, eth0: sending DHCP_DISCOVER with xid 1256379199 Debug, eth0: sending DHCP_DISCOVER with xid 1256379199 Debug, eth0: sending DHCP_DISCOVER with xid 1256379199 Error, eth0: timed out Info, eth0: exiting # dhcpcd -N -R -d -l 43200 eth0 Info, eth0: dhcpcd 3.0.16 starting Info, eth0: hardware address = 00:14:22:fa:96:93 Info, eth0: broadcasting for a lease Debug, eth0: sending DHCP_DISCOVER with xid 602271590 Debug, eth0: waiting on select for 20 seconds Debug, eth0: sending DHCP_DISCOVER with xid 602271590 Debug, eth0: sending DHCP_DISCOVER with xid 602271590 Debug, eth0: sending DHCP_DISCOVER with xid 602271590 Debug, eth0: sending DHCP_DISCOVER with xid 602271590 Debug, eth0: sending DHCP_DISCOVER with xid 602271590 Debug, eth0: sending DHCP_DISCOVER with xid 602271590 Error, eth0: timed out Info, eth0: exiting Thanks. -- Kim Reproducible: Always Steps to Reproduce: uberlord@gentoo.org 2007-04-04 21:59:40 0000 Could you attach raw tcpdumps or wireshark traces for dhcpcd-2.0.5 and dhcpcd-3.0.16? If you would rather not attach them here, please email them to me. Thanks kim@runholt.dk 2007-04-04 22:08:20 0000 Created an attachment (id=115477) Wireshark dump kim@runholt.dk 2007-04-04 22:08:55 0000 Created an attachment (id=115478) Wireshark dump, shows failure uberlord@gentoo.org 2007-04-04 22:32:48 0000 Well, both look fine. Could you try requesting an infinite least time? dhcpcd -N -R -d -l -1 eth0 kim@runholt.dk 2007-04-04 22:38:04 0000 Same result: # dhcpcd -N -R -d -l -1 eth0 Info, eth0: dhcpcd 3.0.16 starting Info, eth0: hardware address = 00:14:22:fa:96:93 Info, eth0: broadcasting for a lease Debug, eth0: sending DHCP_DISCOVER with xid 916755478 Debug, eth0: waiting on select for 20 seconds Debug, eth0: sending DHCP_DISCOVER with xid 916755478 Debug, eth0: sending DHCP_DISCOVER with xid 916755478 Debug, eth0: sending DHCP_DISCOVER with xid 916755478 Debug, eth0: sending DHCP_DISCOVER with xid 916755478 Debug, eth0: sending DHCP_DISCOVER with xid 916755478 Debug, eth0: sending DHCP_DISCOVER with xid 916755478 Error, eth0: timed out Info, eth0: exiting kim@runholt.dk 2007-04-05 07:56:44 0000 I experimented with different parameters and finally got it to work. It seems that my cable router expects "large requests": FAILS: dhcpcd -N -R -d -i "12345678901234567890123456789012345" eth0 WORKS: dhcpcd -N -R -d -i "123456789012345678901234567890123456" eth0 FAILS: dhcpcd -N -R -d -h "12345678901234567890123456" eth0 WORKS: dhcpcd -N -R -d -h "123456789012345678901234567" eth0 FAILS: dhcpcd -N -R -d -u "1234567890123456789" eth0 WORKS: dhcpcd -N -R -d -u "12345678901234567890" eth0 FAILS: dhcpcd -N -R -d -I "1234567890123456789012345678" eth0 WORKS: dhcpcd -N -R -d -I "12345678901234567890123456789" eth0 FAILS: dhcpcd -N -R -d -I x -h x -u "" -i 1234567890123456789012345678901234567890 eth0 WORKS: dhcpcd -N -R -d -I x -h x -u "" -i 12345678901234567890123456789012345678901 eth0 FAILS: dhcpcd -N -R -d -I x -h x -u "" -l -1 -i 1234567890123456789012345678901234 eth0 WORKS: dhcpcd -N -R -d -I x -h x -u "" -l -1 -i 12345678901234567890123456789012345 eth0 FAILS: dhcpcd -N -R -d -I 12345678901 -h 12345678901 -u 1234567890 -i 1234567890 eth0 WORKS: dhcpcd -N -R -d -I 12345678901 -h 12345678901 -u 12345678901 -i 1234567890 eth0 WORKS: dhcpcd -N -R -d -I 123456789012345678901234567890123456789012345678 -h 12345678901234567890123456789012345678901234567890 -u 12345678901234567890123456789012345678901234567890 -i 123456789012345678901234567890123456789012345678 eth0 So just by specifying a long vendor ID, I got it to work: # dhcpcd -N -R -d -i 123456789012345678901234567890123456 eth0 Info, eth0: dhcpcd 3.0.16 starting Info, eth0: hardware address = 00:14:22:fa:96:93 Info, eth0: broadcasting for a lease Debug, eth0: sending DHCP_DISCOVER with xid 1771614337 Debug, eth0: waiting on select for 20 seconds Debug, eth0: got a packet with xid 1771614337 Debug, eth0: no facility to parse DHCP code 52 Info, eth0: offered 192.168.1.248 from 192.168.1.1 `ÿ' Debug, eth0: sending DHCP_REQUEST with xid 1771614337 Debug, eth0: waiting on select for 19 seconds Debug, eth0: got a packet with xid 1771614337 Debug, eth0: no facility to parse DHCP code 52 Error, eth0: given MTU 64 is too low, minium is 576 Info, eth0: leased 192.168.1.248 for 43200 seconds Info, eth0: no renewal time supplied, assuming 21600 seconds Info, eth0: no rebind time supplied, assuming 37800 seconds Debug, eth0: setting MTU to 576 Info, eth0: adding IP address 192.168.1.248/24 Info, eth0: adding default route via 192.168.1.1 metric 0 Debug, eth0: no dns information to write Debug, eth0: writing /var/lib/dhcpcd/dhcpcd-eth0.info Debug, eth0: forking to background I suspect that the cable router is to blame. Thanks anyway. Let me know if you need help trying something out on such a router. -- Kim uberlord@gentoo.org 2007-04-05 08:47:02 0000 Ah, and another faulty MTU sender too! dhcpcd-3.0.17 will handle this a little better by simply ignoring values <576 instead of setting 576. It will also have an option just to ignore it. Do you want to open an upstream bug or ticket and reference it here or should we just close this? kim@runholt.dk 2007-04-05 09:05:23 0000 (In reply to comment #7) If the router is to blame, then this bug should be closed. My problem has been solved (worked-around), so I'm happy. It does, however, appear that the way dhcpcd-2.0.5 worked is more robust against faulty servers... uberlord@gentoo.org 2007-04-05 09:26:43 0000 (In reply to comment #8) > (In reply to comment #7) > > If the router is to blame, then this bug should be closed. > My problem has been solved (worked-around), so I'm happy. > > It does, however, appear that the way dhcpcd-2.0.5 worked is more robust > against faulty servers... Well, so far just this one. dhcpcd-3.x works against 3 servers that 1.x and 2.x didn't, so it's a silly argument anyway. Ah well. I'm pretty sure it is a server issue as there is no minimum DHCP packet size as such. olger901@gmail.com 2007-04-11 16:57:23 0000 I am having the exact same problem, dhcpcd-3.0.16 does not work, a dhcp request just times out, and when I revert back to dhcpcd-2.0.5 everything works fine. uberlord@gentoo.org 2007-04-11 17:05:40 0000 (In reply to comment #10) > I am having the exact same problem, dhcpcd-3.0.16 does not work, a dhcp request > just times out, and when I revert back to dhcpcd-2.0.5 everything works fine. And if you create a long packet as above it works? What router/AP are you using? olger901@gmail.com 2007-04-11 17:49:52 0000 I am using a Conceptronic C100BRS4 router, and yes, it does seem to be solving the problem. olger901@gmail.com 2007-04-11 17:54:39 0000 BTW: My notebook is a Dell Inspiron 6400 with Broadcom 440 100Mbps LAN card and an Intel IPW3945 wireless card (both showing the same symptoms) in case you need to know. uberlord@gentoo.org 2007-04-11 17:56:54 0000 OK I'll re-open this olger901@gmail.com 2007-04-11 18:16:38 0000 BTW: I dont know if its going to be fixed, but if its not going to be fixed, I would like to suggest to add some sort of compatibility flag, which you can define in your /etc/conf.d/net For example adding the option dhcpcompat which will send a long request then. kim@runholt.dk 2007-04-11 18:28:28 0000 I think an even simpler solution would be to change the default vendor ID. For me, dhcpcd-2.0.5 uses the vendor ID string "Linux 2.6.19-gentoo-r5 i686". dhcpcd-3.0.16 uses the string "dhcpcd 3.0.16". While it was a coincidence, that version 2.0.5 worked for me, the long string was a blessing. If it hadn't worked, I would probably never had figured out how to get version 3.0.16 to work. So if dhcpcd was changed to default to a long vendor ID string, some failing situations would be avoided while I don't think new failing situations would arise. I think that would be a better solution than a new configuration parameter which does the same as "-i <long string>" uberlord@gentoo.org 2007-04-11 18:35:46 0000 Created an attachment (id=115987) Define a minimum packet length This patch adds a define for a minimum packet length. The default packet my PC sends is 276 bytes, but the BOOTP spec has a minimum size of 300 bytes. Of course, the this restriction is gone in DHCP spec, but I think this is the real error. If the patch fails, try a larger number like say 500 and then decrease until we find the magic number kim@runholt.dk 2007-04-11 18:50:48 0000 (In reply to comment #17) I can confirm that the patch solves the problem for me. uberlord@gentoo.org 2007-04-11 20:12:02 0000 Fixed in -r1, thanks 115477 2007-04-04 22:08 0000 Wireshark dump dhcpcd-2.0.5-works application/octet-stream 1MOyoQIABAAAAAAAAAAAAP//AAABAAAALwwURqbPBwBOAgAATgIAAP///////wAUIvqWkwgARQAC QBuKAABAEV0kAAAAAP////8ARABDAiwiuAEBBgAm4sJWAAoAAAAAAAAAAAAAAAAAAAAAAAAAFCL6 lpMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY4JTYzUBATkCAkAzBP////83DwEDBgwP ERccHR8hKCkqdzwbTGludXggMi42LjE5LWdlbnRvby1yNSBpNjg2PQcBABQi+paT/wAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAALwwURqXZBwA8AAAAPAAAAP///////wALrOVEMAgGAAEIAAYEAAEAC6zlRDDAqAEBAAAAAAAA wKgB+DTtbwB4y3EAAluymgALrOVEMDAMFEaT0gcATgIAAE4CAAD///////8AFCL6lpMIAEUAAkAb iwAAQBFdIwAAAAD/////AEQAQwIsDSMBAQYAJuLCVgAKAAAAAAAAAAAAAAAAAAAAAAAAABQi+paT AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGOCU2M1AQM5AgJANgTAqAEBMgTAqAH4MwQA AKjANw8BAwYMDxEXHB0fISgpKnc8G0xpbnV4IDIuNi4xOS1nZW50b28tcjUgaTY4Nj0HAQAUIvqW k/8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ADAMFEYM6AcAPAAAADwAAAD///////8AFCL6lpMIBgABCAAGBAABABQi+paTAAAAAAAAAAAAAMCo AfgAAAAAAAAAAAAAAAAAAAAAAAAwDBRGxq8IADwAAAA8AAAA////////ABQi+paTCAYAAQgABgQA AQAUIvqWkwAAAAAAAAAAAADAqAH4AAAAAAAAAAAAAAAAAAAAAAAAMAwURg95CQA8AAAAPAAAAP// /////wAUIvqWkwgGAAEIAAYEAAEAFCL6lpMAAAAAAAAAAAAAwKgB+AAAAAAAAAAAAAAAAAAAAAAA ADAMFEaKRAoAPAAAADwAAAD///////8AFCL6lpMIBgABCAAGBAABABQi+paTAAAAAAAAAAAAAMCo AfgAAAAAAAAAAAAAAAAAAAAAAAAwDBRGVg8LADwAAAA8AAAA////////ABQi+paTCAYAAQgABgQA AQAUIvqWkwAAAAAAAAAAAADAqAH4AAAAAAAAAAAAAAAAAAAAAAAAMAwURmHjCwA8AAAAPAAAAP// /////wAUIvqWkwgGAAEIAAYEAAIAFCL6lpPAqAH4AAus5UQw/////wAAAAAAAAAAAAAAAAAAAAAA ADAMFEbQ7AsAPAAAADwAAAD///////8AFCL6lpMIBgABCAAGBAABABQi+paTwKgB+AAAAAAAAMCo AQEAAAAAAAAAAAAAAAAAAAAAAAA= 115478 2007-04-04 22:08 0000 Wireshark dump, shows failure dhcpcd-3.0.16-fails application/octet-stream 1MOyoQIABAAAAAAAAAAAAP//AAABAAAAcRAURv7OBgBGAQAARgEAAP///////wAUIvqWkwgARRAB NwAAAABAEXmnAAAAAP////8ARABDASPYwwEBBgB9BW1MAAAAAAAAAAAAAAAAAAAAAAAAAAAAFCL6 lpMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY4JTYzUBATMEAACowDcBBgwEa3J1MzwN ZGhjcGNkIDMuMC4xNj0HAQAUIvqWk/98dBAURlDOBgBGAQAARgEAAP///////wAUIvqWkwgARRAB NwAAAABAEXmnAAAAAP////8ARABDASPYwAEBBgB9BW1MAAMAAAAAAAAAAAAAAAAAAAAAAAAAFCL6 lpMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY4JTYzUBATMEAACowDcBBgwEa3J1MzwN ZGhjcGNkIDMuMC4xNj0HAQAUIvqWk/9IdhAURuEbAwA8AAAAPAAAAAATAluymgALrOVEMAgARQAA HXDWAABwESy81YEVIsCoAfIRlBGUAAkAAP8AAAAAAAAAAAAAAAAAAAAAAHcQFEbIzgYARgEAAEYB AAD///////8AFCL6lpMIAEUQATcAAAAAQBF5pwAAAAD/////AEQAQwEj2L0BAQYAfQVtTAAGAAAA AAAAAAAAAAAAAAAAAAAAABQi+paTAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGOCU2M1 AQEzBAAAqMA3AQYMBGtydTM8DWRoY3BjZCAzLjAuMTY9BwEAFCL6lpP/wHgQFEbYiwUALwAAAC8A AAAAC6zlRDAAEwJbspoIAEUAACEyckAAQBFbHMCoAfLVgRUiEZQRlAANMG0AAAAA/3oQFEYqzwYA RgEAAEYBAAD///////8AFCL6lpMIAEUQATcAAAAAQBF5pwAAAAD/////AEQAQwEj2LoBAQYAfQVt TAAJAAAAAAAAAAAAAAAAAAAAAAAAABQi+paTAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AGOCU2M1AQEzBAAAqMA3AQYMBGtydTM8DWRoY3BjZCAzLjAuMTY9BwEAFCL6lpP/VH0QFEZczwYA RgEAAEYBAAD///////8AFCL6lpMIAEUQATcAAAAAQBF5pwAAAAD/////AEQAQwEj2LcBAQYAfQVt TAAMAAAAAAAAAAAAAAAAAAAAAAAAABQi+paTAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AGOCU2M1AQEzBAAAqMA3AQYMBGtydTM8DWRoY3BjZCAzLjAuMTY9BwEAFCL6lpP/eH8QFEboGgMA PAAAADwAAAAAEwJbspoAC6zlRDAIAEUAAB1w4AAAcBEsstWBFSLAqAHyEZQRlAAJAAD/AAAAAAAA AAAAAAAAAAAAAACAEBRGTNAGAEYBAABGAQAA////////ABQi+paTCABFEAE3AAAAAEAReacAAAAA /////wBEAEMBI9i0AQEGAH0FbUwADwAAAAAAAAAAAAAAAAAAAAAAAAAUIvqWkwAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAABjglNjNQEBMwQAAKjANwEGDARrcnUzPA1kaGNwY2QgMy4wLjE2 PQcBABQi+paT/0yBEBRGAS4NAC8AAAAvAAAAAAus5UQwABMCW7KaCABFAAAhMnNAAEARWxvAqAHy 1YEVIhGUEZQADTBtAAAAAP+DEBRGctAGAEYBAABGAQAA////////ABQi+paTCABFEAE3AAAAAEAR eacAAAAA/////wBEAEMBI9ixAQEGAH0FbUwAEgAAAAAAAAAAAAAAAAAAAAAAAAAUIvqWkwAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABjglNjNQEBMwQAAKjANwEGDARrcnUzPA1kaGNwY2Qg My4wLjE2PQcBABQi+paT/yA= 115987 2007-04-11 18:35 0000 Define a minimum packet length dhcpcd-300.patch text/plain SW5kZXg6IGRoY3AuYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBkaGNwLmMJKHJldmlzaW9uIDE4OCkKKysrIGRo Y3AuYwkod29ya2luZyBjb3B5KQpAQCAtMzgsNiArMzgsNyBAQAogI2luY2x1ZGUgImxvZ2dlci5o IgogI2luY2x1ZGUgInNvY2tldC5oIgogCisjZGVmaW5lIERIQ1BfUEFDS0VUX0xFTlRIX01JTiAz MDAKICNkZWZpbmUgQlJPQURDQVNUX0ZMQUcgMHg4MDAwCiAKIHN0YXRpYyBjb25zdCBjaGFyICpk aGNwX21lc3NhZ2VbXSA9IHsKQEAgLTI2Niw2ICsyNjcsMTEgQEAKIAogICAqcCsrID0gREhDUF9F TkQ7CiAKKyNpZmRlZiBESENQX1BBQ0tFVF9MRU5USF9NSU4KKyAgd2hpbGUgKHAgLSBtIDwgREhD UF9QQUNLRVRfTEVOVEhfTUlOKQorCSAgKnArKyA9IDA7CisjZW5kaWYKKyAgCiAgIG1lc3NhZ2Vf bGVuZ3RoID0gcCAtIG07CiAKICAgbWVtc2V0ICgmcGFja2V0LCAwLCBzaXplb2YgKHN0cnVjdCB1 ZHBfZGhjcF9wYWNrZXQpKTsK