diff for duplicates of <1471326942.3980.3.camel@synopsys.com>

diff --git a/a/1.txt b/N1/1.txt
index c9446a5..69e05ae 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,43 +1,43 @@
 Hello,
 
-On Mon, 2016-07-11@06:15 +0000, Alexey Brodkin wrote:
+On Mon, 2016-07-11 at 06:15 +0000, Alexey Brodkin wrote:
 > Hi Russel,
 > 
-> On Sun, 2016-07-10@00:19 -0700, Russell Senior wrote:
-> >?
-> > > > > > > "Alexey" == Alexey Brodkin <Alexey.Brodkin at synopsys.com> writes:
+> On Sun, 2016-07-10 at 00:19 -0700, Russell Senior wrote:
+> > 
+> > > > > > > "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
 > > Alexey> Hi Aaron,
-> > Alexey> On Sat, 2016-07-09@07:47 -0400, Aaron Z wrote:
-> > >?
+> > Alexey> On Sat, 2016-07-09 at 07:47 -0400, Aaron Z wrote:
+> > > 
 > > > > On Sat, Jul 9, 2016 at 4:37 AM, Alexey Brodkin
 > > > > <Alexey.Brodkin@synopsys.com> wrote:
-> > > > >?
+> > > > > 
 > > > > > Hello,
 > > > > > 
 > > > > > I was playing with quite simple bridged setup on different boards
 > > > > with > very recent kernels (4.6.3 as of this writing) and found one
 > > > > interesting > behavior that I cannot yet understand and googling
 > > > > din't help here as well.
-> > > > >?
+> > > > > 
 > > > > > My setup is pretty simple: >
-> > > > -------------???????------------------???????-------------------------
-> > > > >?
-> > > > > > HOST??????|???????| "Dumb AP"??????|???????| Wireless
-> > > > client???????| > > with DHCP |<----->(eth0)?????(wlan0)<----->|
-> > > > attempting to?????????| > > server????|???????|????\ br0
-> > > > /?????|???????| get settings via DHCP | >
-> > > > -------------???????------------------???????-------------------------
-> > > > > * HOST is my laptop with DHCP server that works for sure.??> *
+> > > > -------------       ------------------       -------------------------
+> > > > > 
+> > > > > > HOST      |       | "Dumb AP"      |       | Wireless
+> > > > client       | > > with DHCP |<----->(eth0)     (wlan0)<----->|
+> > > > attempting to         | > > server    |       |    \ br0
+> > > > /     |       | get settings via DHCP | >
+> > > > -------------       ------------------       -------------------------
+> > > > > * HOST is my laptop with DHCP server that works for sure.  > *
 > > > > "Dumb AP" is a separate board (I tried ARM-based Wandboard and
-> > > > ARC-based > ? AXS10x boards but results are exactly the same) with
-> > > > wired (eth0) and wireless > ? (wlan0) network controllers bridged
-> > > > together (br0). That "br0" bridge flawlessly > ? gets its settings
-> > > > from DHCP server on host.??> * Wireless client could be either a
-> > > > smatrphone or another laptop etc but > ? what's important it should
+> > > > ARC-based >   AXS10x boards but results are exactly the same) with
+> > > > wired (eth0) and wireless >   (wlan0) network controllers bridged
+> > > > together (br0). That "br0" bridge flawlessly >   gets its settings
+> > > > from DHCP server on host.  > * Wireless client could be either a
+> > > > smatrphone or another laptop etc but >   what's important it should
 > > > > be configured to get network settings by DHCP as well.
 > > > > > 
 > > > > > So what happens "br0" always gets network settings from DHCP server
-> > > > on HOST.??> That's fine. But wireless client only reliably gets
+> > > > on HOST.  > That's fine. But wireless client only reliably gets
 > > > > settings from DHCP server > if IPv6 is enabled on "Dumb AP" board. If
 > > > > IPv6 is disabled I may see that > wireless client sends "DHCP
 > > > > Discover" then server replies with "DHCP Offer" but > that offer
