Re: Resolved (was: Re: OT: Using my (new) cable based ISP with their modem in bridge mode and my existing router)

[songbird]

rhkra...@gmail.com wrote:
...
> ...  Sometimes I feel 
> like an idiot.
>
> All seems well.

  :)

  i've had days like that...  glad you figured it out.

  completely OT from your issue, but today i finally upgraded
my stable partition from whatever it was on (last major update
was probably a year or more ago).

  glad to say that with a bit of heavy hammer hitting i got it
all to update and than as usual it did the os-prober at the
end which was ok, but since my /boot partition on that setup
did not have the right efi/EFI/ it was not able to
immediately switch into my refind menu like i am used to doing
(because i did not install refind on my stable partition).
so of course i go off to do that and then at the end it asks
about putting stuff on my efi partition and i say yes and then
a second later i'm wondering if i just overwrote my refind
configuration file.  after a bit of nosing around i could
breath a bit better because no it did not destroy my config
so i was all set.  so you are not the only one here who can
mess up something.  :)


  songbird

Resolved (was: Re: OT: Using my (new) cable based ISP with their modem in bridge mode and my existing router)

[rhkramer]

Intentionally top posting:

Thanks to all who replied, I got the Arris DG2470A modem (/ router) working in 
bridge mode with my existing router (Ubiquiti Edge Router X).

I made a dumb mistake -- I had my router and another computer plugged into the 
Arris (I used the other computer to configure the Arris), and then I switched 
to bridge mode.  At least once I noticed that I could ping the Internet from 
that other computer, which meant that the Arris was in bridge mode, but that 
computer was using the Arris modem instead of my router.

Since then, I've done better -- e.g., configured the Arris to bridge mode, then 
powered down the Arris, unplugged that other computer, plugged in my Ubiquiti 
router and configured it to connect to the WAN by DHCP.

Aside: In my previous (DSL) installation, the modem was a modem only, and had 
only one place to connect an Ethernet cable.  With the Arris, being a router 
as well as a modem, it had 4 places to plug in an Ethernet cable, and, without 
thinking about it, I plugged in two devices (a computer and the Ubiquiti), 
but, in bridge mode, only one of those was going to work.  Sometimes I feel 
like an idiot.

All seems well.


On Friday, April 28, 2023 11:08:45 PM David Wright wrote:

-- 
rhk 

| No entity has permission to use this email to train an AI. 

Re: OT: Using my (new) cable based ISP with their modem in bridge mode and my existing router

[David Wright]

On Fri 28 Apr 2023 at 14:25:20 (-0400), rhkra...@gmail.com wrote:
> Some key phrases / sub topics:
>* Astound (cable based) ISP in eastern Pa. area
>* Arris DG2470A modem / router in bridge mode with Ubiquiti Edge Router X
>* Ubiquiti Edge Router X in DMZ 

[ … ]

> I did think about using both the Ubiquiti (and DHCP, if that's what Astound 
> uses in this area) and the Arris sort of in series (the Ubiquiti 
> ("downstream" 
> of the Arris) then doing the DHCP (and other features, e.g. QOS) for the LAN, 
> but I'm leery of doing that because I've seen (somewhat vague) warnings on 
> the 
> Internet about doing double NAT.  (Maybe that is only an issue of speed, 
> which 
> I don't think would bother me -- the Astound connection could be 30 (or  more 
> (or less)) times as fast as the DSL connection.)
> 
> I suppose I could do the two in series (as mentioned above), leave DHCP 
> turned 
> on in both, but the firewall turned off in the upstream modem / router.
> 
> I'm getting too old -- trial and error (as I've done a few times) is nerve 
> wracking for me.  Even getting the Ubiquiti back to the configuration to use 
> on 
> my DSL ISP drove me crazy, I had to try a few times to do that (I haven't 
> cancelled my DSL ISP yet), and I'm not sure that I know the exact steps to 
> get 
> that setup working again if I have to (i.e., if I try the Astound connection 
> and don't get it working), but I feel, since I accomplished it once, I can do 
> it again (i.e., I'm seeking comments on the problems of connecting to 
> Astound rather than those of reconnecting to my DSL ISP).

Your post is rather technical for me, so I'll just describe what I do.
We used to have a cable modem (Cisco DPC3010), apparently in bridge
mode (unclear whether there was another mode), connected with Cat5
to my router, a Netgear WNDR3400v3. Near the beginning of the
pandemic, the modem burnt out, so I replaced it with some sort of
Panoramic modem/router, about which I know little except that it has
two LAN ports. I connected one of these to the WAN of our router, by
now a Netgear R6020, and that was it. We just pretend the Panoramic
is the old Cisco.

The R6020 connects to the WAN with DHCP, as it always did before with
the Cisco, and it runs a DHCP server on the LAN side for all our
devices, wired and wireless, with a small range (192.168.1.200 up)
for strangers.

The old Netgear WNDR3400v3 had been retired with a dead WAN port,
but because our house is rather long, I now use it as an extender.
I turned off the WAN stuff, and also its DHCP, and connected one
LAN port to a R6020 LAN port (both have four). Its wireless, which
usually works, has the same SSID and PSK as the R6020. (To know
which router you're connected to, the easiest way is to ping
either router and then type   ip n   for the MAC.)

When we no longer need to network and zoom with the university,
we'll probably ditch the Panoramic and buy a plain modem again.

Cheers,
David.

Re: OT: Using my (new) cable based ISP with their modem in bridge mode and my existing router

[john doe]

On 4/28/23 20:25, rhkra...@gmail.com wrote:

Some key phrases / sub topics:
* Astound (cable based) ISP in eastern Pa. area
* Arris DG2470A modem / router in bridge mode with Ubiquiti Edge Router X
* Ubiquiti Edge Router X in DMZ



I'm tired but I'm lost at your set up and I'm not in the US! :)

- Is Astound simply the name of your ISP or is it a  HW from your ISP?
- Arris DG2470A, where is it coming from (provided by your ISP?)
- Ubiquiti Edge Router X in DMZ, why is DMZ relevent in this set up?


Aside: I'm in a catch 22 -- my new, cable-based ISP (Astound / RCN) says my
questions are out of scope and I should talk to the manufacturer.  The
manufacturer says that the Arris DG2470A modem / router is not something they
sell to the end user (only to ISPs or such), and thus I should get support
from the ISP, so:



Okay, Arris is the modem provided by your ISP! :)


