Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-11 > #15767 > unrolled thread

Mounting a drive on the USB port of my router

Back to article view | Back to alt.comp.os.windows-11

Contents

  Mounting a drive on the USB port of my router MajorLanGod <lonelydad58@gmail.com> - 2024-12-30 02:09 +0000
    Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2024-12-29 22:48 -0600
    Re: Mounting a drive on the USB port of my router Graham J <nobody@nowhere.co.uk> - 2024-12-30 08:29 +0000
      Re: Mounting a drive on the USB port of my router wasbit <wasbit@nowhere.com> - 2024-12-30 09:28 +0000
        Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2024-12-30 16:14 +0000
          Re: Mounting a drive on the USB port of my router Ken Blake <Ken@invalid.news.com> - 2024-12-30 09:40 -0700
            Re: Mounting a drive on the USB port of my router Mark Lloyd <not.email@all.invalid> - 2024-12-30 18:13 +0000
          Re: Mounting a drive on the USB port of my router "Carlos E.R." <robin_listas@es.invalid> - 2024-12-30 23:32 +0100
            Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2024-12-30 23:22 +0000
              Re: Mounting a drive on the USB port of my router "Carlos E.R." <robin_listas@es.invalid> - 2024-12-31 03:12 +0100
                Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2024-12-31 06:31 -0500
                  Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2024-12-31 12:12 +0000
                    Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2024-12-31 07:48 -0600
                      Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2024-12-31 14:07 +0000
                        Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2024-12-31 16:40 -0600
                          Re: Mounting a drive on the USB port of my router Jeff Barnett <jbb@notatt.com> - 2024-12-31 15:53 -0700
                            Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2025-01-01 00:00 +0000
                              Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2024-12-31 20:46 -0600
                                Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2025-01-01 04:44 +0000
                                  Re: Mounting a drive on the USB port of my router "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-01-01 10:41 +0000
                                    Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2025-01-01 18:48 +0000
                                      Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2025-01-02 00:36 -0600
                                        Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2025-01-02 15:13 +0000
                                          Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-02 21:49 -0600
                                        Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2025-01-02 15:57 +0000
                                        Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-02 13:21 -0500
                                          Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-02 21:46 -0600
                                            Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-03 15:49 -0500
                                      Re: Mounting a drive on the USB port of my router Daniel70 <daniel47@eternal-september.org> - 2025-01-25 23:13 +1100
                                        Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2025-01-25 08:07 -0600
                                    Re: Mounting a drive on the USB port of my router "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-01-25 17:42 +0000
                                  Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2025-01-01 09:03 -0600
                                    Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2025-01-01 18:55 +0000
                                      Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2025-01-02 00:16 -0600
                              Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2025-01-01 13:22 +0000
                            Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-01 14:44 -0500
                              Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-01 16:12 -0600
                                Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-02 01:37 -0500
                                  Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-02 01:51 -0600
                                    Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-02 04:00 -0500
                                      Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-02 21:47 -0600
                    Re: Mounting a drive on the USB port of my router MajorLanGod <lonelydad58@gmail.com> - 2024-12-31 19:16 +0000
              Re: Mounting a drive on the USB port of my router MajorLanGod <lonelydad58@gmail.com> - 2024-12-31 19:13 +0000
                Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2024-12-31 21:16 +0000
                Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-01 14:54 -0500
          Re: Mounting a drive on the USB port of my router wasbit <wasbit@nowhere.com> - 2024-12-31 09:39 +0000
            Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2024-12-31 07:27 -0500
            Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2024-12-31 20:20 +0000
              Re: Mounting a drive on the USB port of my router Graham J <nobody@nowhere.co.uk> - 2024-12-31 20:34 +0000
                Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2024-12-31 20:53 +0000
                Re: Mounting a drive on the USB port of my router "Carlos E.R." <robin_listas@es.invalid> - 2024-12-31 21:57 +0100
                  Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2024-12-31 21:36 +0000
        Re: Mounting a drive on the USB port of my router ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2024-12-30 13:18 -0700
      OT NAS for Router, was: Mounting a drive on the USB port of my router "Alan K." <alan@invalid.com> - 2024-12-30 08:08 -0500
        Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2024-12-30 13:46 +0000
          Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Joerg Walther <joerg.walther@magenta.de> - 2024-12-30 16:19 +0100
          Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Graham J <nobody@nowhere.co.uk> - 2024-12-30 16:27 +0000
            Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Peter Johnson <peter@parksidewood.nospam> - 2024-12-30 17:06 +0000
              Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Graham J <nobody@nowhere.co.uk> - 2024-12-30 17:29 +0000
                Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2024-12-30 20:33 +0000
                  Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2024-12-30 18:36 -0500
              Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2024-12-30 12:46 -0500
              Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Zaidy036 <Zaidy036@air.isp.spam> - 2024-12-30 14:34 -0500
                Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2024-12-31 15:17 +0000
                  Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Zaidy036 <Zaidy036@air.isp.spam> - 2024-12-31 21:22 -0500
            Re: OT NAS for Router, was: Mounting a drive on the USB port of my router "Alan K." <alan@invalid.com> - 2024-12-30 16:36 -0500
            Re: OT NAS for Router, was: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2024-12-31 14:40 +0000
    Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2024-12-30 06:07 -0500
      Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-01 16:48 -0500
    Re: Mounting a drive on the USB port of my router Ed Cryer <ed@somewhere.in.the.uk> - 2024-12-30 12:18 +0000
    Re: Mounting a drive on the USB port of my router Mark Lloyd <not.email@all.invalid> - 2024-12-30 18:09 +0000
    Re: Mounting a drive on the USB port of my router MajorLanGod <lonelydad58@gmail.com> - 2024-12-30 22:40 +0000
    Re: Mounting a drive on the USB port of my router "Carlos E.R." <robin_listas@es.invalid> - 2024-12-30 23:37 +0100
      Re: Mounting a drive on the USB port of my router MajorLanGod <lonelydad58@gmail.com> - 2024-12-31 19:20 +0000
    Re: Mounting a drive on the USB port of my router The Man With the Golden Touch <invalid@invalid.com> - 2024-12-31 01:01 +0000
      Re: Mounting a drive on the USB port of my router MajorLanGod <lonelydad58@gmail.com> - 2024-12-31 19:22 +0000
    Re: Mounting a drive on the USB port of my router VanguardLH <V@nguard.LH> - 2024-12-31 05:46 -0600
      Re: Mounting a drive on the USB port of my router MajorLanGod <lonelydad58@gmail.com> - 2024-12-31 19:28 +0000
        Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2024-12-31 20:57 +0000
          Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-01 15:16 -0500
            Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2025-01-01 20:25 +0000
              Re: Mounting a drive on the USB port of my router Ed Cryer <ed@somewhere.in.the.uk> - 2025-01-01 21:23 +0000
                Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2025-01-01 21:42 +0000
              Re: Mounting a drive on the USB port of my router Java Jive <java@evij.com.invalid> - 2025-01-01 21:50 +0000
                Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-02 11:59 -0500
              Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-01 16:58 -0500
                Re: Mounting a drive on the USB port of my router "Carlos E.R." <robin_listas@es.invalid> - 2025-01-01 23:19 +0100
                Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-01 17:58 -0600
                  Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-02 05:10 -0500
                  Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2025-01-02 16:17 +0000
                    Re: Mounting a drive on the USB port of my router Paul <nospam@needed.invalid> - 2025-01-02 13:10 -0500
                      Re: Mounting a drive on the USB port of my router Frank Slootweg <this@ddress.is.invalid> - 2025-01-02 19:14 +0000
                    Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-02 21:50 -0600
                  Re: Mounting a drive on the USB port of my router "Carlos E.R." <robin_listas@es.invalid> - 2025-01-02 23:18 +0100
                    Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-02 21:44 -0600
                      Re: Mounting a drive on the USB port of my router "Carlos E.R." <robin_listas@es.invalid> - 2025-01-04 02:58 +0100
                      Re: Mounting a drive on the USB port of my router Andy Burns <usenet@andyburns.uk> - 2025-01-05 16:09 +0000
                        Re: Mounting a drive on the USB port of my router Char Jackson <none@none.invalid> - 2025-01-05 13:13 -0600
                          Re: Mounting a drive on the USB port of my router Andy Burns <usenet@andyburns.uk> - 2025-01-05 19:36 +0000

