Here we go again.
Again? Meanwhile while Marto and his paid shill or multiple account Loshia continue to spam threads... What does Technobit do? They ignore another customer. Best to avoid this company people don't risk your BTC. [/size] Meanwhile, he shipped my stuff Tuesday. I admit he needed a little pushing, but it happened. He actually did what he has done for long, produce and ship hardware. Now it's your turn to get something going bick, fees from others or collecting other people's comments, twisting words and adding a lot of lies to build some sort of authority, it ain't working. Nice said are you paid shill like me buddy Marto has a big PR pocket obviously
|
|
|
got it running now that I know new version doesn't fill gaps if settings are kept will check on next update.
Cool
|
|
|
no don't have a rocker so didn't look in that one That is the problem. when upgrading your old cgminer config is kept. without rocker config it will not start 1. Upgrade 2. Check all cgminer web tabs and leve nothing blank. Just fill default values as suggested. That is enough 3. exec fix_rc - it will reboot the tplink 4. Enjoy 5. And do not use dhcp client of course Finaly: If all works do not touch it leve old version
|
|
|
http://technobit.eu/0_4_0.rar* 0.4.0 * Known Issues reported by users: 1. dhcp client my brick your router - do not use it 2. Openwrt failsafe mode is not working 3. Startup scripts are messed up during upgrade. Fix them via web or check and execute /usr/bin/fix_rc. Minimum is (s)cgminer and udev (Hotplug) to be enabled during startup * cgminer for hex BTC Miners - patch to cgminer 4.6.1 rev_9afd0a216a0f95adb650e4818f24af1a61ad837d.patch * cgminer for hex Scrypt Miners - patch to cgminer 4.6.1 srev_9afd0a216a0f95adb650e4818f24af1a61ad837d.patch * cgminer - HEXR driver production release * Compile Rocker HEXR ./autogen.sh ..... --enable-hexminerr * Rocker (HEXR) new cgminer config options --hexminerr-asic-diff use at least 16 here and meake sure your pool worker min difficulty is configured accourdingly in order not to loose hash rate --hexminerr-pic-roll - Default: 60 or 90. MicroChip PIC work internal roll count - Reduces dramatically USB load - range 0-255. Please use at least 10 or 20 here --hexminerr-chip-mask - 255 enable all chips --hexminerr-voltage - core voltage Default: 690 --hexminerr-options chip_count:frequency Default: 4:650 * openwrt - New HEXR web config tabs to reflect above * openwrt updated to 42657 Todo * Fix dhcp,failsafe and startup scripts when time alows * Fix bugs HEXR (Spondoolies-Tech Rocker ASICs) in preparation for board launch - done done the new update and the minoin did not start the settings are the same as before had to roll back to the last update. Did you fill blanks in the Rocker cgminer config? Did you fix startup scripts? you can always ssh to tplink and exec screen -r btc it will tell you what went wrong
|
|
|
I receive this today, and i'm trying to run it, I have already turn it on, but using this tutorial: https://bitcointalk.org/index.php?topic=586166.20Cgminer says that failed to initialize the hexminer 3 and hexminer 8... what's happening? anyone can help me please? you need to fill all boxes in cgminer setup including miners you do not have How do I do that? the error that I see is this in the image: Check this guide and download the latest build: https://bitcointalk.org/index.php?topic=569689Still the same error... Run this as administrator dude
|
|
|
- [2014-09-23 17:32:05] Started cgminer 4.5.0 [2014-09-23 17:32:06] No devices detected! [2014-09-23 17:32:06] Waiting for USB hotplug devices or press q to quit [2014-09-23 17:32:06] Probing for an alive pool [2014-09-23 17:32:08] Pool 0 difficulty changed to 32 [2014-09-23 17:32:09] Network diff set to 29.8G [2014-09-23 17:32:14] API running in IP access mode on port 4028 (12) [2014-09-23 17:32:56] Pool 0 difficulty changed to 8 [2014-09-23 17:32:56] Stratum from pool 0 requested work restart
this all right?
No Miner is not connected
|
|
|
We'll order samples for sure Will see where it goes Right in the shitter with so many more of your projects. How about giving people what they order before ramping up production on another DOA miner? Hey bickLEDski, We all know that the main reason for doa miners is the chip price. I am talking in general. You are the one who was receiving free chips in quantities right? And what you have blinking LEDs alive on arival right Ops I beg your pardon it was just a YouTube video and no one has seen them alive So let me remind you that Christmas is coming so get your ass back to work. Walmart is waiting for your LEDs. You know I remember the picture of you wasp pool with the bug behind your ass https://bitcointa.lk/threads/the-wasp-project-collective-information-thread.240650/page-14I am wandering how is your ass lately doing By the way con made a free pool open sourced . It is brilliant pice of work. All you need to do is steal it and put wasp logo on it. So hurry up That is where you are good at And to troll of course
|
|
|
What a joy dude Next time use stock china firmware when yo mine. So you will mine with 0 GH guaranteed but reset will work eventually What's your point??? ps I am positive about the tb/cgminer, if you missed that. Yeah i missed that My English sucks. Sorry I am glad you like it. Best L
|
|
|
What a joy dude Next time use stock china firmware when yo mine. So you will mine with 0 GH guaranteed but reset will work eventually For the record there is no such thing as factory reset in openwrt using buttons. Reset can be performed only via web.just read what fail safe openwrt mode is and how to use it 2good 1. I never use dhcp for mining 2. I have to dig serial cable like you and I will check this out I have enough bricks already due to various reasons so I will find a serial cable and max232 probably pull up res is needed also and will check that out. And I will recover all my bricks I hope marto staff will fix that in upcoming image I vote dhcp to be removed. If a miner can not set ip mask gw and DNS this stuf is not for him at all I am sure marto will take care of the above two issues.
|
|
|
Hey, Are you sure your PC date is ok?
Yes, it's OK. Please check Opera browser result post above. Looks like something is wrong with their certificate from GeoTrust Inc. All other webpages in https:// mode on my PC are working fine, including BitcoinTalk for example. Can you guys post your results from your browsers? EDIT: Look at this - Qualys SSL Labs check showing "Grade F", test failed for this website. Results: https://www.ssllabs.com/ssltest/analyze.html?d=technobit.eu&s=5.104.170.146And some clues: " This server supports anonymous (insecure) suites (see below for details). Grade set to F. The server does not support Forward Secrecy with the reference browsers. MORE INFO » " So I guess some pics are hosted so where else without https. That is why your browser is complaining. And what is the problem with that?
|
|
|
Hi marto74, Looks like your website TLS certificate is broken. https://technobit.eu/index.phpAlso there is no class of certificate defined, and Firefox cannot verify who signed this certificate. Can you explain why is that? Hey, Are you sure your PC date is ok?
|
|
|
I was wondering if one of the other Bulgarians in the forum can confirm what Kusmet means? In Hebrew it apparently means mage. Just curious as it was apparently the default username Joshua Zipkin /AMT was using to mine with our hardware with. I noticed both my miners configured with that usernames against F2pool.
I mentioned previously that the discovery that he has been mining with our hardware on f2pool, user kusmet. All the default images on the miner have the logs still present on them so its easy to validate for anyone with the image (of course AMT will take these down so I will post the default image I recommend others do also, use windiskimage to create a raw file of the stock image for archival purposes)
I created an unaltered image for checking and am willing to provide the original SDcard for forensic examination to the legal team. I have one miner I have not powered on yet for this very reason.
kusmet късмет means luck In Bulgarian ....
|
|
|
What software are you using?
No open source software no customers! Avoid this folks Besides remove 40% from hash rate and add 20% to power usage 1.4T from five modules if the pic is real at all is just a dirty lie Hey china boys are my estimations correct Do not buy this stuff just because they do not play fair not because miner origin is from china I mostly agree with loshia on this. The china thing I don't totally agree with but do to some extent. Bitmain operates out of Hong Kong (technically China), I think some good stuff can come out of China....BUT yea avoid this at all costs. These are the same machines AMT is hawking around and you only need to read the first few and last pages of any of the threads to know whats going on. If the build quality is the same (as they have yet to show proof) they likely will come to you missing power supplies and already having been used for mining and rusty metal in the packaging and who knows what else. Since AMT is done for this could be them under an alias account trying to sell this hardware. They did say they would do exactly this. As I said I am not against china a I am against lairs 1.4t with that amount of chips and power dirty lie that's all over spec ... For me 5 modules will ever be 1t or 1.1t maxxxxx
|
|
|
What software are you using?
No open source software no customers! Avoid this folks Besides remove 40% from hash rate and add 20% to power usage 1.4T from five modules if the pic is real at all is just a dirty lie Hey china boys are my estimations correct Do not buy this stuff just because they do not play fair not because miner origin is from china
|
|
|
reverse engender Hehe. Hehe my grammar sucks You need oscilloscope and a packet analyzer. Add some brain cels and you are there. This is not a rocket science you know. The Chinese stollen "KNOWHOW" can easily be revealed. But why someone needs to do that? Nonsense Opening the source will allow other folks to do job instead of them they just do not get it. Sometimes I am wondering how Chinese move forward in general but this is another story But all of you got general idea right? Do not buy something which is not open sourced. No matter of its origin China US or Europe!!!! Period! And when you need to complain use google to translate your massage to mandarin and send a pigeon(attach your message to the leg of the bird) mail to your Chinese hardware vendor Hehe
|
|
|
Wait 2 weeks from this Monday. bitmain is supposed to be updating to a newer version of cgminer other than 3.12. I have no clue if ckolivias or kano have any involvement but I'd hope they pick it to pieces when its released to the public.
I don't care of Bitmain posts the update or if Kano has to do it. Con + Kano still get donations, as they're the ones that wrote the software. I'd much rather be running 4.5 rather than 3.12. And so? When they get donations they are obliged to lick your ass and reverse engender Chinese shit? Donation means that you give something and you do expect NOTHING IN RETURN so to make long story short bitmain took your money not like donation go and ask him to update cgminer will you? Besides both you as customer and bitmain are violating the law. You know that right? But you just do not care correct? You will eventually donate and that makes you in position to order people what to do? Funny
|
|
|
160 Ghs Congrats dude Happy mining
|
|
|
Ok Sorry to say that gator but there is 0 activity on tplink LAN then It is not asking for ip and also it is not broadcasting so
The only option left is to hack it and use console it is hardware hack
Yo can still try various buttons to reset it while sniffing it can revival itself eventually
Best
|
|
|
I even put a router in between the laptop and the TP-Link just to make sure it's served a DHCP address, because setting DHCP Client is what caused this mess, nothing, laptop got a DHCP address, but the TP-Link Lights are on but no one is home. Connect tplink directly to your LAN card of PC
Fire wire shark Stop all pings Start capturing packets Power tplink Want 10 secs and post captured packets here
No. Time Source Destination Protocol Length Info 1 0.000000000 0.0.0.0 255.255.255.255 DHCP 342 DHCP Discover - Transaction ID 0x5ff377b
Frame 1: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol
No. Time Source Destination Protocol Length Info 2 0.452228000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 2: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info 3 0.452317000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 3: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22) Internet Group Management Protocol
No. Time Source Destination Protocol Length Info 4 2.438787000 0.0.0.0 255.255.255.255 DHCP 342 DHCP Discover - Transaction ID 0x9c8bcfd5
Frame 4: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol
No. Time Source Destination Protocol Length Info 5 2.452347000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 5: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info 6 2.452401000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 6: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22) Internet Group Management Protocol
No. Time Source Destination Protocol Length Info 7 2.952388000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 7: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22) Internet Group Management Protocol
No. Time Source Destination Protocol Length Info 8 3.452432000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 8: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info 9 3.959501000 169.254.85.24 239.255.255.250 SSDP 175 M-SEARCH * HTTP/1.1
Frame 9: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 239.255.255.250 (239.255.255.250) User Datagram Protocol, Src Port: 52739 (52739), Dst Port: ssdp (1900) Hypertext Transfer Protocol
No. Time Source Destination Protocol Length Info 10 4.452530000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 10: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info 11 6.448461000 0.0.0.0 255.255.255.255 DHCP 342 DHCP Discover - Transaction ID 0x3210f771
Frame 11: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol
No. Time Source Destination Protocol Length Info 12 6.452567000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 12: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info 13 6.452647000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 13: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22) Internet Group Management Protocol
No. Time Source Destination Protocol Length Info 14 6.952622000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
Frame 14: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22) Internet Group Management Protocol
No. Time Source Destination Protocol Length Info 15 6.959884000 169.254.85.24 239.255.255.250 SSDP 175 M-SEARCH * HTTP/1.1
Frame 15: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 239.255.255.250 (239.255.255.250) User Datagram Protocol, Src Port: 52739 (52739), Dst Port: ssdp (1900) Hypertext Transfer Protocol
No. Time Source Destination Protocol Length Info 16 7.452624000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 16: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info 17 8.452699000 Inventec_af:1b:31 Broadcast ARP 42 Who has 169.254.85.24? Tell 0.0.0.0
Frame 17: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info 18 9.465652000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.252 for any sources
Frame 18: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22) Internet Group Management Protocol
No. Time Source Destination Protocol Length Info 19 9.473102000 169.254.85.24 169.254.255.255 UDP 112 Source port: 27036 Destination port: 27036
Frame 19: 112 bytes on wire (896 bits), 112 bytes captured (896 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255) User Datagram Protocol, Src Port: 27036 (27036), Dst Port: 27036 (27036) Data (70 bytes)
0000 ff ff ff ff 21 4c 5f a0 0d 00 00 00 08 e9 bd d5 ....!L_......... 0010 a9 df d9 db 96 fa 01 10 01 29 00 00 00 08 06 10 .........)...... 0020 06 18 e7 82 03 22 0a 41 43 45 52 2d 36 39 33 35 .....".Laptop 0030 47 30 03 38 09 4a 0b 09 c6 71 f8 05 01 00 10 01 G0.8.J...q...... 0040 10 00 50 e4 82 03 ..P...
No. Time Source Destination Protocol Length Info 20 9.473210000 169.254.85.24 169.254.255.255 UDP 73 Source port: 27036 Destination port: 27036
Frame 20: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255) User Datagram Protocol, Src Port: 27036 (27036), Dst Port: 27036 (27036) Data (31 bytes)
0000 ff ff ff ff 21 4c 5f a0 0d 00 00 00 08 e9 bd d5 ....!L_......... 0010 a9 df d9 db 96 fa 01 10 00 02 00 00 00 08 35 ..............5
No. Time Source Destination Protocol Length Info 21 9.473936000 169.254.85.24 169.254.255.255 UDP 73 Source port: 27036 Destination port: 27036
Frame 21: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255) User Datagram Protocol, Src Port: 27036 (27036), Dst Port: 27036 (27036) Data (31 bytes)
0000 ff ff ff ff 21 4c 5f a0 0d 00 00 00 08 e9 bd d5 ....!L_......... 0010 a9 df d9 db 96 fa 01 10 00 02 00 00 00 08 36 ..............6
No. Time Source Destination Protocol Length Info 22 9.475913000 169.254.85.24 239.255.255.250 SSDP 175 M-SEARCH * HTTP/1.1
Frame 22: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 239.255.255.250 (239.255.255.250) User Datagram Protocol, Src Port: 52739 (52739), Dst Port: ssdp (1900) Hypertext Transfer Protocol
No. Time Source Destination Protocol Length Info 23 9.497883000 169.254.85.24 169.254.255.255 NBNS 92 Name query NB ISATAP<00>
Frame 23: 92 bytes on wire (736 bits), 92 bytes captured (736 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255) User Datagram Protocol, Src Port: netbios-ns (137), Dst Port: netbios-ns (137) NetBIOS Name Service
No. Time Source Destination Protocol Length Info 24 9.529278000 169.254.85.24 169.254.255.255 NBNS 110 Registration NB LaptopG<00>
Frame 24: 110 bytes on wire (880 bits), 110 bytes captured (880 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 169.254.255.255 (169.254.255.255) User Datagram Protocol, Src Port: netbios-ns (137), Dst Port: netbios-ns (137) NetBIOS Name Service
No. Time Source Destination Protocol Length Info 25 9.952803000 169.254.85.24 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.252 for any sources
Frame 25: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 224.0.0.22 (224.0.0.22) Internet Group Management Protocol
No. Time Source Destination Protocol Length Info 26 9.959922000 169.254.85.24 239.255.255.250 SSDP 175 M-SEARCH * HTTP/1.1
Frame 26: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits) on interface 0 Ethernet II, Src: Inventec_af:1b:31 (00:a0:d1:af:1b:31), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa) Internet Protocol Version 4, Src: 169.254.85.24 (169.254.85.24), Dst: 239.255.255.250 (239.255.255.250) User Datagram Protocol, Src Port: 52739 (52739), Dst Port: ssdp (1900) Hypertext Transfer Protocol
No. Time Source Destination Protocol Length Info 27 10.229933000 169.254.85.24 169.254.255.255 NBNS 92 Name query NB Laptop<00>
Gator, Do not put a router in between please you need a hub in between not a switch in order to sniff. But I am dam sure you do not have HUB aground this stuff is too old Do it one more time as i suggested please. Connect tplink in your PC with one utp wire. Nothing more Then capture again
|
|
|
I was asking just for fair review that is all The rest of the story is in my signature Dear Bick ......
|
|
|
|