I've now signed up to a new ISP (Astound / RCN) that provides access via cable
(and, of course, a cable modem, an Arris DG2470A -- it does include a router
but without all the features I'd like to have).  So far, I have not been able
to connect to Astound with the modem in bridge mode (and using DHCP in the
router).


Bridge mode will disable router capability which include DHCP  capability.


I'm not 100% sure whether Astound (in my area, around Allentown, Pa.) uses
PPPoE or DHCP to make the connection.  So far, I've tried only DHCP.


I would say cable uses DHCP or a static IP if you pay for it.



Astound does need to do something on their end to register the modem in order
to make it work.  They have told me that the thing they need to register the
modem is the MAC address (and, of course, they have that for the Arris).


This is possible but that could also be something else.
My ISP does not use the mac addr!


I've also seen a suggestion that I put the Ubiquiti in the DMZ zone of the
Arris, but I haven't fully assimilated that suggestion, for example, I'm not
sure what IP address to assign to the (WAN) port of the Ubiquiti in that case
-- a private address on my LAN or something else.



If you use your Arris in router mode, you could use the DMZ capability
to avoid FW and some other stuff that the Arris would do if your Ubikiti
was not in the DMZ.
In other words, bridge mode will give the public IP from your ISP to
your Ubikiti while DMZ will let you use the FW from your Ubikiti to
protect the network that is behind your Ubikiti while getting an private
IP from your ISP Arris modem router.


(Right now I've got a bunch of web pages open, some of which I've started to
read -- when I find / get back to the page that suggests putting the Ubiquiti
in the DMZ, my questions might be answered (on the subject of putting the
Ubiquiti in the DMZ).



If I can, I'll always use a modem from my ISP with my own stuff behind it.
If my ISP does not give a modem, I'll revert to put it in bridge mode
which will act effectively as a modem.
If I can not get a modem or have access to bridge mode, I will resort to
a DMZ capability from my ISP crap!


I'm also not sure what problems having the Ubiquiti in the DMZ might cause --
in general, I'd prefer to have the Ubiquiti connected to the Arris in bridge
mode (because of my past experience).


+1



I did think about using both the Ubiquiti (and DHCP, if that's what Astound
uses in this area) and the Arris sort of in series (the Ubiquiti ("downstream"
of the Arris) then doing the DHCP (and other features, e.g. QOS) for the LAN,
but I'm leery of doing that because I've seen (somewhat vague) warnings on the
Internet about doing double NAT.  (Maybe that is only an issue of speed, which


Double NAT is one thing but the real issue to me in this case what is
the deffinition of DMZ for the Arris.


I don't think would bother me -- the Astound connection could be 30 (or  more
(or less)) times as fast as the DSL connection.)

I suppose I could do the two in series (as mentioned above), leave DHCP turned
on in both, but the firewall turned off in the upstream modem / router.


Which is what the DMZ should do, note that in the DMZ set up the client
side of your Arris would get a lease from your ISP with a public address
then the DHCP server of the Arris would dish out an private Ip to your
Ubikiti DHCP client in this case and the DHCP server of your Ubikiti
will provide private IPs to your network(s).



I'm getting too old -- trial and error (as I've done a few times) is nerve
wracking for me.  Even getting the Ubiquiti back to the configuration to use on
my DSL ISP drove me crazy, I had to try a few times to do that (I haven't
cancelled my DSL ISP yet), and I'm not sure that I know the exact steps to get
that setup working again if I have to (i.e., if I try the Astound connection
and don't get it working), but I feel, since I accomplished it once, I can do
it again (i.e., I'm seeking comments on the problems of connecting to
Astound rather than those of reconnecting to my DSL ISP).



You shou

Re: OT: Using my (new) cable based ISP with their modem in bridge mode and my existing router

[Dan Ritter]

rhkra...@gmail.com wrote: 
> Some key phrases / sub topics:
>* Astound (cable based) ISP in eastern Pa. area
>* Arris DG2470A modem / router in bridge mode with Ubiquiti Edge Router X
>* Ubiquiti Edge Router X in DMZ 

> I've now signed up to a new ISP (Astound / RCN) that provides access via 
> cable 
> (and, of course, a cable modem, an Arris DG2470A -- it does include a router 
> but without all the features I'd like to have).  So far, I have not been able 
> to connect to Astound with the modem in bridge mode (and using DHCP in the 
> router).
> 
> I'm not 100% sure whether Astound (in my area, around Allentown, Pa.) uses 
> PPPoE or DHCP to make the connection.  So far, I've tried only DHCP. 

All the other RCN connections I've heard of used DHCP to assign
an IPv4 address. (I used them for seven years.)

> I am thinking of doing something like cloning the modem's MAC address in the 
> router (and also maybe putting a different MAC address in the Arris) so that 
> maybe Astound will accept a logon from the Ubiquiti router (of course, I 
> don't 
> know if the problem is that Astound doesn't like that the Ubiquiti is trying 
> to make the connection).

Let me offer a different solution: buy your own cable modem.

The 2470A is a 24x8 DOCSIS 3.0 modem, along with the aggravating
router portion.

You can get a Motorola MG7621 for under $100. It's also a 24x8
DOCSIS 3.0 modem.

Others include Linksys CM3024, Netgear CM600, and TP-Link
TC7650.

All of these are on RCN's own approved list.

Once you have one of them, call up the service center to get it
authorized on your account, and then connect up your router to
the ethernet port.

-dsr-

OT: Using my (new) cable based ISP with their modem in bridge mode and my existing router

[rhkramer]

Some key phrases / sub topics:
   * Astound (cable based) ISP in eastern Pa. area
   * Arris DG2470A modem / router in bridge mode with Ubiquiti Edge Router X
   * Ubiquiti Edge Router X in DMZ 

Aside: I'm in a catch 22 -- my new, cable-based ISP (Astound / RCN) says my 
questions are out of scope and I should talk to the manufacturer.  The 
manufacturer says that the Arris DG2470A modem / router is not something they 
sell to the end user (only to ISPs or such), and thus I should get support 
from the ISP, so:

For the the last 10 years or so I've used a DSL modem (in bridge mode) and a 
Ubiquiti Edge Router X.  With the modem in bridge mode the router was 
responsible for connection to the ISP (and using, afaict, pppoe).

I've now signed up to a new ISP (Astound / RCN) that provides access via cable 
(and, of course, a cable modem, an Arris DG2470A -- it does include a router 
but without all the features I'd like to have).  So far, I have not been able 
to connect to Astound with the modem in bridge mode (and using DHCP in the 
router).

(The new modem / router does work fine in non-bridge mode, so my connection and 
such works.)

I'm not 100% sure whether Astound (in my area, around Allentown, Pa.) uses 
PPPoE or DHCP to make the connection.  So far, I've tried only DHCP. 

Astound does need to do something on their end to register the modem in order 
to make it work.  They have told me that the thing they need to register the 
modem is the MAC address (and, of course, they have that for the Arris).

I am thinking of doing something like cloning the modem's MAC address in the 
router (and also maybe putting a different MAC address in the Arris) so that 
maybe Astound will accept a logon from the Ubiquiti router (of course, I don't 
know if the problem is that Astound doesn't like that the Ubiquiti is trying 
to make the connection).

I've also seen a suggestion that I put the Ubiquiti in the DMZ zone of the 
Arris, but I haven't fully assimilated that suggestion, for example, I'm not 
sure what IP address to assign to the (WAN) port of the Ubiquiti in that case 
-- a private address on my LAN or something else.  

(Right now I've got a bunch of web pages open, some of which I've started to 
read -- when I find / get back to the page that suggests putting the Ubiquiti 
in the DMZ, my questions might be answered (on the subject of putting the 
Ubiquiti in the DMZ).  

I'm also not sure what problems having the Ubiquiti in the DMZ might cause -- 
in general, I'd prefer to have the Ubiquiti connected to the Arris in bridge 
mode (because of my past experience).

I did think about using both the Ubiquiti (and DHCP, if that's what Astound 
uses in this area) and the Arris sort of in series (the Ubiquiti ("downstream" 
of the Arris) then doing the DHCP (and other features, e.g. QOS) for the LAN, 
but I'm leery of doing that because I've seen (somewhat vague) warnings on the 
Internet about doing double NAT.  (Maybe that is only an issue of speed, which 
I don't think would bother me -- the Astound connection could be 30 (or  more 
(or less)) times as fast as the DSL connection.)

I suppose I could do the two in series (as mentioned above), leave DHCP turned 
on in both, but the firewall turned off in the upstream modem / router.

I'm getting too old -- trial and error (as I've done a few times) is nerve 
wracking for me.  Even getting the Ubiquiti back to the configuration to use on 
my DSL ISP drove me crazy, I had to try a few times to do that (I haven't 
cancelled my DSL ISP yet), and I'm not sure that I know the exact steps to get 
that setup working again if I have to (i.e., if I try the Astound connection 
and don't get it working), but I feel, since I accomplished it once, I can do 
it again (i.e., I'm seeking comments on the problems of connecting to 
Astound rather than those of reconnecting to my DSL ISP).

Thanks!

Re: (deb-cat) Utilitzar un modem GSM - HP lt4112

[Narcis Garcia]

Gràcies Josep, la teva observació va ser crucial per a investigar en una 
altra direcció, encara que no indicava el problema.

El rang d'adreces 172.16.0.0 - 172.31.255.255 és per a xarxes privades.

Ho he resolt provant diferents servidors APN que el proveïdor ha anat 
utilitzant al llarg de la història. I doncs, resulta que l'assistent de 
NetworkManager, en comptes de llegir-lo de la targeta SIM, porta 
associat un servidor APN segons l'operador que tries, i en aquest cas 
era obsolet.


Igualment, l'operador no m'ha assignat una IP pública sinó privada, d'un 
altre rang. I ja accedeixo a Internet a través de la seva porta d'enllaç 
LAN. La perseverança guanya!
Ja només em falta automatitzar la configuració del controlador i 
l'activació del dispositiu cada vegada que s'inicia l'ordinador i que 
surt del repòs.


Gràcies a tothom.


El 20/3/23 a les 19:08, Josep Lladonosa ha escrit:

Hola, Narcís,

Se'm va passar de comentar-te que aquestes adreces IP que apareixen 
(172.19.x.x) són adreces IP privades.
Ho dic perquè comentaves sobre "adreça pública"... Realment obté el teu 
aparell una adreça IP pública? Que no sigui el tema d'usuari/contrasenya 
del PPP (gestor de mòdem) que depèn del proveïdor de connexió i que, en 
no facilitar la correcta, et quedes amb una adreça IP d'enllaç amb el 
servei d'autenticació -l'adreça inicial- i prou (la seva "intranet", 
vaja, com l'antiga "Infovía" anys enrere en l'ADSL/XDSI de la Telefónica).


Cordialment,
Josep

On Mon, 20 Mar 2023 at 18:56, Narcis Garcia <mailto:debianli...@actiu.net>> wrote:


Hi he donat moltes voltes, i no sé per on tirar.
Arreu hi ha gent que diu que amb el mateix dispositiu lt4112
aconsegueix
funcionar amb GNU/Linux i des de fa anys, i no sembla que haguessin de
superar la meva mateixa dificultat.

Estic travat amb què connecta, senyalitza el nivell de cobertura,
adquireix la configuració IP (IP, porta, DNS), però no hi ha
comunicació
més enllà de la IP pública.
Tampoc no es rebutja la comunicació, sinó que no assoleix cap
destinació
externa.

Ara ja només se m'acudeix provar amb més i més distribucions de
GNU/Linux.

Gràcies als què heu intentat ajudar-me.


El 17/3/23 a les 22:04, Josep Lladonosa ha escrit:
 > Hola, Narcís,
 >
 > Quan he parlat de PPP em referia al fet que es fan servir els
codis de
 > configuració de connexions estil "mòdems". De fet, en principi, el
 > NetworkManager no hauria de configurar res (tot i que a algun
lloc en
 > parlen que podria fer la feina) ja que normalment s'usa el
 > "ModemManager" que és qui parla amb l'adaptador USB i configura
aquesta
 > connexió PPP (els paquets IP anirien dins aquesta). Per això em
referia
 > que no sigui algun paràmetre de configuració d'aquest enllaç PPP.
 >
 > He trobat aquest web que llista els adaptadors compatibles amb Linux:
 >
 >
https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ 
<https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/>
 >
<https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ 
<https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/>>
 >
 > Cordialment,
 > Josep
 >
 >
 >
 > On Fri, 17 Mar 2023 at 16:13, Narcis Garcia
mailto:debianli...@actiu.net>
 > <mailto:debianli...@actiu.net <mailto:debianli...@actiu.net>>> wrote:
 >
 >     Hola Josep, l'opció de l'encaminador no em convenç per dues
raons:
 >     Perquè es fa un altre salt amb comunicació enrutada (LAN) i
aèria (la
 >     qual cosa perd latència etc.) i també perquè cal carregar més
trastos
 >     apart de l'ordinador. Per això ja em serviria el telèfon
mòbil que
 >     té el
 >     mateix paper, i el què tinc em resulta lent.
 >
 >     El dispositiu es detecta en un primer moment com a emmagatzematge
 >     (0685:2000 ZD Incorporated USB Qualcomm Storage), però en uns
segons
 >     canvia a modem (12d1:1001 Huawei Technologies Co., Ltd.
 >     E161/E169/E620/E800 HSDPA Modem). Suposo que es tracta d'una
correcció
 >     que fa el udev o el què sigui que organitza els dispositius.
 >
 >     1. Utilitzo el NetworkManager. Com s'enumeren les connexions PPP?
 >     És el què dóna «nmcli connection show» o com es distingeixen
quan estan
 >     establertes com a PPP?
 >     2. Amb la comanda «netstat -rn» veig que la ruta per defecte està
 >     definida, i al mateix espai d'adreces que el dispositiu modem:
 >
 >     $ ip address show dev wwan0
 >     5: wwan0:  mtu 1500 qdisc
 >     pfifo_fast 

Re: (deb-cat) Utilitzar un modem GSM - HP lt4112

[Josep Lladonosa]

Hola, Narcís,

Se'm va passar de comentar-te que aquestes adreces IP que apareixen
(172.19.x.x) són adreces IP privades.
Ho dic perquè comentaves sobre "adreça pública"... Realment obté el teu
aparell una adreça IP pública? Que no sigui el tema d'usuari/contrasenya
del PPP (gestor de mòdem) que depèn del proveïdor de connexió i que, en no
facilitar la correcta, et quedes amb una adreça IP d'enllaç amb el servei
d'autenticació -l'adreça inicial- i prou (la seva "intranet", vaja, com
l'antiga "Infovía" anys enrere en l'ADSL/XDSI de la Telefónica).

Cordialment,
Josep

On Mon, 20 Mar 2023 at 18:56, Narcis Garcia  wrote:

> Hi he donat moltes voltes, i no sé per on tirar.
> Arreu hi ha gent que diu que amb el mateix dispositiu lt4112 aconsegueix
> funcionar amb GNU/Linux i des de fa anys, i no sembla que haguessin de
> superar la meva mateixa dificultat.
>
> Estic travat amb què connecta, senyalitza el nivell de cobertura,
> adquireix la configuració IP (IP, porta, DNS), però no hi ha comunicació
> més enllà de la IP pública.
> Tampoc no es rebutja la comunicació, sinó que no assoleix cap destinació
> externa.
>
> Ara ja només se m'acudeix provar amb més i més distribucions de GNU/Linux.
>
> Gràcies als què heu intentat ajudar-me.
>
>
> El 17/3/23 a les 22:04, Josep Lladonosa ha escrit:
> > Hola, Narcís,
> >
> > Quan he parlat de PPP em referia al fet que es fan servir els codis de
> > configuració de connexions estil "mòdems". De fet, en principi, el
> > NetworkManager no hauria de configurar res (tot i que a algun lloc en
> > parlen que podria fer la feina) ja que normalment s'usa el
> > "ModemManager" que és qui parla amb l'adaptador USB i configura aquesta
> > connexió PPP (els paquets IP anirien dins aquesta). Per això em referia
> > que no sigui algun paràmetre de configuració d'aquest enllaç PPP.
> >
> > He trobat aquest web que llista els adaptadors compatibles amb Linux:
> >
> > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/
> > <
> https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/>
> >
> > Cordialment,
> > Josep
> >
> >
> >
> > On Fri, 17 Mar 2023 at 16:13, Narcis Garcia  > <mailto:debianli...@actiu.net>> wrote:
> >
> > Hola Josep, l'opció de l'encaminador no em convenç per dues raons:
> > Perquè es fa un altre salt amb comunicació enrutada (LAN) i aèria (la
> > qual cosa perd latència etc.) i també perquè cal carregar més trastos
> > apart de l'ordinador. Per això ja em serviria el telèfon mòbil que
> > té el
> > mateix paper, i el què tinc em resulta lent.
> >
> > El dispositiu es detecta en un primer moment com a emmagatzematge
> > (0685:2000 ZD Incorporated USB Qualcomm Storage), però en uns segons
> > canvia a modem (12d1:1001 Huawei Technologies Co., Ltd.
> > E161/E169/E620/E800 HSDPA Modem). Suposo que es tracta d'una
> correcció
> > que fa el udev o el què sigui que organitza els dispositius.
> >
> > 1. Utilitzo el NetworkManager. Com s'enumeren les connexions PPP?
> > És el què dóna «nmcli connection show» o com es distingeixen quan
> estan
> > establertes com a PPP?
> > 2. Amb la comanda «netstat -rn» veig que la ruta per defecte està
> > definida, i al mateix espai d'adreces que el dispositiu modem:
> >
> > $ ip address show dev wwan0
> > 5: wwan0:  mtu 1500 qdisc
> > pfifo_fast state UNKNOWN group default qlen 1000
> >   link/ether 96:75:07:e1:d1:29 brd ff:ff:ff:ff:ff:ff
> >   inet 172.19.211.64/25 <http://172.19.211.64/25> brd
> > 172.19.211.127 scope global noprefixroute
> > wwan0
> >  valid_lft forever preferred_lft forever
> >
> > $ ping -c 1 172.19.211.64
> > PING 172.19.211.64 (172.19.211.64) 56(84) bytes of data.
> > 64 bytes from 172.19.211.64 <http://172.19.211.64>: icmp_seq=1
> > ttl=64 time=0.057 ms
> > --- 172.19.211.64 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> > rtt min/avg/max/mdev = 0.057/0.057/0.057/0.000 ms
> >
> > $ netstat -rn
> > Kernel IP routing table
> > Destination Gateway Genmask Flags   MSS Window
> > irtt
> > Iface
> > 0.0.0.0 172.19.211.10.0.0.0 UG0 0
> >0
> > wwan0
> > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
> >0
> > wwan0
> > 172.19.211.00.0.0.0 

Re: (deb-cat) Utilitzar un modem GSM - HP lt4112

[Narcis Garcia]

Hi he donat moltes voltes, i no sé per on tirar.
Arreu hi ha gent que diu que amb el mateix dispositiu lt4112 aconsegueix 
funcionar amb GNU/Linux i des de fa anys, i no sembla que haguessin de 
superar la meva mateixa dificultat.


Estic travat amb què connecta, senyalitza el nivell de cobertura, 
adquireix la configuració IP (IP, porta, DNS), però no hi ha comunicació 
més enllà de la IP pública.
Tampoc no es rebutja la comunicació, sinó que no assoleix cap destinació 
externa.


Ara ja només se m'acudeix provar amb més i més distribucions de GNU/Linux.

Gràcies als què heu intentat ajudar-me.


El 17/3/23 a les 22:04, Josep Lladonosa ha escrit:

Hola, Narcís,

Quan he parlat de PPP em referia al fet que es fan servir els codis de 
configuració de connexions estil "mòdems". De fet, en principi, el 
NetworkManager no hauria de configurar res (tot i que a algun lloc en 
parlen que podria fer la feina) ja que normalment s'usa el 
"ModemManager" que és qui parla amb l'adaptador USB i configura aquesta 
connexió PPP (els paquets IP anirien dins aquesta). Per això em referia 
que no sigui algun paràmetre de configuració d'aquest enllaç PPP.


He trobat aquest web que llista els adaptadors compatibles amb Linux:

https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ 
<https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/>


Cordialment,
Josep



On Fri, 17 Mar 2023 at 16:13, Narcis Garcia <mailto:debianli...@actiu.net>> wrote:


Hola Josep, l'opció de l'encaminador no em convenç per dues raons:
Perquè es fa un altre salt amb comunicació enrutada (LAN) i aèria (la
qual cosa perd latència etc.) i també perquè cal carregar més trastos
apart de l'ordinador. Per això ja em serviria el telèfon mòbil que
té el
mateix paper, i el què tinc em resulta lent.

El dispositiu es detecta en un primer moment com a emmagatzematge
(0685:2000 ZD Incorporated USB Qualcomm Storage), però en uns segons
canvia a modem (12d1:1001 Huawei Technologies Co., Ltd.
E161/E169/E620/E800 HSDPA Modem). Suposo que es tracta d'una correcció
que fa el udev o el què sigui que organitza els dispositius.

1. Utilitzo el NetworkManager. Com s'enumeren les connexions PPP?
És el què dóna «nmcli connection show» o com es distingeixen quan estan
establertes com a PPP?
2. Amb la comanda «netstat -rn» veig que la ruta per defecte està
definida, i al mateix espai d'adreces que el dispositiu modem:

$ ip address show dev wwan0
5: wwan0:  mtu 1500 qdisc
pfifo_fast state UNKNOWN group default qlen 1000
      link/ether 96:75:07:e1:d1:29 brd ff:ff:ff:ff:ff:ff
      inet 172.19.211.64/25 <http://172.19.211.64/25> brd
172.19.211.127 scope global noprefixroute
wwan0
         valid_lft forever preferred_lft forever

$ ping -c 1 172.19.211.64
PING 172.19.211.64 (172.19.211.64) 56(84) bytes of data.
64 bytes from 172.19.211.64 <http://172.19.211.64>: icmp_seq=1
ttl=64 time=0.057 ms
--- 172.19.211.64 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.057/0.057/0.057/0.000 ms

$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window 
irtt

Iface
0.0.0.0         172.19.211.1    0.0.0.0         UG        0 0   
   0

wwan0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0   
   0

wwan0
172.19.211.0    0.0.0.0         255.255.255.128 U         0 0   
   0

wwan0

$ ping -c 1 172.19.211.1
PING 172.19.211.1 (172.19.211.1) 56(84) bytes of data.
--- 172.19.211.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms



El 17/3/23 a les 11:35, Josep Lladonosa ha escrit:
 > Hola, Adrià, Narcís,
 >
 > A la feina ens vam trobar que a partir d'una determinada versió
Ubuntu
 > determinats USB 3G van deixar de funcionar.
 > Actualment s'utilitzen "encaminadors" amb bateria (que es
carreguen per
 > USB) que porten la SIM i engegats donen una WiFi a la que diversos
 > equips poden connectar alhora.
 >
 > Si no recordo malament, hi havia temes de reconeixement de
dispositiu
 > com a emmagatzematge (que no seria el teu cas) i altres temes de com
 > s'usa el PPP.
 > Aquests adaptadors 3G/4G no deixen de ser aparells que estableixen
 > connexions a l'estil dels "antics" mòdems. Podria ser que es faci la
 > connexió PPP però a aquesta no se la definís com a ruta per defecte.
 > Estic aportant des de la imaginació i aquest supòsit.
 >
 > Cordialment,
 > Josep
 >
 > On Fri, 17 Mar 2023 at 11:24, Adrià mailto:ad...@fsfe.org>
 > <mailto:ad...@fsfe.org <mailto:ad...@fs

Re: (deb-cat) Utilitzar un modem GSM - HP lt4112

[Josep Lladonosa]

Hola, Narcís,

Quan he parlat de PPP em referia al fet que es fan servir els codis de
configuració de connexions estil "mòdems". De fet, en principi, el
NetworkManager no hauria de configurar res (tot i que a algun lloc en
parlen que podria fer la feina) ja que normalment s'usa el "ModemManager"
que és qui parla amb l'adaptador USB i configura aquesta connexió PPP (els
paquets IP anirien dins aquesta). Per això em referia que no sigui algun
paràmetre de configuració d'aquest enllaç PPP.

He trobat aquest web que llista els adaptadors compatibles amb Linux:

https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/

Cordialment,
Josep



On Fri, 17 Mar 2023 at 16:13, Narcis Garcia  wrote:

> Hola Josep, l'opció de l'encaminador no em convenç per dues raons:
> Perquè es fa un altre salt amb comunicació enrutada (LAN) i aèria (la
> qual cosa perd latència etc.) i també perquè cal carregar més trastos
> apart de l'ordinador. Per això ja em serviria el telèfon mòbil que té el
> mateix paper, i el què tinc em resulta lent.
>
> El dispositiu es detecta en un primer moment com a emmagatzematge
> (0685:2000 ZD Incorporated USB Qualcomm Storage), però en uns segons
> canvia a modem (12d1:1001 Huawei Technologies Co., Ltd.
> E161/E169/E620/E800 HSDPA Modem). Suposo que es tracta d'una correcció
> que fa el udev o el què sigui que organitza els dispositius.
>
> 1. Utilitzo el NetworkManager. Com s'enumeren les connexions PPP?
> És el què dóna «nmcli connection show» o com es distingeixen quan estan
> establertes com a PPP?
> 2. Amb la comanda «netstat -rn» veig que la ruta per defecte està
> definida, i al mateix espai d'adreces que el dispositiu modem:
>
> $ ip address show dev wwan0
> 5: wwan0:  mtu 1500 qdisc
> pfifo_fast state UNKNOWN group default qlen 1000
>  link/ether 96:75:07:e1:d1:29 brd ff:ff:ff:ff:ff:ff
>  inet 172.19.211.64/25 brd 172.19.211.127 scope global noprefixroute
> wwan0
> valid_lft forever preferred_lft forever
>
> $ ping -c 1 172.19.211.64
> PING 172.19.211.64 (172.19.211.64) 56(84) bytes of data.
> 64 bytes from 172.19.211.64: icmp_seq=1 ttl=64 time=0.057 ms
> --- 172.19.211.64 ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 0.057/0.057/0.057/0.000 ms
>
> $ netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags   MSS Window  irtt
> Iface
> 0.0.0.0 172.19.211.10.0.0.0 UG0 0  0
> wwan0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
> wwan0
> 172.19.211.00.0.0.0 255.255.255.128 U 0 0  0
> wwan0
>
> $ ping -c 1 172.19.211.1
> PING 172.19.211.1 (172.19.211.1) 56(84) bytes of data.
> --- 172.19.211.1 ping statistics ---
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
>
>
> El 17/3/23 a les 11:35, Josep Lladonosa ha escrit:
> > Hola, Adrià, Narcís,
> >
> > A la feina ens vam trobar que a partir d'una determinada versió Ubuntu
> > determinats USB 3G van deixar de funcionar.
> > Actualment s'utilitzen "encaminadors" amb bateria (que es carreguen per
> > USB) que porten la SIM i engegats donen una WiFi a la que diversos
> > equips poden connectar alhora.
> >
> > Si no recordo malament, hi havia temes de reconeixement de dispositiu
> > com a emmagatzematge (que no seria el teu cas) i altres temes de com
> > s'usa el PPP.
> > Aquests adaptadors 3G/4G no deixen de ser aparells que estableixen
> > connexions a l'estil dels "antics" mòdems. Podria ser que es faci la
> > connexió PPP però a aquesta no se la definís com a ruta per defecte.
> > Estic aportant des de la imaginació i aquest supòsit.
> >
> > Cordialment,
> > Josep
> >
> > On Fri, 17 Mar 2023 at 11:24, Adrià  > <mailto:ad...@fsfe.org>> wrote:
> >
> > Am 16/03/2023 um 14:18 schrieb Narcis Garcia:
> >  > No tinc ni idea de què fer amb Wireshark per a comprovar no sé el
> > què.
> >  > A GNU/Linux el dispositiu es configura (IP, porta, DNS), però no
> >  > aconsegueixo arribar a cap servei extern, ni tan sols respon ping
> > cap a
> >  > la porta d'enllaç ni els servidors DNS, ni aquests resolen
> adreces.
> >  > Com a molt la pròpia IP pública respon a ping, però qualsevol IP
> >  > d'Internet ja no.
> >
> > Hola Narcís,
> >
> > en aquest cas, i havent provat que amb un altre sistema operatiu pot
> > funcionar, cal descartar que l'operador posi pals a les rodes.
> >
> > Jo et diria de comprovar si un tallafocs està impe

Re: (deb-cat) Utilitzar un modem GSM

[Narcis Garcia]

El 17/3/23 a les 11:23, Adrià ha escrit:

Am 16/03/2023 um 14:18 schrieb Narcis Garcia:

No tinc ni idea de què fer amb Wireshark per a comprovar no sé el què.
A GNU/Linux el dispositiu es configura (IP, porta, DNS), però no 
aconsegueixo arribar a cap servei extern, ni tan sols respon ping cap 
a la porta d'enllaç ni els servidors DNS, ni aquests resolen adreces.
Com a molt la pròpia IP pública respon a ping, però qualsevol IP 
d'Internet ja no.


Hola Narcís,

en aquest cas, i havent provat que amb un altre sistema operatiu pot 
funcionar, cal descartar que l'operador posi pals a les rodes.


Jo et diria de comprovar si un tallafocs està impedint la connexió 
d'aquesta interfície de xarxa (amb això Wireshark podria ajudar veient 
que s'envien paquets a l'altre extrem i veient si hi arriben o què passa 
amb la resposta), però com que ho has provat amb un parell d'Ubuntus on 
entenc que el tallafocs ve desactivat per defecte, llavors no sabria què 
dir-te.


El que m'estranya és que el ping respongui a la IP pública mentre que no 
ho faci a la porta d'enllaç; no li veig el sentit.


Jo analitzaria una connexió simple (ICMP, o sigui ping) contra un 
dispositiu del mateix segment de xarxa amb el Wireshark, i 
n'interpretaria els resultats. Que no funcioni res _ho puc arribar a 
entendre_, però que funcioni el ping només a la pròpia IP pública em 
desconcerta.


A veure si a algú més se li acut alguna altra cosa perquè puguis provar.



El Wireshark no el sé fer anar ni entenc el sentit dels registres que 
mostra. Se m'ha acudit iniciar-lo com a root, i dir-li que «inicii captura».
Mentrestant, he fet un ping a la porta d'enllaç amb una finestra de 
Terminal. Al Wireshark apareixen moltes línies de bon principi, i podria 
ser que una d'aquestes tingui a veure:


421	39.062700140	172.19.211.64	172.19.211.1	ICMP	54	Timestamp request 
id=0xafee, seq=0/0, ttl=50


557	64.658607871	172.19.211.64	172.19.211.1	ICMP	98	Echo (ping) request 
id=0x0008, seq=2/512, ttl=64 (no response found!)



--


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.

Re: (deb-cat) Utilitzar un modem GSM - HP lt4112

[Narcis Garcia]

Hola Josep, l'opció de l'encaminador no em convenç per dues raons: 
Perquè es fa un altre salt amb comunicació enrutada (LAN) i aèria (la 
qual cosa perd latència etc.) i també perquè cal carregar més trastos 
apart de l'ordinador. Per això ja em serviria el telèfon mòbil que té el 
mateix paper, i el què tinc em resulta lent.


El dispositiu es detecta en un primer moment com a emmagatzematge 
(0685:2000 ZD Incorporated USB Qualcomm Storage), però en uns segons 
canvia a modem (12d1:1001 Huawei Technologies Co., Ltd. 
E161/E169/E620/E800 HSDPA Modem). Suposo que es tracta d'una correcció 
que fa el udev o el què sigui que organitza els dispositius.


1. Utilitzo el NetworkManager. Com s'enumeren les connexions PPP?
És el què dóna «nmcli connection show» o com es distingeixen quan estan 
establertes com a PPP?
2. Amb la comanda «netstat -rn» veig que la ruta per defecte està 
definida, i al mateix espai d'adreces que el dispositiu modem:


$ ip address show dev wwan0
5: wwan0:  mtu 1500 qdisc 
pfifo_fast state UNKNOWN group default qlen 1000

link/ether 96:75:07:e1:d1:29 brd ff:ff:ff:ff:ff:ff
inet 172.19.211.64/25 brd 172.19.211.127 scope global noprefixroute 
wwan0

   valid_lft forever preferred_lft forever

$ ping -c 1 172.19.211.64
PING 172.19.211.64 (172.19.211.64) 56(84) bytes of data.
64 bytes from 172.19.211.64: icmp_seq=1 ttl=64 time=0.057 ms
--- 172.19.211.64 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.057/0.057/0.057/0.000 ms

$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt 
Iface
0.0.0.0 172.19.211.10.0.0.0 UG0 0  0 
wwan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
wwan0
172.19.211.00.0.0.0 255.255.255.128 U 0 0  0 
wwan0


$ ping -c 1 172.19.211.1
PING 172.19.211.1 (172.19.211.1) 56(84) bytes of data.
--- 172.19.211.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms



El 17/3/23 a les 11:35, Josep Lladonosa ha escrit:

Hola, Adrià, Narcís,

A la feina ens vam trobar que a partir d'una determinada versió Ubuntu 
determinats USB 3G van deixar de funcionar.
Actualment s'utilitzen "encaminadors" amb bateria (que es carreguen per 
USB) que porten la SIM i engegats donen una WiFi a la que diversos 
equips poden connectar alhora.