Page 5 of 5 — ← Prev page 1 2 3 4 [5]

#15915

Paul <nospam@needed.invalid> wrote:
> On Tue, 12/31/2024 3:57 PM, Frank Slootweg wrote:
> > MajorLanGod <lonelydad58@gmail.com> wrote:
> > [...]
> >> When I log in to the router it shows up:
> >>
> >>
> >> Product NameEXTERNAL_USB
> >> 1.ManufacturerTOSHIBA_EXTERNAL_USB_1_f0c1
> >> 1.Total Space1863.01GB
> >> 1.Used Space1193.58GB
> >> 1.Free Space669.44GB
> > 
> >   See Graham's suggestion to try \\<IP_address> as the share name or
> > live dangerously and try \\EXTERNAL_USB. 
> > 
> >   Are you sure, you're a "LAN & PC wizard"!?
> 
> You're just saying that to make him work harder :-)
> 
> I think he's getting real close, if he got this far.
> If the port was dead, this wouldn't have happened.

  But as Carlos mentioned, there's still the problem of the
login/password of the share, so there's still work ahead! :-)

  As I mentioned, getting into the web-UI of the router/modem would be
the most logical first step. But being logical is so overrated these
days. 

[toc] | [prev] | [next] | [standalone]

#15917

Frank Slootweg wrote:

 >>But being logical is so overrated these days.

That must count as the most stupid sentence I've ever read
I'll try and give it some kind of authority by rephrasing it.
1. Rational discourse is rare these days.
2. Beware of intellect; it scares people away.
3. Do you want to get on with people? Talk dumb.

