devil-linux-discuss

[Devil-Linux-discuss] Devil Linux 1.2 doesn't load firewall rules at startup.

[Paolo S. <pao...@gm...>]

  Hi guys,
I have been using Devil Linux 1.2  since 2008.
It's configured to work as a Firewall, Dns, Dhcp and Vpn Server; until yesterday all was ok and  in particular Firewall  
loaded rules at start up too.
Now something is wrong; although firewall service is flagged to run at start up, it doesn't  work well. No one can use 
Internet, check mail and so on after a system reboot.
So i have to connect to devil linux server via ssh and run command ./firewall restart and all things begin to work well.
Any ideas, why ?

Kind  regards,
-- 

*Paolo Spizzirri*

Software Developer

Mobile: +39 349 7784465
Email: pao...@gm...

Re: [Devil-Linux-discuss] Devil Linux 1.2 doesn't load firewall rules at startup.

[Heiko Z. <he...@zu...>]

Maybe the symlinks for init got lost somehow.

What's the output of this command?

find /etc/init.d/ -name \*firewall

 

On my DL1.4 it looks like this:

/etc/init.d/firewall

/etc/init.d/rc3.d/K17firewall

/etc/init.d/rc3.d/S06firewall

/etc/init.d/rc5.d/K17firewall

/etc/init.d/rc5.d/S06firewall

 

Please keep in mind that the numbers are more than likely different.

If this is the root cause, then you should be able to fix it by
executing:

insserv -d /etc/init.d/firewall

 

Heiko

 

From: Paolo Spizzirri [mailto:pao...@gm...] 
Sent: Wednesday, September 15, 2010 5:16 AM
To: dev...@li...
Subject: [Devil-Linux-discuss] Devil Linux 1.2 doesn't load firewall
rules at startup.

 

Hi guys,
I have been using Devil Linux 1.2  since 2008.
It's configured to work as a Firewall, Dns, Dhcp and Vpn Server; until
yesterday all was ok and  in particular Firewall  loaded rules at start
up too.
Now something is wrong; although firewall service is flagged to run at
start up, it doesn't  work well. No one can use Internet, check mail and
so on after a system reboot.
So i have to connect to devil linux server via ssh and run command
./firewall restart and all things begin to work well.
Any ideas, why ?

Kind  regards,

-- 

Paolo Spizzirri

Software Developer

Mobile: +39 349 7784465
Email: pao...@gm...

Re: [Devil-Linux-discuss] Devil Linux 1.2 doesn't load firewall rules at startup.

[Paolo S. <pao...@gm...>]

  I checked the symlinks as you have suggested and they were all ok apparently. But the problem continued.
So i decided to look at the DL console during system reboot and i saw that the firewall service stopped because it 
didn't find tun0 interface defined in VPN Service.
The problem is that Firewall Service starts before VPN Service. I corrected the problem, changing the start up order.
I changed symlink K17firewall to K99firewall and S06firewall to S99firewall in /etc/init.d/rc3.d and /etc/init.d/rc5.d; 
so Firewall service should be the last one to be started up.
I made a test, rebooting the system and all was ok.

Thank you Heiko.

Kind  regards,

Paolo.



On 09/15/2010 02:41 PM, Heiko Zuerker wrote:
>
> Maybe the symlinks for init got lost somehow.
>
> What's the output of this command?
>
> find /etc/init.d/ -name \*firewall
>
> On my DL1.4 it looks like this:
>
> /etc/init.d/firewall
>
> /etc/init.d/rc3.d/K17firewall
>
> /etc/init.d/rc3.d/S06firewall
>
> /etc/init.d/rc5.d/K17firewall
>
> /etc/init.d/rc5.d/S06firewall
>
> Please keep in mind that the numbers are more than likely different.
>
> If this is the root cause, then you should be able to fix it by executing:
>
> insserv -d /etc/init.d/firewall
>
> Heiko
>
> *From:* Paolo Spizzirri [mailto:pao...@gm...]
> *Sent:* Wednesday, September 15, 2010 5:16 AM
> *To:* dev...@li...
> *Subject:* [Devil-Linux-discuss] Devil Linux 1.2 doesn't load firewall rules at startup.
>
> Hi guys,
> I have been using Devil Linux 1.2  since 2008.
> It's configured to work as a Firewall, Dns, Dhcp and Vpn Server; until yesterday all was ok and  in particular 
> Firewall  loaded rules at start up too.
> Now something is wrong; although firewall service is flagged to run at start up, it doesn't  work well. No one can use 
> Internet, check mail and so on after a system reboot.
> So i have to connect to devil linux server via ssh and run command ./firewall restart and all things begin to work well.
> Any ideas, why ?
>
> Kind  regards,
>
> -- 
>
> *Paolo Spizzirri*
>
> Software Developer
>
> Mobile: +39 349 7784465
> Email: pao...@gm... <mailto:pao...@gm...>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
>
>
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss


-- 

*Paolo Spizzirri*

Software Developer

Mobile: +39 349 7784465
Email: pao...@gm...

[Devil-Linux-discuss] devil-linux-1.4RC4 default gateway

[Bogdan P. <pet...@ya...>]

Hi all,

I just upgraded to devil-linux-1.4RC4. I have one small problem that I can't figure out though, may be someone here can help ...

After each boot the default route points to eth0 instead of ppp0. I have pppd configured to overwrite the default route, and I see the line saying "Starting ADSL connection" during the boot process but somehow the default gateway is not updated.

I can delete the default route and restart pppd to fix the issue, but I wonder if maybe there's a right way to do this somewhere in the config files. Any advice is welcome.

Best regards

--------------------------------

In the beginning there was nothing. Then, God said, "Let there be light". 

And there was still nothing, but at least you could see it.

--------------------------------




      

Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway

[Serge L. <ser...@gm...>]

Hi Bogdan,

May I ask you to post /etc/sysconfig/nic/ifcfg-eth0 config file and
/etc/sysconfig/ppp/pptpadsl.conf (if you use pptpadsl script)?

I'll try to simulate the case in my "home lab". Please remove login/password/etc
- I need only information about topology.

PS. I've modified network script significantly and most probably it's a side
effect of those changes.

Thank you,
Serge

On 09/19/2010 10:33 AM, Bogdan Petrisor wrote:
> Hi all,
> 
> I just upgraded to devil-linux-1.4RC4. I have one small problem that I
> can't figure out though, may be someone here can help ...
> 
> After each boot the default route points to eth0 instead of ppp0. I have
> pppd configured to overwrite the default route, and I see the line
> saying "Starting ADSL connection" during the boot process but somehow
> the default gateway is not updated.
> 
> I can delete the default route and restart pppd to fix the issue, but I
> wonder if maybe there's a right way to do this somewhere in the config
> files. Any advice is welcome.
> 
> Best regards
> 
> --------------------------------
> In the beginning there was nothing. Then, God said, "Let there be light".
> And there was still nothing, but at least you could see it.
> --------------------------------
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> 
> 
> 
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway

[Bogdan P. <pet...@ya...>]

Hi Serge,

root@annuminas:~ # cat /etc/sysconfig/nic/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
MODULE="8139too"
DHCP=yes
IP=
NETMASK=
BROADCAST=""

I couldn't find a /etc/sysconfig/ppp/pptpadsl.conf. I found a /etc/ppp/pptpadsl.conf but I don't think it's used (it looks like a bunch of commented default values)

root@annuminas:~ # cat /etc/ppp/pptpadsl.conf 
#START_PPTPADSL=yes
#PPTPADSL_IP="10.0.0.138"
#PPTPADSL_USER="username@IProvider"
#PPTPADSL_REMOTENAME="10.0.0.138 RELAY_PPP1"
#PPTPADSL_PASSWORD="password"
#PPTPADSL_MTU="1452"
#PPTPADSL_FLAGS=

To start ADSL the gateway seems to use /etc/init.d/adsl, which calls pppoe-start and pppoe-stop. I'll paste the relevant config file, and hope the mails is not too long:

root@annuminas:~ # cat /etc/ppp/pppoe.conf
#***********************************************************************
#
# pppoe.conf
#
# Configuration file for rp-pppoe.  Edit as appropriate and install in
# /etc/ppp/pppoe.conf
#
# NOTE: This file is used by the pppoe-start, pppoe-stop, pppoe-connect and
#       pppoe-status shell scripts.  It is *not* used in any way by the
#       "pppoe" executable.
#
# Copyright (C) 2000 Roaring Penguin Software Inc.
#
# This file may be distributed under the terms of the GNU General
# Public License.
#
# LIC: GPL
# $Id: pppoe.conf,v 1.11 2005/08/09 02:49:12 dfs Exp $
#***********************************************************************

