On 18/11/2015 22:35, Johnny Hughes wrote:
On 11/18/2015 09:51 AM, Eero Volotinen wrote:
strace -f -e open software_binary might help, but I have noticed that
Centos is not really 100% binary compatible in some cases.
CentOS Linux is not 100% bit for bit compatible with RHEL in ANY cases :)
Ce
On 19/11/2015 20:46, Alice Wonder wrote:
I assume you are using one of the boards described here?
http://www.intel.com/support/services/smartconnect/sb/CS-033108.htm
Nope
This is my server:
http://www.supermicro.com/products/system/1u/1028/sys-1028r-mctr.cfm
and this is my board:
http://ww
Hi
There is a Centos 7 up-to-date box with 2 interfaces, let's say
192.168.1.12 - enp2s0, 192.168.1.13 on enp3s0. Default gateway on enp2s0.
The gateway is pfsense, IP is 192.168.1.1 with 2 WAN connections
On the gateway the outgoing traffic is routed by source ip to different
WAN, 192.168.1
9.254.0.0/16 dev enp2s0 scope link metric 1002
>> 169.254.0.0/16 dev enp3s0 scope link metric 1003
>> 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.12
>> 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.13
--Regards
Ashishkumar S. Yada
On 09/08/2016 06:56, Anthony K wrote:
On 08/08/16 21:05, Levente Birta wrote:
But how can I add achieve this only with ip route command ... without
route?
Can I add this in any config files (ex: route-enp2s0)?
Hi Levente.
The iproute2 man page for each command is rather well documented on
On 09/08/2016 22:16, John R Pierce wrote:
On 8/9/2016 11:51 AM, Birta Levente wrote:
I do all this and working on LAN ... all traffic go in/out on the
proper interface ... the problem is when I try to access the internet
on the second interface
how do you try and access the 'internet on
On 09/08/2016 23:08, Gordon Messmer wrote:
On 08/09/2016 11:51 AM, Birta Levente wrote:
If I add "#route add default gw 192.168.1.1 dev enp3s0" all is good,
but cannot add that in route-iface file or with "ip route"
Are you using the "network" or the "NetworkManager" service to configure
On 09/08/2016 23:11, Gordon Messmer wrote:
On 08/09/2016 12:03 PM, John R Pierce wrote:
those are both the same network, and the default gateway is a global
thing. packets forwarded to 192.168.1.1 could use either 192.168.1.12
or .13, as they are all the same. in reality, they will use the fir
On 10/08/2016 15:28, Jonathan Billings wrote:
On Wed, Aug 10, 2016 at 09:29:15AM +0300, Levente Birta wrote:
I read the document again ... and this talk about accessing this multi-homed
host from the internet...
I have all this configured and working!
You say this is working because of the
On 10/08/2016 16:54, Anthony K wrote:
On 10/08/16 16:29, Levente Birta wrote:
And as I said this problem is resolved too ... I asked for another way
to achieve this
When you add a default gateway with:
route add default gw 192.168.1.1 dev enp3s0
you'll note that you now have 2 routes
10 matches
Mail list logo
