Access server connected to PC via Ethernet, through WiFi network on a mobile device

I’m trying to access files stored on my headless file server, from an Android device.

So I have:


[THIS HAS THE FILES I WANT ACCESS TOO]

A headless Debian server.

IP address 169.254.240.2 [Ethernet].

This is connected directly to my laptop via Ethernet.


A Windows 10 laptop.

IP address 169.254.240.1 [Ethernet].

IP address 192.168.0.30 [WiFi].

This is connected directly to my server via Ethernet.

This is also connected to my router via WiFi.


An Android device.

IP address 192.168.0.37 [WiFi].

This is connected to my router via WiFi.


For reasons I won’t go in to, this setup is unchangeable.

Can I access the files from the server on my Android device?

If so, without modifying the cabling at all, how?

Can I bridge the connections together or something?

How to attach attributes to a list of network objects?

I have a list of network objects and a list of dataframes that include vertex attributes. I would like to attach the vertex attributes to the network objects.

In the code below I show how to complete this task for each network object individually. However, I cannot figure out how to complete this task when I have the network objects and vertex attribute dataframes in lists. In reality, I have a large number of network objects which is why I would like to use lists. I have tried to use lapply but couldn’t figure out the solution.

# Use the network library library("network")  # Create first dataset data_frame_1 = data.frame(event1 = c(1, 2, 1, 0),                           event2 = c(0, 0, 3, 0),                           event3 = c(1, 1, 0, 4),                           row.names = letters[1:4])  # Transform first dataset to matrix and to network data_matrix_1 <- as.matrix(data_frame_1) data_network_1 <- as.network(data_matrix_1, matrix.type='bipartite', loops=FALSE, directed = FALSE, ignore.eval=FALSE, names.eval='weight')  # Create first vertex attribute dataset attribute_1 = data.frame(attribute1 = c(2, 5, 7, 1), attribute2 = c(4, 1, 0, 2), row.names = letters[1:4])  # Attach attributes to network data_network_attr_1 <- network::set.vertex.attribute(data_network_1, names(attribute_1), attribute_1)   # Create second dataset data_frame_2 = data.frame(event1 = c(0, 1, 2, 0),                           event2 = c(0, 3, 1, 0),                           event3 = c(4, 2, 0, 1),                           row.names = letters[1:4])  # Transform second dataset to matrix and to network data_matrix_2 <- as.matrix(data_frame_2) data_network_2 <- as.network(data_matrix_2, matrix.type='bipartite', loops=FALSE, directed = FALSE, ignore.eval=FALSE, names.eval='weight')  # Create second vertex attribute dataset attribute_2 = data.frame(attribute1 = c(4, 1, 2, 1), attribute2 = c(5, 0, 2, 1), row.names = letters[1:4])  # Attach attributes to network data_network_attr_2 <- network::set.vertex.attribute(data_network_2, names(attribute_2), attribute_2)   # Repeat the previous steps using lists.  # Create a list of the two networks list_dataframe <-list(data_frame_1, data_frame_2) list_matrix <- lapply(list_dataframe, as.matrix) list_network <- lapply (list_matrix, as.network, matrix.type='bipartite', loops=FALSE, directed = FALSE, ignore.eval=FALSE, names.eval='weight')  # Create a list of the two attribute datasets  list_attributes <-list(attribute_1, attribute_2)  # How do I attach the list of attributes to the list of networks? 

Shouldn’t NASA JPL’s network be secure against Raspberry Pi connections authorized or not?

The question What information was stolen from JPL during the Raspberry Pi hack? refers to an event in recent news (e.g. Engadget’s A rogue Raspberry Pi helped hackers access NASA JPL systems) and references NASA’s Office of Inspector General June 2019 report Cybersecurity Management and Oversight a the Jet Propulsion Laboratory which states on page 17 in the section titled Incomplete and Inaccurate System Component Inventory:

Moreover, system administrators did not consistently update the inventory system when they added devices to the network. Specifically, we found that 8 of 11 system administrators responsible for managing the 13 systems in our sample maintain a separate inventory spreadsheet of their systems from which they periodically update the information manually in the ITSDB. One system administrator told us he does not regularly enter new devices into the ITSDB as required because the database’s updating function sometimes does not work and he later forgets to enter the asset information. Consequently, assets can be added to the network without being properly identified and vetted by security officials. The April 2018 cyberattack exploited this particular weakness when the hacker accessed the JPL network by targeting a Raspberry Pi computer that was not authorized to be attached to the JPL network. 32 The device should not have been permitted on the JPL network without the JPL OCIO’s review and approval.

To me it sounds like overall the report laments the failure to keep an updated list of devices that are authorized to be connected the network as the major security issue; if they’d only had better record-keeping, this wouldn’t have happened. But it seems to me that no matter how well you document after the fact what’s supposed to be connected that doesn’t in any way prevent inadvertent, accidental, or purposeful connection of an unauthorized device, for example “just for a minute” to download a Raspberry Pi update of some kind.

