I an attempting to network the android phone. using WiFi

The router is a billion BP 7800NXL with a WiFi port

The computer file manager is Dolphin


I changed the phone IP to 192.168.1.220 to avoid router DHCP
I modified the "hosts" file to reflect the phone IP address


When the phone connects to the router I open the phone's File Manager.
The phone File Manager menu option is "Connect to Computer"
and then "Start" > select int/ext storage and then directs me to
enter "ftp://192.168.1.220:2121" into the computer file manager.

This always fails the first time because the computer file manager
removes one of the double forward slashes in the ftp address and then
says "no host name specified"

When I correct the ftp address the computer file manager displays the
phone directory structure and the contents . But they are not accessible.

If I use the computer file manager to copy a phone file to the computer
only the meta data is transferred and then a pop up says "Could not read
file "

But I can copy a file from computer to the phone

If I enter the ftp address into the computer browser Firefox, then I can
read and copy files to the computer

I can ping the phone

So I am almost there


cat /etc/hosts
# generated by drakhosts
127.0.0.1 localhost.localdomain localhost
192.168.1.100 unimatrix.cryptid.test unimatrix
192.168.1.200 prnt.cryptid.test prnt
192.168.1.220 phone.cryptid.test phone
192.168.1.254 gateway.cryptid.test gateway
203.123.68.185 wangate.cryptid.test wangate
203.123.90.241 routerwan.cryptid.test router


~]$ ping -c1 phone
PING phone.cryptid.test (192.168.1.220) 56(84) bytes of data.
64 bytes from phone.cryptid.test (192.168.1.220): icmp_seq=1 ttl=64
time=219 ms

- --- phone.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 219.365/219.365/219.365/0.000 ms


Regards


--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 29 Nov 2019 09:54:39 +1100, faeychild wrote:

I an attempting to network the android phone. using WiFi

The router is a billion BP 7800NXL with a WiFi port

The computer file manager is Dolphin

I changed the phone IP to 192.168.1.220 to avoid router DHCP

If you are not going to use DHCP I would disable it if you are
going to enable your router wireless device.

You do need to disable SSID broadcasting and use strongest protocol
possible with a long key.

I have not bothered to study your modem manual. On mine, I found a
section where I can set mine to only allow devices by mac id.

Also, I have no experience with mobile phones.

I modified the "hosts" file to reflect the phone IP address

When the phone connects to the router I open the phone's File Manager.
The phone File Manager menu option is "Connect to Computer"
and then "Start" > select int/ext storage and then directs me to
enter "ftp://192.168.1.220:2121" into the computer file manager.

This always fails the first time because the computer file manager
removes one of the double forward slashes in the ftp address and then
says "no host name specified"

When I correct the ftp address the computer file manager displays the
phone directory structure and the contents . But they are not accessible.

Sounds about right although I have not played with ftp. Just because you
get ftp access, you may have only read access to the "ftp directory"
and no other access outside of the "ftp directory"

If I use the computer file manager to copy a phone file to the computer
only the meta data is transferred and then a pop up says "Could not read
file "

Hmmm, I would have thought you would not even have access to meta data
let alone file data.

But I can copy a file from computer to the phone

Then I can guess the file is in the "ftp directory"

If I enter the ftp address into the computer browser Firefox, then I can
read and copy files to the computer

At this point, I concede I know nothing about why Dolphin fails and
firefox works on the ftp address.

If no one gets you some answers, you might want to post over on comp.os.linux.networking

That assumes you have entered something like
linux wireless android ftp access
in the first box at
https://encrypted.google.com/advanced_search

I tried it and got About 4,710,000 results (0.90 seconds)

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 29/11/19 10:35 am, Bit Twister wrote:

I changed the phone IP to 192.168.1.220 to avoid router DHCP

If you are not going to use DHCP I would disable it if you are
going to enable your router wireless device.

Yes I suppose with the hosts file properly configured, the DHCP is not
needed

You do need to disable SSID broadcasting and use strongest protocol
possible with a long key.

I just tried that and the phone could not detect the WiFi signal.

I have not bothered to study your modem manual. On mine, I found a
section where I can set mine to only allow devices by mac id.

Also, I have no experience with mobile phones.

Me neither. Any serious dive into this and it's a whole new career

