FF-RGB
/
ansible
4
2
Fork 1
Code Issues 3 Pull Requests Activity

ip_forwarding not enabled on eth0 #19

New Issue
Closed
opened 2020-01-22 22:13:46 +01:00 by moepman · 2 comments
moepman commented 2020-01-22 22:13:46 +01:00
Owner
Copy Link

Sometimes eth0 comes up without ip_forwarding enabled, while every other possible ip_forard setting (including default and all) is on enabled.

/proc/sys/net/ipv4/conf/all/forwarding:1
/proc/sys/net/ipv4/conf/bat-ffrgb_uml/forwarding:1
/proc/sys/net/ipv4/conf/br-ffrgb_uml/forwarding:1
/proc/sys/net/ipv4/conf/default/forwarding:1
/proc/sys/net/ipv4/conf/dmy-ffrgb_uml/forwarding:1
/proc/sys/net/ipv4/conf/erspan0/forwarding:1
/proc/sys/net/ipv4/conf/eth0/forwarding:0
/proc/sys/net/ipv4/conf/gre0/forwarding:1
/proc/sys/net/ipv4/conf/gretap0/forwarding:1
/proc/sys/net/ipv4/conf/lo/forwarding:1
/proc/sys/net/ipv4/conf/tun-gw11/forwarding:1
/proc/sys/net/ipv4/conf/tun-gw31/forwarding:1
/proc/sys/net/ipv4/conf/vpn-ffrgb_uml0/forwarding:1
/proc/sys/net/ipv4/conf/vpn-ffrgb_uml1/forwarding:1
/proc/sys/net/ipv4/conf/vpn-ffrgb_uml2/forwarding:1
Sometimes eth0 comes up without ip_forwarding enabled, while every other possible ip_forard setting (including default and all) is on enabled. ``` /proc/sys/net/ipv4/conf/all/forwarding:1 /proc/sys/net/ipv4/conf/bat-ffrgb_uml/forwarding:1 /proc/sys/net/ipv4/conf/br-ffrgb_uml/forwarding:1 /proc/sys/net/ipv4/conf/default/forwarding:1 /proc/sys/net/ipv4/conf/dmy-ffrgb_uml/forwarding:1 /proc/sys/net/ipv4/conf/erspan0/forwarding:1 /proc/sys/net/ipv4/conf/eth0/forwarding:0 /proc/sys/net/ipv4/conf/gre0/forwarding:1 /proc/sys/net/ipv4/conf/gretap0/forwarding:1 /proc/sys/net/ipv4/conf/lo/forwarding:1 /proc/sys/net/ipv4/conf/tun-gw11/forwarding:1 /proc/sys/net/ipv4/conf/tun-gw31/forwarding:1 /proc/sys/net/ipv4/conf/vpn-ffrgb_uml0/forwarding:1 /proc/sys/net/ipv4/conf/vpn-ffrgb_uml1/forwarding:1 /proc/sys/net/ipv4/conf/vpn-ffrgb_uml2/forwarding:1 ```
moepman commented 2020-06-19 21:19:49 +02:00
Author
Owner
Copy Link

Upstream issue: https://github.com/CumulusNetworks/ifupdown2/issues/98

Upstream issue: https://github.com/CumulusNetworks/ifupdown2/issues/98
moepman commented 2020-11-13 11:55:25 +01:00
Author
Owner
Copy Link

Fixed by b239dfb38f

Fixed by b239dfb38f315e32faf9624db061024ddb9f8347
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
yanicfix-statserver
ntp-chrony-proposal
netbox-proposal
Labels
Clear labels   
bug

   
duplicate

   
enhancement

   
help wanted

   
invalid

   
question

   
wontfix
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FF-RGB/ansible#19
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?