@@ -46,7 +46,7 @@ On Mon, 2016-07-11@06:15 +0000, Alexey Brodkin wrote:
 > > > > Do you have WDS enabled? If not, DHCP has issues in that scenario:
 > > > > https://wiki.openwrt.org/doc/howto/clientmode
 > > If the Dumb AP's wireless interface is in ap-mode, then this shouldn't
-> > be an issue.??It's only client-mode interfaces that have trouble with bridging.
+> > be an issue.  It's only client-mode interfaces that have trouble with bridging.
 > > 
 > > I'd suggest running tcpdump on the Dumb AP's wireless interface and the
 > > client's wireless interface and see which of them sees the various parts
@@ -57,27 +57,27 @@ On Mon, 2016-07-11@06:15 +0000, Alexey Brodkin wrote:
 > 
 > That's what I see on the server:
 > ----------------------------->8-------------------------------
-> No. Time????????Source?????Destination??????Protocol Length Info
-> ?3 0.151181000??0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 11 2.760796000??10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f
-> 14 5.220985000??0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 15 5.221150000??10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f
-> 23 15.649835000 0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 24 15.650017000 10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f
-> 32 25.648589000 0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 33 25.648758000 10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f
-> 43 35.864567000 0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 48 38.832837000 10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f
+> No. Time        Source     Destination      Protocol Length Info
+>  3 0.151181000  0.0.0.0    255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 11 2.760796000  10.42.0.1  10.42.0.13       DHCP     342    DHCP Offer    - Transaction ID 0x31dc321f
+> 14 5.220985000  0.0.0.0    255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 15 5.221150000  10.42.0.1  10.42.0.13       DHCP     342    DHCP Offer    - Transaction ID 0x31dc321f
+> 23 15.649835000 0.0.0.0    255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 24 15.650017000 10.42.0.1  10.42.0.13       DHCP     342    DHCP Offer    - Transaction ID 0x31dc321f
+> 32 25.648589000 0.0.0.0    255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 33 25.648758000 10.42.0.1  10.42.0.13       DHCP     342    DHCP Offer    - Transaction ID 0x31dc321f
+> 43 35.864567000 0.0.0.0    255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 48 38.832837000 10.42.0.1  10.42.0.13       DHCP     342    DHCP Offer    - Transaction ID 0x31dc321f
 > ----------------------------->8-------------------------------
 > 
 > That's on the wireless client:
 > ----------------------------->8-------------------------------
-> No.??Time???????????Source???Destination??????Protocol Length Info
-> 1171 94.192971000???0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 1182 99.263686000???0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 1185 109.692642000??0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 1186 119.691474000??0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
-> 1190 129.907507000??0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f
+> No.  Time           Source   Destination      Protocol Length Info
+> 1171 94.192971000   0.0.0.0  255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 1182 99.263686000   0.0.0.0  255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 1185 109.692642000  0.0.0.0  255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 1186 119.691474000  0.0.0.0  255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
+> 1190 129.907507000  0.0.0.0  255.255.255.255  DHCP     342    DHCP Discover - Transaction ID 0x31dc321f
 > ----------------------------->8-------------------------------
 > 
 > I'll try to capture data from Dumb AP sometime soon and will reply to the thread.
@@ -90,8 +90,8 @@ see those packets in tcpdump output - CPU never gets any information about them.
 
 I noticed that problem only happens if Ethernet PHY (in my case this is DP83865) doesn't have
 link established. I.e. either:
-?1) Cable is disconnected
-?2) PHY is still negotiation link mode
+ 1) Cable is disconnected
+ 2) PHY is still negotiation link mode
 
 Once PHY got link established GMAC happily enters promisq mode and all works as expected.
 
diff --git a/a/content_digest b/N1/content_digest
index 2a11d50..9d159a3 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,52 +3,58 @@
  "ref\01468065830.5007.10.camel@synopsys.com\0"
  "ref\087shviklio.fsf@husum.klickitat.com\0"
  "ref\01468217682.5588.4.camel@synopsys.com\0"