If I use the computer file manager to copy a phone file to the computer
only the meta data is transferred and then a pop up says "Could not read
file "

Hmmm, I would have thought you would not even have access to meta data
let alone file data.

Puzzled me too. The copied file remains incomplete, labeled "part" and
is is not viewable - it's a jpg - but the tool tip shows all the
photographic information file size resolution, etc.

But I can copy a file from computer to the phone

Then I can guess the file is in the "ftp directory"

If by the "ftp directory" you mean the window in Dolphin displaying the
phone files, then yes.
I can drag drop files in but not out, And the ones dragged in do
actually appear in the phone - successfully transferred

At this point, I concede I know nothing about why Dolphin fails and
firefox works on the ftp address.

It's at this point that I accept that I know absolutely nothing.
And reading manuals and search pages just causes initialism and acronym burnout. Manuals are written for the initiates. For instance read a
manual on brain surgery and how much you comprehend
As you once said, Bits, it's simple when you know how.

If no one gets you some answers, you might want to post over on comp.os.linux.networking

That assumes you have entered something like
linux wireless android ftp access
in the first box at
https://encrypted.google.com/advanced_search

I tried it and got About 4,710,000 results (0.90 seconds)

If I can read 100 per day, that's only 130 years.
Maybe the first one is the jackpot :-)
The volume of information is getting staggeringly out of hand.

Besides if I can get away with using the browser then that will be
enough and one day while looking for something else I may stumble across
the answer.
It has happened before

Hey!! the USB cable still works. I just though the WiFi would be more
elegant

regards

I had to look - you know.

And the answer is like the recipe for rabbit stew - only in this case,
first install an ftp server on the android.

If not!! then you can't get there from here.

--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 29 Nov 2019 17:34:55 +1100, faeychild wrote:

On 29/11/19 10:35 am, Bit Twister wrote:

I changed the phone IP to 192.168.1.220 to avoid router DHCP

If you are not going to use DHCP I would disable it if you are
going to enable your router wireless device.

Yes I suppose with the hosts file properly configured, the DHCP is not
needed

Only for guest devices.

You do need to disable SSID broadcasting and use strongest protocol
possible with a long key.

I just tried that and the phone could not detect the WiFi signal.

Yeah, when in that mode, device/phone needs to know all the details.

Then I can guess the file is in the "ftp directory"

If by the "ftp directory" you mean the window in Dolphin displaying the
phone files, then yes.

The "ftp directory" is like a web server directory. It is where you
have configure the server for file storage/permissions for world read/write access.

Hey!! the USB cable still works. I just though the WiFi would be more
elegant

Yeah, and much easier access for the neighbor criminal. My wireless
cameras have been cracked, and malware installed allowing the criminal
to connect to them and has been scanning ports, trying to get into the
desktop systems.


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 29/11/19 7:50 pm, Bit Twister wrote:

Then I can guess the file is in the "ftp directory"

If by the "ftp directory" you mean the window in Dolphin displaying the
phone files, then yes.

The "ftp directory" is like a web server directory. It is where you
have configure the server for file storage/permissions for world read/write access.

In that case I don't have one

Hey!! the USB cable still works. I just though the WiFi would be more
elegant

Yeah, and much easier access for the neighbor criminal. My wireless
cameras have been cracked, and malware installed allowing the criminal
to connect to them and has been scanning ports, trying to get into the desktop systems.

Woah really. He got past all your passwords and stuff. That's impressive!!

Are you going to build a honeypot?

I am curious about wifi cracking. My password is 16 characters long. something like "+e<>ZJ&yNS25$EG6"
I assumed that that was difficult to crack, maybe not?

regards

--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sat, 30 Nov 2019 08:33:29 +1100, faeychild wrote:

Woah really. He got past all your passwords and stuff. That's impressive!!

Are you going to build a honeypot?

Only if I had a spare computer.

You might want to read
https://en.wikipedia.org/wiki/Wi-Fi_Protected_Access

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 30/11/19 9:38 am, Bit Twister wrote:

On Sat, 30 Nov 2019 08:33:29 +1100, faeychild wrote:

Woah really. He got past all your passwords and stuff. That's
impressive!!

Are you going to build a honeypot?

Only if I had a spare computer.

