This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
change eth0 to static
#11
Open a terminal and type "nano ~/.config/openplotter/openplotter.conf"
Reply
#12
(2017-06-29, 02:08 PM)abarrow Wrote: Open a terminal and type "nano ~/.config/openplotter/openplotter.conf"

Not working...
I'm getting this:
Code:
pi@openplotter:~ $ nano -/.config/openplotter/openplotter.conf
nano: invalid option -- '/'
Usage: nano [OPTIONS] [[+LINE,COLUMN] FILE]...

Option        GNU long option        Meaning
-h, -?        --help            Show this message
+LINE,COLUMN                Start at line LINE, column COLUMN
-A        --smarthome        Enable smart home key
-B        --backup        Save backups of existing files
-C <dir>    --backupdir=<dir>    Directory for saving unique backup files
-D        --boldtext        Use bold instead of reverse video text
-E        --tabstospaces        Convert typed tabs to spaces
-F        --multibuffer        Enable multiple file buffers
-H        --historylog        Log & read search/replace string history
-I        --ignorercfiles        Don't look at nanorc files
-K        --rebindkeypad        Fix numeric keypad key confusion problem
-L        --nonewlines        Don't add newlines to the ends of files
-N        --noconvert        Don't convert files from DOS/Mac format
-O        --morespace        Use one more line for editing
-Q <str>    --quotestr=<str>    Quoting string
-R        --restricted        Restricted mode
-S        --smooth        Scroll by line instead of half-screen
-T <#cols>    --tabsize=<#cols>    Set width of a tab to #cols columns
-U        --quickblank        Do quick statusbar blanking
-V        --version        Print version information and exit
-W        --wordbounds        Detect word boundaries more accurately
-Y <str>    --syntax=<str>        Syntax definition to use for coloring
-c        --const            Constantly show cursor position
-d        --rebinddelete        Fix Backspace/Delete confusion problem
-i        --autoindent        Automatically indent new lines
-k        --cut            Cut from cursor to end of line
-l        --nofollow        Don't follow symbolic links, overwrite
-m        --mouse            Enable the use of the mouse
-o <dir>    --operatingdir=<dir>    Set operating directory
-p        --preserve        Preserve XON (^Q) and XOFF (^S) keys
-q        --quiet            Silently ignore startup issues like rc file errors
-r <#cols>    --fill=<#cols>        Set wrapping point at column #cols
-s <prog>    --speller=<prog>    Enable alternate speller
-t        --tempfile        Auto save on exit, don't prompt
-u        --undo            Allow generic undo [EXPERIMENTAL]
-v        --view            View mode (read-only)
-w        --nowrap        Don't wrap long lines
-x        --nohelp        Don't show the two help lines
-z        --suspend        Enable suspension
-$        --softwrap        Enable soft line wrapping
-a, -b, -e,                
-f, -g, -j                (ignored, for Pico compatibility)

I've also triet nano /.config/openplotter/openplotter.conf
That is just an emty file...
Same with sudo in front.
Reply
#13
The first character isn't a dash "-" it is a tilde "~" (on my US keyboard is is left of "1").

If you are already in your pi home directory (it will look something like "pi@openplotter:~ $") just type "nano .config/openplotter/openplotter.conf".
Reply
#14
Think i got it :Smile Restarting Pi now

Okay
I went to /.config/openplotter/openplotter.conf

change enable 1 to enable 2 at wlan

went to /etc/network/interfaces

change eth0 dhcp to eth0 static and wrote what I had to do.

Restart Pi

Opened /etc/network/interfaces and got this:
Code:
File: /etc/network/interfaces                          

allow-hotplug usb0
iface usb0 inet static
address 192.168.42.100
netmask 255.255.255.0

No AP over wlan0 anymore.. 
Must set enable back to 1 and try something else.

I've triet but bridge to eth0, but is it not seems working correctly.
I'll try again in a moment and paste what I get.
Reply
#15
Now i'm back to square 1;
I put wlan0 as access point(or openplotter did), use wlan1 for access wireless, bridge to eth0

my ifconfig looks like this:

Code:
br0       Link encap:Ethernet  HWaddr b8:27:eb:27:b5:b7  
         inet addr:10.10.10.1  Bcast:10.10.10.255  Mask:255.255.255.0
         inet6 addr: fe80::101a:af01:99ff:29b/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:29303 errors:0 dropped:0 overruns:0 frame:0
         TX packets:24272 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:3738849 (3.5 MiB)  TX bytes:12044372 (11.4 MiB)