- "From\0Alexey.Brodkin@synopsys.com (Alexey Brodkin)\0"
- "Subject\0[LEDE-DEV] DHCP via bridge in case of IPv4\0"
+ "From\0Alexey Brodkin <Alexey.Brodkin@synopsys.com>\0"
+ "Subject\0Re: [LEDE-DEV] DHCP via bridge in case of IPv4\0"
  "Date\0Tue, 16 Aug 2016 05:57:28 +0000\0"
- "To\0linux-snps-arc@lists.infradead.org\0"
+ "To\0netdev@vger.kernel.org <netdev@vger.kernel.org>\0"
+ "Cc\0russell@personaltelco.net <russell@personaltelco.net>"
+  lede-dev@lists.infradead.org <lede-dev@lists.infradead.org>
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  davem@davemloft.net <davem@davemloft.net>
+  aczlan+ledev@gmail.com <aczlan+ledev@gmail.com>
+ " linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.org>\0"
  "\00:1\0"
  "b\0"
  "Hello,\n"
  "\n"
- "On Mon, 2016-07-11@06:15 +0000, Alexey Brodkin wrote:\n"
+ "On Mon, 2016-07-11 at 06:15 +0000, Alexey Brodkin wrote:\n"
  "> Hi Russel,\n"
  "> \n"
- "> On Sun, 2016-07-10@00:19 -0700, Russell Senior wrote:\n"
- "> >?\n"
- "> > > > > > > \"Alexey\" == Alexey Brodkin <Alexey.Brodkin at synopsys.com> writes:\n"
+ "> On Sun, 2016-07-10 at 00:19 -0700, Russell Senior wrote:\n"
+ "> >\302\240\n"
+ "> > > > > > > \"Alexey\" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:\n"
  "> > Alexey> Hi Aaron,\n"
- "> > Alexey> On Sat, 2016-07-09@07:47 -0400, Aaron Z wrote:\n"
- "> > >?\n"
+ "> > Alexey> On Sat, 2016-07-09 at 07:47 -0400, Aaron Z wrote:\n"
+ "> > >\302\240\n"
  "> > > > On Sat, Jul 9, 2016 at 4:37 AM, Alexey Brodkin\n"
  "> > > > <Alexey.Brodkin@synopsys.com> wrote:\n"
- "> > > > >?\n"
+ "> > > > >\302\240\n"
  "> > > > > Hello,\n"
  "> > > > > \n"
  "> > > > > I was playing with quite simple bridged setup on different boards\n"
  "> > > > with > very recent kernels (4.6.3 as of this writing) and found one\n"
  "> > > > interesting > behavior that I cannot yet understand and googling\n"
  "> > > > din't help here as well.\n"
- "> > > > >?\n"
+ "> > > > >\302\240\n"
  "> > > > > My setup is pretty simple: >\n"
- "> > > > -------------???????------------------???????-------------------------\n"
- "> > > > >?\n"
- "> > > > > > HOST??????|???????| \"Dumb AP\"??????|???????| Wireless\n"
- "> > > > client???????| > > with DHCP |<----->(eth0)?????(wlan0)<----->|\n"
- "> > > > attempting to?????????| > > server????|???????|????\\ br0\n"
- "> > > > /?????|???????| get settings via DHCP | >\n"
- "> > > > -------------???????------------------???????-------------------------\n"
- "> > > > > * HOST is my laptop with DHCP server that works for sure.??> *\n"
+ "> > > > -------------\302\240\302\240\302\240\302\240\302\240\302\240\302\240------------------\302\240\302\240\302\240\302\240\302\240\302\240\302\240-------------------------\n"
+ "> > > > >\302\240\n"
+ "> > > > > > HOST\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\240\302\240\302\240\302\240| \"Dumb AP\"\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\240\302\240\302\240\302\240| Wireless\n"
+ "> > > > client\302\240\302\240\302\240\302\240\302\240\302\240\302\240| > > with DHCP |<----->(eth0)\302\240\302\240\302\240\302\240\302\240(wlan0)<----->|\n"
+ "> > > > attempting to\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240| > > server\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\240\\ br0\n"
+ "> > > > /\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\240\302\240\302\240\302\240| get settings via DHCP | >\n"
+ "> > > > -------------\302\240\302\240\302\240\302\240\302\240\302\240\302\240------------------\302\240\302\240\302\240\302\240\302\240\302\240\302\240-------------------------\n"
+ "> > > > > * HOST is my laptop with DHCP server that works for sure.\302\240\302\240> *\n"
  "> > > > \"Dumb AP\" is a separate board (I tried ARM-based Wandboard and\n"