# When you configure a variable, DO NOT leave spaces around the "=" sign.

# Ethernet card connected to DSL modem
ETH='eth0'

# PPPoE user name.  You may have to supply "@provider.com"  Sympatico
# users in Canada do need to include "@sympatico.ca"
# Sympatico uses PAP authentication.  Make sure /etc/ppp/pap-secrets
# contains the right username/password combination.
# For Magma, use xx...@ma...
USER='me@mydslprovider'

# Bring link up on demand?  Default is to leave link up all the time.
# If you want the link to come up on demand, set DEMAND to a number indicating
# the idle time after which the link is brought down.
DEMAND=no
#DEMAND=300

# DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2;
# NOCHANGE=do not adjust.
DNSTYPE=SERVER

# Obtain DNS server addresses from the peer (recent versions of pppd only)
# In old config files, this used to be called USEPEERDNS.  Changed to
# PEERDNS for better Red Hat compatibility
PEERDNS=yes

DNS1=
DNS2=

# Make the PPPoE connection your default route.  Set to
# DEFAULTROUTE=no if you don't want this.
DEFAULTROUTE=yes

### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT

# How long pppoe-start waits for a new PPP interface to appear before
# concluding something went wrong.  If you use 0, then pppoe-start
# exits immediately with a successful status and does not wait for the
# link to come up.  Time is in seconds.
#
# WARNING WARNING WARNING:
#
# If you are using rp-pppoe on a physically-inaccessible host, set
# CONNECT_TIMEOUT to 0.  This makes SURE that the machine keeps trying
# to connect forever after pppoe-start is called.  Otherwise, it will
# give out after CONNECT_TIMEOUT seconds and will not attempt to
# connect again, making it impossible to reach.
CONNECT_TIMEOUT=30

# How often in seconds pppoe-start polls to check if link is up
CONNECT_POLL=2

# Specific desired AC Name
ACNAME=

# Specific desired service name
SERVICENAME=

# Character to echo at each poll.  Use PING="" if you don't want
# anything echoed
PING="."

# File where the pppoe-connect script writes its process-ID.
# Three files are actually used:
#   $PIDFILE       contains PID of pppoe-connect script
#   $PIDFILE.pppoe contains PID of pppoe process
#   $PIDFILE.pppd  contains PID of pppd process
CF_BASE=`basename $CONFIG`
PIDFILE="/var/run/$CF_BASE-pppoe.pid"

# Do you want to use synchronous PPP?  "yes" or "no".  "yes" is much
# easier on CPU usage, but may not work for you.  It is safer to use
# "no", but you may want to experiment with "yes".  "yes" is generally
# safe on Linux machines with the n_hdlc line discipline; unsafe on others.
SYNCHRONOUS=no

# Do you want to clamp the MSS?  Here's how to decide:
# - If you have only a SINGLE computer connected to the DSL modem, choose
#   "no".
# - If you have a computer acting as a gateway for a LAN, choose "1412".
#   The setting of 1412 is safe for either setup, but uses slightly more
#   CPU power.
CLAMPMSS=1412
#CLAMPMSS=no

# LCP echo interval and failure count.
LCP_INTERVAL=20
LCP_FAILURE=3

# PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
PPPOE_TIMEOUT=80

# Firewalling: One of NONE, STANDALONE or MASQUERADE
FIREWALL=NONE

# Linux kernel-mode plugin for pppd.  If you want to try the kernel-mode
# plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
LINUX_PLUGIN=

# Any extra arguments to pass to pppoe.  Normally, use a blank string
# like this:
PPPOE_EXTRA=""

# Rumour has it that "Citizen's Communications" with a 3Com
# HomeConnect DSL Modem DualLink requires these extra options:
# PPPOE_EXTRA="-f 3c12:3c13 -S ISP"

# Any extra arguments to pass to pppd.  Normally, use a blank string
# like this:
PPPD_EXTRA=""


########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
# If you wish to COMPLETELY overrride the pppd invocation:
# Example:
# OVERRIDE_PPPD_COMMAND="pppd call dsl"

# If you want pppoe-connect to exit when connection drops:
# RETRY_ON_FAILURE=no

--------------------------------
In the beginning there was nothing. Then, God said, "Let there be light". 
And there was still nothing, but at least you could see it.
--------------------------------




--- On Sun, 9/19/10, Serge Leschinsky <ser...@gm...> wrote:

> From: Serge Leschinsky <ser...@gm...>
> Subject: Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway
> To: dev...@li...
> Date: Sunday, September 19, 2010, 3:35 PM
> Hi Bogdan,
> 
> May I ask you to post /etc/sysconfig/nic/ifcfg-eth0 config
> file and
> /etc/sysconfig/ppp/pptpadsl.conf (if you use pptpadsl
> script)?
> 
> I'll try to simulate the case in my "home lab". Please
> remove login/password/etc
> - I need only information about topology.
> 
> PS. I've modified network script significantly and most
> probably it's a side
> effect of those changes.
> 
> Thank you,
> Serge
> 
> On 09/19/2010 10:33 AM, Bogdan Petrisor wrote:
> > Hi all,
> > 
> > I just upgraded to devil-linux-1.4RC4. I have one
> small problem that I
> > can't figure out though, may be someone here can help
> ...
> > 
> > After each boot the default route points to eth0
> instead of ppp0. I have
> > pppd configured to overwrite the default route, and I
> see the line
> > saying "Starting ADSL connection" during the boot
> process but somehow
> > the default gateway is not updated.
> > 
> > I can delete the default route and restart pppd to fix
> the issue, but I
> > wonder if maybe there's a right way to do this
> somewhere in the config
> > files. Any advice is welcome.
> > 
> > Best regards
> > 
> > --------------------------------
> > In the beginning there was nothing. Then, God said,
> "Let there be light".
> > And there was still nothing, but at least you could
> see it.
> > --------------------------------
> > 
> > 
> > 
> > 
> >
> ------------------------------------------------------------------------------
> > Start uncovering the many advantages of virtual
> appliances
> > and start using them to simplify application
> deployment and
> > accelerate your shift to cloud computing.
> > http://p.sf.net/sfu/novell-sfdev2dev
> > 
> > 
> > 
> > _______________________________________________
> > Devil-linux-discuss mailing list
> > Dev...@li...
> > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> 
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment
> and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> 


      

Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway

[Serge L. <ser...@gm...>]

Bogdan.

OK, thank you. I see you use pppoe but not pptp as I assumed. I'll bring pppoe
server up and try your configs.

Serge