Si no recordo malament, hi havia temes de reconeixement de dispositiu 
com a emmagatzematge (que no seria el teu cas) i altres temes de com 
s'usa el PPP.
Aquests adaptadors 3G/4G no deixen de ser aparells que estableixen 
connexions a l'estil dels "antics" mòdems. Podria ser que es faci la 
connexió PPP però a aquesta no se la definís com a ruta per defecte.

Estic aportant des de la imaginació i aquest supòsit.

Cordialment,
Josep

On Fri, 17 Mar 2023 at 11:24, Adrià <mailto:ad...@fsfe.org>> wrote:


Am 16/03/2023 um 14:18 schrieb Narcis Garcia:
 > No tinc ni idea de què fer amb Wireshark per a comprovar no sé el
què.
 > A GNU/Linux el dispositiu es configura (IP, porta, DNS), però no
 > aconsegueixo arribar a cap servei extern, ni tan sols respon ping
cap a
 > la porta d'enllaç ni els servidors DNS, ni aquests resolen adreces.
 > Com a molt la pròpia IP pública respon a ping, però qualsevol IP
 > d'Internet ja no.

Hola Narcís,

en aquest cas, i havent provat que amb un altre sistema operatiu pot
funcionar, cal descartar que l'operador posi pals a les rodes.

Jo et diria de comprovar si un tallafocs està impedint la connexió
d'aquesta interfície de xarxa (amb això Wireshark podria ajudar veient
que s'envien paquets a l'altre extrem i veient si hi arriben o què
passa
amb la resposta), però com que ho has provat amb un parell d'Ubuntus on
entenc que el tallafocs ve desactivat per defecte, llavors no sabria
què
dir-te.

El que m'estranya és que el ping respongui a la IP pública mentre
que no
ho faci a la porta d'enllaç; no li veig el sentit.

Jo analitzaria una connexió simple (ICMP, o sigui ping) contra un
dispositiu del mateix segment de xarxa amb el Wireshark, i
n'interpretaria els resultats. Que no funcioni res _ho puc arribar a
entendre_, però que funcioni el ping només a la pròpia IP pública em
desconcerta.

A veure si a algú més se li acut alguna altra cosa perquè puguis provar.



--
--
Salutacions...Josep
--


--


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.

Re: (deb-cat) Utilitzar un modem GSM

[Josep Lladonosa]

Hola, Adrià, Narcís,

A la feina ens vam trobar que a partir d'una determinada versió Ubuntu
determinats USB 3G van deixar de funcionar.
Actualment s'utilitzen "encaminadors" amb bateria (que es carreguen per
USB) que porten la SIM i engegats donen una WiFi a la que diversos equips
poden connectar alhora.

Si no recordo malament, hi havia temes de reconeixement de dispositiu com a
emmagatzematge (que no seria el teu cas) i altres temes de com s'usa el PPP.
Aquests adaptadors 3G/4G no deixen de ser aparells que estableixen
connexions a l'estil dels "antics" mòdems. Podria ser que es faci la
connexió PPP però a aquesta no se la definís com a ruta per defecte.
Estic aportant des de la imaginació i aquest supòsit.

Cordialment,
Josep

On Fri, 17 Mar 2023 at 11:24, Adrià  wrote:

> Am 16/03/2023 um 14:18 schrieb Narcis Garcia:
> > No tinc ni idea de què fer amb Wireshark per a comprovar no sé el què.
> > A GNU/Linux el dispositiu es configura (IP, porta, DNS), però no
> > aconsegueixo arribar a cap servei extern, ni tan sols respon ping cap a
> > la porta d'enllaç ni els servidors DNS, ni aquests resolen adreces.
> > Com a molt la pròpia IP pública respon a ping, però qualsevol IP
> > d'Internet ja no.
>
> Hola Narcís,
>
> en aquest cas, i havent provat que amb un altre sistema operatiu pot
> funcionar, cal descartar que l'operador posi pals a les rodes.
>
> Jo et diria de comprovar si un tallafocs està impedint la connexió
> d'aquesta interfície de xarxa (amb això Wireshark podria ajudar veient
> que s'envien paquets a l'altre extrem i veient si hi arriben o què passa
> amb la resposta), però com que ho has provat amb un parell d'Ubuntus on
> entenc que el tallafocs ve desactivat per defecte, llavors no sabria què
> dir-te.
>
> El que m'estranya és que el ping respongui a la IP pública mentre que no
> ho faci a la porta d'enllaç; no li veig el sentit.
>
> Jo analitzaria una connexió simple (ICMP, o sigui ping) contra un
> dispositiu del mateix segment de xarxa amb el Wireshark, i
> n'interpretaria els resultats. Que no funcioni res _ho puc arribar a
> entendre_, però que funcioni el ping només a la pròpia IP pública em
> desconcerta.
>
> A veure si a algú més se li acut alguna altra cosa perquè puguis provar.
>
>

-- 
--
Salutacions...Josep
--

Re: (deb-cat) Utilitzar un modem GSM

[Adrià]

Am 16/03/2023 um 14:18 schrieb Narcis Garcia:

No tinc ni idea de què fer amb Wireshark per a comprovar no sé el què.
A GNU/Linux el dispositiu es configura (IP, porta, DNS), però no 
aconsegueixo arribar a cap servei extern, ni tan sols respon ping cap a 
la porta d'enllaç ni els servidors DNS, ni aquests resolen adreces.
Com a molt la pròpia IP pública respon a ping, però qualsevol IP 
d'Internet ja no.


Hola Narcís,

en aquest cas, i havent provat que amb un altre sistema operatiu pot 
funcionar, cal descartar que l'operador posi pals a les rodes.


Jo et diria de comprovar si un tallafocs està impedint la connexió 
d'aquesta interfície de xarxa (amb això Wireshark podria ajudar veient 
que s'envien paquets a l'altre extrem i veient si hi arriben o què passa 
amb la resposta), però com que ho has provat amb un parell d'Ubuntus on 
entenc que el tallafocs ve desactivat per defecte, llavors no sabria què 
dir-te.


El que m'estranya és que el ping respongui a la IP pública mentre que no 
ho faci a la porta d'enllaç; no li veig el sentit.


Jo analitzaria una connexió simple (ICMP, o sigui ping) contra un 
dispositiu del mateix segment de xarxa amb el Wireshark, i 
n'interpretaria els resultats. Que no funcioni res _ho puc arribar a 
entendre_, però que funcioni el ping només a la pròpia IP pública em 
desconcerta.


A veure si a algú més se li acut alguna altra cosa perquè puguis provar.

Re: (deb-cat) Utilitzar un modem GSM

[Narcis Garcia]

El 6/2/23 a les 21:27, Adrià ha escrit:

Am 06/02/2023 um 14:08 schrieb Narcis Garcia:

 > He arribat fins al punt que realitza la connexió de xarxa (indica
 > cobertura, autoassigna IP pròpia, porta d'enllaç i DNS), però
 > aconsegueixo fer CAP comunicació via TCP, ICMP o DNS.
 > El «ping» es queda esperant sense resultat per a qualsevol adreça
 > no-local que li demani (incloent a porta d'enllaç).
 >
 > Algú sap com esbrinar on és ara el problema?

Jo miraria amb un analitzador de tràfic tipus Wireshark què està 
passant. Això per esbrinar tècnicament què passa.


A nivell pràctic, però, preguntaria a l'operadora si permeten usar la 
línia com a mòdem, perquè si es pot implementar qualsevol mesura que 
discrimini l'ús que es fa d'un servei, ho faran si veuen que pot 
reportar-los qualsevol benefici. I de vegades és millor sortir de dubtes 
que trencar-se les banyes amb un problema (tot i que ho puguem trobar 
entretingut, divertit i satisfactori quan el solucionem).




Gràcies Adrià; tenia aquest fil en espera de comprovar en el possible el 
tema de l'operador telefònic. No n'he tret l'aigua del tot clara, ja que 
a la central (per telèfon) em deien que les targetes SIM que utilitzo no 
són per a modem sinó per a terminals amb sistema operatiu xungo 
(Android, iOS) i em derivaven a una botiga de la cadena.
I a la botiga em diuen que l'operador no diferencia entre targetes SIM 
per aquest tema. I a la botiga em van demostrar que la meva targeta SIM 
funciona perfectament amb un router meu que jo portava.


A la botiga no vaig posar a prova un llapis-modem USB ni el modem 
integrat lt4112 perquè ja sé que ens embolicaríem amb què utilitzo 
programari estrany, i què estic carregant el controlador a mà.
Ara també he provat amb Ubuntu 22.04 (Live) i Ubuntu 22.10 (Live) amb el 
mateix resultat, negatiu.
Finalment, i per a rematar les comprovacions, he instal·lat MS-Windows 
10. Doncs resulta que funciona perfectament: Detecta el dispositiu 
intern (HP lt4112 Gobi 4G) i amb dir-li que connecti a la xarxa tan sols 
demana el PIN i ja està. Es navega perfectament amb EDGE/2G i LTE/4G.


No tinc ni idea de què fer amb Wireshark per a comprovar no sé el què.
A GNU/Linux el dispositiu es configura (IP, porta, DNS), però no 
aconsegueixo arribar a cap servei extern, ni tan sols respon ping cap a 
la porta d'enllaç ni els servidors DNS, ni aquests resolen adreces.
Com a molt la pròpia IP pública respon a ping, però qualsevol IP 
d'Internet ja no.


--

Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

Re: (deb-cat) Utilitzar un modem GSM

[Adrià]

Am 06/02/2023 um 14:08 schrieb Narcis Garcia:

> He arribat fins al punt que realitza la connexió de xarxa (indica
> cobertura, autoassigna IP pròpia, porta d'enllaç i DNS), però
> aconsegueixo fer CAP comunicació via TCP, ICMP o DNS.
> El «ping» es queda esperant sense resultat per a qualsevol adreça
> no-local que li demani (incloent a porta d'enllaç).
>
> Algú sap com esbrinar on és ara el problema?

Jo miraria amb un analitzador de tràfic tipus Wireshark què està 
passant. Això per esbrinar tècnicament què passa.


A nivell pràctic, però, preguntaria a l'operadora si permeten usar la 
línia com a mòdem, perquè si es pot implementar qualsevol mesura que 
discrimini l'ús que es fa d'un servei, ho faran si veuen que pot 
reportar-los qualsevol benefici. I de vegades és millor sortir de dubtes 
que trencar-se les banyes amb un problema (tot i que ho puguem trobar 
entretingut, divertit i satisfactori quan el solucionem).

(deb-cat) Utilitzar un modem GSM

[Narcis Garcia]

Bones,

Estic intentant utilitzar una connexió mòbil amb un ordinador portàtil 
que ja porta integrat un modem GSM (HP, Inc lt4112 Gobi 4G Module 
Network Device).
Li he ficat una targeta SIM (que abans he comprovat amb un telèfon que 
connecta amb tots els serveis), i m'hi he anat trencant el cap fins 
aconseguir que el NetworkManager detecti bé el modem i així crear-li un 
perfil de connexió.


He arribat fins al punt que realitza la connexió de xarxa (indica 
cobertura, autoassigna IP pròpia, porta d'enllaç i DNS), però 
aconsegueixo fer CAP comunicació via TCP, ICMP o DNS.
El «ping» es queda esperant sense resultat per a qualsevol adreça 
no-local que li demani (incloent a porta d'enllaç).


Algú sap com esbrinar on és ara el problema?

Tinc el gobi-loader instal·lat però no sé si realment l'utilitza el 
sistema, i he instal·lat el gsm-utils però per a qualsevol operació 
sobre /dev/cdc-wdm0 em diu «errno: 25/Inappropriate ioctl for device»


Gràcies.

--


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.

Re: Qualcomm Snapdragon X12 LTE Modem

[Grzesiek]

Replaying to myself:

To get iIP information use the following:


# mmcli -m 0 -b 1
  
  General|  dbus path: /org/freedesktop/ModemManager1/Bearer/1
 |   type: default
  
  Status |  connected: yes
 |  suspended: no
 |  interface: wwan0
 | ip timeout: 20
  
  Properties |apn: darmowy
 |roaming: allowed
  
  IPv4 configuration | method: static
 |address: 100.83.243.37
 | prefix: 30
 |gateway: 100.83.243.38
 |dns: 212.2.127.254, 212.2.96.52
 |mtu: 1500
  
  Statistics |   attempts: 1

Re: Qualcomm Snapdragon X12 LTE Modem

[Grzesiek]

On 5/25/21 10:33 PM, Polyna-Maude Racicot-Summerside wrote:

Hi !
How about using dhclient ?


Does not work (like udhcpc).

Greg

Re: Qualcomm Snapdragon X12 LTE Modem

[Grzesiek Sójka]

Hi there,

I managed to connect _but_ I do no know how to obtain address. I tried:

udhcpc -q -f -n -i wwan0

no luck, unfortunately. Any suggestions?

To connect I use the following:

# mmcli -m 0 --simple-connect="apn=darmowy"
successfully connected the modem
# mmcli -m 0
  
  General  |dbus path: 
/org/freedesktop/ModemManager1/Modem/0
   |device id: 
09cd50ccb01495e91195c6792755a95ef0ad604c

  
  Hardware | manufacturer: Qualcomm
   |model: Snapdragon(TM) X12 LTE-A
   |firmware revision: T77W676.F0.0.0.4.7.GC.017
   |   041
   | h/w revision: Snapdragon(TM) X12 LTE-A
   |supported: gsm-umts, lte
   |  current: gsm-umts, lte
   | equipment id: 359195080308286
  
  System   |   device: 
/sys/devices/pci:00/:00:14.0/usb2/2-3

   |  drivers: cdc_mbim
   |   plugin: generic
   | primary port: cdc-wdm2
   |ports: cdc-wdm2 (mbim), wwan0 (net)
  
  Status   |   unlock retries: sim-pin2 (3)
   |state: connected
   |  power state: on
   |  access tech: lte
   |   signal quality: 9% (recent)
  
  Modes|supported: allowed: 3g; preferred: none
   |   allowed: 4g; preferred: none
   |   allowed: 3g, 4g; preferred: 4g
   |   allowed: 3g, 4g; preferred: 3g
   |  current: allowed: 3g, 4g; preferred: 4g
  
  Bands|supported: utran-1, utran-4, utran-6,
   |   utran-5, utran-8, utran-2,
   |   eutran-1, eutran-2, eutran-3,
   |   eutran-4, eutran-5, eutran-7,
   |   eutran-8,
   |   eutran-12, eutran-13, eutran-17,
   |   eutran-18, eutran-19, eutran-20,
   |   eutran-21, eutran-25, eutran-26,
   |   eutran-28, eutran-29, eutran-30,
   |   eutran-38, eutran-39, eutran-40,
   |   eutran-41, eutran-66, utran-19
   |  current: utran-1, utran-4, utran-6,
   |   utran-5, utran-8, utran-2,
   |   eutran-1, eutran-2, eutran-3,
   |   eutran-4, eutran-5, eutran-7,
   |   eutran-8,
   |   eutran-12, eutran-13, eutran-17,
   |   eutran-18, eutran-19, eutran-20,
   |   eutran-21, eutran-25, eutran-26,
   |   eutran-28, eutran-29, eutran-30,
   |   eutran-38, eutran-39, eutran-40,
   |   eutran-41, eutran-66, utran-19
  
  IP   |supported: ipv4, ipv6, ipv4v6
  
  3GPP | imei: 3591950803
   |enabled locks: fixed-dialing
   |  operator id: 26001
   |operator name: Aero2
   | registration: home
  
  3GPP EPS | initial bearer dbus path: 
/org/freedesktop/ModemManager1/Bearer/0

  
  SIM  |dbus path: /org/freedesktop/ModemManager1/SIM/0
  
  Bearer   |dbus path: 
/org/freedesktop/ModemManager1/Bearer/1



Regards
Greg

Re: Modem MACs and how ISPs view them, was Re: on the verge of …

[rhkramer]

On Tuesday, March 09, 2021 03:54:18 PM David Wright wrote:
> On Tue 09 Mar 2021 at 08:12:47 (-0500), rhkra...@gmail.com wrote:
> > I have DSL service, and a spare modem that I've occasionally put in
> > service (for testing the "main" modem) and have not had to notify the
> > ISP.  (They were both provided by the ISP (Earthlink).)
> > 
> > I don't know if cable modems would work the same -- I don't know if the
> > ISP sees the MAC address on a DSL line.
> 
> You may well have login authentication. Perhaps you have the
> credentials configured in the router, and forgotten that they're
> there.

Well, I know I have login authentication, and the credentials in one case are 
in the router (the modem is in bridge mode or whatever the right term is), and 
in the other case, the credentials are in the modem (which also does the 
routing), with a switch downstream (to send Ethernet to 3 different parts of my 
home).

But, I don't know (but don't think) that the ISP sees the MAC address of 
either the modem in one case, or the router in the other case (or the modem in 
"bridge mode").

But, my comment was only intended to be a data point, so unless someone knows 
whether or not the MAC address is seen by the ISP, there is no need to follow 
up on this (that I can see).

Re: Modem MACs and how ISPs view them, was Re: on the verge of …

[IL Ka]

I will try to share my knowledge about DSL and DOCSIS (cable modems)
although it may be inaccurate and/or outdated and valid only for my country.

MAC address only exists in Ethernet networks or something that emulates it.
Ethernet (Level 2) networks are connected with Level 3 devices called
routers.
MAC address is only visible inside of one Ethernet network, so anyone on
the other side of the router doesn't know your MAC address.

Both DOCSIS (cable) modem and DSL modem can run in one of two modes:

* Router mode. In this mode it acts as a router (Level 3 device) and your
Ethernet traffic (Level 2) never goes to the ISP.
Your PC mac address is not important in this scenario.

* Bridge mode: modem forwards your Ethernet traffic to the ISP and your MAC
address may be important here (at least, your ISP may see it)

With DSL you have a modem (either standalone or built into a DSL router)
Your modem connects to your ISP's device (called DSLAM).

There is a protocol called ATM that runs on top of DSL.

ATM uses VPI and VCI to create a "virtual channel" between your modem and
ISP device.
These two numbers (VPI/VCI) are used to "address" a device inside of ISP's
ATM network.

Then, ATM creates a so-called AAL (ATM adaptation layer) to run some
protocol on top of it.

* It can run IP directly on top of an ATM. There is no MAC address here and
only router mode is supported.
* It can run PPP over ATM (PPPoA): again, no MAC address, much like dialup.
PPP runs some protocol to authenticate you (PAP, CHAP or some other). Only
router mode is supported.
* It can emulate Ethernet. It is called LANE. It uses a MAC address! In
bridge mode your MAC address is important. In router mode it is not.
* It can run PPP over emulated Ethernet (previous case but with PPP on top
of it). PPPoE. In bridge mode you run PPP on your PC and MAC address may be
important
(sometimes it is not not, if your ISP uses PAP or CHAP to authenticate
you). In router mode PPP runs on your modem and PC MAC address is
irrelevant.

Most ISPs in my country prefer to run PPP (ether over ATM (PPPoA) or over
emulated Ethernet using PPP over Ethernet (PPPoE))
because PPP is a convenient protocol for AAA (accounting authorization
authentication)

I've seen an ISP that uses PPTP (vpn) over IP over emulated Ethernet. Modem
in router mode provides your PC access to the network, and then you run VPN
client on your PC.
Again, ISP doesn't see your PC mac address.

https://flylib.com/books/3/206/1/html/2/images/0130938106/graphics/14fig02.gif

Honestly, I have never seen an ADSL ISP that cares about the MAC address.
Usually they are happy with PPP login/password.


With DOCSIS (cable modem) your modem connects to the ISP device named CMTS.
It then downloads configuration from ISP.
There is no MAC address at this moment.

Then, it switches to the one of the two following modes:
* Bridge mode: modem acts as bridge (ethernet switch). It forwards your
Ethernet
frames from your PC, so ISP is aware of your PC mac address.
In most cases it happens when you connect your PC to the Ethernet (RJ45)
port on your cable modem.

Almost always the MAC address is important in this case! You must tell your
ISP which MAC you are going to use.
Or you can change your NIC's mac address to the one ISP already knows about.

* Router mode: modem acts as router. It uses its internal MAC address
(written
on small white paper on the modem) and then forwards IP packets to your PC.
It happens when you connect your PC to the USB port of your modem.

Most DOCSIS ISPs in my country prefer bridge mode and ask for your MAC
address.

But if you connect WiFi router to your modem (so you have two different
devices) ISP only sees your router's mac address, not your PC address.
Remember: mac address never crosses your router because router terminates
level 2 (Ethernet) network.
https://www.cisco.com/en/US/docs/cable/modems/ubr924/configuration/guide/scg924bc.html

Conclusion:

For bridge mode MAC address may be important (but with ADSL chances are
high that ISP uses PPP authentication (PAP, CHAP) and doesn't care about
MAC address).
For router mode your MAC address is never important

If you are using a Wifi router then your PC MAC is never important.

Typical setup in my country:
For DSL:  Wifi router with DSL modem built into it. It runs some kind of
PPP and doesn't care about your MAC address.
For DOCSIS: Cable modem in bridge mode + Wifi router. You must set your
Wifi router MAC address to the one ISP knows about. But your PC MAC is not
important.

Re: Modem MACs and how ISPs view them, was Re: on the verge of …

[Nicholas Geovanis]

My sanity requires top-posting:
See your very last sentence:
You go to an HTTP port at a non-routable address which should be on the
box. Usually on a yellow sticker. Now I've never tried to program that
interaction but I bet it could be done. For comparison, biggish Juniper
routers are configured by salt/saltstack these days. Just like your linux
server farm.

But maybe start trying with wget or curl. Work your way up the language
hierarchy.  HTH.

On Tue, Mar 9, 2021, 2:54 PM David Wright  wrote:

> Change of topic overdue:
>
> On Tue 09 Mar 2021 at 00:12:40 (-0500), Felix Miata wrote:
> > David Wright composed on 2021-03-08 22:37 (UTC-0600):
> > > On Sun 07 Mar 2021 at 21:37:37 (-0500), Felix Miata wrote:
> >
> > >> Having != connected. The extras are spares. :)
> >
> > > I realise that, but if your service were to become unsatisfactory,
> > > then before you complained, you'd want to check that it's not your
> > > modem at fault. Would you expect your spare modem to work, because it
> > > has a different MAC from what's expected by the ISP's end of the line.
> >
> > > (Similarly, if your modem were to burn out, which is what happened
> > > to mine after seven years.)
> >
> > Whenever I get a mind to, I call my ISP, tell them I'm changing modems,
> and what
> > the new MAC is. It gives me some confidence it's still useful. If
> there's a
> > problem they or I think a modem switch might shed light on, I do the
> same.
>
> Perhaps I'll try that as things settle after the pandemic.
> I changed our modem within two hours, but that was with a visit
> to the office (2½ miles), and the replacement one is rented.
>
> I'll change it out when not every day is a zoom day. At the
> moment, the internet is still about as important as running
> water.
>
> On Tue 09 Mar 2021 at 08:12:47 (-0500), rhkra...@gmail.com wrote:
>
> > I have DSL service, and a spare modem that I've occasionally put in
> service
> > (for testing the "main" modem) and have not had to notify the ISP.
> (They were
> > both provided by the ISP (Earthlink).)
> >
> > I don't know if cable modems would work the same -- I don't know if the
> ISP
> > sees the MAC address on a DSL line.
>
> You may well have login authentication. Perhaps you have the
> credentials configured in the router, and forgotten that they're
> there.
>
> On Tue 09 Mar 2021 at 13:35:18 (+), Joe wrote:
> > On Tue, 9 Mar 2021 08:12:47 -0500 rhkra...@gmail.com wrote:
> > >
> > > I have DSL service, and a spare modem that I've occasionally put in
> > > service (for testing the "main" modem) and have not had to notify the
> > > ISP.  (They were both provided by the ISP (Earthlink).)
> > >
> > > I don't know if cable modems would work the same -- I don't know if
> > > the ISP sees the MAC address on a DSL line.
> >
> > I used to change routers without telling anyone, but that was years ago.
>
> That doesn't add a lot of information as you've not mentioned
> the type of connection. (I presume router means a modem/router
> combination.)
>
> > As an anecdote, I recall a BT service/router which literally would not
> > work if it detected another NAT on the LAN. It was in a client's
> > network, and I had to reconfigure things to work without the Debian
> > server acting as a firewall. If it had been my network, the wretched
> > thing would have gone back instantly, my network runs through two NATs
> > and that isn't negotiable.
>
> I had a BT service briefly (replacing a plusnet service running over
> a BT line), and they supplied a Homehub. AFAICT the authentication, if
> any, was "burnt" into modem and router combination, and the T didn't
> allow for you to swap it out.
>
> On Tue 09 Mar 2021 at 10:07:39 (-0500), Stefan Monnier wrote:
> >
> > You should be able to change the MAC used by your device, i.e. you
> > should be able to arrange for both devices to expose the same MAC so
> > your ISP won't notice the difference.
>
> Quite possibly, though I'd rather not have to do that if possible.
> As well as the MAC, there is also a Serial Number and a Modem Number,
> and AIUI the device logs changes such as these that are made, at
> least as long as they stick (perhaps until a factory reset?).
>
> What software would I need? For example, how would I alter the MAC
> address on this Cicso DPC3010 modem? If I connect a computer to its
> Ethernet port, all I see is the seething morass called the Internet.
> How do I talk to it, ie to the modem itself?
>
> Cheers,
> David.
>
>

Modem MACs and how ISPs view them, was Re: on the verge of …

[David Wright]

Change of topic overdue:

On Tue 09 Mar 2021 at 00:12:40 (-0500), Felix Miata wrote:
> David Wright composed on 2021-03-08 22:37 (UTC-0600):
> > On Sun 07 Mar 2021 at 21:37:37 (-0500), Felix Miata wrote:
> 
> >> Having != connected. The extras are spares. :)
> 
> > I realise that, but if your service were to become unsatisfactory,
> > then before you complained, you'd want to check that it's not your
> > modem at fault. Would you expect your spare modem to work, because it
> > has a different MAC from what's expected by the ISP's end of the line.
> 
> > (Similarly, if your modem were to burn out, which is what happened
> > to mine after seven years.)
> 
> Whenever I get a mind to, I call my ISP, tell them I'm changing modems, and 
> what
> the new MAC is. It gives me some confidence it's still useful. If there's a
> problem they or I think a modem switch might shed light on, I do the same.

Perhaps I'll try that as things settle after the pandemic.
I changed our modem within two hours, but that was with a visit
to the office (2½ miles), and the replacement one is rented.

I'll change it out when not every day is a zoom day. At the
moment, the internet is still about as important as running
water.

On Tue 09 Mar 2021 at 08:12:47 (-0500), rhkra...@gmail.com wrote:

> I have DSL service, and a spare modem that I've occasionally put in service 
> (for testing the "main" modem) and have not had to notify the ISP.  (They 
> were 
> both provided by the ISP (Earthlink).)
> 
> I don't know if cable modems would work the same -- I don't know if the ISP 
> sees the MAC address on a DSL line.

You may well have login authentication. Perhaps you have the
credentials configured in the router, and forgotten that they're
there.

On Tue 09 Mar 2021 at 13:35:18 (+), Joe wrote:
> On Tue, 9 Mar 2021 08:12:47 -0500 rhkra...@gmail.com wrote:
> > 
> > I have DSL service, and a spare modem that I've occasionally put in
> > service (for testing the "main" modem) and have not had to notify the
> > ISP.  (They were both provided by the ISP (Earthlink).)
> > 
> > I don't know if cable modems would work the same -- I don't know if
> > the ISP sees the MAC address on a DSL line.
> 
> I used to change routers without telling anyone, but that was years ago.

That doesn't add a lot of information as you've not mentioned
the type of connection. (I presume router means a modem/router
combination.)

> As an anecdote, I recall a BT service/router which literally would not
> work if it detected another NAT on the LAN. It was in a client's
> network, and I had to reconfigure things to work without the Debian
> server acting as a firewall. If it had been my network, the wretched
> thing would have gone back instantly, my network runs through two NATs
> and that isn't negotiable.

I had a BT service briefly (replacing a plusnet service running over
a BT line), and they supplied a Homehub. AFAICT the authentication, if
any, was "burnt" into modem and router combination, and the T didn't
allow for you to swap it out.

On Tue 09 Mar 2021 at 10:07:39 (-0500), Stefan Monnier wrote:
> 
> You should be able to change the MAC used by your device, i.e. you
> should be able to arrange for both devices to expose the same MAC so
> your ISP won't notice the difference.

Quite possibly, though I'd rather not have to do that if possible.
As well as the MAC, there is also a Serial Number and a Modem Number,
and AIUI the device logs changes such as these that are made, at
least as long as they stick (perhaps until a factory reset?).

What software would I need? For example, how would I alter the MAC
address on this Cicso DPC3010 modem? If I connect a computer to its
Ethernet port, all I see is the seething morass called the Internet.
How do I talk to it, ie to the modem itself?

Cheers,
David.

Re: Qualcomm Snapdragon X12 LTE Modem

[Celejar]

On Tue, 18 Aug 2020 10:18:51 +0200
Grzesiek Sójka  wrote:

> Hi there,
> 
> To be more specific: I already installed Debian Sid and the tablet is HP 
> Elite X2 1013 G3. I'm trying to learn how to use the modem mentioned to 
> connect to the internet.

Disclaimer: I have no experience with this sort of thing, but here are
some possible leads.

This post claims that LTE on that device works under linux:

https://www.reddit.com/r/linux/comments/9sxymj/linux_driver_compatibility_with_modern_2in1/

You may need something like the 'libmbim-utils' package. Perhaps
this page will help you out:

https://gist.github.com/Juul/e42c5b6ec71ce11923526b36d3f1cb2c

Another option seems to be the 'modemmanager' package. This seems to be
a higher level tool (it has dependencies on some libmbim packages).

Celejar

Re: Qualcomm Snapdragon X12 LTE Modem

[Grzesiek Sójka]

Hi there,

To be more specific: I already installed Debian Sid and the tablet is HP 
Elite X2 1013 G3. I'm trying to learn how to use the modem mentioned to 
connect to the internet.

Re: Qualcomm Snapdragon X12 LTE Modem

[Celejar]

On Tue, 18 Aug 2020 01:33:58 +0200
Grzesiek Sójka  wrote:

> Hi there,
> 
> I have a tablet equipped with the modem mentioned above. I do not have 
> any experience with such devices. I would be grateful for some links 
> with some information how to use it on Debian.

Are you trying to install Debian on the tablet (or have already done
so), or do you want to use the tablet and its modem to connect a Debian
system to a network?

Celejar

Re: Qualcomm Snapdragon X12 LTE Modem

[deloptes]

Grzesiek Sójka wrote:

> I have a tablet equipped with the modem mentioned above. I do not have
> any experience with such devices. I would be grateful for some links
> with some information how to use it on Debian.

Is your tablet running debian - can you share make and model of the tablet?

Qualcomm Snapdragon X12 LTE Modem

[Grzesiek Sójka]

Hi there,

I have a tablet equipped with the modem mentioned above. I do not have 
any experience with such devices. I would be grateful for some links 
with some information how to use it on Debian.


regards

Re: Accès depuis Debian à l'interface web d'un modem D-Link DSL-320B

[Sébastien Dinot]

Olivier a écrit :
> 3. Echec avec Chromium/GalliumOS, Chromium/Jessie.

Certes, mais que ce passe-t-il exactement dans ce cas là ? Quel est le
message d'erreur et/ou le comportement constaté ?

Sébastien

-- 
Sébastien Dinot, sebastien.di...@free.fr
http://www.palabritudes.net/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Re: Accès depuis Debian à l'interface web d'un modem D-Link DSL-320B

[Olivier]

1. L'erreur exacte est ERR_CONNECTION_REFUSED.

Sur Windows, quand je saisis l'URL http://192.168.1.1 du modem, il y a un
formulaire "Sécurité Windows" (Edge/win10) ou "Ouvrir une session"
(Chrome/win10) qui s'affiche
et qui me demande la saisie d'un login-mot de passe.

Le Dlink DSL-320B est un très vieux produit qui est visiblement encore
fourni par des opérateurs.

2. J'ai aussi réussi à accéder à l'interface web dans les 2 cas suivants:
Firefox/Jessie, Firefox/GalliumOS (dérivé d'Ubuntu).

3. Echec avec Chromium/GalliumOS, Chromium/Jessie.

J'ai donc une solution de contournement mais reste frustré par sa nécessité
!

Le jeu. 28 mai 2020 à 23:00, Sébastien Dinot  a
écrit :

> Bonsoir,
>
> Olivier a écrit :
> > J'ai réussi à le faire avec un PC sous Windows 10 mais j'ai
> > systématiquement un message d'erreur (je ne me rappelle plus du
> > message exact) quand je le fais avec le navigateur d'une machine sous
> > debian (Firefox, Chromium).
>
> Justement, sans avoir le message d'erreur exact, il est bien difficile
> de poser un diagnostic. Par expérience (générale et non de ce modem que
> je ne connais pas), je pencherais pour un problème de certificat TLS/SSL
> auto-signé, refusé par les navigateurs, de plus en plus pointilleux - et
> avec raison - sur ce point. Je dirais donc qu'il faut passer outre et
> accepter une exception. Cela doit être faisable avec Firefox, mais je ne
> suis pas certain que ce le soit avec Chromium.
>
> Si le problème est bien celui-là mais que les versions de Firefox ou de
> Chromium utilisées ne permettent pas de passer outre ce contrôle, il
> faut récupérer le certificat du serveur web du modem et l'ajouter au
> trousseau local de certificats de Firefox ou du système. Pour cela, il
> est possible d'utiliser la commande s_client d'OpenSSL.
>
> Sébastien
>
> --
> Sébastien Dinot, sebastien.di...@free.fr
> http://www.palabritudes.net/
> Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !
>
>

Re: Accès depuis Debian à l'interface web d'un modem D-Link DSL-320B

[Sébastien Dinot]

Bonsoir,

Olivier a écrit :
> J'ai réussi à le faire avec un PC sous Windows 10 mais j'ai
> systématiquement un message d'erreur (je ne me rappelle plus du
> message exact) quand je le fais avec le navigateur d'une machine sous
> debian (Firefox, Chromium).

Justement, sans avoir le message d'erreur exact, il est bien difficile
de poser un diagnostic. Par expérience (générale et non de ce modem que
je ne connais pas), je pencherais pour un problème de certificat TLS/SSL
auto-signé, refusé par les navigateurs, de plus en plus pointilleux - et
avec raison - sur ce point. Je dirais donc qu'il faut passer outre et
accepter une exception. Cela doit être faisable avec Firefox, mais je ne
suis pas certain que ce le soit avec Chromium.

Si le problème est bien celui-là mais que les versions de Firefox ou de
Chromium utilisées ne permettent pas de passer outre ce contrôle, il
faut récupérer le certificat du serveur web du modem et l'ajouter au
trousseau local de certificats de Firefox ou du système. Pour cela, il
est possible d'utiliser la commande s_client d'OpenSSL.

Sébastien

-- 
Sébastien Dinot, sebastien.di...@free.fr
http://www.palabritudes.net/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Accès depuis Debian à l'interface web d'un modem D-Link DSL-320B

[Olivier]

Bonjour,

Je souhaite accéder à l'interface de configuration d'un modem ADSL D-Link
DSL-320B.

J'ai réussi à le faire avec un PC sous Windows 10 mais j'ai
systématiquement un message d'erreur (je ne me rappelle plus du message
exact) quand je le fais avec le navigateur d'une machine sous debian
(Firefox, Chromium).

Qui a testé avec succès un contournement simple (autre que se déplacer sur
site avec un PC sous Windows 10) ?

Slts

Re: voicecall via LTE internal modem

[deloptes]

Eri wrote:

> I'm using Debian Bullseye on a Thinkpad T490s with FIBOCOM L830-EB-00 WWAN
> modem.
> I would like to know if it is possible to make voice calls with that
> modem. I was able to make a phone call with AT COMMANDS
> ATD + NUMBER;
> or answer
> ATA
> 
> Tha user manual of the modem says that voice calls are allowed, but I can
> not find a way to have audio.
> Using mmcli with
> mmcli -m 0 --voice-status
> I get:
> error: modem has no voice capability
> 
> Anyone has better experience?
> 
> Thanks,
> Enrico Maria Casarotti

Did you install/try ofono? Look at the dbus interface

voicecall via LTE internal modem

[Eri]

I'm using Debian Bullseye on a Thinkpad T490s with FIBOCOM L830-EB-00 WWAN
modem.
I would like to know if it is possible to make voice calls with that modem.
I was able to make a phone call with AT COMMANDS
ATD + NUMBER;
or answer
ATA

Tha user manual of the modem says that voice calls are allowed, but I can
not find a way to have audio.
Using mmcli with
mmcli -m 0 --voice-status
I get:
error: modem has no voice capability

Anyone has better experience?

Thanks,
Enrico Maria Casarotti

Re: USB Fax modem yardım

[Umit Bozkir]

Selamlar,


On 4/9/19 6:10 AM, Recai Uyan wrote:

Merhaba, Conexant Systems (Rockwell), Inc. SoftK56 Data Fax Voice CARP
usb fax modem i günlerdir ubuntu 14.04 ve raspbian jessie ye
tanıtamıyorum. Bu konuda daha önce çalışmış olan yardımcı olabilecek
bir arkadaşa ihtiyacım var. Lütfen biliyorsanız yardımınızı rica
ediyorum.



Burada soyle bir sayfa [1] var. Yardimci olabilir (Sayfada 14.04 icin 
bir aciklama goremedim).



Iyi calismalar


1) https://help.ubuntu.com/community/DialupModemHowto/Conexant

