WAN DHCP issue and one package

[franco]

Thanks, it would help to know your requirements of a vnstat plugin in terms of what you want to see implemented. We have a few talented contributors that pick up smaller bugs and feature requests so making the request formal on GitHub might speed up the development of said plugin.

[none]

Hi franco,

I am half the way to tell opnsense and 5501 won't match. I can't access the webgui now. I get:

Code: [Select]

last pid: 23672;  load averages:  2.06,  2.07,  2.07    up 2+01:35:32  16:40:11
44 processes:  3 running, 41 sleeping
CPU: 88.1% user,  0.0% nice,  9.0% system,  3.0% interrupt,  0.0% idle
Mem: 23M Active, 127M Inact, 47M Wired, 43M Buf, 273M Free
Swap:

  PID USERNAME    THR PRI NICE   SIZE    RES STATE    TIME    WCPU COMMAND
56865 root          1  76    0 13016K  6728K RUN     38:58  14.70% lighttpd
23421 root          1  52    0 30712K 18832K piperd   0:01   6.98% php
22415 root          1  20    0 11232K  2372K RUN      0:00   0.59% top
68862 root          1  21    0 10796K  2976K pause    0:00   0.29% csh
38802 root          1  20    0 10200K  1876K bpf      5:08   0.00% filterlog
46618 root          1  52    0 34792K 23080K accept   4:23   0.00% php-cgi
 1809 root          1  20    0 12040K  4144K select   3:48   0.00% miniupnpd
91538 root          1  52    0 34792K 21500K accept   3:01   0.00% php-cgi
61369 root          1  52    0 10432K  2048K wait     2:07   0.00% sh
29823 _dhcp         1  20    0 10160K  1940K select   1:40   0.00% dhclient
 5138 root          1  20    0 10140K  1892K select   1:37   0.00% syslogd
16831 unbound       1  20    0 25948K 14976K select   1:08   0.00% unbound
 9500 root          1  52    0 10432K  2048K wait     0:29   0.00% sh
74116 root          1  20    0 10020K  1880K select   0:28   0.00% radvd
  197 root          1  20    0 23744K 16300K accept   0:11   0.00% python2.7
 5951 root          1  20    0 10084K  1816K nanslp   0:02   0.00% cron
22498 dhcpd         1  20    0 16224K  9128K select   0:01   0.00% dhcpd

The internet is fine so far, but webui is inaccessible.

Are there any other users running this version on 5501-70 ?

thanks,

[weust]

Please explain to me why you even bother with running such an old piece of hardware.
It only has 512MB RAM in your model, which is known to have installation issues, so you having done that is impressive enough.

[none]

That's easy.

I have it. I have two ISP's and both combined sums 15Mbps. So why use a regular dlink, that is far too limited, and not use this ? It is stable and does all I need.

And to settle all, runs on less then 15W

no need to retire it so far.

[weust]

Apart from the issues you're having right now?
You can't even configure it because of the non-working webconfig.

[none]

Well,

last version was ok, this is a bug, I suppose, not a feature. So far, I like what I see here, and I am willing to give the stable final production release a try. Then I can decide.

There is always the option to run OpenBSD or FreeBSD native, vanilla version.

thanks,

[franco]

none, lighttpd is up, are you sure it's not a lockout issue? How are you accessing the GUI, HTTP or HTTPS? Do you see the root menu? Are you sure the boot went okay and wasn't OOM-killed?

I'm building a last test image for 15.7.9 later tonight.

[franco]

https://pkg.opnsense.org/snapshots/OPNsense-15.7.9-LibreSSL-nano-i386.img.bz2

I've said it in the other thread: last test release, based on 15.7.9.

Images for both amd64 and i386 will be available for 15.7.10. Thank you for your support and feedback so far.

[none]

Hi Franco,

when 15.7.10 will show up ? I can try it then. I have some issues on opnsense, as said, that makes things here unstable. My wife can't complaint more about her internet access

I have dns issues, as related on another topic, and these slowness and dhcp issues on main isp.

I tried to test the WebUI responsiveness on a faster machine, Pentium dual core 1.8GHz and around 4GB ram. As my extra NIC's were usb from Linksys, I could not go much far. The WebUI was faster, that's a good thing (something I expect from the slow soekris), but I couldn't get as far as have both ISP's running. All boot it made me reboot for nic assignment. So I got on a loop where all boot both nic's were re-detected. I don't have how to test them without those usb nic's. As this pc was just a test (I can't have it as firewall 24/7), this is off for some time now. I also noticed that the install media, from usb memstick, wouldn't see the usb nic's. They are detected after the install script starts, so I get just the onboard nic as option in the first install run. When I passed that, I never got to have the WAN interface again. Created interfaces from there are OPTx. I dunno if that messes up something and that led me to no stable usb nics after all (the nic drivers are fine, I used them in other scenarios fine).

Just to help a little here, I must say FreeBSD itself has issues here. Before usb nics were all UEx, when axe based nics were axe0, axe1 and so on, it was easier to use them. Once axe1, I remember them so keep that index. Now they keep swapping. Saw this on vanilla FreeBSD not too long ago, so I guess that's the culprit to every boot opnsense scripts get confused.

Well, I got back to the old FW so far, but I have two cf cards, one being the opnsense test one. Just need to known when I will try it again. Is a problem to use the old cfg file ?

thanks,

none

[franco]

Not a problem. I understand your concerns. Unbound is being worked on to be more stable, I just pushed a larger rework that needs more testing to get accepted for the stable version. I think that some of your USB nicks are not available on bootup because the kernel driver isn't loaded. That needs to be addressed in /boot/loader.conf. A lot of variables that make this hard to track and find a fix for. We have little time and a lot of priorities.

By all means try with 15.7.10 one more time when it's out and if it doesn't work you'll have to wait longer, maybe 16.1 to give it another go. Getting through this with us or spending a few times on waiting for issues to be tackled is the options you have.

Can only get better, right.


Cheers,
Franco

[none]

Hi franco,

just as feedback, I just installed 15.7.11, and apart from a dhcp disconnect (just as before) less then an hour after boot, the UI is has better responsiveness, the load is way lower (less then 1, by far):

Code: [Select]

12:51PM  up 59 mins, 1 user, load averages: 0.04, 0.10, 0.11
USER       TTY      FROM                      LOGIN@  IDLE WHAT
root       u0       -                        12:05PM     - w

even though I have the UI opened on browser.

I will test more, this is the first boot after 15.7.8, but so far is great news. I will follow-up news about dhcp and the vnstat, when possible.

thanks,

none

[none]

small update:

the dns issue still stands. The machines that use the alternate gw must use 8.8.8.8 dns :/

I will try changing to dns resolver and see.

thanks,

[franco]

DNS and DHCP issues may be related. Could it be that at some point the ISP drops the lease and the box won't bother picking a new one?

[none]

franco,

I don't know, but could be. I just need to renew dhcp and it is back again. That's on the main ISP. The other, dhcp/cable as well, never shows this behavior. That's odd.

[franco]

Indeed, do you renew via the GUI button on the interface status page or on the command line?