OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 17.7 Legacy Series »
  • Update, Ping, and Trace Route are using the LoopBack port
« previous next »
  • Print
Pages: [1]

Author Topic: Update, Ping, and Trace Route are using the LoopBack port  (Read 2944 times)

Rinval86

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
    • View Profile
Update, Ping, and Trace Route are using the LoopBack port
« on: October 09, 2017, 08:40:48 pm »
Hello and Thank you in advance.

I am completely new to OPNsense, IE this is my first install. I have previously used Pfsense (Until hardware failure.) I was hearing OPNsense 17.7 is more secure and such. I am very happy so far with setup and overall ease of use of the web interface. I have found a few minor things such as creating a firewall rule to allow access to the firewall remotely and allow the firewall to ping.

I have found 3 issues that seem to be related but I cannot seem to figure out what is wrong.  So, what is happening is that whenever I run a trace route from Shell or the WUI, all hops are the loopback port. Pinging shows the IP is resolved but uses the Loopback port to ping... Also, when I try to update or download the package list it fails stating it cannot reach the host, and it would seem a file is missing. I am sure they are related somehow and probably due to a missing route or firewall issue, but I cannot seem to find any faults or help on this issue.


WUI


PING mirrors.nycbug.org (66.111.2.15): 56 data bytes
36 bytes from localhost (127.0.0.1): Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 0054 19cd   0 0000  01  01 9ab5 192.168.0.1  66.111.2.15


traceroute to mirrors.nycbug.org (66.111.2.15), 18 hops max, 40 byte packets
 1  * 127.0.0.1  0.044 ms  0.036 ms
 2  127.0.0.1  0.039 ms  0.045 ms  0.023 ms
 3  127.0.0.1  0.024 ms  0.026 ms  0.024 ms



SHELL



root@.....:~ # ping mirrors.nycbug.org
PING mirrors.nycbug.org (66.111.2.15): 56 data bytes
36 bytes from localhost (127.0.0.1): Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 0054 8e4c   0 0000  01  01 2636 192.168.0.1  66.111.2.15



root@.....:~ # traceroute mirrors.nycbug.org
traceroute to mirrors.nycbug.org (66.111.2.15), 64 hops max, 40 byte packets
 1  localhost (127.0.0.1)  0.220 ms  0.023 ms  0.019 ms
 2  localhost (127.0.0.1)  0.025 ms  0.022 ms  0.021 ms



Enter an option: 12

This will automatically fetch all available updates, apply them,
and reboot if necessary.

Proceed with this action? [y/N]: y

Updating OPNsense repository catalogue...
pkg-static: Repository OPNsense load error: access repo file(/var/db/pkg/repo-OPNsense.sqlite) failed: No such file or directory
pkg-static: http://mirrors.nycbug.org/pub/opnsense/FreeBSD:11:amd64/17.7/latest/meta.txz: No route to host
repository OPNsense has no meta file, using default settings
pkg-static: http://mirrors.nycbug.org/pub/opnsense/FreeBSD:11:amd64/17.7/latest/packagesite.txz: No route to host
Unable to update repository OPNsense
Error updating repositories!
A firmware update is currently in progress.

Any help on this would be greatly appreciated.
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13671
  • Karma: 1175
    • View Profile
Re: Update, Ping, and Trace Route are using the LoopBack port
« Reply #1 on: October 09, 2017, 11:20:32 pm »
Do you use the captive portal, web proxy or multi-wan?

Either this, or your DNS is resolved weirdly.


Cheers,
Franco
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 17.7 Legacy Series »
  • Update, Ping, and Trace Route are using the LoopBack port
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2