What else do we have better than logic and reason? Faith in some 
supernature? Trust in some prime minister? Simple smile and wait until 
God straightens it all out?
Whatever you choose, don't abandon logic and reason, pal. You won't find 
anything better.

Ed

[toc] | [prev] | [next] | [standalone]

#15918

Ed Cryer <ed@somewhere.in.the.uk> wrote:
> Frank Slootweg wrote:
> 
>  >>But being logical is so overrated these days.
> 
> That must count as the most stupid sentence I've ever read

  Thanks. :-( Do I have to say it was/is sarcasm?

> I'll try and give it some kind of authority by rephrasing it.
> 1. Rational discourse is rare these days.

  That's not exactly what I mean, but the closest of the three.

> 2. Beware of intellect; it scares people away.
> 3. Do you want to get on with people? Talk dumb.
> 
> What else do we have better than logic and reason? Faith in some 
> supernature? Trust in some prime minister? Simple smile and wait until 
> God straightens it all out?
> Whatever you choose, don't abandon logic and reason, pal. You won't find 
> anything better.

  Exactly. Logic and - hopefully - reason have been my strong traits all
my life. (And earned me the big bucks! :-)) I have no intention to
change any of it.

[toc] | [prev] | [next] | [standalone]

#15920

On 2025-01-01 20:25, Frank Slootweg wrote:
>
> As I mentioned, getting into the web-UI of the router/modem would be
> the most logical first step. 

Yes, it sounds like he needs to find the relevant part of the router 
configuration, either in the web GUI or else less easily by logging in 
via SSH or TELNET (but preferably not the latter as it's so insecure and 
thus possibly not even enabled on the router).

> But being logical is so overrated these
> days.

LOL!

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]

#15974