On 09/19/2010 08:15 PM, Bogdan Petrisor wrote:
> Hi Serge,
> 
> root@annuminas:~ # cat /etc/sysconfig/nic/ifcfg-eth0
> DEVICE=eth0
> ONBOOT=yes
> MODULE="8139too"
> DHCP=yes
> IP=
> NETMASK=
> BROADCAST=""
> 
> I couldn't find a /etc/sysconfig/ppp/pptpadsl.conf. I found a /etc/ppp/pptpadsl.conf but I don't think it's used (it looks like a bunch of commented default values)
> 
> root@annuminas:~ # cat /etc/ppp/pptpadsl.conf 
> #START_PPTPADSL=yes
> #PPTPADSL_IP="10.0.0.138"
> #PPTPADSL_USER="username@IProvider"
> #PPTPADSL_REMOTENAME="10.0.0.138 RELAY_PPP1"
> #PPTPADSL_PASSWORD="password"
> #PPTPADSL_MTU="1452"
> #PPTPADSL_FLAGS=
> 
> To start ADSL the gateway seems to use /etc/init.d/adsl, which calls pppoe-start and pppoe-stop. I'll paste the relevant config file, and hope the mails is not too long:
> 
> root@annuminas:~ # cat /etc/ppp/pppoe.conf
> #***********************************************************************
> #
> # pppoe.conf
> #
> # Configuration file for rp-pppoe.  Edit as appropriate and install in
> # /etc/ppp/pppoe.conf
> #
> # NOTE: This file is used by the pppoe-start, pppoe-stop, pppoe-connect and
> #       pppoe-status shell scripts.  It is *not* used in any way by the
> #       "pppoe" executable.
> #
> # Copyright (C) 2000 Roaring Penguin Software Inc.
> #
> # This file may be distributed under the terms of the GNU General
> # Public License.
> #
> # LIC: GPL
> # $Id: pppoe.conf,v 1.11 2005/08/09 02:49:12 dfs Exp $
> #***********************************************************************
> 
> # When you configure a variable, DO NOT leave spaces around the "=" sign.
> 
> # Ethernet card connected to DSL modem
> ETH='eth0'
> 
> # PPPoE user name.  You may have to supply "@provider.com"  Sympatico
> # users in Canada do need to include "@sympatico.ca"
> # Sympatico uses PAP authentication.  Make sure /etc/ppp/pap-secrets
> # contains the right username/password combination.
> # For Magma, use xx...@ma...
> USER='me@mydslprovider'
> 
> # Bring link up on demand?  Default is to leave link up all the time.
> # If you want the link to come up on demand, set DEMAND to a number indicating
> # the idle time after which the link is brought down.
> DEMAND=no
> #DEMAND=300
> 
> # DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2;
> # NOCHANGE=do not adjust.
> DNSTYPE=SERVER
> 
> # Obtain DNS server addresses from the peer (recent versions of pppd only)
> # In old config files, this used to be called USEPEERDNS.  Changed to
> # PEERDNS for better Red Hat compatibility
> PEERDNS=yes
> 
> DNS1=
> DNS2=
> 
> # Make the PPPoE connection your default route.  Set to
> # DEFAULTROUTE=no if you don't want this.
> DEFAULTROUTE=yes
> 
> ### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT
> 
> # How long pppoe-start waits for a new PPP interface to appear before
> # concluding something went wrong.  If you use 0, then pppoe-start
> # exits immediately with a successful status and does not wait for the
> # link to come up.  Time is in seconds.
> #
> # WARNING WARNING WARNING:
> #
> # If you are using rp-pppoe on a physically-inaccessible host, set
> # CONNECT_TIMEOUT to 0.  This makes SURE that the machine keeps trying
> # to connect forever after pppoe-start is called.  Otherwise, it will
> # give out after CONNECT_TIMEOUT seconds and will not attempt to
> # connect again, making it impossible to reach.
> CONNECT_TIMEOUT=30
> 
> # How often in seconds pppoe-start polls to check if link is up
> CONNECT_POLL=2
> 
> # Specific desired AC Name
> ACNAME=
> 
> # Specific desired service name
> SERVICENAME=
> 
> # Character to echo at each poll.  Use PING="" if you don't want
> # anything echoed
> PING="."
> 
> # File where the pppoe-connect script writes its process-ID.
> # Three files are actually used:
> #   $PIDFILE       contains PID of pppoe-connect script
> #   $PIDFILE.pppoe contains PID of pppoe process
> #   $PIDFILE.pppd  contains PID of pppd process
> CF_BASE=`basename $CONFIG`
> PIDFILE="/var/run/$CF_BASE-pppoe.pid"
> 
> # Do you want to use synchronous PPP?  "yes" or "no".  "yes" is much
> # easier on CPU usage, but may not work for you.  It is safer to use
> # "no", but you may want to experiment with "yes".  "yes" is generally
> # safe on Linux machines with the n_hdlc line discipline; unsafe on others.
> SYNCHRONOUS=no
> 
> # Do you want to clamp the MSS?  Here's how to decide:
> # - If you have only a SINGLE computer connected to the DSL modem, choose
> #   "no".
> # - If you have a computer acting as a gateway for a LAN, choose "1412".
> #   The setting of 1412 is safe for either setup, but uses slightly more
> #   CPU power.
> CLAMPMSS=1412
> #CLAMPMSS=no
> 
> # LCP echo interval and failure count.
> LCP_INTERVAL=20
> LCP_FAILURE=3
> 
> # PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
> PPPOE_TIMEOUT=80
> 
> # Firewalling: One of NONE, STANDALONE or MASQUERADE
> FIREWALL=NONE
> 
> # Linux kernel-mode plugin for pppd.  If you want to try the kernel-mode
> # plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
> LINUX_PLUGIN=
> 
> # Any extra arguments to pass to pppoe.  Normally, use a blank string
> # like this:
> PPPOE_EXTRA=""
> 
> # Rumour has it that "Citizen's Communications" with a 3Com
> # HomeConnect DSL Modem DualLink requires these extra options:
> # PPPOE_EXTRA="-f 3c12:3c13 -S ISP"
> 
> # Any extra arguments to pass to pppd.  Normally, use a blank string
> # like this:
> PPPD_EXTRA=""
> 
> 
> ########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
> # If you wish to COMPLETELY overrride the pppd invocation:
> # Example:
> # OVERRIDE_PPPD_COMMAND="pppd call dsl"
> 
> # If you want pppoe-connect to exit when connection drops:
> # RETRY_ON_FAILURE=no
> 
> --------------------------------
> In the beginning there was nothing. Then, God said, "Let there be light". 
> And there was still nothing, but at least you could see it.
> --------------------------------
> 
> 
> 
> 
> --- On Sun, 9/19/10, Serge Leschinsky <ser...@gm...> wrote:
> 
>> From: Serge Leschinsky <ser...@gm...>
>> Subject: Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway
>> To: dev...@li...
>> Date: Sunday, September 19, 2010, 3:35 PM
>> Hi Bogdan,
>>
>> May I ask you to post /etc/sysconfig/nic/ifcfg-eth0 config
>> file and
>> /etc/sysconfig/ppp/pptpadsl.conf (if you use pptpadsl
>> script)?
>>
>> I'll try to simulate the case in my "home lab". Please
>> remove login/password/etc
>> - I need only information about topology.
>>
>> PS. I've modified network script significantly and most
>> probably it's a side
>> effect of those changes.
>>
>> Thank you,
>> Serge
>>
>> On 09/19/2010 10:33 AM, Bogdan Petrisor wrote:
>>> Hi all,
>>>
>>> I just upgraded to devil-linux-1.4RC4. I have one
>> small problem that I
>>> can't figure out though, may be someone here can help
>> ...
>>>
>>> After each boot the default route points to eth0
>> instead of ppp0. I have
>>> pppd configured to overwrite the default route, and I
>> see the line
>>> saying "Starting ADSL connection" during the boot
>> process but somehow
>>> the default gateway is not updated.
>>>
>>> I can delete the default route and restart pppd to fix
>> the issue, but I
>>> wonder if maybe there's a right way to do this
>> somewhere in the config
>>> files. Any advice is welcome.
>>>
>>> Best regards
>>>
>>> --------------------------------
>>> In the beginning there was nothing. Then, God said,
>> "Let there be light".
>>> And there was still nothing, but at least you could
>> see it.
>>> --------------------------------
>>>
>>>
>>>
>>>
>>>
>> ------------------------------------------------------------------------------
>>> Start uncovering the many advantages of virtual
>> appliances
>>> and start using them to simplify application
>> deployment and
>>> accelerate your shift to cloud computing.
>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>
>>>
>>>
>>> _______________________________________________
>>> Devil-linux-discuss mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment
>> and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
> 
> 
>       
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> 

Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway

[Serge L. <ser...@gm...>]

Hi Bogdan,

After some tests I'm sure that pppoe server and client on DL work correctly. The
specific of pppd behavior is declared in '/usr/sbin/pppoe-start' script (and in
log file if you start pppoe in debug mode)

$ECHO "* The following section lists your routing table." >> $DEBUG
$ECHO "* If you have an entry which starts with '0.0.0.0', you probably" >> $DEBUG
$ECHO "* have defined a default route and gateway, and pppd will" >> $DEBUG
$ECHO "* not create a default route using your ISP.  Try getting" >> $DEBUG
$ECHO "* rid of this route." >> $DEBUG

Unfortunately, I still don't understand your setup. If your adsl modem works in
bridge mode, it shouldn’t respond on DHCP, if it's in router mode - there is no
necessity to use pppoe... Assuming that it's in brige mode I'd suggest keeping
the interface connected to adsl modem unconfigured (i.e. set "DHCP=no" in the
config you posted) or add a line to adsl init script which will remove default
gateway before pppd starting.

Serge

On 09/19/2010 08:15 PM, Bogdan Petrisor wrote:
> Hi Serge,
> 
> root@annuminas:~ # cat /etc/sysconfig/nic/ifcfg-eth0
> DEVICE=eth0
> ONBOOT=yes
> MODULE="8139too"
> DHCP=yes
> IP=
> NETMASK=
> BROADCAST=""

.....

Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway

[Bogdan P. <pet...@ya...>]

Hi Serge,

I'll try this tomorrow (it's a bit late here) and let you know how it works.
The DSL modem should be in bridge mode, I'll check that too ...

Thank you for your time

--------------------------------
In the beginning there was nothing. Then, God said, "Let there be light". 
And there was still nothing, but at least you could see it.
--------------------------------


--- On Mon, 9/27/10, Serge Leschinsky <ser...@gm...> wrote:

> From: Serge Leschinsky <ser...@gm...>
> Subject: Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway
> To: dev...@li...
> Date: Monday, September 27, 2010, 2:40 AM
> Hi Bogdan,
> 
> After some tests I'm sure that pppoe server and client on
> DL work correctly. The
> specific of pppd behavior is declared in
> '/usr/sbin/pppoe-start' script (and in
> log file if you start pppoe in debug mode)
> 
> $ECHO "* The following section lists your routing table."
> >> $DEBUG
> $ECHO "* If you have an entry which starts with '0.0.0.0',
> you probably" >> $DEBUG
> $ECHO "* have defined a default route and gateway, and pppd
> will" >> $DEBUG
> $ECHO "* not create a default route using your ISP. 
> Try getting" >> $DEBUG
> $ECHO "* rid of this route." >> $DEBUG
> 
> Unfortunately, I still don't understand your setup. If your
> adsl modem works in
> bridge mode, it shouldn’t respond on DHCP, if it's in
> router mode - there is no
> necessity to use pppoe... Assuming that it's in brige mode
> I'd suggest keeping
> the interface connected to adsl modem unconfigured (i.e.
> set "DHCP=no" in the
> config you posted) or add a line to adsl init script which
> will remove default
> gateway before pppd starting.
> 
> Serge
> 
> On 09/19/2010 08:15 PM, Bogdan Petrisor wrote:
> > Hi Serge,
> > 
> > root@annuminas:~ # cat /etc/sysconfig/nic/ifcfg-eth0
> > DEVICE=eth0
> > ONBOOT=yes
> > MODULE="8139too"
> > DHCP=yes
> > IP=
> > NETMASK=
> > BROADCAST=""
> 
> .....
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment
> and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> 


      

Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway

[Bogdan P. <pet...@ya...>]

I removed DHCP from eth0 and seems to work now
The thing is my DSL router (TP-Link) has a DHCP server even when you set it in bridge mode and I thought it was a good idea to enable it on my gateway too. It worked until now so I completely ignored this setting.

Again thank you for your help and keep up the good work 

--------------------------------
In the beginning there was nothing. Then, God said, "Let there be light". 
And there was still nothing, but at least you could see it.
--------------------------------


--- On Mon, 9/27/10, Bogdan Petrisor <pet...@ya...> wrote:

> From: Bogdan Petrisor <pet...@ya...>
> Subject: Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway
> To: dev...@li...
> Date: Monday, September 27, 2010, 10:35 PM
> Hi Serge,
> 
> I'll try this tomorrow (it's a bit late here) and let you
> know how it works.
> The DSL modem should be in bridge mode, I'll check that too
> ...
> 
> Thank you for your time
> 
> --------------------------------
> In the beginning there was nothing. Then, God said, "Let
> there be light". 
> And there was still nothing, but at least you could see
> it.
> --------------------------------
> 
> 
> --- On Mon, 9/27/10, Serge Leschinsky
> <ser...@gm...>
> wrote:
> 
> > From: Serge Leschinsky <ser...@gm...>
> > Subject: Re: [Devil-Linux-discuss] devil-linux-1.4RC4
> default gateway
> > To: dev...@li...
> > Date: Monday, September 27, 2010, 2:40 AM
> > Hi Bogdan,
> > 
> > After some tests I'm sure that pppoe server and client
> on
> > DL work correctly. The
> > specific of pppd behavior is declared in
> > '/usr/sbin/pppoe-start' script (and in
> > log file if you start pppoe in debug mode)
> > 
> > $ECHO "* The following section lists your routing
> table."
> > >> $DEBUG
> > $ECHO "* If you have an entry which starts with
> '0.0.0.0',
> > you probably" >> $DEBUG
> > $ECHO "* have defined a default route and gateway, and
> pppd
> > will" >> $DEBUG
> > $ECHO "* not create a default route using your ISP. 
> > Try getting" >> $DEBUG
> > $ECHO "* rid of this route." >> $DEBUG
> > 
> > Unfortunately, I still don't understand your setup. If
> your
> > adsl modem works in
> > bridge mode, it shouldn’t respond on DHCP, if it's
> in
> > router mode - there is no
> > necessity to use pppoe... Assuming that it's in brige
> mode
> > I'd suggest keeping
> > the interface connected to adsl modem unconfigured
> (i.e.
> > set "DHCP=no" in the
> > config you posted) or add a line to adsl init script
> which
> > will remove default
> > gateway before pppd starting.
> > 
> > Serge
> > 
> > On 09/19/2010 08:15 PM, Bogdan Petrisor wrote:
> > > Hi Serge,
> > > 
> > > root@annuminas:~ # cat
> /etc/sysconfig/nic/ifcfg-eth0
> > > DEVICE=eth0
> > > ONBOOT=yes
> > > MODULE="8139too"
> > > DHCP=yes
> > > IP=
> > > NETMASK=
> > > BROADCAST=""
> > 
> > .....
> > 
> >
> ------------------------------------------------------------------------------
> > Start uncovering the many advantages of virtual
> appliances
> > and start using them to simplify application
> deployment
> > and
> > accelerate your shift to cloud computing.
> > http://p.sf.net/sfu/novell-sfdev2dev
> > _______________________________________________
> > Devil-linux-discuss mailing list
> > Dev...@li...
> > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> > 
> 
> 
>       
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment
> and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> 


      

Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway

[Serge L. <ser...@gm...>]

Bogdan,

you are welcome

Serge

On 09/28/2010 08:33 PM, Bogdan Petrisor wrote:
> I removed DHCP from eth0 and seems to work now
> The thing is my DSL router (TP-Link) has a DHCP server even when you set it in bridge mode and I thought it was a good idea to enable it on my gateway too. It worked until now so I completely ignored this setting.
> 
> Again thank you for your help and keep up the good work 
> 
> --------------------------------
> In the beginning there was nothing. Then, God said, "Let there be light". 
> And there was still nothing, but at least you could see it.
> --------------------------------
> 
> 
> --- On Mon, 9/27/10, Bogdan Petrisor <pet...@ya...> wrote:
> 
>> From: Bogdan Petrisor <pet...@ya...>
>> Subject: Re: [Devil-Linux-discuss] devil-linux-1.4RC4 default gateway
>> To: dev...@li...
>> Date: Monday, September 27, 2010, 10:35 PM
>> Hi Serge,
>>
>> I'll try this tomorrow (it's a bit late here) and let you
>> know how it works.
>> The DSL modem should be in bridge mode, I'll check that too
>> ...
>>
>> Thank you for your time
>>
>> --------------------------------
>> In the beginning there was nothing. Then, God said, "Let
>> there be light". 
>> And there was still nothing, but at least you could see
>> it.
>> --------------------------------
>>
>>
>> --- On Mon, 9/27/10, Serge Leschinsky
>> <ser...@gm...>
>> wrote:
>>
>>> From: Serge Leschinsky <ser...@gm...>
>>> Subject: Re: [Devil-Linux-discuss] devil-linux-1.4RC4
>> default gateway
>>> To: dev...@li...
>>> Date: Monday, September 27, 2010, 2:40 AM
>>> Hi Bogdan,
>>>
>>> After some tests I'm sure that pppoe server and client
>> on
>>> DL work correctly. The
>>> specific of pppd behavior is declared in
>>> '/usr/sbin/pppoe-start' script (and in
>>> log file if you start pppoe in debug mode)
>>>
>>> $ECHO "* The following section lists your routing
>> table."
>>>>> $DEBUG
>>> $ECHO "* If you have an entry which starts with
>> '0.0.0.0',
>>> you probably" >> $DEBUG
>>> $ECHO "* have defined a default route and gateway, and
>> pppd
>>> will" >> $DEBUG
>>> $ECHO "* not create a default route using your ISP. 
>>> Try getting" >> $DEBUG
>>> $ECHO "* rid of this route." >> $DEBUG
>>>
>>> Unfortunately, I still don't understand your setup. If
>> your
>>> adsl modem works in
>>> bridge mode, it shouldn’t respond on DHCP, if it's
>> in
>>> router mode - there is no
>>> necessity to use pppoe... Assuming that it's in brige
>> mode
>>> I'd suggest keeping
>>> the interface connected to adsl modem unconfigured
>> (i.e.
>>> set "DHCP=no" in the
>>> config you posted) or add a line to adsl init script
>> which
>>> will remove default
>>> gateway before pppd starting.
>>>
>>> Serge
>>>
>>> On 09/19/2010 08:15 PM, Bogdan Petrisor wrote:
>>>> Hi Serge,
>>>>
>>>> root@annuminas:~ # cat
>> /etc/sysconfig/nic/ifcfg-eth0
>>>> DEVICE=eth0
>>>> ONBOOT=yes
>>>> MODULE="8139too"
>>>> DHCP=yes
>>>> IP=
>>>> NETMASK=
>>>> BROADCAST=""
>>>
>>> .....
>>>
>>>