In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot.
Probably to play nicely with windows boxen. In Windows 2000+, if there
is no DHCP server available, an APIPA address (169.254.x.x) is
assigned.
Yep. RedHat 9 introduces zeroconf, which you need to disable if you
don&#
Around Mon,Jun 09 2003, at 07:59, MKlinke, wrote:
> On Monday 09 June 2003 18:28, Roger wrote:
> > Around Mon,Jun 09 2003, at 10:06, Nick White, wrote:
> > > In RedHat 9 the 169.254.0.0/16 gets added to the routing table on
> > > boot. Probably to play nicely with
, June 09, 2003 10:24 AM
To: [EMAIL PROTECTED]
Subject: Re: routing table
Nick White wrote:
>In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot.
>Probably to play nicely with windows boxen. In Windows 2000+, if there
>is no DHCP server available, an APIPA address (
On Monday 09 June 2003 18:28, Roger wrote:
> Around Mon,Jun 09 2003, at 10:06, Nick White, wrote:
> > In RedHat 9 the 169.254.0.0/16 gets added to the routing table on
> > boot. Probably to play nicely with windows boxen. In Windows
> > 2000+, if there is no DHCP serve
Around Mon,Jun 09 2003, at 10:06, Nick White, wrote:
> In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot.
> Probably to play nicely with windows boxen. In Windows 2000+, if there
> is no DHCP server available, an APIPA address (169.254.x.x) is assigned.
>
Not
Nick White wrote:
In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot.
Probably to play nicely with windows boxen. In Windows 2000+, if there
is no DHCP server available, an APIPA address (169.254.x.x) is assigned.
To stop RedHat from using it, try adding the following line to
In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot.
Probably to play nicely with windows boxen. In Windows 2000+, if there
is no DHCP server available, an APIPA address (169.254.x.x) is assigned.
To stop RedHat from using it, try adding the following line to
/etc/sysconfig
antonio wrote:
An additional clue:
in my office network that is very similar to my home network of my
previous message output of netstat .nr is:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
192.168.100.1 0.0.0.0
available internally).
Im a bit scared since last time I checked the routing table in one of my
boxes I found the following:
$ netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
192.168.0.0 0.0.0.0 255.255.255.0 U
xes, d-link broadband router, nfs to be available internally).
>
> Im a bit scared since last time I checked the routing table in one of my
> boxes I found the following:
> $ netstat -nr
> Kernel IP routing table
> Destination Gateway Genmask Flags
files. My question is: which are the immediate steps (for
an unexperienced user) to minimize security risks with this setting (two
boxes, d-link broadband router, nfs to be available internally).
Im a bit scared since last time I checked the routing table in one of my
boxes I found the following
I am currenlty running sendmail on red hat 7.3 and I am having difficulities with a change to the Domain routing table. I want sendmail to route to an internal server ( server X ) which we have setup and it is working properly. The problem we are running into is that we want to change the server
>Here's my routing table before ppp is initiated:
>
>$ netstat -rn
>Kernel IP routing table
>Destination GatewayGenmask Flags MSS Window irtt Iface
>192.168.1.100 0.0.0.0255.255.255.255 UH0 00 eth0
>192.168.1.0 0.0.0.02
ss is that after ppp is started, my hostname is changed
to that of the remote ppp interface.
Here's my routing table before ppp is initiated:
$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
192.168.1.100 0.0.0.0
14 matches
Mail list logo