On Wed, 1/1/2025 4:50 PM, Java Jive wrote:
> On 2025-01-01 20:25, Frank Slootweg wrote:
>>
>> As I mentioned, getting into the web-UI of the router/modem would be
>> the most logical first step. 
> 
> Yes, it sounds like he needs to find the relevant part of the router configuration, either in the web GUI or else less easily by logging in via SSH or TELNET (but preferably not the latter as it's so insecure and thus possibly not even enabled on the router).
> 
>> But being logical is so overrated these
>> days.
> 
> LOL!
> 

Well, the important part is done. Proving that the
available documentation is wrong or incomplete.

Since there is no manual for the product, the process
now will be as variable as commercial routers are variable.
My SGS Thompson, had like one setting at the first level,
and if that's what you were looking at, you might be
quite discouraged. The $39.95 D-Link I bought, that
was a great implementation, everything orderly in the
web interface, anything you could think of setting was
there.

He can work at his own pace now. If a company can't write
a manual, what other things might they not be able to do ?
The product is made by Technicolor, for Google. As an OEM'ed
product, Google is responsible for writing the manual
(yes, like that would happen). Based on the hardware
pictures, I suspect a good deal of implemented features,
are hidden from the eye. Like the Wifi in there, there
are eight patch antennas. This isn't exactly some
forty buck 802.11n. It's a higher class than that,
whatever it is. Could be a 6E, not likely to be a 7.

Looking at the pictures, my concern is that it will
overheat, under load. The passive vents on it are
pretty bad. This is not an item I would lock in
a broom closet.

   Paul

[toc] | [prev] | [next] | [standalone]

#15922

On Wed, 1/1/2025 3:25 PM, Frank Slootweg wrote:
> Paul <nospam@needed.invalid> wrote:
>> On Tue, 12/31/2024 3:57 PM, Frank Slootweg wrote:
>>> MajorLanGod <lonelydad58@gmail.com> wrote:
>>> [...]
>>>> When I log in to the router it shows up:
>>>>
>>>>
>>>> Product NameEXTERNAL_USB
>>>> 1.ManufacturerTOSHIBA_EXTERNAL_USB_1_f0c1
>>>> 1.Total Space1863.01GB
>>>> 1.Used Space1193.58GB
>>>> 1.Free Space669.44GB
>>>
>>>   See Graham's suggestion to try \\<IP_address> as the share name or
>>> live dangerously and try \\EXTERNAL_USB. 
>>>
>>>   Are you sure, you're a "LAN & PC wizard"!?
>>
>> You're just saying that to make him work harder :-)
>>
>> I think he's getting real close, if he got this far.
>> If the port was dead, this wouldn't have happened.
> 
>   But as Carlos mentioned, there's still the problem of the
> login/password of the share, so there's still work ahead! :-)
> 
>   As I mentioned, getting into the web-UI of the router/modem would be
> the most logical first step. But being logical is so overrated these
> days. 
> 

Actually, you wouldn't do that. You would access the TTL-level console
connector. With a serial TTL level adapter. Lots of electronics
have that for debug. It can be a Linux console, ready for you
to drop standard Linux commands into. This would bypass the
buggery of the three-level password on the Web UI. Three level
password is standard practice on rental routers, which is why
I bought the retail version of the ISP router, just so the
passwords would be unlocked.

Even hard drives have a four pin header inside.

I see a four pin connector in the FCCID picture of the PCB,
but the legend is unclear and I don't think it actually
says "debug port". It could just as easily be
a power extender port for the second PCB. The connector
might be accessible, without ripping any thermal tape
and taking the heatsink off.

I've not done any of this sort of hacking, but I've
read of a few accounts of people attacking balky
equipment this way. The hard drive hack was hilarious,
in that the commands were machine code type commands
and not plain English commands. And someone broke
their NDA sharing that with us. I suspect official
approval was given for that one. The disk drive companies
have Green Beret level lawyers. Any time there is a leak,
the perp "disappears".

   Paul

[toc] | [prev] | [next] | [standalone]

#15926

On 2025-01-01 22:58, Paul wrote:
> On Wed, 1/1/2025 3:25 PM, Frank Slootweg wrote:
>> Paul <nospam@needed.invalid> wrote:
>>> On Tue, 12/31/2024 3:57 PM, Frank Slootweg wrote:
>>>> MajorLanGod <lonelydad58@gmail.com> wrote:
>>>> [...]
>>>>> When I log in to the router it shows up:
>>>>>
>>>>>
>>>>> Product NameEXTERNAL_USB
>>>>> 1.ManufacturerTOSHIBA_EXTERNAL_USB_1_f0c1
>>>>> 1.Total Space1863.01GB
>>>>> 1.Used Space1193.58GB
>>>>> 1.Free Space669.44GB
>>>>
>>>>    See Graham's suggestion to try \\<IP_address> as the share name or
>>>> live dangerously and try \\EXTERNAL_USB.
>>>>
>>>>    Are you sure, you're a "LAN & PC wizard"!?
>>>
>>> You're just saying that to make him work harder :-)
>>>
>>> I think he's getting real close, if he got this far.
>>> If the port was dead, this wouldn't have happened.
>>
>>    But as Carlos mentioned, there's still the problem of the
>> login/password of the share, so there's still work ahead! :-)
>>
>>    As I mentioned, getting into the web-UI of the router/modem would be
>> the most logical first step. But being logical is so overrated these
>> days.
>>
> 
> Actually, you wouldn't do that. You would access the TTL-level console
> connector. With a serial TTL level adapter. Lots of electronics
> have that for debug. It can be a Linux console, ready for you
> to drop standard Linux commands into. This would bypass the
> buggery of the three-level password on the Web UI. Three level
> password is standard practice on rental routers, which is why
> I bought the retail version of the ISP router, just so the
> passwords would be unlocked.

To do that sort of thing I would have to open the plastic case, and my 
router is rented, not owned.

Can't do.

And probably not necessary, just to use a functionality that is there 
waiting for use with an easy interface.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#15933

On Wed, 1 Jan 2025 16:58:21 -0500, Paul <nospam@needed.invalid> wrote:

>On Wed, 1/1/2025 3:25 PM, Frank Slootweg wrote:
>> Paul <nospam@needed.invalid> wrote:
>>> On Tue, 12/31/2024 3:57 PM, Frank Slootweg wrote:
>>>> MajorLanGod <lonelydad58@gmail.com> wrote:
>>>> [...]
>>>>> When I log in to the router it shows up:
>>>>>
>>>>>
>>>>> Product NameEXTERNAL_USB
>>>>> 1.ManufacturerTOSHIBA_EXTERNAL_USB_1_f0c1
>>>>> 1.Total Space1863.01GB
>>>>> 1.Used Space1193.58GB
>>>>> 1.Free Space669.44GB
>>>>
>>>>   See Graham's suggestion to try \\<IP_address> as the share name or
>>>> live dangerously and try \\EXTERNAL_USB. 
>>>>
>>>>   Are you sure, you're a "LAN & PC wizard"!?
>>>
>>> You're just saying that to make him work harder :-)
>>>
>>> I think he's getting real close, if he got this far.
>>> If the port was dead, this wouldn't have happened.
>> 
>>   But as Carlos mentioned, there's still the problem of the
>> login/password of the share, so there's still work ahead! :-)
>> 
>>   As I mentioned, getting into the web-UI of the router/modem would be
>> the most logical first step. But being logical is so overrated these
>> days. 
>> 
>
>Actually, you wouldn't do that. You would access the TTL-level console
>connector. With a serial TTL level adapter. Lots of electronics
>have that for debug. It can be a Linux console, ready for you
>to drop standard Linux commands into. This would bypass the
>buggery of the three-level password on the Web UI. Three level
>password is standard practice on rental routers, which is why
>I bought the retail version of the ISP router, just so the
>passwords would be unlocked.
>
>Even hard drives have a four pin header inside.
>
>I see a four pin connector in the FCCID picture of the PCB,
>but the legend is unclear and I don't think it actually
>says "debug port". It could just as easily be
>a power extender port for the second PCB. The connector
>might be accessible, without ripping any thermal tape
>and taking the heatsink off.
>
>I've not done any of this sort of hacking, but I've
>read of a few accounts of people attacking balky
>equipment this way. The hard drive hack was hilarious,
>in that the commands were machine code type commands
>and not plain English commands. And someone broke
>their NDA sharing that with us. I suspect official
>approval was given for that one. The disk drive companies
>have Green Beret level lawyers. Any time there is a leak,
>the perp "disappears".

I saw a video a few days ago, put together to talk about the "TP-Link may well
be banned in the US because it's easy to hack" issue. The guy opened the case
and identified the main components, but then he noticed 4 solder pads that he
(correctly) guessed might be a UART interface. He soldered pins to the pads,
guessed at the baud rate (115kbps), and immediately got a login prompt in his
terminal.

He didn't know the username and password, but he was able to download the
firmware and disassemble it, giving him the piss-poor credentials. Once he was
properly logged in, he was able to see all kinds of things, especially things
that would make the unit highly susceptible to being part of a botnet. Pretty
interesting video.

[toc] | [prev] | [next] | [standalone]

#15960

On Wed, 1/1/2025 6:58 PM, Char Jackson wrote:
> On Wed, 1 Jan 2025 16:58:21 -0500, Paul <nospam@needed.invalid> wrote:
> 
>> On Wed, 1/1/2025 3:25 PM, Frank Slootweg wrote:
>>> Paul <nospam@needed.invalid> wrote:
>>>> On Tue, 12/31/2024 3:57 PM, Frank Slootweg wrote:
>>>>> MajorLanGod <lonelydad58@gmail.com> wrote:
>>>>> [...]
>>>>>> When I log in to the router it shows up:
>>>>>>
>>>>>>
>>>>>> Product NameEXTERNAL_USB
>>>>>> 1.ManufacturerTOSHIBA_EXTERNAL_USB_1_f0c1
>>>>>> 1.Total Space1863.01GB
>>>>>> 1.Used Space1193.58GB
>>>>>> 1.Free Space669.44GB
>>>>>
>>>>>   See Graham's suggestion to try \\<IP_address> as the share name or
>>>>> live dangerously and try \\EXTERNAL_USB. 
>>>>>
>>>>>   Are you sure, you're a "LAN & PC wizard"!?
>>>>
>>>> You're just saying that to make him work harder :-)
>>>>
>>>> I think he's getting real close, if he got this far.
>>>> If the port was dead, this wouldn't have happened.
>>>
>>>   But as Carlos mentioned, there's still the problem of the
>>> login/password of the share, so there's still work ahead! :-)
>>>
>>>   As I mentioned, getting into the web-UI of the router/modem would be
>>> the most logical first step. But being logical is so overrated these
>>> days. 
>>>
>>
>> Actually, you wouldn't do that. You would access the TTL-level console
>> connector. With a serial TTL level adapter. Lots of electronics
>> have that for debug. It can be a Linux console, ready for you
>> to drop standard Linux commands into. This would bypass the
>> buggery of the three-level password on the Web UI. Three level
>> password is standard practice on rental routers, which is why
>> I bought the retail version of the ISP router, just so the
>> passwords would be unlocked.
>>
>> Even hard drives have a four pin header inside.
>>
>> I see a four pin connector in the FCCID picture of the PCB,
>> but the legend is unclear and I don't think it actually
>> says "debug port". It could just as easily be
>> a power extender port for the second PCB. The connector
>> might be accessible, without ripping any thermal tape
>> and taking the heatsink off.
>>
>> I've not done any of this sort of hacking, but I've
>> read of a few accounts of people attacking balky
>> equipment this way. The hard drive hack was hilarious,
>> in that the commands were machine code type commands
>> and not plain English commands. And someone broke
>> their NDA sharing that with us. I suspect official
>> approval was given for that one. The disk drive companies
>> have Green Beret level lawyers. Any time there is a leak,
>> the perp "disappears".
> 
> I saw a video a few days ago, put together to talk about the "TP-Link may well
> be banned in the US because it's easy to hack" issue. The guy opened the case
> and identified the main components, but then he noticed 4 solder pads that he
> (correctly) guessed might be a UART interface. He soldered pins to the pads,
> guessed at the baud rate (115kbps), and immediately got a login prompt in his
> terminal.
> 
> He didn't know the username and password, but he was able to download the
> firmware and disassemble it, giving him the piss-poor credentials. Once he was
> properly logged in, he was able to see all kinds of things, especially things
> that would make the unit highly susceptible to being part of a botnet. Pretty
> interesting video.
> 

If you declare the port as "console", it is live immediately,
with a shell prompt sitting there for you. The example below
is live immediately.

There is some other declaration, which leave the login prompt.
And would need authentication.

This is a declaration of kernel boot line parameters.
The first one, causes the serial port on the SuperIO,
to receive the dmesg boot log as the OS boots. The serial port
gets the boot messages, instead of the main LCD screen. This is
handy when your graphics driver is broken.

console=ttyS0,57600n8   nouveau.noaccel=1

If you want to do that for a USB serial port, it's a bit more
difficult to do, as the USB port is more "dynamic" in terms of
numbering. The tty at S0, does not move, and it stays at S0.

    Paul

[toc] | [prev] | [next] | [standalone]

#15973

Char Jackson <none@none.invalid> wrote:
[...]

> I saw a video a few days ago, put together to talk about the "TP-Link
> may well be banned in the US because it's easy to hack" issue.

  Yeah, I saw the stories/reports about TP-Link (routers) and thought
"Bummer, I have some of that stuff!". But they are (Wi-Fi) Range
Extenders and I don't use/need them anymore, so I thought I'am OK.

  Only a little while later, I bought a Kenwood FM/DAB+/Internet/Spotify
'SmartRadio'.

  I thought Kenwood is Japanese, but - like many other products - the
radio is 'Made in China'. And it got 'worse', because the actual
SmartRadio electronics are developed and manufacturered in China by
Frontier Smart Technologies (<https://www.frontiersmart.com/about/>).

  So, am I now spied on by the 'radio' on my desk!? :-)

[...]

[toc] | [prev] | [next] | [standalone]

#15976

On Thu, 1/2/2025 11:17 AM, Frank Slootweg wrote:
> Char Jackson <none@none.invalid> wrote:
> [...]
> 
>> I saw a video a few days ago, put together to talk about the "TP-Link
>> may well be banned in the US because it's easy to hack" issue.
> 
>   Yeah, I saw the stories/reports about TP-Link (routers) and thought
> "Bummer, I have some of that stuff!". But they are (Wi-Fi) Range
> Extenders and I don't use/need them anymore, so I thought I'am OK.
> 
>   Only a little while later, I bought a Kenwood FM/DAB+/Internet/Spotify
> 'SmartRadio'.
> 
>   I thought Kenwood is Japanese, but - like many other products - the
> radio is 'Made in China'. And it got 'worse', because the actual
> SmartRadio electronics are developed and manufacturered in China by
> Frontier Smart Technologies (<https://www.frontiersmart.com/about/>).
> 
>   So, am I now spied on by the 'radio' on my desk!? :-)
> 
> [...]
> 

The people writing the firmware/software, are the ones most likely
to directly affect the product quality. The Frontier company
would be writing that part. They wouldn't have soldering irons,
a solder tunnel, a workshop with thermoplastic extrusion for
cases and so on. They would be buying and subcontracting piece
parts.

If anything were to happen to your radio, it would be making
a Botnet out of your radio. And having it transmit packets
against a target. Thousands of radios doing the same thing
at the same time. Rather than the radio having a microphone,
doing speech recognition and having that sent back to someone.

Only networked TV sets do that, right ? :-) It would never
be a lowly radio. Never.

   Paul

