Add Ethernet settings on http://192.168.10.1/#/settings

[pasniak]

When I plug Ethernet cable I cannot see Stratux on my network. It would be great to have it accessible from desktop for debugging or log viewing.

[cyoung]

ifup eth0 from the Wi-Fi connection.

[pasniak]

Where is the file? Yes, I'm familiar with Linux but each time I get to look at Pi's settings, network config is a different file, which looks somewhat cryptic.... + I'd have to do it every time I get a new Stratux img.... +If I f.up I'd have to reinstall img (it's a headless setup)...

[cyoung]

/etc/network/interfaces

[pasniak]

I added ifup eth0 to /etc/network/interfaces
in the second (empty) line (before something with eth0 already)
Now, I do not see the ip on my desktop nor I can bring up WiFi (Edimax is not even blinking).

[pasniak]

I had to ssh into stratux and execute sudo ifup eth0.
If it is that simple why not add it to the gui? (when we can already run update shell from there...)

[peepsnet]

This is not a planned way of using stratux. When we look at features they have to make sense in the common way people will use the device. Your example is one of development level needs. Try to imagine an instance where a pilot would need to know the IP of eth0 while flying the plane and looking at traffic... ⁣Sent from BlueMail ​

…

On May 25, 2017, 9:40 PM, at 9:40 PM, pasniak ***@***.***> wrote: I had to ssh into stratux and execute `sudo ifup eth0`. If it is that simple why not add it to the gui? (when we can already run update shell from there...) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #605 (comment)

[pasniak]

I meant adding this in http://192.168.10.1/#/settings: https://i.imgur.com/QRsdvQV.png

[ssokol]

I've had a number of customers ask for oddball network configurations for various reasons. I'm beginning to think a Networking tab that controls the wireless and the wired Ethernet port might be something worthwhile. It would be hidden by default but would appear using the same trigger as the Developer tab. Some of the networking requests I've seen are: - Wireless client mode (system attempts to join an existing wireless network, falls back to AP mode if connection fails - Wireless security (enable WPA2 password on the AP) - Manual IP destinations for GDL-90 streams - Ethernet port automatically starts up with DHCP client - Ethernet port starts up with static IP - Ethernet port starts up with static IP and DHCP server The number of these that I've seen has been minimal, so it shouldn't be part of the "normal" Stratux UI experience.

…

On Fri, May 26, 2017 at 4:47 AM, pasniak ***@***.***> wrote: I meant adding this in http://192.168.10.1/#/settings: https://i.imgur.com/QRsdvQV.png — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#605 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVYPMxmVRnGlAMoixlrENQ6A7SFPxINks5r9p-pgaJpZM4Nmh9t> .

-- Steven Sokol 408 Camelot Drive Liberty, MO 64068 mobile: +1 816-806-8844 fax: +1 816-817-0441

[peepsnet]

@ssokol,
The Idea of that is great but, I believe, there are too many variables in play.

• Wireless client mode (system attempts to join an existing wireless
  network, falls back to AP mode if connection fails

This, in theory, sounds easy but...

1. If you connect to an existing network then by default you are not able to get data from 192.168.10.1. You would have to then set the "Static IPs" under "Developer Options" in "Settings".
   The solution I have gone with is adding an EDIMAX dongle and modifying the appropriate files.
   See: https://github.com/cyoung/stratux/blob/master/image/interfaces#L13-L55

Wireless Security (enable WPA2 password on the AP)

1. See: 575d51c

2. I can try this again to see if I can get it to work again...

• Manual IP destinations for GDL-90 streams

This exists in Settings->Developers Options-> Static IP's

• Ethernet port automatically starts up with DHCP client

These all seem like Developer Options. If you want to help develop then I believe you might need the knowledge on how to do these things

• Ethernet port starts up with static IP

Seems like the users DHCP server can take care of this. Assign IP by MAC address. This is what I do.

• Ethernet port starts up with static IP and DHCP server

Again this seems like DEV stuff. Are there really users plugging their Stratux into a router in the aircraft and allowing all on board to watch the Status page in flight?? Seems to me like this is a custom application that can be accomplished with a WAP and is not up to us to do this.

Just my thoughts.

Also as a note to the processes of the first request.
Workflow as I see it.

1. When the RPI boots and wlan0 in started the interface is brought up and then stratux-wifi.sh is started(see: https://github.com/cyoung/stratux/blob/master/image/interfaces#L11)

2. This takes the settings we set in dhcpd.conf, isc-dhcp-server, and interfaces and apply the hostapd file to them.

It seems like the current process would have to change before bringing up the wlan0.

I guess I could write a script that looks at the Stratux Config file and see if the user wants to connect to a specified AP(imagine: apName=MyPlanesWiFi). If so then move files around to use the appropriate required settings.

It would require rewriting the interfaces and wpa_supplicant.conf on the fly with every boot.

Just a quick bunch of thoughts for the process. Not FUN! But Possible... I wouldn't shy away from the challenge if there is enough need and someone to build the web interface and modify the associated.GO files as needed.

Don

[pasniak]

Yesterday, just executed sudo ifup eth0, wouldn't it be sufficient if this was executed from web server?

When I run it I got both WiFi (Edimax blue light blinking) and Ethernet working. Just trying to go for low hanging fruit here... It's not about anything in aircraft but debugging or even getting logs off, which is much more convenient from desktops, typically plugged into routers.

[cyoung]

Throw it in /etc/rc.local (before the last line) so it does it every time. It doesn't matter if you have ethernet plugged in or not. Not sure what I changed but it should come up automatically. Try either that or systemctl enable dhcpcd and see if it comes up on ethernet every time you reboot.

[peepsnet]

I use an app like this on my Android tablet to create a few commands I use regularly
https://play.google.com/store/apps/details?id=crosien.HotButton

Like "sudo shutdown -h now"

You could do this for the ifup also!!

[D35Bonanza]

You can get the stratux webpage on both wlan0 and eth0 when active. No issue.
In developer mode I use static IP to send the gdl90 UDP packets They are still sent to wlan0 DHCP clients. 192.168.10.* is wlan0 192.168.3.* is eth0 both wlan0 and eth0 have udp connections from the stratux software.
root@raspberrypi:~# netstat -u

Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State

udp 0 0 raspberrypi:45833 192.168.3.109:4000 ESTABLISHED

udp 0 0 raspberrypi:43397 192.168.3.110:4000 ESTABLISHED

udp 0 0 raspberrypi:41359 192.168.3.104:4000 ESTABLISHED

udp 0 0 raspberrypi:50143 192.168.10.10:4000 ESTABLISHED

udp 0 0 raspberrypi:43519 192.168.10.11:4000 ESTABLISHED

root@raspberrypi:~#

add entry /etc/network/interfaces
allow-hotplug eth0 //interface is active on boot.
before
iface eth0 inet dhcp //my setting

ifup eth0 no longer required.
interfaces
auto lo
#br0

iface lo inet loopback

#eth0
allow-hotplug eth0

iface eth0 inet dhcp

allow-hotplug wlan0

iface wlan0 inet static
address 192.168.10.1
netmask 255.255.255.0
post-up /usr/sbin/stratux-wifi.sh

see man interfaces

[bradanlane]

Alternate Option:

It's possible to have a Raspberry Pi configured to automatically switch its WiFi between access point and client mode.

This would still require exposing some admin UI for the purposes of the user entering one or more of their SSID networks.

Once setup, it would be automatic and it would also mean not having to expose the ethernet port thru the case/housing or using a wired connection.

[jocamero]

@cyoung Any progress on this? Or is there a tutorial out there somewhere where I can figure out how to modify the network settings so the Stratux connects to my iPad's Personal Hotspot? This way the iPad would have cellular Internet while on the ground and the Stratux would be able to get software updates without opening the case to expose the Ethernet port.

I think my preference would be on the following order to connect to iPad's Personal Hotspot, home network SSID, and if neither of those are available, then revert to the default AP mode offering up the Stratux network SSID. Possible?

[wa9als]

I think you can get what you want by making your ipad-Stratux connection static (mine is 192.168.10.18) and give it a fixed DNS as well like 8.8.4.4 and router 192.168.10.1. I do this with my ipad, then the ipad can still use the Stratux and also connect to my phone hotspot and use Internet.

On 2019-02-04 15:05, jocamero wrote: @cyoung [1] Any progress on this? Or is there a tutorial out there somewhere where I can figure out how to modify the network settings so the Stratux connects to my iPad's Personal Hotspot? This way the iPad would have cellular Internet while on the ground and the Stratux would be able to get software updates without opening the case to expose the Ethernet port. I think my preference would be on the following order to connect to iPad's Personal Hotspot, home network SSID, and if neither of those are available, then revert to the default AP mode offering up the Stratux network SSID. Possible? -- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub [2], or mute the thread [3].

Links: ------ [1] https://github.com/cyoung [2] #605 (comment) [3] https://github.com/notifications/unsubscribe-auth/AlCPMyy5_bwkUri0dcNdOWZsRldw6hG4ks5vKJKZgaJpZM4Nmh9t

[HoeckDK]

Hi all,

I'm looking for the eth0 DHCP server+static IP.
My use case is that I have run out of serial in my Open Vario and would like to avoid using wifi. Therefore if the LAN port would act as the WLAN does, it would be sweet, and provide the vario with an IP.

I have tried to modify /etc/network/interfaces, but changes seems to be reverted on next reboot. And I never manage to get an IP other that 127.0.0.