Question: Shouldn’t such a valuable US government network be secure against all connections equally, authorized or not?

This answer starts to outline the seriousness of the breach.

Detect network traffic and execute command [on hold]

using kind of a dial-up connection, I was wondering if there is any option using Linux (Raspberry Pi as router) to detect incoming traffic on interface wlan0 (and maybe a specific device) so that a command can be executed:

I have two network interfaces on my Pi. One is used for the local WiFi network to be accessed by all my devices, while the traffic is routed to the second interface to the external gateway. That works fine. The issue is that it requires a login from time to time, which is an issue for Alexa devices and bothers me in general. Therefore, I need to execute a script, when a client (of wlan0) wants to use the internet. Any suggestions?

How do I get my network (lan) card to power down on computer shutdown

In Windows when I shut down my computer the network card powers off as well.

In Ubuntu when I power down the network card powers off for a second (at least going by the lan light on my router) but then powers back on.

I know this is to allow wake on lan but I have no need or desire to wake the computer.

How do I do this in Ubuntu?

I am willing and capable of using terminal commands, but if you are going to give them to me please explain what they do as well. Other than safety, which is not really a concern on this sight, the other users will pounce on an unsafe command, it is hard to learn if commands are just thrown out with no explanation.

I would prefer the Lan card to shut off in both power off and sleep but will settle for power off only.

Get social network service for you for $1

Hello sir, Get 40+ REAL SUBSCRIBERS on your channel for just $ 1 Want subscribers for your channel but tired of fake services? Don’t worry! CreativeGuy is here. Features: Best quality in the marketReal subscribersCheapest price on SeoClerk100% satisfaction guaranteedSplit available Important Note: No fake subscribersMake sure that subscriber counter of your channel is visible Thank You

by: rummansathe
Created: —
Category: Social Networks
Viewed: 130


Why is it called network “topology”? Why not network “graph”?

I want to understand why we use the term “network topology” as opposed to “network graph“, or another term, to talk about the structure of networks. I’m working on a network design for a project, and want to make sure I don’t use any terms that I don’t truly understand.

Wikipedia defines network topology as “the arrangement of the various elements (links, nodes, etc.) of a computer network.” This strikes me as interesting, because when I hear the words link and node, I immediately think of graph theory and the objects it is concerned with.

Topology, according to Wikipedia again, is “concerned with the properties of space that are preserved under continuous deformations…” And when you look at the basic examples of topological objects, you see coffee cups and Möbius strips, as opposed to the discrete vertices and edges you see with graph theory.

So why do we refer to networks as having a “topology”?

SSH brute-force from my network / domain

Twice a week I receive an email to abuse@mydomain.tld that says:

An attempt to brute-force account passwords over SSH/FTP by a machine in your domain or in your network has been detected. Attached are the host who attacks and time / date of activity. Please take the necessary action(s) to stop this activity immediately. If you have any questions please reply to this email.  Host of attacker: <MYIP> => server.mydomain.tld => mydomain.tld Responsible email contacts: abuse@mydomain.tld, abuse@ovh.net Attacked hosts in our Network: 37.228.155.101, 185.39.222.116, 77.75.254.116, 185.39.221.179, 37.228.154.167, 37.228.154.61, 85.158.181.17, 185.39.222.20  Logfile entries (time is MET / GMT+1): Sat Jun 22 06:51:55 2019: user: vnc service: ssh target: 185.39.221.179 source: <MYIP> Sat Jun 22 06:48:29 2019: user: mysqldump service: ssh target: 185.39.222.116 source: <MYIP> Sat Jun 22 06:46:59 2019: user: testftp service: ssh target: 185.39.222.116 source: <MYIP> Sat Jun 22 06:45:59 2019: user: www-data service: ssh target: 185.39.222.116 source: <MYIP> Sat Jun 22 06:44:29 2019: user: ubuntu service: ssh target: 185.39.222.116 source: <MYIP> Sat Jun 22 06:43:29 2019: user: postgres service: ssh target: 185.39.222.116 source: <MYIP> Sat Jun 22 06:41:59 2019: user: ubuntu service: ssh target: 185.39.222.116 source: <MYIP> Sat Jun 22 06:40:59 2019: user: dong service: ssh target: 185.39.222.116 source: <MYIP> Sat Jun 22 06:39:29 2019: user: root service: ssh target: 185.39.222.116 source: <MYIP> [ ... other 4 IPs ... ] 

They are always the same 4 IPs. For SSH authentication I use Google 2 factor, I have root user disabled and only an user allowed. I have also changed che port. This is a VPS by OVH where I have a mail server so I’m a little worried.