[toc] | [prev] | [next] | [standalone]

#15984

Paul <nospam@needed.invalid> wrote:
> On Thu, 1/2/2025 11:17 AM, Frank Slootweg wrote:
> > Char Jackson <none@none.invalid> wrote:
> > [...]
> > 
> >> I saw a video a few days ago, put together to talk about the "TP-Link
> >> may well be banned in the US because it's easy to hack" issue.
> > 
> >   Yeah, I saw the stories/reports about TP-Link (routers) and thought
> > "Bummer, I have some of that stuff!". But they are (Wi-Fi) Range
> > Extenders and I don't use/need them anymore, so I thought I'am OK.
> > 
> >   Only a little while later, I bought a Kenwood FM/DAB+/Internet/Spotify
> > 'SmartRadio'.
> > 
> >   I thought Kenwood is Japanese, but - like many other products - the
> > radio is 'Made in China'. And it got 'worse', because the actual
> > SmartRadio electronics are developed and manufacturered in China by
> > Frontier Smart Technologies (<https://www.frontiersmart.com/about/>).
> > 
> >   So, am I now spied on by the 'radio' on my desk!? :-)
> > 
> > [...]
> > 
> 
> The people writing the firmware/software, are the ones most likely
> to directly affect the product quality. The Frontier company
> would be writing that part. They wouldn't have soldering irons,
> a solder tunnel, a workshop with thermoplastic extrusion for
> cases and so on. They would be buying and subcontracting piece
> parts.
> 
> If anything were to happen to your radio, it would be making
> a Botnet out of your radio. And having it transmit packets
> against a target. Thousands of radios doing the same thing
> at the same time. Rather than the radio having a microphone,
> doing speech recognition and having that sent back to someone.
> 
> Only networked TV sets do that, right ? :-) It would never
> be a lowly radio. Never.

  Yes, but they could collect all my personal/private information, like
