On Fri, Feb 20, 2015 at 9:31 AM, James B. Byrne
wrote:
>
> On Thu, February 19, 2015 12:33, Les Mikesell wrote:
> > On Thu, Feb 19, 2015 at 9:48 AM, James B. Byrne
> > wrote:
> >>
> >>> I added these directives to the route-eth0:192 file:
> >>>
> >>> ADDRESS0=192.168.6.9
> >>> NETMASK0=255.255.2
On Thu, February 19, 2015 12:33, Les Mikesell wrote:
> On Thu, Feb 19, 2015 at 9:48 AM, James B. Byrne
> wrote:
>>
>>> I added these directives to the route-eth0:192 file:
>>>
>>> ADDRESS0=192.168.6.9
>>> NETMASK0=255.255.255.0
>>> GATEWAY0=192.168.6.1
>>>
>>
>> Which should have been:
>>
>> ADDR
On Thu, Feb 19, 2015 at 9:48 AM, James B. Byrne wrote:
>
>> I added these directives to the route-eth0:192 file:
>>
>> ADDRESS0=192.168.6.9
>> NETMASK0=255.255.255.0
>> GATEWAY0=192.168.6.1
>>
>
> Which should have been:
>
> ADDRESS0=192.168.6.0
>
> NETMASK0=255.255.255.0
> GATEWAY0=192.168.6.1
>
On Thu, February 19, 2015 10:19, James B. Byrne wrote:
>
> I added these directives to the route-eth0:192 file:
>
> ADDRESS0=192.168.6.9
> NETMASK0=255.255.255.0
> GATEWAY0=192.168.6.1
>
Which should have been:
ADDRESS0=192.168.6.0
NETMASK0=255.255.255.0
GATEWAY0=192.168.6.1
Sigh.
--
***
On Wed, February 18, 2015 13:07, Les Mikesell wrote:
> On Wed, Feb 18, 2015 at 11:39 AM, James B. Byrne
> wrote:
>> 2. How does one configure the routing table on network startup to
>> specifically detail the route particular addresses are supposed to
>> take?
>>
>
> Not exactly sure how routing
On Thu, Feb 19, 2015 at 9:19 AM, James B. Byrne wrote:
>
> On Wed, February 18, 2015 13:07, Les Mikesell wrote:
>> On Wed, Feb 18, 2015 at 11:39 AM, James B. Byrne
>> wrote:
>>> 2. How does one configure the routing table on network startup to
>>> specifically detail the route particular addresse
Hi James,
Antonio is correct. The default address is used when the destination address
is not on a subnet that is on one of your local interfaces.
Any packet destined for an address on the 192.168.6.0/24 subnet will
automatically be sent with a source
address of 192.168.6.1
Same with any packe
On Wed, Feb 18, 2015 at 11:39 AM, James B. Byrne wrote:
>
> We have a host that has multiple IPv4 addresses aliased to eth0. The
> primary address is 216.185.71.x and the alias is 192.168.6.x.
>
> This host connects to devices on both netblocks without problems.
> Only default routing is used an
Hi James,
Simply remove the GATEWAY line from the eth0:192 interface config :D
Then you'll had only one default gateway. And the source IP to all unknown
address
will be the routeable one.
Att.,
Antonio.
- "James B. Byrne" escreveu:
> De: "James B. Byrne"
> Para: centos
9 matches
Mail list logo