Messages

1

18.1 Legacy Series / Re: Cannot Access Internet from any network AFTER reboot.

« on: March 13, 2018, 03:57:12 am »

OK, I found the issue and it was right under my nose!

Under gateway management, the check box of "use this as a default gateway" was UNCHECKED.

That certainly can ruin a party!!!

Ty for the help!

/s/ Ms. Phoenix.

2

18.1 Legacy Series / Re: Cannot Access Internet from any network AFTER reboot.

« on: March 13, 2018, 03:42:17 am »

Unchecking "Shared Forwarding" and that did not help, I checked the default routes and I did not see a default gateway after all.

Why would it drop the default gateway after a reboot?

Just for clarity, my ISP (Cable Company) assigns me an internal 192.168.0.x/24 IP via DHCP but I am using 192.168.0.37 assigned manually and have the default gateway assigned (under gateway management) and still thinks there is no default route?

3

18.1 Legacy Series / Re: Cannot Access Internet from any network AFTER reboot.

« on: March 13, 2018, 03:08:40 am »

Default gateway is set, I checked and looks like "Shared Forwarding" is set as per the attached screen shot, so to confirm, this should be disabled or unchecked?

4

18.1 Legacy Series / Cannot Access Internet from any network AFTER reboot.

« on: March 11, 2018, 10:51:55 pm »

I am not sure what info you will need but here is the situation.

I am running opnsense 18.1.4, I took a snapshot (hosted on vmware 6.5) before making changes, I added a guest network for wifi, added traffic shaping and after the snapshot added a captive portal. Right now the internet routes perfectly fine, i can ping 4.2.2.2 from any of my vlans (I use trunking on a cisco switch and use vmware to deal with the vlans), if I reboot the opnsense firewall, no internet. I am able to revert to the snapshot and the internet and everything is fine until I reboot...

Here is a sample of a ping before and after reboot:

Before reboot:
64 bytes from 4.2.2.2: icmp_seq=28 ttl=56 time=870.099 ms
64 bytes from 4.2.2.2: icmp_seq=29 ttl=56 time=89.181 ms
64 bytes from 4.2.2.2: icmp_seq=30 ttl=56 time=23.127 ms
64 bytes from 4.2.2.2: icmp_seq=31 ttl=56 time=21.368 ms
64 bytes from 4.2.2.2: icmp_seq=32 ttl=56 time=22.556 ms
64 bytes from 4.2.2.2: icmp_seq=33 ttl=56 time=21.538 ms
64 bytes from 4.2.2.2: icmp_seq=34 ttl=56 time=21.103 ms
64 bytes from 4.2.2.2: icmp_seq=35 ttl=56 time=25.184 ms
64 bytes from 4.2.2.2: icmp_seq=36 ttl=56 time=25.058 ms

After Reboot:
36 bytes from opnsense-fw01.pmyers.local (192.168.99.1): Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 747c   0 0000  3f  01 dccb 192.168.99.181  4.2.2.2

Request timeout for icmp_seq 19
36 bytes from opnsense-fw01.pmyers.local (192.168.99.1): Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 eafa   0 0000  3f  01 664d 192.168.99.181  4.2.2.2

I even get a destination unreachable when I ping from the GUI to 4.2.2.2 from the WAN interface.

This does not make any sense to me at all.  Please let me know what logs and steps you would like me to take in order to resolve this issue.  Thank you in advance!

Edit: I can ping the opnsense LAN ip with out a problem.  The default gateway outside of my network is also ping-able. I would like to add also if I re-IP any interface the internet also goes down with the same issue...

Phoenix