USB Fax modem yardım

[Recai Uyan]

Merhaba, Conexant Systems (Rockwell), Inc. SoftK56 Data Fax Voice CARP
usb fax modem i günlerdir ubuntu 14.04 ve raspbian jessie ye
tanıtamıyorum. Bu konuda daha önce çalışmış olan yardımcı olabilecek
bir arkadaşa ihtiyacım var. Lütfen biliyorsanız yardımınızı rica
ediyorum.


Recai Uyan

Re: USB "null modem" cables and related Linux driver questions

[rhkramer]

On Monday, June 18, 2018 08:44:20 AM Michael Stone wrote:
> He really doesn't want a sensible solution, just let it go.

+1

Re: USB "null modem" cables and related Linux driver questions

[Richard Owlett]

On 06/18/2018 07:17 AM, David wrote:

On 1 June 2018 at 00:21, Richard Owlett  wrote:


I have two computers with USB ports.
I wish them to communicate as simply as mid-20th-century computers did.


What is the make and model number of each computer?


No longer a relevant question.
I have purchased a cable based on the Prolific PL-25A1 chipset.
Current kernels can make it look like an Ethernet connection.
Once I finish some configuration homework {primary motivation has 
shifted to education} I'll be able to have a client-server setup.

Re: USB "null modem" cables and related Linux driver questions

[Michael Stone]

On Mon, Jun 18, 2018 at 10:17:21PM +1000, David wrote:

On 1 June 2018 at 00:21, Richard Owlett  wrote:


I have two computers with USB ports.
I wish them to communicate as simply as mid-20th-century computers did.


What is the make and model number of each computer?


He really doesn't want a sensible solution, just let it go.

Re: USB "null modem" cables and related Linux driver questions

[David]

On 1 June 2018 at 00:21, Richard Owlett  wrote:
>
> I have two computers with USB ports.
> I wish them to communicate as simply as mid-20th-century computers did.

What is the make and model number of each computer?

Re: USB "null modem" cables and related Linux driver questions

[Michael Stone]

On Thu, Jun 07, 2018 at 08:07:15AM +0100, Tixy wrote:

On Wed, 2018-06-06 at 22:26 -0600, Joe Pfeiffer wrote:

Richard Owlett  writes:

> I have two computers with USB ports.
> I wish them to communicate as simply as mid-20th-century computers
> did.
> Then we used RS232-C with a null modem &/or  appropriate software
> software at both ends.
>
> The underlying problem is that both ends egotistically expect to be
> *MASTER*.
>
> The hardware problem is solvable
> [e.g. http://www.ftdichip.com/Products/Cables/USBtoUSB.htm].

Given how FTDI does things, I'd be really surprised if this didn't
meet
your desires.  Have you actually tried it?  Are you sure there is no
driver in the kernel?


There is a driver in Linux because, from what the datasheet says, that
cable is two of FTDIs standard USB-to-serial chips wired together. I.e.
it's equivalent to getting 2 USB to serial cables and connecting them
with a null modem cable.


Yes, that's right. I have no idea why someone would want to do that, but 
that's exactly what it is.


There are also usb transfer cables which are basically a proprietary 
FIFO buffer with a usb master on both sides, which allow higher speed 
networking.  (Which at least seems more useful than going through a 
RS-232 conversion, but much more limited than an actual network. In some 
cases where you want more than gigabit speeds and will never have more 
than two computers it might be useful. I'm not sure how many of them can 
connect machines with different OSs, either. This is the "laplink" style 
connection.)


If you want a true, standardized, network session over your peripheral 
connection, then get firewire. (This is what not having a bus master 
allows.) It'll be old hardware, because it turns out that nobody 
actually wanted to pay more so that every device could be a master, and 
so firewire died. But once upon a time, this was one of its big 
advantages over usb.


Mike Stone

Re: USB "null modem" cables and related Linux driver questions

[Curt]

On 2018-06-07, Joe Pfeiffer  wrote:
>
> This depends on what you mean by "universal".  It was intended to be a
> protocol for computers to use to communicate with peripherals;
> "universal" in this context was restricted to peripherals.

And to the planet earth rather than all the way to the furthest reaches
of the cosmos and back as I doubt whether the folks living out by
Kepler-16 have much use for them.

Re: USB "null modem" cables and related Linux driver questions

[Tixy]

On Wed, 2018-06-06 at 22:26 -0600, Joe Pfeiffer wrote:
> Richard Owlett  writes:
> 
> > I have two computers with USB ports.
> > I wish them to communicate as simply as mid-20th-century computers
> > did.
> > Then we used RS232-C with a null modem &/or  appropriate software
> > software at both ends.
> > 
> > The underlying problem is that both ends egotistically expect to be
> > *MASTER*.
> > 
> > The hardware problem is solvable
> > [e.g. http://www.ftdichip.com/Products/Cables/USBtoUSB.htm].
> 
> Given how FTDI does things, I'd be really surprised if this didn't
> meet
> your desires.  Have you actually tried it?  Are you sure there is no
> driver in the kernel?

There is a driver in Linux because, from what the datasheet says, that
cable is two of FTDIs standard USB-to-serial chips wired together. I.e.
it's equivalent to getting 2 USB to serial cables and connecting them
with a null modem cable.

-- 
Tixy

Re: USB "null modem" cables and related Linux driver questions

[Joe Pfeiffer]

Richard Owlett  writes:

> On 06/01/2018 08:21 AM, to...@tuxteam.de wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote:
 The one choice you have is that one of both sides takes a step
 back and plays "gadget" [...]
>>
>>> The gadget API is the programming API offered by the kernel for the OTG
>>> ports: no OTG => no gadget!
>>>
 [OTG]
>>
>>> More importantly, the USB ports which support OTG are driven by
>>> different hardware.
>>
>> Ah, so the hardware has to play along...
>>
>>> Right, you need both your hardware's USB port to support OTG and you
>>> need your kernel to have a driver that supports this hardware.
>>> AFAIK the driver is usually available.
>>
>> Did I say I was handwaving?
>>
>> Thanks for the clarifications!
>>
>
> It also suggests that I frequently grasp some of the implications of
> what I read. Thank you.
> As an illustration of my mindset:
> If they had really intended USB to be *UNIVERSAL* serial bus, then it
> should have been OTG from the get go.
> P.S. I know of thousands of reasons they did not.
>  Vast majority preceded by $ ;/

This depends on what you mean by "universal".  It was intended to be a
protocol for computers to use to communicate with peripherals;
"universal" in this context was restricted to peripherals.

Re: USB "null modem" cables and related Linux driver questions

[Joe Pfeiffer]

Richard Owlett  writes:

> I have two computers with USB ports.
> I wish them to communicate as simply as mid-20th-century computers did.
> Then we used RS232-C with a null modem &/or  appropriate software
> software at both ends.
>
> The underlying problem is that both ends egotistically expect to be
> *MASTER*.
>
> The hardware problem is solvable
> [e.g. http://www.ftdichip.com/Products/Cables/USBtoUSB.htm].

Given how FTDI does things, I'd be really surprised if this didn't meet
your desires.  Have you actually tried it?  Are you sure there is no
driver in the kernel?

As for your actual needs...  if you want two computers to communicate,
you really ought to be using some sort of networking hardware.  You've
got a computer with a USB port, no serial port, and no ethernet or wifi?

Re: USB "null modem" cables and related Linux driver questions

[David Wright]

On Fri 01 Jun 2018 at 09:08:53 (-0500), Richard Owlett wrote:
> On 06/01/2018 08:21 AM, to...@tuxteam.de wrote:
> >On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote:
> >>>The one choice you have is that one of both sides takes a step
> >>>back and plays "gadget" [...]
> >
> >>The gadget API is the programming API offered by the kernel for the OTG
> >>ports: no OTG => no gadget!
> >>
> >>>[OTG]
> >
> >>More importantly, the USB ports which support OTG are driven by
> >>different hardware.
> >
> >Ah, so the hardware has to play along...
> >
> >>Right, you need both your hardware's USB port to support OTG and you
> >>need your kernel to have a driver that supports this hardware.
> >>AFAIK the driver is usually available.
> >
> >Did I say I was handwaving?
> >
> >Thanks for the clarifications!
> >
> 
> It also suggests that I frequently grasp some of the implications of
> what I read. Thank you.
> As an illustration of my mindset:
> If they had really intended USB to be *UNIVERSAL* serial bus, then
> it should have been OTG from the get go.
> P.S. I know of thousands of reasons they did not.
>  Vast majority preceded by $ ;/

I think you're misunderstanding the use of the word universal.
USB was designed to be a universal way of connecting "any"
peripherals to a PC (sensu lato) which acts as a unique,
controlling host for them.

It wasn't designed to duplicate networking hardware, communicating
between multiple hosts. Nor was OTG. OTG was designed to allow, for
example, what's normally a peripheral to be disconnected from the
host, be connected to a peripheral and effectively become a host
controlling it. Eg, a camera could act as a peripheral while
uploading photos to a PC, then act as a host when connected to an
inkjet to print them.

Cheers,
David.

Re: USB "null modem" cables and related Linux driver questions

[Michael Stone]

On Fri, Jun 01, 2018 at 02:16:47PM -0500, Richard Owlett wrote:
USB-Ethernet dongles would be a lot more useful in the long term 
than USB-Serial dongles.


*WHO* said anything about a "USB-Serial dongle"?
I want a USB-USB object. Subtle, but important, distinction.


Well, you started out talking about RS232 and null modem cables, so 
don't be surprised if people are having trouble figuring out what you're 
asking for. Then you asked for better ideas. Then you got mad about all 
the ideas and started laughing hysterically. I have no idea what you 
actually want at this point.


RS-232 had a really good 40 year run, but for general communications 
it was mostly obsolete nearly 20 years ago. You mentioned file 
transfers-


So what?
I get grief for not mentioning immediate goals.
I casually mention a potential use and get *UNIVERSAL ADVICE*:
   Don't do that. !


So you can't articulate what you're trying to do at all? That will 
certainly reduce the odds of getting helpful advice.


It seems like you want to connect two computers via USB "just because". 
Good luck with that.


Mike Stone

Re: USB "null modem" cables and related Linux driver questions

[Andy Smith]

Richard,

On Fri, Jun 01, 2018 at 02:16:47PM -0500, Richard Owlett wrote:
> On 06/01/2018 09:01 AM, Michael Stone wrote:
> >I can't think of any applications where that's going to be better
> >over a pair of USB-Serial dongles than a pair of USB-Ethernet
> >dongles.
> 
> Please read my stated goals.
> Not my PREsumed goals.
> *ROFL*

Laugh all you want at people trying to help you, but time and time
again you end up posting volumes of text here without finding a
solution because you suck at concisely describing what you want to
achieve. Everyone else fails to understand you, every time, so is
everyone just stupid, or is it that the common factor here is you?

Your first email said you wanted your machines to "communicate".
That's as specific as you got.

Dan then tried to narrow it down to one specific form of
communication by spending a lot of their time listing out everything
they could think of that you might have meant, and you replied,
"Your list pretty much covers it." Useless and frustrating.

Then Stefan tried:

> > What kind of "communicate" do you need there?

Your response?

> Essentially any :/

I don't know what kind of response you expect to that uselessly
vague comment. By doing that you force people to spend a lot of
their time trying to cover every base, and then you complain at them
when they try. It really seems like you just want to complain when
people try their best to help you, even against your best efforts.

I expect to just get a barrel of whinging back for this, but I hate
to write a totally useless email myself, so…

You mentioned you want to transfer files.

If both machines have Ethernet interfaces then (as you've already
been advised) the simplest, most reliable and most performant way
will be direct Ethernet connection, or connection via a switch. If
file transfer is your goal, no need to bother with USB.

If somehow these machines don't both have Ethernet and USB really is
the only way, then again as you've already been advised, USB
Ethernet is the way to go.

We are now leaving the realms of simplicity and performance for more
subjective lands of doing things "just because" or for the retro
computing experience. You can certainly use a pair of USB serial adaptors
and then run a null modem cable between them, then run PPP over
that. Absolutely no idea why you would want to do this rather than
run Ethernet over USB. Instead of PPP you could use more arcane
forms of serial data transfer like zmodem or kermit.

If it's just a console you want, i.e. the console output and login
prompt from one machine to appear in a serial terminal program on
the other, then you can do that over Ethernet too! See "netconsole".

For a serial console when you don't have Ethernet (or want it
separate from the Ethernet infrastructure) then again it's USB
serial dongles on both ends, a null modem cable in between, then use
a serial terminal emulator like minicom or screen on the end you
want to be the client. There are configuration details involved for
the server end to get it to send console output to this USB-serial,
and put a login prompt on it.

Ask which parts you need more info on. Please be specific. Please
don't make this harder than it needs to be!

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: USB "null modem" cables and related Linux driver questions

[Richard Owlett]

On 06/01/2018 09:01 AM, Michael Stone wrote:

On Fri, Jun 01, 2018 at 04:56:32AM -0500, Richard Owlett wrote:

On 05/31/2018 06:58 PM, David Wright wrote:

(thanks for your link) gives an idea of the price, and in this case I
can see some justification for it because they describe the
electronics hidden inside the plugs (we hope).

But considering that two NICs cost less than that cable, I'd need a
pressing reason to purchase the cable instead.


There is a perceived elegance aspect.
There is also a practical aspect the only known working and 

8>> conveniently physically accessible ports are USB.


USB-Ethernet dongles would be a lot more useful in the long term than 
USB-Serial dongles.


*WHO* said anything about a "USB-Serial dongle"?
I want a USB-USB object. Subtle, but important, distinction.



RS-232 had a really good 40 year run, but for 
general communications it was mostly obsolete nearly 20 years ago. You 
mentioned file transfers-


So what?
I get grief for not mentioning immediate goals.
I casually mention a potential use and get *UNIVERSAL ADVICE*:
Don't do that. !


-I can't think of any applications where
that's going to be better over a pair of USB-Serial dongles than a pair 
of USB-Ethernet dongles.


Please read my stated goals.
Not my PREsumed goals.
*ROFL*



Mike Stone

Re: USB "null modem" cables and related Linux driver questions

[Gene Heskett]

On Friday 01 June 2018 06:20:59 Richard Owlett wrote:

> On 05/31/2018 10:07 PM, Stefan Monnier wrote:
> >> I have two computers with USB ports.
> >> I wish them to communicate as simply as mid-20th-century computers
> >> did.
> >
> > What kind of "communicate" do you need there?
>
> Essentially any ;/
> In fact one of the thought experiments I was pursuing was how to do
> file copying/sharing over RS232 - even I would not actually attempt to
> implement.

Other than speed of the copy while the error correction verify's it 
sector by sector, why not. Both rsync and rzsz are quite capable of 
sending a file halfway around the planet with the last 17 miles on a 
barbed wire fence. And getting identical crc's in the final check.

For a circuit that was actually that dirty, I think I'd choose rzsz as 
its default packet size is 256 bytes.  If the crc of that packet fails, 
it requests a resend until it gets it right. So does rsync, but rsync's 
default packet is 64k, demanding a far cleaner path. rzsz unforch has 
several cousins 3x removed, so there is less than 100% compatibility. 
And the linux version is one of the worse compatibility violators.

> > The "way back machine" to simulate a "null modem" serial cable
> > exists, as you've seen, but it's rarely the best solution for
> > nowadays's needs,
>
> "Best" is not an invariant absolute.
>
> > since nowadays connecting two computers is something completely
> > normal, supported by a deluge of tools, but they all expect a
> > "network" connection rather than a serial cable.
> >
> > In most cases those two computers also have ethernet or wifi "ports"
> > so you can connect them via such a network (which usually offers
> > faster transmission than a serial cable, lets you seamlessly
> > multiplex several connections, and lets you use the many tools
> > working over the network to connect computers).
>
> An explicit requirement is a wired, NOT WiFi, connection.
> I that seriously. My internet access is a WiFi hotspot with its WiFi
> capability disabled.
>
> > In some cases one of the two computers's USB port is an "OTG" port,
> > meaning that it can act either as "master" or not, in which case you
> > can just use a regular USB cable (and usually you then configure the
> > OTG side to pretend it's a network card, so it ends up looking to
> > the software like you've connected the two machines via an ethernet
> > cable. That's what I use between my BananaPi "router" and my office
> > desktop).
>
> I saw it and it meets most (all?) my requirements except my reading
> suggested:
>1. obsolete
>2. available only for Windows/Mac
>3. no way to determine if any of machines were equipped
>
> > If none of that are options, you can resort to using an "ethernet
> > dongle" on both sides and an ethernet cable between the two.
>
> That's a 1 versus 3 items required per connection.
>
> > All of those things will typically work "out of the box" on a
> > vanilla Linux kernel (the usbnet drivers have been incorporated
> > years ago).
> >
> > Oh, and in case those computers are somewhat old, they may also come
> > with Firewire ports, and those (contrary to USB) don't have the
> > "slave/master" distinction so you can connect your computers this
> > way with a plain normal Firewire cable (and make it appear to the
> > software, again, as some kind of ethernet-like connection).
> >
> >
> >  Stefan



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: USB "null modem" cables and related Linux driver questions

[Joe]

On Fri, 1 Jun 2018 10:01:57 -0400
Michael Stone  wrote:

> On Fri, Jun 01, 2018 at 04:56:32AM -0500, Richard Owlett wrote:
> >On 05/31/2018 06:58 PM, David Wright wrote:  
> >>(thanks for your link) gives an idea of the price, and in this case
> >>I can see some justification for it because they describe the
> >>electronics hidden inside the plugs (we hope).
> >>
> >>But considering that two NICs cost less than that cable, I'd need a
> >>pressing reason to purchase the cable instead.  
> >
> >There is a perceived elegance aspect.
> >There is also a practical aspect the only known working and 
> >conveniently physically accessible ports are USB.  
> 
> USB-Ethernet dongles would be a lot more useful in the long term than 
> USB-Serial dongles. RS-232 had a really good 40 year run, but for 
> general communications it was mostly obsolete nearly 20 years ago.
> You mentioned file transfers--I can't think of any applications where
> that's going to be better over a pair of USB-Serial dongles than a
> pair of USB-Ethernet dongles.
> 
>
Radio? This gadget:

https://www.lensadaptor.com/mtf-effect-control-unit-3-kit

 uses straight point-to-point 8-bit serial over Zigbee type RF
tranceivers. Bluetooth is basically 8-bit serial over radio, though
with a very short range.

-- 
Joe
https://en.wikipedia.org/wiki/Zigbee

Re: USB "null modem" cables and related Linux driver questions

[David Wright]

On Fri 01 Jun 2018 at 05:26:01 (-0500), Richard Owlett wrote:
> On 06/01/2018 01:27 AM, deloptes wrote:
> >Richard Owlett wrote:
> >
> >>I have two computers with USB ports.
> >>I wish them to communicate as simply as mid-20th-century computers did.
> >>Then we used RS232-C with a null modem &/or  appropriate software
> >>software at both ends.
> >>
> >
> >J., why not take a crossover cable - all pcs have now ethernet port
> >
> >https://en.wikipedia.org/wiki/Ethernet_crossover_cable
> >
> >
> 
> Some combinations require crossover cable, some don't.
> I investigated that and wen so fa as to purchase a {still shrink
> wrapped} 8-port switch as a solution. Decided clutter not worth it.

Just forget anyone said "crossover cable¹". You'd have to be making a
direct connection between two museum pieces to require one, and as
you have a switch, you have absolutely no need to ever do that.
Coonect both to the switch instead.

Accessibility? Using the NIC (usually at the back), it gets inserted
permanently and then forgotten, rather than needing to be inserted
on each occasion you want connectivity. Tidier too.

Bear in mind you're using the hardware as intended: no risk of
blowing up your USB port. (Ever noticed how often flaky USB ports
are mentioned here?)

You might even find you can use wakeonlan on the desktop PCs
to save some power.

¹ If you *have* obtained one, just use it like an ordinary cable nowadays.

Cheers,
David.

Re: USB "null modem" cables and related Linux driver questions

[Richard Owlett]

On 06/01/2018 08:21 AM, to...@tuxteam.de wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote:

The one choice you have is that one of both sides takes a step
back and plays "gadget" [...]



The gadget API is the programming API offered by the kernel for the OTG
ports: no OTG => no gadget!


[OTG]



More importantly, the USB ports which support OTG are driven by
different hardware.


Ah, so the hardware has to play along...


Right, you need both your hardware's USB port to support OTG and you
need your kernel to have a driver that supports this hardware.
AFAIK the driver is usually available.


Did I say I was handwaving?

Thanks for the clarifications!



It also suggests that I frequently grasp some of the implications of 
what I read. Thank you.

As an illustration of my mindset:
If they had really intended USB to be *UNIVERSAL* serial bus, then it 
should have been OTG from the get go.

P.S. I know of thousands of reasons they did not.
 Vast majority preceded by $ ;/

Re: USB "null modem" cables and related Linux driver questions

[Michael Stone]

On Fri, Jun 01, 2018 at 04:56:32AM -0500, Richard Owlett wrote:

On 05/31/2018 06:58 PM, David Wright wrote:

(thanks for your link) gives an idea of the price, and in this case I
can see some justification for it because they describe the
electronics hidden inside the plugs (we hope).

But considering that two NICs cost less than that cable, I'd need a
pressing reason to purchase the cable instead.


There is a perceived elegance aspect.
There is also a practical aspect the only known working and 
conveniently physically accessible ports are USB.


USB-Ethernet dongles would be a lot more useful in the long term than 
USB-Serial dongles. RS-232 had a really good 40 year run, but for 
general communications it was mostly obsolete nearly 20 years ago. You 
mentioned file transfers--I can't think of any applications where
that's going to be better over a pair of USB-Serial dongles than a pair 
of USB-Ethernet dongles.


Mike Stone

Re: USB "null modem" cables and related Linux driver questions

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote:
> > The one choice you have is that one of both sides takes a step
> > back and plays "gadget" [...]

> The gadget API is the programming API offered by the kernel for the OTG
> ports: no OTG => no gadget!
> 
> > [OTG]

> More importantly, the USB ports which support OTG are driven by
> different hardware.

Ah, so the hardware has to play along...

> Right, you need both your hardware's USB port to support OTG and you
> need your kernel to have a driver that supports this hardware.
> AFAIK the driver is usually available.

Did I say I was handwaving?

Thanks for the clarifications!

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlsRSHYACgkQBcgs9XrR2kYP9ACfb7mVtI1Qu/CjDeTIB5uoyOPv
jNYAni1/EbprNJ8Gu6DuHMfyWoO+tCGP
=dhmw
-END PGP SIGNATURE-

Re: USB "null modem" cables and related Linux driver questions

[Stefan Monnier]

> The one choice you have is that one of both sides takes a step
> back and plays "gadget" (the jargon term, somewhat unfortunate
> as search engine fodder). There seems to be something out there
> for that, e.g. [2].

The gadget API is the programming API offered by the kernel for the OTG
ports: no OTG => no gadget!

> The other choice seems to be USB On The Go (aka "OTG") [3].
> You seem to need a special cable for that.

More importantly, the USB ports which support OTG are driven by
different hardware.

> There seem to be Linux drivers to let the USB "stack" play along
> with OTG [4], but I have no experience whatsoever with this

Right, you need both your hardware's USB port to support OTG and you
need your kernel to have a driver that supports this hardware.
AFAIK the driver is usually available.


Stefan

Re: USB "null modem" cables and related Linux driver questions

[Stefan Monnier]

>> In some cases one of the two computers's USB port is an "OTG" port,
>> meaning that it can act either as "master" or not, in which case you can
>> just use a regular USB cable (and usually you then configure the OTG
>> side to pretend it's a network card, so it ends up looking to the
>> software like you've connected the two machines via an ethernet cable.
>> That's what I use between my BananaPi "router" and my office desktop).
>
> I saw it and it meets most (all?) my requirements except my reading
> suggested:
>   1. obsolete
>   2. available only for Windows/Mac
>   3. no way to determine if any of machines were equipped

Not obsolete at all.
Availability has nothing to do with the OS (I never use either of macOS
or Windows).

But yes, OTG rare (read: non-existing) on laptops/desktops.
They're very common on "embedded systems" which are expected to be
(occasionally) plugged into a computer.  E.g. many phones's USB port
is OTG.

>> If none of that are options, you can resort to using an "ethernet
>> dongle" on both sides and an ethernet cable between the two.
> That's a 1 versus 3 items required per connection.

I just gave you alternatives.  You'll let you decide what's better for
your planned use cases.


Stefan

Re: USB "null modem" cables and related Linux driver questions

[Richard Owlett]

On 06/01/2018 01:27 AM, deloptes wrote:

Richard Owlett wrote:


I have two computers with USB ports.
I wish them to communicate as simply as mid-20th-century computers did.
Then we used RS232-C with a null modem &/or  appropriate software
software at both ends.



J., why not take a crossover cable - all pcs have now ethernet port

https://en.wikipedia.org/wiki/Ethernet_crossover_cable




Some combinations require crossover cable, some don't.
I investigated that and wen so fa as to purchase a {still shrink 
wrapped} 8-port switch as a solution. Decided clutter not worth it.

Re: USB "null modem" cables and related Linux driver questions

[Richard Owlett]

On 05/31/2018 10:07 PM, Stefan Monnier wrote:

I have two computers with USB ports.
I wish them to communicate as simply as mid-20th-century computers did.


What kind of "communicate" do you need there?


Essentially any ;/
In fact one of the thought experiments I was pursuing was how to do file 
copying/sharing over RS232 - even I would not actually attempt to implement.




The "way back machine" to simulate a "null modem" serial cable exists,
as you've seen, but it's rarely the best solution for nowadays's needs,


"Best" is not an invariant absolute.


since nowadays connecting two computers is something completely normal,
supported by a deluge of tools, but they all expect a "network"
connection rather than a serial cable.

In most cases those two computers also have ethernet or wifi "ports" so
you can connect them via such a network (which usually offers faster
transmission than a serial cable, lets you seamlessly multiplex several
connections, and lets you use the many tools working over the network to
connect computers).


An explicit requirement is a wired, NOT WiFi, connection.
I that seriously. My internet access is a WiFi hotspot with its WiFi 
capability disabled.




In some cases one of the two computers's USB port is an "OTG" port,
meaning that it can act either as "master" or not, in which case you can
just use a regular USB cable (and usually you then configure the OTG
side to pretend it's a network card, so it ends up looking to the
software like you've connected the two machines via an ethernet cable.
That's what I use between my BananaPi "router" and my office desktop).


I saw it and it meets most (all?) my requirements except my reading 
suggested:

  1. obsolete
  2. available only for Windows/Mac
  3. no way to determine if any of machines were equipped



If none of that are options, you can resort to using an "ethernet
dongle" on both sides and an ethernet cable between the two.


That's a 1 versus 3 items required per connection.



All of those things will typically work "out of the box" on a vanilla
Linux kernel (the usbnet drivers have been incorporated years ago).

Oh, and in case those computers are somewhat old, they may also come
with Firewire ports, and those (contrary to USB) don't have the
"slave/master" distinction so you can connect your computers this way
with a plain normal Firewire cable (and make it appear to the software,
again, as some kind of ethernet-like connection).


 Stefan

Re: USB "null modem" cables and related Linux driver questions

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 01, 2018 at 08:27:13AM +0200, deloptes wrote:
> Richard Owlett wrote:
> 
> > I have two computers with USB ports.
> > I wish them to communicate as simply as mid-20th-century computers did.
> > Then we used RS232-C with a null modem &/or  appropriate software
> > software at both ends.
> > 
> 
> J., why not take a crossover cable - all pcs have now ethernet port

FWIW these days, most devices are capable of doing the crossover thing
automatically [1], so you can just use a straight cable. From personal
experience, I haven't needed a crossover cable the last ten years (and
I do muck around with oldish hardware).

Cheers

[1] https://en.wikipedia.org/wiki/Medium_Dependent_Interface#Auto_MDI-X

- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlsRAmAACgkQBcgs9XrR2kbpPwCfYH3wQicOhfiQrgAvcDUPytCZ
29YAn0sYNXgIXIFfMDq3tt5wCJUKM8DK
=tkoi
-END PGP SIGNATURE-

Re: USB "null modem" cables and related Linux driver questions

[deloptes]

Richard Owlett wrote:

> I have two computers with USB ports.
> I wish them to communicate as simply as mid-20th-century computers did.
> Then we used RS232-C with a null modem &/or  appropriate software
> software at both ends.
> 

J., why not take a crossover cable - all pcs have now ethernet port

https://en.wikipedia.org/wiki/Ethernet_crossover_cable

Re: USB "null modem" cables and related Linux driver questions

[Stefan Monnier]

> If none of that are options, you can resort to using an "ethernet
> dongle" on both sides and an ethernet cable between the two.

[ If one of the two computers has a free ethernet port, you can of
  course also such a dongle on the other computer.  ]

BTW, those ethernet dongles can be found pretty cheaply (like $10 or
less) and they can be handy in many cases to add an ethernet port (or
several ports, even).  IOW, it's a good tool to have in your box.


Stefan

Re: USB "null modem" cables and related Linux driver questions

[Stefan Monnier]

> I have two computers with USB ports.
> I wish them to communicate as simply as mid-20th-century computers did.

What kind of "communicate" do you need there?

The "way back machine" to simulate a "null modem" serial cable exists,
as you've seen, but it's rarely the best solution for nowadays's needs,
since nowadays connecting two computers is something completely normal,
supported by a deluge of tools, but they all expect a "network"
connection rather than a serial cable.

In most cases those two computers also have ethernet or wifi "ports" so
you can connect them via such a network (which usually offers faster
transmission than a serial cable, lets you seamlessly multiplex several
connections, and lets you use the many tools working over the network to
connect computers).

In some cases one of the two computers's USB port is an "OTG" port,
meaning that it can act either as "master" or not, in which case you can
just use a regular USB cable (and usually you then configure the OTG
side to pretend it's a network card, so it ends up looking to the
software like you've connected the two machines via an ethernet cable.
That's what I use between my BananaPi "router" and my office desktop).

If none of that are options, you can resort to using an "ethernet
dongle" on both sides and an ethernet cable between the two.

All of those things will typically work "out of the box" on a vanilla
Linux kernel (the usbnet drivers have been incorporated years ago).

Oh, and in case those computers are somewhat old, they may also come
with Firewire ports, and those (contrary to USB) don't have the
"slave/master" distinction so you can connect your computers this way
with a plain normal Firewire cable (and make it appear to the software,
again, as some kind of ethernet-like connection).


Stefan

Re: USB "null modem" cables and related Linux driver questions

[Dan Ritter]

On Thu, May 31, 2018 at 09:21:27AM -0500, Richard Owlett wrote:
> I have two computers with USB ports.
> I wish them to communicate as simply as mid-20th-century computers did.
> Then we used RS232-C with a null modem &/or  appropriate software software
> at both ends.
> 
> The underlying problem is that both ends egotistically expect to be
> *MASTER*.
> 
> The hardware problem is solvable [e.g.
> http://www.ftdichip.com/Products/Cables/USBtoUSB.htm].
> 
> The software is another case :<
> The best Linux specific link I've found is dated September 2005
> [http://www.linux-usb.org/usbnet/]
> 
> I've done DuckDuckGo searches for permutations/combinations of
>   usb, "peer to peer", lan, and bridge.
> Most is Windows/Mac centric.
> There were hints that needed drivers may exist in current Linux core.
> 
> Pointers to good references and/or better search terms?

Do you want:

- One end is a terminal, the other end offers login?   "agetty
  serial" and "minicom"

- TCP/IP over RS-232 serial?   Keyword is "PPP".

- TCP/IP over ethernet attached via USB? "usbnet" and treat them
  like ethernet adapters.

- Connect an actual hardware terminal like a VT320 to your Linux
  box? "agetty serial" again.

- Something else? Describe it.

-dsr-

Re: USB "null modem" cables and related Linux driver questions

[Reco]

Hi.

On Thu, May 31, 2018 at 09:21:27AM -0500, Richard Owlett wrote:
> I have two computers with USB ports.
> I wish them to communicate as simply as mid-20th-century computers did.
> Then we used RS232-C with a null modem &/or  appropriate software software
> at both ends.
> 
> The underlying problem is that both ends egotistically expect to be
> *MASTER*.

I did the thing in the not-so-distant past.

It took two USB-RS232 converters (FDTI chipsets should work out of the
box), and a conventional RS232 null modem cable. Communication was
limited to 112500 bps, but I needed it for the serial console anyway.

As for the software part, agetty and minicom were all that was needed.

Reco

USB "null modem" cables and related Linux driver questions

[Richard Owlett]

I have two computers with USB ports.
I wish them to communicate as simply as mid-20th-century computers did.
Then we used RS232-C with a null modem &/or  appropriate software 
software at both ends.


The underlying problem is that both ends egotistically expect to be 
*MASTER*.


The hardware problem is solvable [e.g. 
http://www.ftdichip.com/Products/Cables/USBtoUSB.htm].


The software is another case :<
The best Linux specific link I've found is dated September 2005 
[http://www.linux-usb.org/usbnet/]


I've done DuckDuckGo searches for permutations/combinations of
  usb, "peer to peer", lan, and bridge.
Most is Windows/Mac centric.
There were hints that needed drivers may exist in current Linux core.

Pointers to good references and/or better search terms?
TIA

Re: hostname of the modem gateway

[David Wright]

On Tue 02 Jan 2018 at 08:50:13 (+0100), john doe wrote:
> On 1/2/2018 8:16 AM, john doe wrote:
> >On 1/2/2018 8:01 AM, Tom Furie wrote:
> >>On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote:
> >>
> >>>My default route is not 192.168.1.1 and host(1) gives me that
> >>>same error.
> >>
> >>What the error actually means is that there is no reverse DNS resolution
> >>for that IP address, in other words the IP address cannot be resolved to
> >>its hostname. It has nothing at all to do with routing.
> >>
> >
> >The OP has said that he want it to get the hostname of his
> >upstream router/gateway.
> >'ip -r r' will show the FQDN of his default route (192.168.1.1) in
> >that case.
> >
> 
> Rereading the all conversation I should have said to "David Wright
> " that the error:
> 
> $ host 192.168.1.1
> Host 1.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
> 
> Meens that there is no hostname associated with that ip.
> But in the case of the OP it should work.

I haven't a clue what works for the OP, not even after glancing at the
subsequent thread that seems to continue the debate. I don't even know
exactly how they generated the lines:

|> # route
|> gateway = home.telecomitalia.it
|> # ip route
|> gateway = 192.168.1.1

All I did was to suggest how the OP could get ip to do what route
appears to do by default, which is to print names in place of
dotted quads.

I have a name associated with 192.168.1.1 but it's not resolvable
through DNS: there's no resolver in the router. I have to resolve
it with getent, and I asume my system is doing just that:

$ getent hosts 192.168.1.1
192.168.1.1 router
$ ping router
PING router (192.168.1.1) 56(84) bytes of data.
64 bytes from router (192.168.1.1): icmp_seq=1 ttl=64 time=2.24 ms
64 bytes from router (192.168.1.1): icmp_seq=2 ttl=64 time=1.53 ms
64 bytes from router (192.168.1.1): icmp_seq=3 ttl=64 time=1.15 ms
64 bytes from router (192.168.1.1): icmp_seq=4 ttl=64 time=1.42 ms
^C
--- router ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.157/1.590/2.245/0.402 ms
$ head -12 /etc/hosts
# /root/hosts-0-acer

127.0.0.1   localhost
127.0.1.1   acer

#
# /root/hosts-1-local-template
# List of local hosts.
# Comment out the line of this host when installing.
# Check the IPv6 lines occasionally because they change them.

192.168.1.1 router
$ 

Cheers,
David.

Re: hostname of the modem gateway

[Greg Wooledge]

On Tue, Jan 02, 2018 at 02:59:41PM +, Glenn English wrote:
> On Mon, Jan 1, 2018 at 11:12 PM, Max Power  wrote:
> 
> > with the new release of Debian 'Stretch', the route command has been 
> > replaced
> 
> Wipe your disk and install Buster. You get route++ back.

Worst advice ever.

Re: hostname of the modem gateway

[Glenn English]

On Mon, Jan 1, 2018 at 11:12 PM, Max Power  wrote:

> with the new release of Debian 'Stretch', the route command has been replaced

Wipe your disk and install Buster. You get route++ back.

Or create some shell scripts...

--
Glenn English

Re: hostname of the modem gateway

[Greg Wooledge]

On Tue, Jan 02, 2018 at 12:12:47AM +0100, Max Power wrote:
> Hi guys,
> with the new release of Debian 'Stretch', the route command has been replaced
> but what other command returns the hostname of the modem/router gateway...?
> # route
> gateway = home.telecomitalia.it
> # ip route
> gateway = 192.168.1.1
> 
> Thanks for reply, Max Power.

http://mywiki.wooledge.org/XyProblem
http://mywiki.wooledge.org/IpAddress

I bet one or both of those will help, in the long run.

Note that the gateway address given by DHCP is available in a variable
that dhclient-enter-hooks scripts can use.  You probably want to get it
that way instead of running "ip route" or "route" or "netstat -r" or
any other command.

Re: hostname of the modem gateway

[Tom Furie]

On Tue, Jan 02, 2018 at 12:12:47AM +0100, Max Power wrote:

> with the new release of Debian 'Stretch', the route command has been replaced
> but what other command returns the hostname of the modem/router gateway...?
> # route
> gateway = home.telecomitalia.it
> # ip route
> gateway = 192.168.1.1

As has already been mentioned, 'ip -r route' (or 'ip -r r', for short)
will work. However if you want to use the 'route' command, or 'netstat
-r' which is equivalent, it is still available in the 'net-tools'
package.

Cheers,
Tom

-- 
Any sufficiently advanced technology is indistinguishable from a rigged demo.
-- Andy Finkel, computer guy


signature.asc
Description: Digital signature

Re: hostname of the modem gateway

[john doe]

On 1/2/2018 8:16 AM, john doe wrote:

On 1/2/2018 8:01 AM, Tom Furie wrote:

On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote:

My default route is not 192.168.1.1 and host(1) gives me that same 
error.


What the error actually means is that there is no reverse DNS resolution
for that IP address, in other words the IP address cannot be resolved to
its hostname. It has nothing at all to do with routing.



The OP has said that he want it to get the hostname of his upstream 
router/gateway.
'ip -r r' will show the FQDN of his default route (192.168.1.1) in that 
case.




Rereading the all conversation I should have said to "David Wright 
" that the error:


$ host 192.168.1.1
Host 1.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)

Meens that there is no hostname associated with that ip.
But in the case of the OP it should work.

--
John Doe

Re: hostname of the modem gateway

[john doe]

On 1/2/2018 8:01 AM, Tom Furie wrote:

On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote:


My default route is not 192.168.1.1 and host(1) gives me that same error.


What the error actually means is that there is no reverse DNS resolution
for that IP address, in other words the IP address cannot be resolved to
its hostname. It has nothing at all to do with routing.



The OP has said that he want it to get the hostname of his upstream 
router/gateway.
'ip -r r' will show the FQDN of his default route (192.168.1.1) in that 
case.


--
John Doe

Re: hostname of the modem gateway

[Tom Furie]

On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote:

> My default route is not 192.168.1.1 and host(1) gives me that same error.

What the error actually means is that there is no reverse DNS resolution
for that IP address, in other words the IP address cannot be resolved to
its hostname. It has nothing at all to do with routing.

Cheers,
Tom

-- 
Man is a rational animal who always loses his temper when he is called upon
to act in accordance with the dictates of reason.
-- Oscar Wilde


signature.asc
Description: Digital signature

Re: hostname of the modem gateway

[john doe]

On 1/2/2018 7:45 AM, Tom Furie wrote:

On Tue, Jan 02, 2018 at 07:38:54AM +0100, john doe wrote:


Looks like 192.168.1.1 is not your default route.


What led you to that conclusion?



My default route is not 192.168.1.1 and host(1) gives me that same error.

--
John Doe

Re: hostname of the modem gateway

[Tom Furie]

On Tue, Jan 02, 2018 at 07:38:54AM +0100, john doe wrote:

> Looks like 192.168.1.1 is not your default route.

What led you to that conclusion?

Cheers,
Tom

-- 
A good scapegoat is hard to find.
A guilty conscience is the mother of invention.
-- Carolyn Wells


signature.asc
Description: Digital signature

Re: hostname of the modem gateway

[john doe]

On 1/2/2018 7:15 AM, David Wright wrote:

On Tue 02 Jan 2018 at 06:25:29 (+0100), john doe wrote:

On 1/2/2018 12:12 AM, Max Power wrote:

Hi guys,
with the new release of Debian 'Stretch', the route command has been replaced
but what other command returns the hostname of the modem/router gateway...?
# route
gateway = home.telecomitalia.it
# ip route
gateway = 192.168.1.1


$ ip -r r

You need to ask for the resolver with -r.

man ip-route documents the arguments/commands, but you need
man ip for the options (which are common).



Thanks for reply, Max Power.



You could try the host(1) utility:

$ host 192.168.1.1

https://linux.die.net/man/1/host


$ host 192.168.1.1
Host 1.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
$



Looks like 192.168.1.1 is not your default route.

--
John Doe

Re: hostname of the modem gateway

[David Wright]

On Tue 02 Jan 2018 at 06:25:29 (+0100), john doe wrote:
> On 1/2/2018 12:12 AM, Max Power wrote:
> >Hi guys,
> >with the new release of Debian 'Stretch', the route command has been replaced
> >but what other command returns the hostname of the modem/router gateway...?
> ># route
> >gateway = home.telecomitalia.it
> ># ip route
> >gateway = 192.168.1.1

$ ip -r r

You need to ask for the resolver with -r.

man ip-route documents the arguments/commands, but you need
man ip for the options (which are common).

> >
> >Thanks for reply, Max Power.
> >
> 
> You could try the host(1) utility:
> 
> $ host 192.168.1.1
> 
> https://linux.die.net/man/1/host

$ host 192.168.1.1
Host 1.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
$ 

Cheers,
David.

Re: hostname of the modem gateway

[john doe]

On 1/2/2018 12:12 AM, Max Power wrote:

Hi guys,
with the new release of Debian 'Stretch', the route command has been replaced
but what other command returns the hostname of the modem/router gateway...?
# route
gateway = home.telecomitalia.it
# ip route
gateway = 192.168.1.1

Thanks for reply, Max Power.



You could try the host(1) utility:

$ host 192.168.1.1

https://linux.die.net/man/1/host

--
John Doe

hostname of the modem gateway

[Max Power]

Hi guys,
with the new release of Debian 'Stretch', the route command has been replaced
but what other command returns the hostname of the modem/router gateway...?
# route
gateway = home.telecomitalia.it
# ip route
gateway = 192.168.1.1

Thanks for reply, Max Power.

Re: iinet modem, esternal usb hdd

[Dan Ritter]

On Thu, Sep 07, 2017 at 09:29:30PM +1000, Stephen Grant Brown wrote:
> -Original Message- From: Dan Ritter
> Sent: Thursday, September 7, 2017 8:08 PM
> To: Stephen Grant Brown
> Cc: Debian User
> Subject: Re: iinet modem, esternal usb hdd
> 
> On Thu, Sep 07, 2017 at 05:39:57PM +1000, Stephen Grant Brown wrote:
> > Hi All,
> > I am seeing the external usb hdd connected to the iinet modem via the
> > usb port as being accessible via both Samba and DLNA.
> > 
> > How do I access it on a Debian machine.
> 
> 
> https://wiki.debian.org/SAMBAClientSetup
> 
> I recommend starting with a graphical file browser that speaks
> SMB to make sure that it all works, then use an fstab mount
> if you want to make it permanent.
> 
> -dsr-
> Hi All,
> Thanks Dan for your speedy reply.
> How do I find the computer name?

The name of the router/modem with the attached USB disk? If you
haven't configured it otherwise, the WORKGROUP group should
have all the discoverable devices in it.

-dsr-

Re: iinet modem, esternal usb hdd

[Stephen Grant Brown]

-Original Message- 
From: Dan Ritter

Sent: Thursday, September 7, 2017 8:08 PM
To: Stephen Grant Brown
Cc: Debian User
Subject: Re: iinet modem, esternal usb hdd

On Thu, Sep 07, 2017 at 05:39:57PM +1000, Stephen Grant Brown wrote:

Hi All,
I am seeing the external usb hdd connected to the iinet modem via the usb 
port as being accessible via both Samba and DLNA.


How do I access it on a Debian machine.



https://wiki.debian.org/SAMBAClientSetup

I recommend starting with a graphical file browser that speaks
SMB to make sure that it all works, then use an fstab mount
if you want to make it permanent.

-dsr-
Hi All,
Thanks Dan for your speedy reply.
How do I find the computer name?
Yours Sincerely
Stephen Grant Brown

Re: iinet modem, esternal usb hdd

[Dan Ritter]

On Thu, Sep 07, 2017 at 05:39:57PM +1000, Stephen Grant Brown wrote:
> Hi All, 
> I am seeing the external usb hdd connected to the iinet modem via the usb 
> port as being accessible via both Samba and DLNA.
> 
> How do I access it on a Debian machine.


https://wiki.debian.org/SAMBAClientSetup

I recommend starting with a graphical file browser that speaks
SMB to make sure that it all works, then use an fstab mount
if you want to make it permanent.

-dsr-

iinet modem, esternal usb hdd

[Stephen Grant Brown]

Hi All, 
I am seeing the external usb hdd connected to the iinet modem via the usb port 
as being accessible via both Samba and DLNA.

How do I access it on a Debian machine.

Yours Sincerely
Stephen Grant Brown

Re: "[Off-topic] Modem USB sin tty"

[Angel Vicente]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

El Mon, 14 Aug 2017 08:34:04 -0300
Cristian Mitchell <mitchell6...@gmail.com> escribió:
> El 13 ago. 2017 3:21 PM, <angel...@wanadoo.es> escribió:
> 
>  Hola a todos.
> 
> Estoy conectando un teléfono Galaxy Ace en modo download,
> supuestamente tiene que ser detectado como un modem, y así lo hace:
> udev detecta un modem USB 1.0, carga el módulo cdc_acm, pero no
> genera un dispositivo ttyACM, si enciendo el teléfono lo enciendo en
> otro modo, debug, si genera el ttyACM.
> 
> He probado en testing, en stable versión 9, incluso en Ubuntu; he
> probado a desactivar ModemManager tal y como he visto en alguna
> sugerencia, y siempre con el mismo resultado.
> 
> Bueno, lo marco como Off-topic, tengo la impresión que es algún
> comportamiento de Linux con este dispositivo concreto.
> 
> Saludos y gracias de antemano
> 
> 
> 
> Si cambiando el modo cambia la configuración de Linux, la lógica
> dicta que el problema es el teléfono, o la documentación que estás
> usando

Sí, también puede ser, ahora mi duda es: si se inserta el módulo,
¿debería crearse la tty, o depende del hardware?



- -- 
Key fingerprint 01DC 0386 2B28 0A02 A270 E243 008B AABF 1822 9851
-BEGIN PGP SIGNATURE-

iHUEAREIAB0WIQQB3AOGKygKAqJw4kMAi6q/GCKYUQUCWZnBKQAKCRAAi6q/GCKY
UQvbAP0e/3UZIUkpvhbTnEEKOOWj9ZC8Cic2p/RH9Q4HYVOthAD/XheISfZIokXl
PO1zwYTcRBLpw8+zHWjd1r6HXr00C9g=
=45RM
-END PGP SIGNATURE-

Re: "[Off-topic] Modem USB sin tty"

[Cristian Mitchell]

El 13 ago. 2017 3:21 PM, <angel...@wanadoo.es> escribió:

 Hola a todos.

Estoy conectando un teléfono Galaxy Ace en modo download, supuestamente
tiene que ser detectado como un modem, y así lo hace: udev detecta un
modem USB 1.0, carga el módulo cdc_acm, pero no genera un dispositivo
ttyACM, si enciendo el teléfono lo enciendo en otro modo, debug, si
genera el ttyACM.

He probado en testing, en stable versión 9, incluso en Ubuntu; he
probado a desactivar ModemManager tal y como he visto en alguna
sugerencia, y siempre con el mismo resultado.

Bueno, lo marco como Off-topic, tengo la impresión que es algún
comportamiento de Linux con este dispositivo concreto.

Saludos y gracias de antemano


P.S. Estoy utilizando la interfaz web de mi correo, le he marcado para
texto, pero no estoy seguro del resultado.



Si cambiando el modo cambia la configuración de Linux, la lógica dicta que
el problema es el teléfono, o la documentación que estás usando

"[Off-topic] Modem USB sin tty"

 Hola a todos.

Estoy conectando un teléfono Galaxy Ace en modo download, supuestamente
tiene que ser detectado como un modem, y así lo hace: udev detecta un
modem USB 1.0, carga el módulo cdc_acm, pero no genera un dispositivo
ttyACM, si enciendo el teléfono lo enciendo en otro modo, debug, si
genera el ttyACM.

He probado en testing, en stable versión 9, incluso en Ubuntu; he
probado a desactivar ModemManager tal y como he visto en alguna
sugerencia, y siempre con el mismo resultado.

Bueno, lo marco como Off-topic, tengo la impresión que es algún
comportamiento de Linux con este dispositivo concreto.

Saludos y gracias de antemano


P.S. Estoy utilizando la interfaz web de mi correo, le he marcado para
texto, pero no estoy seguro del resultado.

Trouble with Sierra Wireless MC7710 mSATA LTE Modem

[Jonathan Marquardt]

Hi!

I am trying to get this thing working.

Debian 8.8 on Lenovo ThinkPad X220

Originally, Linux seems to detect the thing but then does nothing with it.

dmesg:

##

[1.950070] usb 2-1.4: config 1 has an invalid interface number: 7 but max 
is 5
[1.950079] usb 2-1.4: config 1 has no interface number 5
[1.952051] usb 2-1.4: New USB device found, idVendor=1199, idProduct=68a3
[1.952070] usb 2-1.4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=4
[1.952075] usb 2-1.4: Product: MC7710
[1.952080] usb 2-1.4: Manufacturer: Sierra Wireless, Incorporated
[1.952084] usb 2-1.4: SerialNumber: 358178040028229

##

ifconfig doesn't list any wwan0, no /dev/ttyUSB* exists.

So after a lot of searching I found this forum post:
https://ubuntuforums.org/showthread.php?t=2121838
User bmork created a udev rule there which appearently works for the Ubuntu 
guy over there. So I copied the rule and created it for me as well. I'm 
copying it here just in case:

##

ACTION!="add|change", GOTO="mbim_to_qmi_rules_end"

SUBSYSTEM!="usb", GOTO="mbim_to_qmi_rules_end"

# ignore any device with only one configuration
ATTR{bNumConfigurations}=="1", GOTO="mbim_to_qmi_rules_end"

# force Sierra Wireless MC7710 to configuration #1
ATTR{idVendor}=="1199",ATTR{idProduct}=="68a2",ATTR{bConfigurationValue}="1"

LABEL="mbim_to_qmi_rules_end"

##

Now dmesg says a few more things after a reboot:

##

[1.950070] usb 2-1.4: config 1 has an invalid interface number: 7 but max 
is 5
[1.950079] usb 2-1.4: config 1 has no interface number 5
[1.952051] usb 2-1.4: New USB device found, idVendor=1199, idProduct=68a3
[1.952070] usb 2-1.4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=4
[1.952075] usb 2-1.4: Product: MC7710
[1.952080] usb 2-1.4: Manufacturer: Sierra Wireless, Incorporated
[1.952084] usb 2-1.4: SerialNumber: 358178040028229



[6.549427] usbcore: registered new interface driver usbserial
[6.549437] usbcore: registered new interface driver usbserial_generic
[6.549445] usbserial: USB Serial support registered for generic
[6.550227] usbcore: registered new interface driver sierra
[6.550235] usbserial: USB Serial support registered for Sierra USB modem
[6.550251] sierra 2-1.4:1.0: Sierra USB modem converter detected
[6.550748] usb 2-1.4: Sierra USB modem converter now attached to ttyUSB0
[6.550765] sierra 2-1.4:1.1: Sierra USB modem converter detected
[6.551106] usb 2-1.4: Sierra USB modem converter now attached to ttyUSB1
[6.551121] sierra 2-1.4:1.2: Sierra USB modem converter detected
[6.551476] usb 2-1.4: Sierra USB modem converter now attached to ttyUSB2
[6.551491] sierra 2-1.4:1.3: Sierra USB modem converter detected
[6.551895] usb 2-1.4: Sierra USB modem converter now attached to ttyUSB3
[6.551908] sierra 2-1.4:1.4: Sierra USB modem converter detected
[6.552328] usb 2-1.4: Sierra USB modem converter now attached to ttyUSB4
[6.553662] systemd-udevd[283]: starting version 215
[6.556804] sierra_net 2-1.4:1.7 wwan0: register 'sierra_net' at 
usb-:00:1d.0-1.4, Sierra Wireless USB-to-WWAN Modem, 36:74:99:5c:01:07
[6.558933] usbcore: registered new interface driver sierra_net



[9.855501] usb 2-1.4: USB disconnect, device number 3
[9.855593] sierra ttyUSB2: resubmit read urb failed.(-19)
[9.855842] sierra ttyUSB1: resubmit read urb failed.(-19)   
 
[9.856130] sierra ttyUSB0: Sierra USB modem converter now disconnected from 
ttyUSB0
[9.856142] sierra 2-1.4:1.0: device disconnected
[9.856288] sierra ttyUSB1: Sierra USB modem converter now disconnected from 
ttyUSB1
[9.856298] sierra 2-1.4:1.1: device disconnected
[9.856843] sierra ttyUSB2: Sierra USB modem converter now disconnected from 
ttyUSB2
[9.856854] sierra 2-1.4:1.2: device disconnected
[9.856967] sierra ttyUSB3: Sierra USB modem converter now disconnected from 
ttyUSB3
[9.856980] sierra 2-1.4:1.3: device disconnected
[9.857091] sierra ttyUSB4: Sierra USB modem converter now disconnected from 
ttyUSB4
[9.857104] sierra 2-1.4:1.4: device disconnected
[9.860717] sierra_net 2-1.4:1.7 wwan0: unregister 'sierra_net' 
usb-:00:1d.0-1.4, Sierra Wireless USB-to-WWAN Modem
[9.909695] sierra_net 2-1.4:1.7 (unregistered net_device): usb_control_msg 
failed, status -19

##

So, now ttyUSB{1..4} are being created, the drivers are being loaded and 
everything, but shortly after during the booting process the "USB"

Re: Problema con modem 4G

[Antonio Trujillo Carmona]

El 11/05/17 a las 03:49, Alan escribió:
> Saludos a todos. Tengo un conocido que tiene un extraño inconveniente
> con un modem 4G de Movistar. El modelo es un Huawei E1756.
>
> Resulta que ese modelo en algunas distribuciones GNU/Linux anda
> perfecto, y en otras no hay forma de hacerlo andar...
>
> Funciona en una distro con un kernel cargado de componentes privativos
> como Ubuntu (lo que usa ahora) pero también en Trisquel, que es 100%
> software libre.  Sin embargo, en otras distros como Xubuntu y Fedora no
> anda. Debian, lamentablemente, está en este último grupo, aunque en
> Canaima, que está basada en Debian, funciona bien.
>
> Me he cansado de buscar información al respecto y de probar distintos
> métodos, y ninguno sirve. Aprovechando mi reciente descubrimiento de
> esta lista comparto el inconveniente por si alguien sabe cómo
> solucionarlo o, por lo menos, sabe a qué se debe (confieso que me
> intriga el tema).
>
> Aclaro también que probamos con diversos entornos de escritorio y el
> asunto no parece pasar por ese lado. En Windows el modem se conectaba
> mediante un programa llamado "Escritorio Movistar" pero en GNU/Linux no
> hay tal cosa (existió en su momento pero todas las páginas están
> borradas, y aunque se "revivan" con The Internet Archive no queda nada
> útil).
>
> Muchas gracias por su tiempo.
>
> Saludos cordiales.
>
>

Suena a un problema de firmware, revisa que paquetes de firmware estan
instalados en los sistemas que si funciona y compáralo con los que no
funciona.

También podría tener que ver con el "usb-modeswitch", compara versiones.

-- 

*Antonio Trujillo Carmona*

*Técnico de redes y sistemas.*

*Subdirección de Tecnologías de la Información y Comunicaciones*

Servicio Andaluz de Salud. Consejería de Salud de la Junta de Andalucía

_antonio.trujillo.sspa@juntadeandalucia.es_

Tel. +34 670947670 747670)

Problema con modem 4G

[Alan]

Saludos a todos. Tengo un conocido que tiene un extraño inconveniente
con un modem 4G de Movistar. El modelo es un Huawei E1756.

Resulta que ese modelo en algunas distribuciones GNU/Linux anda
perfecto, y en otras no hay forma de hacerlo andar...

Funciona en una distro con un kernel cargado de componentes privativos
como Ubuntu (lo que usa ahora) pero también en Trisquel, que es 100%
software libre.  Sin embargo, en otras distros como Xubuntu y Fedora no
anda. Debian, lamentablemente, está en este último grupo, aunque en
Canaima, que está basada en Debian, funciona bien.

Me he cansado de buscar información al respecto y de probar distintos
métodos, y ninguno sirve. Aprovechando mi reciente descubrimiento de
esta lista comparto el inconveniente por si alguien sabe cómo
solucionarlo o, por lo menos, sabe a qué se debe (confieso que me
intriga el tema).

Aclaro también que probamos con diversos entornos de escritorio y el
asunto no parece pasar por ese lado. En Windows el modem se conectaba
mediante un programa llamado "Escritorio Movistar" pero en GNU/Linux no
hay tal cosa (existió en su momento pero todas las páginas están
borradas, y aunque se "revivan" con The Internet Archive no queda nada
útil).

Muchas gracias por su tiempo.

Saludos cordiales.

Re: modem SagemCom F@st 3284

[andre_debian]

On Saturday 28 January 2017 23:19:25 Miquel Demur  wrote:
> s'agit il d'une installation rapide ou d'une configuration ? 

C'est dans la partie de configuration de la Wifi,
modifier le SSID et la clé WiFi :
WPA-PSK [TKIP] + WPA2-PSK [AES],
Il y a 3 champs à remplir alors qu'un seul devrait suffire.

Il faut sans doute qu'une personne de la liste possède un tel modem
pour pouvoir m'aider.

Bon dimanche.

André

Re: modem SagemCom F@st 3284

[Alexandre GRIVEAUX]

Bonsoir,

Pour le wifi il s'agit des fréquences utilisé (en gros 5Ghz pour A & N
2,4Ghz B,G & N)

Une petite copie d'écrans pourrait nous aider.


@+Alex


Le 28/01/2017 à 21:30, andre_deb...@numericable.fr a écrit :
> Bonsoir,
>
> Y a t-il parmi vous des personnes qui ont un modem
> SagemCom F@st 3284 ?
> (c'est le modèle pour SFR et Numericable)
>
> Je ne vois absolument pas comment configurer la WiFi,
> il y a 2 types de WIFI : WI-FI 2,4 GHZ et  WI-FI 5 GHZ
> Laquelle choisir et comment choisir sa clé ?
> qui propose 3 champs à remplir, mais le(s)quel(s) remplir ?
> À quoi sert celui du milieu ?
> Si je coche "Afficher le mot de passe" ou non,
> ça ne change rien :
> les deux à gauche et à droite restent avec des étoiles *
> et celui du milieu reste en clair.
>
> Bref, c'était si simple avant avec l'ancien modem Netgear qui
> est tombé en panne.
>
> Merci de votre aide.
>
> André
>

modem SagemCom F@st 3284

[andre_debian]

Bonsoir,

Y a t-il parmi vous des personnes qui ont un modem
SagemCom F@st 3284 ?
(c'est le modèle pour SFR et Numericable)

Je ne vois absolument pas comment configurer la WiFi,
il y a 2 types de WIFI : WI-FI 2,4 GHZ et  WI-FI 5 GHZ
Laquelle choisir et comment choisir sa clé ?
qui propose 3 champs à remplir, mais le(s)quel(s) remplir ?
À quoi sert celui du milieu ?
Si je coche "Afficher le mot de passe" ou non,
ça ne change rien :
les deux à gauche et à droite restent avec des étoiles *
et celui du milieu reste en clair.

Bref, c'était si simple avant avec l'ancien modem Netgear qui
est tombé en panne.

Merci de votre aide.

André

Integrating usb-modeswitch and ifupdown for modem stick

[Rainer Dorsch]

Hi,

I use usb-modeswitch in jessie-backports to bringup the Aldi Webstick (Mediatek 
MD 99079), which works nicely.

I integrated the network interface in /etc/network/interfaces

#auto ppp0
iface ppp0 inet ppp
provider alditalk
pre-up /usr/local/bin/setPIN.sh

which also works nicely with "ifup ppp0".

The downside I see though is that if I uncomment the "auto ppp0" I get a

root@mohot:~# ifup ppp0
/usr/sbin/pppd: In file /etc/ppp/peers/alditalk: unrecognized option 
'/dev/ttyUSB0'
Failed to bring up ppp0.
root@mohot:~# 

I suspect it is because at the time ifupdown tries to bringup /dev/ttyUSB0, 
usb-modeswitch did not yet run on this interface.

root@mohot:~# grep ttyUSB0 /var/log/syslog
Dec 11 08:50:47 mohot networking[227]: Configuring network 
interfaces.../usr/sbin/pppd: In file /etc/ppp/peers/alditalk: unrecognized 
option '/dev/ttyUSB0'
Dec 11 08:50:47 mohot pppd[256]: In file /etc/ppp/peers/alditalk: unrecognized 
option '/dev/ttyUSB0'
Dec 11 08:50:56 mohot kernel: [   17.462944] usb 1-1: GSM modem (1-port) 
converter now attached to ttyUSB0
root@mohot:~#

Is there a way to get this dependency included in the boot process?

Many thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

Re: Modem oem-config sur debian 8.4

[Jean Bernon]

Je ne connais pas vraiment le contexte de votre question, mais je risque une 
réponse. Manifestement le paquet oem-config est propre à ubuntu. On peut 
toujours tester une installation sur Debian. Sinon, si vous installez Debian 
avec un environnement graphique Gnome, la fonction "utilisateurs" de Gnome 
semble être une alternative. Il faut livrer le PC avec le mot de passe de root 
et l'interface de la fonction "utilisateurs" permet au client de configurer le 
compte utilisateur installé par défaut (nom affiché, type de compte, 
langue/pays, mot de passe), voire de supprimer ce compte par défaut pour en 
créer un ou plusieurs de son choix. N'est-ce pas suffisant ? 

- Mail original -

> De: "Michel Memeteau - EKIMIA" <cont...@ekimia.fr>
> À: "debian-user-french" <debian-user-french@lists.debian.org>
> Envoyé: Samedi 26 Novembre 2016 11:18:51
> Objet: Re: Modem oem-config sur debian 8.4

> Bonjour , aucune réponse ? in

> ça nous gêne un peu car on vends des Pcs avec debian préinstallé et
> on est obligé de pré configuré un compte et un mot de passe.

> Si quelqu'un a une idée ...

> photo
> Michel Memeteau
> Directeur, Ekimia SAS
> +33 (0)9 72 30 83 34 | m...@ekimia.fr | Notre WebBoutique :
> http://shop.ekimia.fr | 49 chemin union 13720 La bouilladisse
> FRANCE

> Contactez nous directement par Tchat sur http://bit.ly/ekichat

> Le 18 mai 2016 à 20:57, Michel Memeteau - EKIMIA < cont...@ekimia.fr
> > a écrit :

> > Bonjour a tous ,
> 

> > Y a t il un mode oem-config dans Debian comme sur Ubuntu qui permet
> > de mettre le système dans un état "usine" pour que la personne
> > puisse choisir son nom d’utilisateur et son mot de passe ?
> 

> > Merci .
> 

> > photo
> 
> > Michel Memeteau
> 
> > Directeur, Ekimia SAS
> 
> > +33 (0)9 72 30 83 34 | m...@ekimia.fr | WebBoutique Pc GNU/Linux :
> > http://shop.ekimia.fr | 49 chemin union 13720 La bouilladisse
> 
> > FRANCE
> 

> > Contactez nous directement par Tchat sur http://bit.ly/ekichat
> 

Re: Modem oem-config sur debian 8.4

[Michel Memeteau - EKIMIA]

Bonjour , aucune réponse ?

ça nous gêne un peu car on vends des Pcs avec debian préinstallé et on est
obligé de pré configuré un compte et un mot de passe.

Si quelqu'un a une idée ...

[image: photo]
*Michel Memeteau*
Directeur, Ekimia SAS
+33 (0)9 72 30 83 34 <+33+9+72+30+83+34> | m...@ekimia.fr | Notre WebBoutique
: http://shop.ekimia.fr  | 49 chemin union 13720 La
bouilladisse
 FRANCE




Contactez nous directement par Tchat sur http://bit.ly/ekichat




Le 18 mai 2016 à 20:57, Michel Memeteau - EKIMIA  a
écrit :

> Bonjour a tous ,
>
> Y a t il un mode oem-config dans Debian comme sur Ubuntu qui permet de
> mettre le système dans un état "usine" pour que la personne puisse choisir
> son nom d’utilisateur et son mot de passe ?
>
> Merci .
>
>
>
>
>
> [image: photo]
> *Michel Memeteau*
> Directeur, Ekimia SAS
> +33 (0)9 72 30 83 34 <+33+9+72+30+83+34> | m...@ekimia.fr | WebBoutique Pc
> GNU/Linux : http://shop.ekimia.fr  | 49 chemin
> union 13720 La bouilladisse
>  FRANCE
> 
> 
> 
>
> Contactez nous directement par Tchat sur http://bit.ly/ekichat
> 
>
>
>

OFF-TOPIC MODEM MER

[Vitor Hugo]

 Existem algum outro modem que trabalha com MER além do D-LINK DSL 500B?
  

Remember Z-modem??

[Ric Moore]

Charles Forsburg has passed away.
http://www.anewtradition.com/obituaries/obituary/12060_Charles_Alton_Forsberg

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: Remember Z-modem??

[Gene Heskett]

On Friday 20 November 2015 14:04:48 Ric Moore wrote:

> Charles Forsburg has passed away.
> http://www.anewtradition.com/obituaries/obituary/12060_Charles_Alton_F
>orsberg

Oh fudge.  Damn.  His rzsz software that I last built at version 3.3.6, 
but made some serious speedups in, for the os9/nitros9 operating system, 
has been part of my stable of code for nearly 25 years now.

Chuck wrote good code 98% of the time. Well organized, methodical, it was 
actually easy to improve it, gaining around 200 cps of overall speed 
with my hacks, on a 1.78 Mhz motorola 6809 cpu.  Taking advantage of the 
Hitachi 63c09 in place of the motorola chip, the speedup was closer to 
325 cps.

He will be missed.  I hope his ride here was a pleasant one.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page