Messages

up (what are the chances to get mitmproxy still in opnsense? I think it does really have unique feats others don't)

Surely there is something built-in to opnsense that can get the internet back without rebooting from within the GUI?

unfortunately not.

Didn't think I would have to cron a script to reboot as mentioned a few posts above.

you might look into finagling a cron script to restart the interface instead of rebooting the entire machine. these are the lines i use for just such an approach:

Code Select Expand


/usr/local/sbin/configctl interface linkup stop ue0
/usr/local/sbin/configctl interface reconfigure ue0
/usr/local/sbin/configctl interface linkup start ue0

don't let the naysayers poopoo the use of cron for something alternatively addressed with the likes of redis. until a redis plugin for opnsense gets closer to feature parity with CLI the amount of sorcery involved in making it work simply ain't worth the trouble.

still trying to do a similar cron job which looks nice: but every how much would you schedule that cron job?
Also I guess you would check first before throwing down and up the interface: how would/are you doing it? Best practices?
Still I really think this is a big negative/missing feature of the OPNsesne router, not to have it streamlined in the normal code.. and no I'm not thinking it should be something overkill like with a redis monitoring etc.. ;)

Hello BB,
thanks for answering!
I guess you meant System -> Gateways -> Configuration then edit the WAN_DHCP and make sure that the monitoring is not disabled (so no checkbox on Disable Gateway Monitoring): I checked and it is not disabled/checked so that seems not to be a solution to the problem.
Actually what happens when he loses the interface is that the values of RTT/RTTd/Loss are empty and even when the interface comes back the values stay blank (I guess because he does not automatically redo a dhcp client request)..
Bummer..

Kr,
tent:wq

up (any solution to this? can we file a bugzilla/bug request or RFE to solve this automatically in future versions of OPNsense? I see really many threads about this, or is there a specific reason this should not be implemented?

If you configure your android to go automatically into usb tether mode (you have to enable first developer mode, and then you'll find it under the default usb mode) as soon as you plug it to the opnsense it will show up as an "ue0" interface..

so any suggestions about how you did (or you would best suggest) to implement an automatic "sudo dhclient ue0" then?
I hope into something better than a crontab running it every 5 minutes.. :D
Actually I would dream to have this by default in the OS TBH...

tent:wq

I have the same issue, not as frequently, but sometimes I even want to quickly disconnect the android from usb and then reconnect it again and would definitely expect the interface to come up and get new IP via dhcp again AUTOMATICALLY.. any suggestions about how to get this done in an intelligent way as the GUI does not offer this option?

I also saw this previous post on previous version that shows similar issue that annoys others as well: https://forum.opnsense.org/index.php?topic=33533.0

(BTW the command that seems to be suggested there does definitely not work ("sudo configctl interface reconfigure 5" what instead works for me ist a "sudo dhclient ue0" on the console or pressing reload icon on the interface, but seriously? ;))

Kr,
tent:wq