eth0      Link encap:Ethernet  HWaddr b8:27:eb:72:e0:e2  
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:128 errors:0 dropped:0 overruns:0 frame:0
         TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:6656 (6.5 KiB)  TX bytes:9122 (8.9 KiB)

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:106860 errors:0 dropped:0 overruns:0 frame:0
         TX packets:106860 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1
         RX bytes:12808783 (12.2 MiB)  TX bytes:12808783 (12.2 MiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:27:b5:b7  
         inet6 addr: fe80::ba27:ebff:fe27:b5b7/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:29239 errors:0 dropped:0 overruns:0 frame:0
         TX packets:24445 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:3735905 (3.5 MiB)  TX bytes:12644749 (12.0 MiB)

wlan1     Link encap:Ethernet  HWaddr 08:6a:0a:64:0a:41  
         inet addr:192.168.1.19  Bcast:192.168.1.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:25078 errors:0 dropped:21 overruns:0 frame:0
         TX packets:17421 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:12247151 (11.6 MiB)  TX bytes:3270837 (3.1 MiB)

My /etc/network/interfaces looks like this:
Code:
File: /etc/network/interfaces                          

auto br0
iface br0 inet static
bridge_ports eth0
address 10.10.10.1
broadcast 10.10.10.255
netmask 255.255.255.0
network 10.10.10.0
bridge_maxwait 1
post-up iptables -t nat -A POSTROUTING -o wlan1 -j MASQUERADE
post-up iptables -A FORWARD -i wlan1 -o br0 -m state --state RELATED,ESTABLISHE$
post-up iptables -A FORWARD -i br0 -o wlan1 -j ACCEPT
post-up systemctl daemon-reload
I have a relay connected to eth0 which is accesseble on 192.168.1.100
If I go to that in browser i see this: 
"Site is unreacheble"
If I hook it in the wlan router that the wlan1 is connected to, I'll get the main controlpage..

I have tried unplugging wlan1, but no differents.
If I then uncheck bridge to eth0 and put in eth0 as shared, it is on 255.255.0.0. This I cant change..

This is the networksettings on my relay. It is working on wlan1, but not on eth0. I dont want the wlan1 router on the boat. i'm only using that in my workshop for setting up the hole system before mounting on the boat.


Network Configuration
MAC Address
E8:EABig GrinA:00:21:F6

IP Address
192.168.1.100
Gateway
192.168.1.1
Subnet Mask
255.255.255.0
Primary DNS
192.168.1.1
Secondary DNS
0.0.0.0
Reply
#16
So you only want a connection to 192.168.1.100 over eth0.
change ip in openplotter.conf to 192.168.1.1
Enable access point
Enable bridge to eth0
Apply
reboot

In this mode OpenPlotter acts like a router (dhcp).
When you connect a notebook or pc to the rpi over eth0 or wlan0 its identical it will get an ip in the 192.168.1.xxx Net.
Reply
#17
WUHUUUUUU it is working Big Grin

Well sort of. Now my accesspoint is down. It says its up and running, but cant see it with by computer or smartphone...

This is now my ifconfig
I triet put everything back in normal, but nothing is working now, except wlan1
Code:
ifconfig
br0       Link encap:Ethernet  HWaddr b8:27:eb:72:e0:e2  
         inet addr:10.10.10.1  Bcast:10.10.10.255  Mask:255.255.255.0
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:22 errors:0 dropped:0 overruns:0 frame:0
         TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:1012 (1012.0 B)  TX bytes:2748 (2.6 KiB)

eth0      Link encap:Ethernet  HWaddr b8:27:eb:72:e0:e2  
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:22 errors:0 dropped:0 overruns:0 frame:0
         TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:1012 (1012.0 B)  TX bytes:2916 (2.8 KiB)

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:3833 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3833 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1
         RX bytes:452909 (442.2 KiB)  TX bytes:452909 (442.2 KiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:27:b5:b7  
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:6600 (6.4 KiB)

wlan1     Link encap:Ethernet  HWaddr 08:6a:0a:64:0a:41  
         inet addr:192.168.1.19  Bcast:192.168.1.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1212 errors:0 dropped:27 overruns:0 frame:0
         TX packets:630 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:512225 (500.2 KiB)  TX bytes:64416 (62.9 KiB)
This is my /etc/network/interfaces:
Code:
File: /etc/network/interfaces                                                                                                                                  

# generated by openplotter
auto lo
iface lo inet loopback
allow-hotplug usb0
iface usb0 inet static
address 192.168.42.100
auto eth0
iface eth0 inet manual
auto wlan0
iface wlan0 inet manual
auto br0
iface br0 inet static
bridge_ports eth0
address 10.10.10.1
broadcast 10.10.10.255
netmask 255.255.255.0
network 10.10.10.0
bridge_maxwait 1
post-up iptables -t nat -A POSTROUTING -o wlan1 -j MASQUERADE
post-up iptables -A FORWARD -i wlan1 -o br0 -m state --state RELATED,ESTABLISHED -j ACCEPT
post-up iptables -A FORWARD -i br0 -o wlan1 -j ACCEPT
post-up systemctl daemon-reload
Reply
#18
Ive got the accesspoint back up again. Put in 10.10.10.1, restart and waited for two hours. So i'm back to basic.

Okay i got an update:

Wlan0 is now running accesspoint as normal.
10.10.10.1
netmast 255.255.255.0

Perfect.

Wlan1 unplugged

eth0 share internet.

eth0 on 255.255.255.0

perfect.

plugged eth0 to router with internet and plugged relay to same router.

get to 192.168.1.100 and wow! now i can control my relay.

run sudo arp-scan --interface eth0 --localnet

got printers, computers, relay and everything on the local net.

Unplugged the internet from the router so only Openplotter and relay connected.

ran sudo arp-scan --interface eth0 --localnet

could see the relay - great!

went to browser and tapped 192.168.1.100
but nothing... "This site can't be reached"....
Reply
#19
Maybe a route issue?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)