You might want to read
https://en.wikipedia.org/wiki/Wi-Fi_Protected_Access

It would appear that nothing is really safe.
fortunately I have no real intention of using wifi with any seriousness.

As an aside - do you remember all the networking episode and the
169.x.x.x address in the routing table caused by zeroconf.

The address is back and my "/etc/sysconfig/network" file was down to
only three entries again
HOSTNAME
NETWORKING
CRDA_DOMAIN

Tuesdays backup (mageia_bu) of the file is the same.

I wonder if a recent update does this?
No one else has this event though. Curious!

I understand why you have scripts monitoring everything.
I have since corrected the "network" file


regards



--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso

egards

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sat, 30 Nov 2019 16:57:31 +1100, faeychild wrote:

As an aside - do you remember all the networking episode and the
169.x.x.x address in the routing table caused by zeroconf.

Yes.

The address is back and my "/etc/sysconfig/network" file was down to
only three entries again
HOSTNAME
NETWORKING
CRDA_DOMAIN

Tuesdays backup (mageia_bu) of the file is the same.

I wonder if a recent update does this?

Not on my system.

No one else has this event though. Curious!

Maybe you dinking around with wireless helped you into the ditch.

I understand why you have scripts monitoring everything.
I have since corrected the "network" file

Yep, easy enough for you to have a sys_audit script to run daily for
a check. Easy test, you need to change line count to match yours.

_count=$(wc -l < /etc/sysconfig/network)
if [ $_count -ne 5 ] ; then
echo "$_app /etc/sysconfig/network line count not equal 5" >> $_rpt_fn
mail -s $_app failures root < $_rpt_fn
fi

Or you can use grep to see if NOZEROCONF disappeared.

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sat, 30 Nov 2019 03:56:15 -0600, Bit Twister wrote:

On Sat, 30 Nov 2019 16:57:31 +1100, faeychild wrote:

As an aside - do you remember all the networking episode and the
169.x.x.x address in the routing table caused by zeroconf.

Yes.

The address is back and my "/etc/sysconfig/network" file was down to
only three entries again
HOSTNAME
NETWORKING
CRDA_DOMAIN

Tuesdays backup (mageia_bu) of the file is the same.

I wonder if a recent update does this?

Not on my system.

No one else has this event though. Curious!

Maybe you dinking around with wireless helped you into the ditch.

I understand why you have scripts monitoring everything.
I have since corrected the "network" file

Yep, easy enough for you to have a sys_audit script to run daily for
a check. Easy test, you need to change line count to match yours.

_count=$(wc -l < /etc/sysconfig/network)
if [ $_count -ne 5 ] ; then
echo "$_app /etc/sysconfig/network line count not equal 5" >> $_rpt_fn
mail -s $_app failures root < $_rpt_fn
fi

Oops, the mail command should have subject quoted.
mail -s "$_app failures" root < $_rpt_fn

Or you can use grep to see if NOZEROCONF disappeared.

Best test would be to have a reference file so you can use diff to
warn you about any change to the file.

Of course all the above is useless if you are not set up to get root
email messages.

If postfix is installed/running and you have changed /etc/postfix/aliases

# tail -11 aliases


and executed
postalias aliases

Which means you also would need to launch thunderbird to see any local
email has been sent to faeychild.

I have a script launched by my DE autostart directory to kick off/up
apps onto different desktops/workspaces when I login.
$ env | grep _desktop= | sort -V -t '=' --key=2
_login_desktop=1
_binaries_desktop=2
_usenet_desktop=3
_browsing_desktop=4
_root_desktop=5
_users_desktop=6
_bank_desktop=7
_mail_desktop=8

Desktop login gets an xterm scrolling the journal,
usenet will have slrn running to read Usenet
and desktop mail has thunderbird to see any local email from root cron jobs.

Desktop shortcuts, jump to desired desktop and launch app if not already running.

If you have more than one test in sys_audit, you can have just one test
at end of script to mail you any report failures.

if [ -e $_rpt_fn ] ; then
mail -s "$_app failures" root < $_rpt_fn
fi

That assumes start of script does a
rm --force $_rpt_fn

