Search found 26 matches
- 2017/01/31 11:42:50
- Forum: CentOS 7 - Security Support
- Topic: Reboot fails after yum upgrade on 20-Dec
- Replies: 4
- Views: 2268
Re: Reboot fails after yum upgrade on 20-Dec
I have the same issue. I have Centos installed on Amazon EC and after the latest update I couldn't login to my instance. After some work I managed to track the problem to firewalld. So I chrooted and disabled firewalld services. Now I can connect but I am not happy to have firewalld disabled. My pro...
- 2016/10/03 10:42:17
- Forum: CentOS 7 - Networking Support
- Topic: Returning traffic through the same NIC
- Replies: 3
- Views: 1178
Re: Returning traffic through the same NIC
I have been struggling with this problem for 2 weeks now. I monitor packets with tcpdump and I simply fail to understand what is wrong. I set GW1 as default gateway, which is assigned to NIC1. All traffic through NIC1 is working correctly. All incoming traffic to NIC2 should also be forwarded to int...
- 2016/09/21 08:58:28
- Forum: CentOS 7 - Networking Support
- Topic: Returning traffic through the same NIC
- Replies: 3
- Views: 1178
Re: Returning traffic through the same NIC
Yes! It is partially working. Here is my setup: ip route show table 1 default via <GW1> dev ens1 <IPRANGE-NIC1> dev ens1 scope link src <IP-NIC1> ip route show table 2 default via <GW2> dev ens2 <IPRANGE-NIC2> dev ens2 scope link src <IP-NIC2> ip route show default via <GW1> dev ens2 proto static me...
- 2016/09/21 08:13:18
- Forum: CentOS 7 - Networking Support
- Topic: Configure 2 NIC's same gateway
- Replies: 4
- Views: 2093
Re: Configure 2 NIC's same gateway
Maybe someone knows more on this issue. But my CentOS doesn't read the eth-xxx files either. Took me a while to figure out that after every restart no custom routing policies were active. From my googling I haven't seen any other possible solution, but the one with the network manager module: http:/...
- 2016/09/20 19:30:41
- Forum: CentOS 7 - Networking Support
- Topic: Returning traffic through the same NIC
- Replies: 3
- Views: 1178
Returning traffic through the same NIC
Hello, I have a server with 3 NICs. NIC1: ISP1 GW1 NIC2: ISP2 GW2 NIC3: Intranet I am unable to get traffic to return through the same NIC. Let's take the case of NIC2. I have used policy routing as such: table 2 default via <GW2> dev ens1 src <IP2> default via <GW2> dev ens1 proto static metric 100...
- 2016/09/20 15:59:06
- Forum: CentOS 7 - Networking Support
- Topic: Configure 2 NIC's same gateway
- Replies: 4
- Views: 2093
Re: Configure 2 NIC's same gateway
I think this is the solution:
http://jensd.be/468/linux/two-network-c ... ment-12887
http://jensd.be/468/linux/two-network-c ... ment-12887
- 2016/09/20 12:37:39
- Forum: CentOS 7 - Networking Support
- Topic: Configure 2 NIC's same gateway
- Replies: 4
- Views: 2093
Re: Configure 2 NIC's same gateway
you need to write your route configs in route-ethx and rule-ethx placed in networking scripts.
In my case it takes the route-ethx files but not the rule-ethx files.
Maybe use a script to run at startup with rc.local ?
In my case it takes the route-ethx files but not the rule-ethx files.
Maybe use a script to run at startup with rc.local ?
- 2016/09/19 14:42:17
- Forum: CentOS 7 - Networking Support
- Topic: IP Forwarding gone wrong
- Replies: 7
- Views: 2534
Re: IP Forwarding gone wrong
Hello everyone.
I solved the problem with the following rules:
I solved the problem with the following rules:
- 2016/09/16 17:24:09
- Forum: CentOS 7 - Networking Support
- Topic: IP Forwarding gone wrong
- Replies: 7
- Views: 2534
Re: IP Forwarding gone wrong
I know. That's why I am replacing the router with a CentOS server. Normally I wouldn't need this. But I have an application on my employees phones that needs to work both when they are on my wireless network and while they are at home. The application connects to a server inside the network mentione...
- 2016/09/16 13:03:11
- Forum: CentOS 7 - Networking Support
- Topic: IP Forwarding gone wrong
- Replies: 7
- Views: 2534
Re: IP Forwarding gone wrong
It did help in the sense that I tried to use just PREROUTING to achieve my goal, unfortunately the result is the same as yesterday. I can't route back to my internal IP . I've been googling for 2 days trying to find a solution. So again: Internal network has internet access over 80/443 = Yes Outside...