all the stations I listen to, my Spotify playlists, not to mention my
Wi-Fi SSID and - heaven forbid - passwords. The paranoids in these
groups would have a field day about my gulliblity! :-)

[toc] | [prev] | [next] | [standalone]

#16012

On 2 Jan 2025 16:17:56 GMT, Frank Slootweg <this@ddress.is.invalid> wrote:

>Char Jackson <none@none.invalid> wrote:
>[...]
>
>> I saw a video a few days ago, put together to talk about the "TP-Link
>> may well be banned in the US because it's easy to hack" issue.
>
>  Yeah, I saw the stories/reports about TP-Link (routers) and thought
>"Bummer, I have some of that stuff!". But they are (Wi-Fi) Range
>Extenders and I don't use/need them anymore, so I thought I'am OK.
>
>  Only a little while later, I bought a Kenwood FM/DAB+/Internet/Spotify
>'SmartRadio'.
>
>  I thought Kenwood is Japanese, but - like many other products - the
>radio is 'Made in China'. And it got 'worse', because the actual
>SmartRadio electronics are developed and manufacturered in China by
>Frontier Smart Technologies (<https://www.frontiersmart.com/about/>).
>
>  So, am I now spied on by the 'radio' on my desk!? :-)
>
>[...]

It's kind of sad how the brands that we used to hold in high esteem have been
sold and resold and now they're just commodity junk. Or maybe that's just me.