- "> > > > ARC-based > ? AXS10x boards but results are exactly the same) with\n"
- "> > > > wired (eth0) and wireless > ? (wlan0) network controllers bridged\n"
- "> > > > together (br0). That \"br0\" bridge flawlessly > ? gets its settings\n"
- "> > > > from DHCP server on host.??> * Wireless client could be either a\n"
- "> > > > smatrphone or another laptop etc but > ? what's important it should\n"
+ "> > > > ARC-based > \302\240 AXS10x boards but results are exactly the same) with\n"
+ "> > > > wired (eth0) and wireless > \302\240 (wlan0) network controllers bridged\n"
+ "> > > > together (br0). That \"br0\" bridge flawlessly > \302\240 gets its settings\n"
+ "> > > > from DHCP server on host.\302\240\302\240> * Wireless client could be either a\n"
+ "> > > > smatrphone or another laptop etc but > \302\240 what's important it should\n"
  "> > > > be configured to get network settings by DHCP as well.\n"
  "> > > > > \n"
  "> > > > > So what happens \"br0\" always gets network settings from DHCP server\n"
- "> > > > on HOST.??> That's fine. But wireless client only reliably gets\n"
+ "> > > > on HOST.\302\240\302\240> That's fine. But wireless client only reliably gets\n"
  "> > > > settings from DHCP server > if IPv6 is enabled on \"Dumb AP\" board. If\n"
  "> > > > IPv6 is disabled I may see that > wireless client sends \"DHCP\n"
  "> > > > Discover\" then server replies with \"DHCP Offer\" but > that offer\n"
@@ -57,7 +63,7 @@
  "> > > > Do you have WDS enabled? If not, DHCP has issues in that scenario:\n"
  "> > > > https://wiki.openwrt.org/doc/howto/clientmode\n"
  "> > If the Dumb AP's wireless interface is in ap-mode, then this shouldn't\n"
- "> > be an issue.??It's only client-mode interfaces that have trouble with bridging.\n"
+ "> > be an issue.\302\240\302\240It's only client-mode interfaces that have trouble with bridging.\n"
  "> > \n"
  "> > I'd suggest running tcpdump on the Dumb AP's wireless interface and the\n"
  "> > client's wireless interface and see which of them sees the various parts\n"
@@ -68,27 +74,27 @@
  "> \n"
  "> That's what I see on the server:\n"
  "> ----------------------------->8-------------------------------\n"