Some possible test to consider, from mine
check number of kernel rpms installed
check for atime in the future
check for rpmnew files
check for no longer supported rpms
check LAN nic line count
check for rpmsave files
checks for dangling links
check for jexec not disabled
check for /etc/hosts mcc screwup
check passwd and group files
check for any updates and failed installs
check for new php file
check for /etc/sysconfig/network mcc screwup
check rkhunter log for difference
check files owned by normal instead of root
check for segfault in journal
check postfix errors/warnings log
system services check
check /etc/at.allow file against /etc/passwd
unread mail in users mailbox check
check for modifed config files
check /accounts /home permissions
check /etc/cron.d for any files
check for in use ipv6 ports
check /etc/resolv.conf
check systemctl service status

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 29/11/19 10:35 am, Bit Twister wrote:

At this point, I concede I know nothing about why Dolphin fails and
firefox works on the ftp address.

I have an Android phone and an Android tablet. My Wifi router can see
both without modification. I haven't given them specific addresses; the
next number in the 192.168 set is allocated automatically. Firefox in
Linux can read the Firefox history from the tablet, and display the
history in the sidebar in Linux.

I did read somewhere that a while back, changes were made to the Android
OS which made file transfer much more difficult, and killed the playing
of media files in other OSs, but I can set up file transfers over
wireless, using an Android app or an advanced file manager, and read the directory structure and move files across the network using FileZilla at
the Linnux end. Both Android apps give me an address and port number to
enter into FileZilla. The port numbers are not the same in both: one is
2221.

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 30/11/19 8:56 pm, Bit Twister wrote:

Maybe you dinking around with wireless helped you into the ditch.

Ahh! And maybe previous dinking around. eg: the printer drama
All of a cascade effect
I am a bit slow this week

I understand why you have scripts monitoring everything.
I have since corrected the "network" file

Yep, easy enough for you to have a sys_audit script to run daily for
a check. Easy test, you need to change line count to match yours.

<snip>

regards


--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 30/11/19 10:09 pm, Bit Twister wrote:

On Sat, 30 Nov 2019 03:56:15 -0600, Bit Twister wrote:

On Sat, 30 Nov 2019 16:57:31 +1100, faeychild wrote:

As an aside - do you remember all the networking episode and the
169.x.x.x address in the routing table caused by zeroconf.

Yes.

The address is back and my "/etc/sysconfig/network" file was down to
only three entries again
HOSTNAME
NETWORKING
CRDA_DOMAIN

Tuesdays backup (mageia_bu) of the file is the same.

I wonder if a recent update does this?

Not on my system.

No one else has this event though. Curious!

Maybe you dinking around with wireless helped you into the ditch.

I understand why you have scripts monitoring everything.
I have since corrected the "network" file

Yep, easy enough for you to have a sys_audit script to run daily for
a check. Easy test, you need to change line count to match yours.

_count=$(wc -l < /etc/sysconfig/network)
if [ $_count -ne 5 ] ; then
echo "$_app /etc/sysconfig/network line count not equal 5" >> $_rpt_fn
mail -s $_app failures root < $_rpt_fn
fi

Oops, the mail command should have subject quoted.
mail -s "$_app failures" root < $_rpt_fn

Or you can use grep to see if NOZEROCONF disappeared.

Best test would be to have a reference file so you can use diff to
warn you about any change to the file.

<snipped again>

One fine day I must start to organise your scripts

Perhaps even your "man-page" "doc" database. "ux" I think.


--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 1/12/19 4:49 am, Doug Laidlaw wrote:

On 29/11/19 10:35 am, Bit Twister wrote:

At this point, I concede I know nothing about why Dolphin fails and
firefox works on the ftp address.

I have an Android phone and an Android tablet.  My Wifi router can see
both without modification.  I haven't given them specific addresses; the next number in the 192.168 set is allocated automatically. Firefox in
Linux can read the Firefox history from the tablet, and display the
history in the sidebar in Linux.

I did read somewhere that a while back, changes were made to the Android
OS which made file transfer much more difficult,

Now requires an "ftp" client / server

For the infrequent time I need to transfer files, the usb connection is
fine. Leaving a wireless port open on a router is not acceptable.

regards


--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2019-11-30, faeychild <faeychild@nomail.afraid.org> wrote:

On 1/12/19 4:49 am, Doug Laidlaw wrote:

On 29/11/19 10:35 am, Bit Twister wrote:

At this point, I concede I know nothing about why Dolphin fails and
firefox works on the ftp address.

I have an Android phone and an Android tablet.  My Wifi router can see
both without modification.  I haven't given them specific addresses; the >> next number in the 192.168 set is allocated automatically. Firefox in
Linux can read the Firefox history from the tablet, and display the
history in the sidebar in Linux.

I did read somewhere that a while back, changes were made to the Android
OS which made file transfer much more difficult,

Now requires an "ftp" client / server

For the infrequent time I need to transfer files, the usb connection is fine. Leaving a wireless port open on a router is not acceptable.

Yes, they now use and mtp filesystem to present to the Linux OS, which
does not seem to actually be monted anywhere, so you cannot access it
via the usual Linux filesystem commands. However, the program android-file-transfer seems to work quite well. (Plug in your phone via
usb to your computer, run android-file-transfer, and transfer the files
hither and yon.

regards

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 1/12/19 9:37 am, William Unruh wrote:

Yes, they now use and mtp filesystem to present to the Linux OS, which
does not seem to actually be monted anywhere, so you cannot access it
via the usual Linux filesystem commands. However, the program

Yes I had noticed that the phone on USB, unlike an actual USB stick, had
no unmount option in the file manger right click menu.

A bit of magic

regards

--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 1/12/19 4:15 pm, faeychild wrote:

On 1/12/19 9:37 am, William Unruh wrote:

Yes, they now use and mtp filesystem to present to the Linux OS, which
does not seem to actually be monted anywhere, so you cannot access it
via the usual Linux filesystem commands. However, the program

Yes I had noticed that the phone on USB, unlike an actual USB stick, had
no unmount option in the file manger right click menu.

A bit of magic

regards

So, why is all this happening? It sounds as though the problem is the
changes to the Android OS. The mtp filesystem was the one to transfer
media files; it stands for "media transfer protocol." It wasn't
intended to transfer other files.

As from Ice Cream Sandwich, mtp has replaced UMS (USB Mass Storage) as
the default protocol. If it is a protocol, is it correct to call mtp a filesystem? Is it more like PTP for transferring photos? You don't
mount the f/s; you mount the drive or USB stick. There is a lengthy description at:

https://www.androidcentral.com/ics-feature-mtp-what-it-why-use-it-and-how-set-i

Doug.

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 2/12/19 6:02 am, Doug Laidlaw wrote:



https://www.androidcentral.com/ics-feature-mtp-what-it-why-use-it-and-how-set-i



That is interesting, Doug, And something to play with and break stuff

The repository has a file system and driver for mtpfs

So, on a quiet afternoon, it may be interesting to set it up.

I don't want to leave wifi running. As BitTwister said, his wireless
cameras have been hacked and I guess his security would be much better
than mine

As an aside: with the NBN seeming to rely on a cheap wifi router after
the "connection" box we will have suburbs filled with juicy poorly
secured wifi sources. Connected to Win machines. A hacker paradise.

regards

--
faeychild
Running plasmashell 5.15.4 on 5.3.11-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 30/11/2019 17:49, Doug Laidlaw wrote:

On 29/11/19 10:35 am, Bit Twister wrote:

At this point, I concede I know nothing about why Dolphin fails and
firefox works on the ftp address.

I have an Android phone and an Android tablet.  My Wifi router can see
both without modification.  I haven't given them specific addresses; the next number in the 192.168 set is allocated automatically. Firefox in
Linux can read the Firefox history from the tablet, and display the
history in the sidebar in Linux.

I did read somewhere that a while back, changes were made to the Android
OS which made file transfer much more difficult, and killed the playing
of media files in other OSs, but I can set up file transfers over
wireless, using an Android app or an advanced file manager, and read the directory structure and move files across the network using FileZilla at
the Linnux end.  Both Android apps give me an address and port number to enter into FileZilla.  The port numbers are not the same in both: one is 2221.

I have an Android phone with ES File Explorer. If I select Network/View
on PC, Filezilla sees both file structures and I can transfer files back
and forth.
G

--
Grimble
Registered Linux User #450547
Machine 'mozart' running Plasma 5.15.4 on 5.3.13-desktop-2.mga7 kernel.
Mageia release 7 (Official) for x86_64

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)