1
18.7 Legacy Series / Re: [SOLVED] Autostart a script after WAN connection is up
« on: November 10, 2018, 11:00:01 am »
The "start" script works great, thanks @franco!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
18.7 Legacy Series / Re: Autostart a script after WAN connection is up
« on: November 10, 2018, 10:41:59 am »
thanks, I just assumed it's the variable I would have to take, or are they "registered" somewhere? My guess was it has to be named like the rc-script I created.
"start" looks great, will check that out thanks
"start" looks great, will check that out thanks
3
18.7 Legacy Series / [SOLVED] Autostart a script after WAN connection is up
« on: November 10, 2018, 09:34:11 am »
I have a machine in a mobile carrier network with a private IP as WAN address. To be able to remotely connect to the machine I use autossh, which seems to work fine. I've created the following /usr/local/etc/rc.autossh script:
#!/bin/sh
autossh -M 19984 -N -f -o "PubkeyAuthentication=yes" -o "PasswordAuthentication=no" -i /root/.ssh/id_rsa -R 24385:localhost:22 remote-ip.somewhere.org -l remoteuser &
For starting it I did:
cat /etc/rc.conf.d/autossh
autossh_enable="YES"
When I reboot the box, this script does not seem to be up. Did I miss something or might this be because there is no default gw yet at the stage where it gets triggered?
If so, is there any way I can let the script get executed once I have a WAN IP & GW?
#!/bin/sh
autossh -M 19984 -N -f -o "PubkeyAuthentication=yes" -o "PasswordAuthentication=no" -i /root/.ssh/id_rsa -R 24385:localhost:22 remote-ip.somewhere.org -l remoteuser &
For starting it I did:
cat /etc/rc.conf.d/autossh
autossh_enable="YES"
When I reboot the box, this script does not seem to be up. Did I miss something or might this be because there is no default gw yet at the stage where it gets triggered?
If so, is there any way I can let the script get executed once I have a WAN IP & GW?
4
18.7 Legacy Series / Re: PPP & LTE cards: How to access AT commands once interface is up?
« on: October 31, 2018, 06:58:30 pm »
Thanks, I went through all the remaining devices (there are 4) but none of them seems to react on AT, I never get an OK back. Except the one I configured as device, which is obviously busy now.
Any other ideas?
Any other ideas?
5
18.7 Legacy Series / PPP & LTE cards: How to access AT commands once interface is up?
« on: September 30, 2018, 12:41:32 pm »
I'm setting up a PC Engines based GW for my second home in Asia, which will run on LTE connection. So far so good, I seem to get an IP and now I start playing with my Sierra Wireless card to figure out how to optimize it.
Main issue I have is that as soon as my PPP connection is up, I cannot connect to /dev/cuaU0.2 anymore, as the device is busy. Is there a way that the PPP connection can be up but at the same time I can check & change stuff on my PPP card using specific AT commands? In particular I want to figure out on what LTE band I am, what the antenna settings are etc. All stuff I can do as long as the PPP connection is not up.
Also I did not really figure out what process is doing the PPP connection in OPNsense, how/where is that done?
Main issue I have is that as soon as my PPP connection is up, I cannot connect to /dev/cuaU0.2 anymore, as the device is busy. Is there a way that the PPP connection can be up but at the same time I can check & change stuff on my PPP card using specific AT commands? In particular I want to figure out on what LTE band I am, what the antenna settings are etc. All stuff I can do as long as the PPP connection is not up.
Also I did not really figure out what process is doing the PPP connection in OPNsense, how/where is that done?
6
Hardware and Performance / [HOWTO] Installing 17.7 (and probably above) on APU2/APU3 boards & SD card
« on: January 20, 2018, 11:20:50 am »
It looks like there are some issues with installing current OPNsense on PC Engines APU2/APU3 boards on an SD card so I thought I will summarize what worked and what doesn't so others can save some time.
What does NOT work: I first tried to dd the NANO image directly to the SD card. While it does boot it screws up on the next reboot. As soon as I rebooted with a proper configuration I got tons of READ errors from the SD card very early in the boot process. Apparently something goes wrong with the disk layout and breaks the install.
This process was how I did it the past years since I started on PFsense and I guess many were used to this. It did work with OPNsense as well until recently.
How to install:
That's it, like this I did not had any problems booting from SD card anymore. Hope this works for everyone.
What does NOT work: I first tried to dd the NANO image directly to the SD card. While it does boot it screws up on the next reboot. As soon as I rebooted with a proper configuration I got tons of READ errors from the SD card very early in the boot process. Apparently something goes wrong with the disk layout and breaks the install.
This process was how I did it the past years since I started on PFsense and I guess many were used to this. It did work with OPNsense as well until recently.
How to install:
- Install the AMD64 "serial" image on an USB stick. dd is your friend
- Plug serial console to your device
- Put the USB stick into the USB port and boot. If it does not boot from the stick directly, press F10 in the beginning and choose USB
- Login with install user
- Plug your SD card and start the install process (guided worked fine for me)
- Select the SDHC card as target
- Select GPT/UEFI mode
- Finish install & reboot without USB stick
That's it, like this I did not had any problems booting from SD card anymore. Hope this works for everyone.
7
17.7 Legacy Series / Re: APU2C4 - Usage of the onboard LEDs
« on: January 20, 2018, 11:03:07 am »
FYI I created an issue and asked if the FreeBSD driver could be included in OPNsense:
https://github.com/opnsense/core/issues/2114
https://github.com/opnsense/core/issues/2114
Pages: [1]