- "> No. Time????????Source?????Destination??????Protocol Length Info\n"
- "> ?3 0.151181000??0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 11 2.760796000??10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f\n"
- "> 14 5.220985000??0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 15 5.221150000??10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f\n"
- "> 23 15.649835000 0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 24 15.650017000 10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f\n"
- "> 32 25.648589000 0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 33 25.648758000 10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f\n"
- "> 43 35.864567000 0.0.0.0????255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 48 38.832837000 10.42.0.1??10.42.0.13???????DHCP?????342????DHCP Offer????- Transaction ID 0x31dc321f\n"
+ "> No. Time\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240Source\302\240\302\240\302\240\302\240\302\240Destination\302\240\302\240\302\240\302\240\302\240\302\240Protocol Length Info\n"
+ "> \302\2403 0.151181000\302\240\302\2400.0.0.0\302\240\302\240\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 11 2.760796000\302\240\302\24010.42.0.1\302\240\302\24010.42.0.13\302\240\302\240\302\240\302\240\302\240\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Offer\302\240\302\240\302\240\302\240- Transaction ID 0x31dc321f\n"
+ "> 14 5.220985000\302\240\302\2400.0.0.0\302\240\302\240\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 15 5.221150000\302\240\302\24010.42.0.1\302\240\302\24010.42.0.13\302\240\302\240\302\240\302\240\302\240\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Offer\302\240\302\240\302\240\302\240- Transaction ID 0x31dc321f\n"
+ "> 23 15.649835000 0.0.0.0\302\240\302\240\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 24 15.650017000 10.42.0.1\302\240\302\24010.42.0.13\302\240\302\240\302\240\302\240\302\240\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Offer\302\240\302\240\302\240\302\240- Transaction ID 0x31dc321f\n"
+ "> 32 25.648589000 0.0.0.0\302\240\302\240\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 33 25.648758000 10.42.0.1\302\240\302\24010.42.0.13\302\240\302\240\302\240\302\240\302\240\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Offer\302\240\302\240\302\240\302\240- Transaction ID 0x31dc321f\n"
+ "> 43 35.864567000 0.0.0.0\302\240\302\240\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 48 38.832837000 10.42.0.1\302\240\302\24010.42.0.13\302\240\302\240\302\240\302\240\302\240\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Offer\302\240\302\240\302\240\302\240- Transaction ID 0x31dc321f\n"
  "> ----------------------------->8-------------------------------\n"
  "> \n"
  "> That's on the wireless client:\n"
  "> ----------------------------->8-------------------------------\n"
- "> No.??Time???????????Source???Destination??????Protocol Length Info\n"
- "> 1171 94.192971000???0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 1182 99.263686000???0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 1185 109.692642000??0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 1186 119.691474000??0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
- "> 1190 129.907507000??0.0.0.0??255.255.255.255??DHCP?????342????DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> No.\302\240\302\240Time\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240Source\302\240\302\240\302\240Destination\302\240\302\240\302\240\302\240\302\240\302\240Protocol Length Info\n"
+ "> 1171 94.192971000\302\240\302\240\302\2400.0.0.0\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 1182 99.263686000\302\240\302\240\302\2400.0.0.0\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 1185 109.692642000\302\240\302\2400.0.0.0\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 1186 119.691474000\302\240\302\2400.0.0.0\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
+ "> 1190 129.907507000\302\240\302\2400.0.0.0\302\240\302\240255.255.255.255\302\240\302\240DHCP\302\240\302\240\302\240\302\240\302\240342\302\240\302\240\302\240\302\240DHCP Discover - Transaction ID 0x31dc321f\n"
  "> ----------------------------->8-------------------------------\n"
  "> \n"
  "> I'll try to capture data from Dumb AP sometime soon and will reply to the thread.\n"
@@ -101,8 +107,8 @@
  "\n"
  "I noticed that problem only happens if Ethernet PHY (in my case this is DP83865) doesn't have\n"
  "link established. I.e. either:\n"
- "?1) Cable is disconnected\n"
- "?2) PHY is still negotiation link mode\n"
+ "\302\2401) Cable is disconnected\n"
+ "\302\2402) PHY is still negotiation link mode\n"
  "\n"
  "Once PHY got link established GMAC happily enters promisq mode and all works as expected.\n"
  "\n"
@@ -112,4 +118,4 @@
  "\n"
  -Alexey
 
-0c6bf63977a785bd5e94dbc759564eeb0bb670827e3e5890b8b09663ec88e62b
+8cba80653cd066c1ac3acc9660f6c19e94f3c609c2aa5b629b3cf50b85d42014