[toc] | [prev] | [next] | [standalone]

#16000

On 2025-01-02 00:58, Char Jackson wrote:
> On Wed, 1 Jan 2025 16:58:21 -0500, Paul <nospam@needed.invalid> wrote:
> 
>> On Wed, 1/1/2025 3:25 PM, Frank Slootweg wrote:
>>> Paul <nospam@needed.invalid> wrote:
>>>> On Tue, 12/31/2024 3:57 PM, Frank Slootweg wrote:
>>>>> MajorLanGod <lonelydad58@gmail.com> wrote:
>>>>> [...]
>>>>>> When I log in to the router it shows up:
>>>>>>
>>>>>>
>>>>>> Product NameEXTERNAL_USB
>>>>>> 1.ManufacturerTOSHIBA_EXTERNAL_USB_1_f0c1
>>>>>> 1.Total Space1863.01GB
>>>>>> 1.Used Space1193.58GB
>>>>>> 1.Free Space669.44GB
>>>>>
>>>>>    See Graham's suggestion to try \\<IP_address> as the share name or
>>>>> live dangerously and try \\EXTERNAL_USB.
>>>>>
>>>>>    Are you sure, you're a "LAN & PC wizard"!?
>>>>
>>>> You're just saying that to make him work harder :-)
>>>>
>>>> I think he's getting real close, if he got this far.
>>>> If the port was dead, this wouldn't have happened.
>>>
>>>    But as Carlos mentioned, there's still the problem of the
>>> login/password of the share, so there's still work ahead! :-)
>>>
>>>    As I mentioned, getting into the web-UI of the router/modem would be
>>> the most logical first step. But being logical is so overrated these
>>> days.
>>>
>>
>> Actually, you wouldn't do that. You would access the TTL-level console
>> connector. With a serial TTL level adapter. Lots of electronics
>> have that for debug. It can be a Linux console, ready for you
>> to drop standard Linux commands into. This would bypass the
>> buggery of the three-level password on the Web UI. Three level
>> password is standard practice on rental routers, which is why
>> I bought the retail version of the ISP router, just so the
>> passwords would be unlocked.
>>
>> Even hard drives have a four pin header inside.
>>
>> I see a four pin connector in the FCCID picture of the PCB,
>> but the legend is unclear and I don't think it actually
>> says "debug port". It could just as easily be
>> a power extender port for the second PCB. The connector
>> might be accessible, without ripping any thermal tape
>> and taking the heatsink off.
>>
>> I've not done any of this sort of hacking, but I've
>> read of a few accounts of people attacking balky
>> equipment this way. The hard drive hack was hilarious,
>> in that the commands were machine code type commands
>> and not plain English commands. And someone broke
>> their NDA sharing that with us. I suspect official
>> approval was given for that one. The disk drive companies
>> have Green Beret level lawyers. Any time there is a leak,
>> the perp "disappears".
> 
> I saw a video a few days ago, put together to talk about the "TP-Link may well
> be banned in the US because it's easy to hack" issue. The guy opened the case
> and identified the main components, but then he noticed 4 solder pads that he
> (correctly) guessed might be a UART interface. He soldered pins to the pads,
> guessed at the baud rate (115kbps), and immediately got a login prompt in his
> terminal.
> 
> He didn't know the username and password, but he was able to download the
> firmware and disassemble it, giving him the piss-poor credentials. Once he was
> properly logged in, he was able to see all kinds of things, especially things
> that would make the unit highly susceptible to being part of a botnet. Pretty
> interesting video.

That a machine is hackable by soldering wires is not important. What is 
important is if it is remotely hackable.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#16008

On Thu, 2 Jan 2025 23:18:28 +0100, "Carlos E.R." <robin_listas@es.invalid>
wrote:

>On 2025-01-02 00:58, Char Jackson wrote:
>> I saw a video a few days ago, put together to talk about the "TP-Link may well
>> be banned in the US because it's easy to hack" issue. The guy opened the case
>> and identified the main components, but then he noticed 4 solder pads that he
>> (correctly) guessed might be a UART interface. He soldered pins to the pads,
>> guessed at the baud rate (115kbps), and immediately got a login prompt in his
>> terminal.
>> 
>> He didn't know the username and password, but he was able to download the
>> firmware and disassemble it, giving him the piss-poor credentials. Once he was
>> properly logged in, he was able to see all kinds of things, especially things
>> that would make the unit highly susceptible to being part of a botnet. Pretty
>> interesting video.
>
>That a machine is hackable by soldering wires is not important. What is 
>important is if it is remotely hackable.

Apologies, my story was too short. In his video, he showed just how easy it is
to remotely hack the item he was working with. The services he was able to
uncover on the LAN side turned out to be also accessible from the WAN side. Once
he knew what to look for, he mentioned doing a limited Internet sweep and
finding countless examples of vulnerable equipment, presumably all TP-Link in
this case.

[toc] | [prev] | [next] | [standalone]

#16060

On 2025-01-03 04:44, Char Jackson wrote:
> On Thu, 2 Jan 2025 23:18:28 +0100, "Carlos E.R." <robin_listas@es.invalid>
> wrote:
> 
>> On 2025-01-02 00:58, Char Jackson wrote:
>>> I saw a video a few days ago, put together to talk about the "TP-Link may well
>>> be banned in the US because it's easy to hack" issue. The guy opened the case
>>> and identified the main components, but then he noticed 4 solder pads that he
>>> (correctly) guessed might be a UART interface. He soldered pins to the pads,
>>> guessed at the baud rate (115kbps), and immediately got a login prompt in his
>>> terminal.
>>>
>>> He didn't know the username and password, but he was able to download the
>>> firmware and disassemble it, giving him the piss-poor credentials. Once he was
>>> properly logged in, he was able to see all kinds of things, especially things
>>> that would make the unit highly susceptible to being part of a botnet. Pretty
>>> interesting video.
>>
>> That a machine is hackable by soldering wires is not important. What is
>> important is if it is remotely hackable.
> 
> Apologies, my story was too short. In his video, he showed just how easy it is
> to remotely hack the item he was working with. The services he was able to
> uncover on the LAN side turned out to be also accessible from the WAN side. Once
> he knew what to look for, he mentioned doing a limited Internet sweep and
> finding countless examples of vulnerable equipment, presumably all TP-Link in
> this case.

Ah, right.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#16132

Char Jackson wrote:

> Carlos E.R.  wrote:
> 
>> That a machine is hackable by soldering wires is not important. What is
>> important is if it is remotely hackable.
> 
> Apologies, my story was too short. In his video, he showed just how easy it is
> to remotely hack the item he was working with. The services he was able to
> uncover on the LAN side turned out to be also accessible from the WAN side. Once
> he knew what to look for, he mentioned doing a limited Internet sweep and
> finding countless examples of vulnerable equipment, presumably all TP-Link in
> this case.
Was this the ANPR camera video?

I didn't so much watch the video as have it on in the background, but I 
thought the device didn't have a WAN side at all, it had a cameras side 
and a local users side ... the problem came when some devices were 
installed off-site with a 4G hotspot on the users side ...

[toc] | [prev] | [next] | [standalone]

#16134

On Sun, 5 Jan 2025 16:09:35 +0000, Andy Burns <usenet@andyburns.uk> wrote:

>Char Jackson wrote:
>
>> Carlos E.R.  wrote:
>> 
>>> That a machine is hackable by soldering wires is not important. What is
>>> important is if it is remotely hackable.
>> 
>> Apologies, my story was too short. In his video, he showed just how easy it is
>> to remotely hack the item he was working with. The services he was able to
>> uncover on the LAN side turned out to be also accessible from the WAN side. Once
>> he knew what to look for, he mentioned doing a limited Internet sweep and
>> finding countless examples of vulnerable equipment, presumably all TP-Link in
>> this case.
>Was this the ANPR camera video?

I believe it was a router. I no longer have the link handy.

>I didn't so much watch the video as have it on in the background, but I 
>thought the device didn't have a WAN side at all, it had a cameras side 
>and a local users side ... the problem came when some devices were 
>installed off-site with a 4G hotspot on the users side ...

[toc] | [prev] | [next] | [standalone]

#16135

Char Jackson wrote:

> Andy Burns wrote:
> 
>> Was this the ANPR camera video?
> 
> I believe it was a router. I no longer have the link handy.
OK, same chap different device.

[toc] | [prev] | [standalone]

Page 5 of 5 — ← Prev page 1 2 3 4 [5]

Back to top | Article view | alt.comp.os.windows-11

csiph-web