Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

system: get_interface_gateway unable to find existing but unassigned gateways #2914

Closed
ccesario opened this issue Nov 14, 2018 · 11 comments
Closed

system: get_interface_gateway unable to find existing but unassigned gateways #2914

ccesario opened this issue Nov 14, 2018 · 11 comments
Assignees
@fichtner
Labels
bug Production bug
Milestone
19.1

Comments

@ccesario
Copy link

Hi,

It seems that versions 18.7.6 and 18.7.7 are not creating automatic outbound rules.
I need create Manual Outbound Rules from LAN to WAN traffic works.

I have a 18.7.3 version that is working very well as expected.

https://forum.opnsense.org/index.php?topic=10183.0
@fichtner fichtner self-assigned this Nov 14, 2018
@fichtner fichtner added the bug Production bug label Nov 14, 2018
@fichtner fichtner added this to the 19.1 milestone Nov 14, 2018
@fichtner
Copy link
Member

Following our discussion in the forum I've been over code and change logs but could not see something sticking out. What I can say for sure is if it's not listed under auto it will not be created as it uses the same data source function in both places. Are you using something like the os-cache plugin? what is your wan setup like?

@ccesario
Copy link
Author

Hi @fichtner ,

  • Are you using something like the os-cache plugin? - No, none plugin or cache system.
  • What is your wan setup like? - In my tests, I have tested Static IP and DHCP.

And after upgrade from 18.7.3 to 18.7.7 my LAN hosts did not get internet accesss, after check the outbound rules, they were empty, I needed create a manual outbound rule to LAN hosts got internet access :)

I will try debug something and post here...

@fichtner
Copy link
Member

Could you give temporary access to the box via SSH, this will be easy to spot from there. I'm out of ideas otherwise. :( let me know via franco@opnsense.org

@ccesario
Copy link
Author

Hi Franco, thank you by your effort. I will deploy other appliance and restore the current appliance backup in this new and I send you the credentials by email.

@fichtner
Copy link
Member

@ccesario thanks!

@ccesario
Copy link
Author

Hi @fichtner ,
I sent you the email with data.

Thank you!

@fichtner
Copy link
Member

Hi Carlos,

Under WAN I set "IPv4 Upstream Gateway" to the actual gateway and it works as expected. The auto-detect doesn't seem to work here. I'll try to investigate why. It may be due to static configuration of WAN.

At least you can use your setups manually with this setting. :)

Cheers,
Franco

@fichtner
Copy link
Member

Found a better fix. Will not fit into 18.7.8 but should be in time for 18.7.9.

@fichtner fichtner changed the title Automatic outbound rules aren't created system: get_interface_gateway unable to find existing but unassigned gateways Nov 19, 2018
@ccesario
Copy link
Author

Hi Franco!
Thank you by excellent help!!!

Nice to know that found a fix!!!!

Best regards,

Carlos

fichtner added a commit that referenced this issue Nov 19, 2018
@fichtner
system: allow auto-detect of gateways in static IPv4 setup #2914
a66c8df 
A bit more weirdness here.  It's time for a larger rework...
fichtner added a commit that referenced this issue Nov 19, 2018
@fichtner
system: improve previous slightly #2914
94f49e3
fichtner added a commit that referenced this issue Nov 20, 2018
@fichtner
system: gateway lookup should honour disable flag #2914
f5d4c2b
fichtner added a commit that referenced this issue Nov 20, 2018
@fichtner
system: IPv6 static gateway lookup #2914
ca1a5fc
fichtner added a commit that referenced this issue Nov 20, 2018
@fichtner
system: switch default argument for return_gateways_status()
936a50b 
Loosely related to #2914, $byname = true seems to be the default
and not returning by name has little benefit.  Getting rid of the
argument in the next commit.
fichtner added a commit that referenced this issue Nov 20, 2018
@fichtner
system: simplify return_gateways_status() for #2914
6e4538d 
* Fill default values first before going through the monitors.
* Remove $byname = false, we can still look up the gateway.
* Avoid calling functions twice; remove spurious variables.
* Use stristr() where status is read to avoid mismatches.
* Kill 'srcip' and 'monitorip' weirdness.
fichtner added a commit that referenced this issue Nov 20, 2018
@fichtner
system: inline get_dpinger_status() #2914
90cd162 
Avoids a couple of calls and checks...
fichtner added a commit that referenced this issue Nov 20, 2018
@fichtner
system: switch default argument for return_gateways_status()
af954cf 
Loosely related to #2914, $byname = true seems to be the default
and not returning by name has little benefit.  Getting rid of the
argument in the next commit.

(cherry picked from commit 936a50b)
fichtner added a commit that referenced this issue Nov 21, 2018
@fichtner
system: fix clashing vars in previous function merge #2914 #2948
dd16e3d
@fichtner
Copy link
Member

should be good on the latest development release shipping with 18.7.8. Workaround possible so we'll try to pull smaller chunks into several 18.7.x until all is in 19.1 eventually. :)

@ccesario
Copy link
Author

Thank you @fichtner !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fichtner fichtner

Labels
bug Production bug
Milestone
19.1
Development

No branches or pull requests
2 participants
@ccesario @fichtner