On 2014-11-04, trondd tro...@gmail.com wrote:
Doesn't the default route go to the egress interface?
No, it's the other way round.
On 2014-11-04, Jason Adams adams...@gmail.com wrote:
On 11/04/2014 11:52 AM, Ted Unangst wrote:
On Tue, Nov 04, 2014 at 11:21, Jason Adams wrote:
So can anyone point me to the settings where the sequence of bringing up
interfaces is controlled at
boot time? Or am I just going to have to set
That needs to go in a dhclient config file, you'll need different config
files for each interface and run dhclient from a hostname.if line like
!dhclient -c /etc/dhclient-nogw em0.
is it not enough to just append the following to /etc/dhclient.conf?:
interface em0 {
ignore routers;
}
On 2014/11/05 10:48, Stefan Olsson wrote:
That needs to go in a dhclient config file, you'll need different config
files for each interface and run dhclient from a hostname.if line like
!dhclient -c /etc/dhclient-nogw em0.
is it not enough to just append the following to
On 11/05/2014 07:48 AM, Stefan Olsson wrote:
That needs to go in a dhclient config file, you'll need different config
files for each interface and run dhclient from a hostname.if line like
!dhclient -c /etc/dhclient-nogw em0.
is it not enough to just append the following to
On 11/05/2014 12:30 AM, Stuart Henderson wrote:
This is a bit of an unusual setup though. Normally on a host which has both
internal and internet interfaces you would hardcode the address of the
internal one.
Agreed, its sort of odd.
Its an instrumentation polling machine, which runs periodic
Stefan Olsson schreef op 5-11-2014 om 16:48:
That needs to go in a dhclient config file, you'll need different config
files for each interface and run dhclient from a hostname.if line like
!dhclient -c /etc/dhclient-nogw em0.
is it not enough to just append the following to
On November 5, 2014 7:23:20 PM CET, Jason Adams adams...@gmail.com wrote:
On 11/05/2014 07:48 AM, Stefan Olsson wrote:
That needs to go in a dhclient config file, you'll need different
config
files for each interface and run dhclient from a hostname.if line
like
!dhclient -c /etc/dhclient-nogw
On Wed, Nov 05, 2014 at 01:23:20PM EST, Jason Adams wrote:
On 11/05/2014 07:48 AM, Stefan Olsson wrote:
is it not enough to just append the following to /etc/dhclient.conf?:
^
interface em0 {
ignore routers;
}
Newbie here...
Machine not intended to be a router, just to have two interfaced, one to local
lan, second to a
cable modem.
Both interfaces connected to networks which supply dhcp address. Both work.
Upon boot, both interfaces come up fine, but the default gateway gets set to my
lan network.
On Tue, Nov 04, 2014 at 11:21, Jason Adams wrote:
So can anyone point me to the settings where the sequence of bringing up
interfaces is controlled at
boot time? Or am I just going to have to set default gateway after it is
booted by something in
rc.local?
/etc/netstart executes hostname.*
On Tue, Nov 4, 2014 at 2:52 PM, Ted Unangst t...@tedunangst.com wrote:
On Tue, Nov 04, 2014 at 11:21, Jason Adams wrote:
So can anyone point me to the settings where the sequence of bringing up
interfaces is controlled at
boot time? Or am I just going to have to set default gateway after
On 11/04/2014 11:52 AM, Ted Unangst wrote:
On Tue, Nov 04, 2014 at 11:21, Jason Adams wrote:
So can anyone point me to the settings where the sequence of bringing up
interfaces is controlled at
boot time? Or am I just going to have to set default gateway after it is
booted by something in
13 matches
Mail list logo
