Re: ppp- and dns-problem

2001-04-29 Thread Vincent Laisney
Am Sonntag, 29. April 2001 06:15 schrieb marty:
> > Here are the results
> >
> > netstat -rn
> > Kernel IP routing table
> > Destination Gateway Genmask Flags   MSS Window  irtt
> > Iface 62.104.208.43   0.0.0.0 255.255.255.255 UH0 0  
> >0 ppp0 192.168.1.0 192.168.1.200   255.255.255.0   UG0 0  
> >0 eth0 192.168.1.0 0.0.0.0 255.255.255.0   U 0
> > 0  0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 
> >   0 0  0 eth0
>
> that last line is a default route to a gateway on the ethernet...
>
> adding a defaultroute to the dialup will break the routing, because you
> can't have two **default** routes...
>
> do you have a gateway on the ethernet?

I understand now. My problem is that with the combi card I had the ethenet 
configured even if there was no cabling in ethenet port and therefore no 
gateway. Now with the scheme everything is working fine. 
Thanks for your help.
Vincent Laisney

>
> if not, bring eth0 back up then do a:
>
> route del default eth0
>
> then dial up the ppp link and either manually add a default route to the
> other end of the link or specify defaultroute in /etc/ppp/options and let
> it do it for you...
>
> > Kernel IP routing table
> > Destination Gateway Genmask Flags   MSS Window  irtt
> > Iface 62.104.208.43   0.0.0.0 255.255.255.255 UH0 0  
> >0 ppp0 0.0.0.0 62.104.208.43   0.0.0.0 UG0 0  
> >0 ppp0
>
> your final route table should look something like this:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags   MSS Window  irtt
> Iface 62.104.208.43   0.0.0.0 255.255.255.255 UH0 0
>  0 ppp0 192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  
>0 eth0 0.0.0.0 62.104.208.43   0.0.0.0 UG0 0
>  0 ppp0
>
> later
> marty
>
> "I can't buy what I want because it's free. Can't be what they want
> because I'm me." - Corduroy, Pearl Jam



Re: ppp- and dns-problem

2001-04-29 Thread Drew Parsons
On Sat, Apr 28, 2001 at 08:27:17PM -0300, Peter Cordes wrote:
> 
>  If you're using ppp, you should just tell pppd to set a default route.  It
> has an option to do this, called defaultroute.  Just add that to your
> /etc/ppp/options, or /etc/ppp/peers/filename.
> 


That doesn't work.  I tried putting defaultroute into /etc/ppp/options, but
the result in /var/log/syslog was:
Apr 29 22:38:59 strider pppd[6345]: not replacing existing default route to
eth0 [192.168.1.1]

route -n before running ppp (pon) was:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG1  00 eth0


and after was:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.34.50.0.0.0 255.255.255.255 UH0  00 ppp0
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG1  00 eth0

from which the internet is not accessible by ppp, of course (I use eth0 at
work, ppp0 from home).

route -n obtained by first removing eth0 with "ifconfig eth0 down" and then
running ppp is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.34.90.0.0.0 255.255.255.255 UH0  00 ppp0
0.0.0.0 192.168.34.90.0.0.0 UG0  00 ppp0


The only way I know of getting ppp to set itself up properly (apart from
doing a complicated manual configuration of the gateway) is to remove eth0
before running ppp.  I do that in a small script and connect via that script.

Drew

-- 
PGP public key available at http://dparsons.webjump.com/drewskey.txt
Fingerprint: A110 EAE1 D7D2 8076 5FE0  EC0A B6CE 7041 6412 4E4A



PCMCIA network configuration

2001-04-29 Thread Sunny Dubey
Hi,

I have a 3com 574 pcmcia networking card that works just fine under linux 
2.2x and linux 2.4x.

my only problem is that if when I insert my networking card into my computer, 
something automatically configures it with networking information (such as 
defualt gateway, DNS, IP, etc).  This is fine, however I'm on mulitple 
networks, and having the same configuration doesn't work on all of them.

Anyone know how I would be able to disable this automatic configuring of my 
NIC, so that I may be able to configure it myself?

thanks

Sunny Dubey



Re: PCMCIA network configuration

2001-04-29 Thread Andreas Tscharner
> Hi,

Hello,
> 
> I have a 3com 574 pcmcia networking card that works just fine under linux
> 
> 2.2x and linux 2.4x.
> 
> my only problem is that if when I insert my networking card into my
> computer, 
> something automatically configures it with networking information (such
> as 
> defualt gateway, DNS, IP, etc).  This is fine, however I'm on mulitple 
> networks, and having the same configuration doesn't work on all of them.
> 
> Anyone know how I would be able to disable this automatic configuring of
> my 
> NIC, so that I may be able to configure it myself?

Look at the file
/etc/pcmcia/network.opts

There you can make different "schemes". The file itself is quite well
commented, so it should be no problem to figure it out yourself, which
values to set.
If you have your different schemes, you may change between them with
cardctl scheme 
The current scheme will be displayed by
cardctl scheme

I hope this helps

Regards
Andreas 
-- 
Andreas Tscharner
Hain't we got all the fools in town on our side?  And hain't that a big
enough majority in any town?  -- Mark Twain, "Huckleberry Finn"



suspend/Thinkpad A20p/Woody/apmd_proxy

2001-04-29 Thread Vivek Dasmohapatra

Hi - just a heads up: 

I upgraded to woody recently, and discovered a quirk in the apmd_proxy
script: It short circuits and ignores system suspend events when
on_ac_power returns true: This has the unfortunate effect of not
shutting down the alsa-sound stuff and misc other things, which
unfortunately means that when the laptop resumes [after a fn-F4], all the
stuff which should have been brought back to life safely is borked, and
needs to be restarted.

I've fixed it [for myself] by removing the short-circuit for
system-suspend when on ac, but perhaps the script should dispatch events
to 2 directories - one for things you want to do when on battery, and one
for things that should happen when on ac power

Apart from that, everything seems to have worked fine: [well, I haven't
checked pcmcia - I'll have to borrow a card off someone and test it - and 
maybe irda works reliably now... have to test that too]

-- 
Come, Goratrix, we must return to the chantry to prepare for tomorrow night!
What are we gonna do tomorrow night, Tremere?
The same thing we do every night, Goratrix: Try to Take Over The World!



apmd_proxy and ac power WAS: suspend/Thinkpad A20p/Woody/apmd_proxy

2001-04-29 Thread Lee Bradshaw
Your message reminded me of a similar problem. My dell cpx500 has
options to suspend when closing the laptop on battery or on ac power.
Suspend when closing on battery was working fine, but suspend when
closing on ac power caused the machine to lock up so I had disabled it
in the BIOS. After seeing your email, I commented out the check which
blocks suspend on ac power, enabled the option in the BIOS and was able
to suspend and resume when closing the lid on ac power.

I'm inclined to think the current scripts are buggy. Locking the
machine is not good.

  #if [ "$1,$2" = "standby,system" -o "$1,$2" = "suspend,system" ]; then
  #   if on_ac_power >/dev/null; then
  #   # Reject system suspends and standbys if we are on AC power
  #   exit 1  # Reject (NOTE kernel support must be enabled)
  #   fi
  #   # otherwise fall through and call the scripts!
  #fi

The script does say kernel support must be enabled, but what does that
mean? Is there some way to ask the kernel if it has the required
support? I think it would be much better to query the running kernel
for this support than to lock the machine if it's not present.

I'm also not sure what "NOTE kernel support must be enabled" means. I've
got APM support in my kernel and everything seems to work fine now that
the "exit 1" statement is commented out. Is there some specific variable
that needs to be set? Here's my current APM config:

  CONFIG_APM=y
  # CONFIG_APM_IGNORE_USER_SUSPEND is not set
  CONFIG_APM_DO_ENABLE=y
  CONFIG_APM_CPU_IDLE=y
  # CONFIG_APM_DISPLAY_BLANK is not set
  CONFIG_APM_RTC_IS_GMT=y
  # CONFIG_APM_ALLOW_INTS is not set
  # CONFIG_APM_REAL_MODE_POWER_OFF is not set
  # CONFIG_TOSHIBA is not set

I'm probably going to file a bug on this if there's not one already
there. But I was hoping someone on the list might be able to propose a
good solution.

On Sun, Apr 29, 2001 at 11:24:24PM +0100, Vivek Dasmohapatra wrote:
> 
> Hi - just a heads up: 
> 
> I upgraded to woody recently, and discovered a quirk in the apmd_proxy
> script: It short circuits and ignores system suspend events when
> on_ac_power returns true: This has the unfortunate effect of not
> shutting down the alsa-sound stuff and misc other things, which
> unfortunately means that when the laptop resumes [after a fn-F4], all the
> stuff which should have been brought back to life safely is borked, and
> needs to be restarted.
> 
> I've fixed it [for myself] by removing the short-circuit for
> system-suspend when on ac, but perhaps the script should dispatch events
> to 2 directories - one for things you want to do when on battery, and one
> for things that should happen when on ac power
> 
> Apart from that, everything seems to have worked fine: [well, I haven't
> checked pcmcia - I'll have to borrow a card off someone and test it - and 
> maybe irda works reliably now... have to test that too]
> 

-- 
Lee Bradshaw [EMAIL PROTECTED]
Texas Instruments[EMAIL PROTECTED]



Re: apmd_proxy and ac power WAS: suspend/Thinkpad A20p/Woody/apmd_proxy

2001-04-29 Thread Vivek Dasmohapatra
On Sun, 29 Apr 2001, Lee Bradshaw wrote:

> Your message reminded me of a similar problem. My dell cpx500 has

That's me - always reminding people of problems :)

> I'm inclined to think the current scripts are buggy. Locking the
> machine is not good.

I agree - the ac_power check should be delegated to the scripts in the
event.d directory - after all, the suspend is _going_ to happen anyway, 
apmd_proxy can't stop that, so it should simply pass this info on to each
sub-script.

> The script does say kernel support must be enabled, but what does that
> mean? Is there some way to ask the kernel if it has the required

I think it just means that apm support should be available, either
compiled in or in a loaded module. I don't think it really matters if
there is no APM support, since the kernel won't resopnd to APM signals
from the hardware, which therefore won't proceed with the suspension. [1]
[Except maybe for critical suspends, but you're in dangerous territory by 
then anyway]

> support? I think it would be much better to query the running kernel
> for this support than to lock the machine if it's not present.
> I'm probably going to file a bug on this if there's not one already
> there. But I was hoping someone on the list might be able to propose a
> good solution.

It _should_ be sufficient to check for the existence of, and possibly
parse the contents of, /proc/apm. 

PS: section 4 - isn't that the section of the metal health act that you
can be, well, sectioned under? Or is this a reference to something else?
[just curious]

[1] Unless I've misunderstood completely how APM works.

-- 
Just one nuclear family can ruin your whole life.



Re: ppp- and dns-problem

2001-04-29 Thread Drew Parsons

On Sat, Apr 28, 2001 at 08:27:17PM -0300, Peter Cordes wrote:
> 
>  If you're using ppp, you should just tell pppd to set a default route.  It
> has an option to do this, called defaultroute.  Just add that to your
> /etc/ppp/options, or /etc/ppp/peers/filename.
> 


That doesn't work.  I tried putting defaultroute into /etc/ppp/options, but
the result in /var/log/syslog was:
Apr 29 22:38:59 strider pppd[6345]: not replacing existing default route to
eth0 [192.168.1.1]

route -n before running ppp (pon) was:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG1  00 eth0


and after was:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.34.50.0.0.0 255.255.255.255 UH0  00 ppp0
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG1  00 eth0

from which the internet is not accessible by ppp, of course (I use eth0 at
work, ppp0 from home).

route -n obtained by first removing eth0 with "ifconfig eth0 down" and then
running ppp is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.34.90.0.0.0 255.255.255.255 UH0  00 ppp0
0.0.0.0 192.168.34.90.0.0.0 UG0  00 ppp0


The only way I know of getting ppp to set itself up properly (apart from
doing a complicated manual configuration of the gateway) is to remove eth0
before running ppp.  I do that in a small script and connect via that script.

Drew

-- 
PGP public key available at http://dparsons.webjump.com/drewskey.txt
Fingerprint: A110 EAE1 D7D2 8076 5FE0  EC0A B6CE 7041 6412 4E4A


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




PCMCIA network configuration

2001-04-29 Thread Sunny Dubey

Hi,

I have a 3com 574 pcmcia networking card that works just fine under linux 
2.2x and linux 2.4x.

my only problem is that if when I insert my networking card into my computer, 
something automatically configures it with networking information (such as 
defualt gateway, DNS, IP, etc).  This is fine, however I'm on mulitple 
networks, and having the same configuration doesn't work on all of them.

Anyone know how I would be able to disable this automatic configuring of my 
NIC, so that I may be able to configure it myself?

thanks

Sunny Dubey


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: PCMCIA network configuration

2001-04-29 Thread Andreas Tscharner

> Hi,

Hello,
> 
> I have a 3com 574 pcmcia networking card that works just fine under linux
> 
> 2.2x and linux 2.4x.
> 
> my only problem is that if when I insert my networking card into my
> computer, 
> something automatically configures it with networking information (such
> as 
> defualt gateway, DNS, IP, etc).  This is fine, however I'm on mulitple 
> networks, and having the same configuration doesn't work on all of them.
> 
> Anyone know how I would be able to disable this automatic configuring of
> my 
> NIC, so that I may be able to configure it myself?

Look at the file
/etc/pcmcia/network.opts

There you can make different "schemes". The file itself is quite well
commented, so it should be no problem to figure it out yourself, which
values to set.
If you have your different schemes, you may change between them with
cardctl scheme 
The current scheme will be displayed by
cardctl scheme

I hope this helps

Regards
Andreas 
-- 
Andreas Tscharner
Hain't we got all the fools in town on our side?  And hain't that a big
enough majority in any town?  -- Mark Twain, "Huckleberry Finn"


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




suspend/Thinkpad A20p/Woody/apmd_proxy

2001-04-29 Thread Vivek Dasmohapatra


Hi - just a heads up: 

I upgraded to woody recently, and discovered a quirk in the apmd_proxy
script: It short circuits and ignores system suspend events when
on_ac_power returns true: This has the unfortunate effect of not
shutting down the alsa-sound stuff and misc other things, which
unfortunately means that when the laptop resumes [after a fn-F4], all the
stuff which should have been brought back to life safely is borked, and
needs to be restarted.

I've fixed it [for myself] by removing the short-circuit for
system-suspend when on ac, but perhaps the script should dispatch events
to 2 directories - one for things you want to do when on battery, and one
for things that should happen when on ac power

Apart from that, everything seems to have worked fine: [well, I haven't
checked pcmcia - I'll have to borrow a card off someone and test it - and 
maybe irda works reliably now... have to test that too]

-- 
Come, Goratrix, we must return to the chantry to prepare for tomorrow night!
What are we gonna do tomorrow night, Tremere?
The same thing we do every night, Goratrix: Try to Take Over The World!


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




apmd_proxy and ac power WAS: suspend/Thinkpad A20p/Woody/apmd_proxy

2001-04-29 Thread Lee Bradshaw

Your message reminded me of a similar problem. My dell cpx500 has
options to suspend when closing the laptop on battery or on ac power.
Suspend when closing on battery was working fine, but suspend when
closing on ac power caused the machine to lock up so I had disabled it
in the BIOS. After seeing your email, I commented out the check which
blocks suspend on ac power, enabled the option in the BIOS and was able
to suspend and resume when closing the lid on ac power.

I'm inclined to think the current scripts are buggy. Locking the
machine is not good.

  #if [ "$1,$2" = "standby,system" -o "$1,$2" = "suspend,system" ]; then
  #   if on_ac_power >/dev/null; then
  #   # Reject system suspends and standbys if we are on AC power
  #   exit 1  # Reject (NOTE kernel support must be enabled)
  #   fi
  #   # otherwise fall through and call the scripts!
  #fi

The script does say kernel support must be enabled, but what does that
mean? Is there some way to ask the kernel if it has the required
support? I think it would be much better to query the running kernel
for this support than to lock the machine if it's not present.

I'm also not sure what "NOTE kernel support must be enabled" means. I've
got APM support in my kernel and everything seems to work fine now that
the "exit 1" statement is commented out. Is there some specific variable
that needs to be set? Here's my current APM config:

  CONFIG_APM=y
  # CONFIG_APM_IGNORE_USER_SUSPEND is not set
  CONFIG_APM_DO_ENABLE=y
  CONFIG_APM_CPU_IDLE=y
  # CONFIG_APM_DISPLAY_BLANK is not set
  CONFIG_APM_RTC_IS_GMT=y
  # CONFIG_APM_ALLOW_INTS is not set
  # CONFIG_APM_REAL_MODE_POWER_OFF is not set
  # CONFIG_TOSHIBA is not set

I'm probably going to file a bug on this if there's not one already
there. But I was hoping someone on the list might be able to propose a
good solution.

On Sun, Apr 29, 2001 at 11:24:24PM +0100, Vivek Dasmohapatra wrote:
> 
> Hi - just a heads up: 
> 
> I upgraded to woody recently, and discovered a quirk in the apmd_proxy
> script: It short circuits and ignores system suspend events when
> on_ac_power returns true: This has the unfortunate effect of not
> shutting down the alsa-sound stuff and misc other things, which
> unfortunately means that when the laptop resumes [after a fn-F4], all the
> stuff which should have been brought back to life safely is borked, and
> needs to be restarted.
> 
> I've fixed it [for myself] by removing the short-circuit for
> system-suspend when on ac, but perhaps the script should dispatch events
> to 2 directories - one for things you want to do when on battery, and one
> for things that should happen when on ac power
> 
> Apart from that, everything seems to have worked fine: [well, I haven't
> checked pcmcia - I'll have to borrow a card off someone and test it - and 
> maybe irda works reliably now... have to test that too]
> 

-- 
Lee Bradshaw [EMAIL PROTECTED]
Texas Instruments[EMAIL PROTECTED]


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: apmd_proxy and ac power WAS: suspend/Thinkpad A20p/Woody/apmd_proxy

2001-04-29 Thread Vivek Dasmohapatra

On Sun, 29 Apr 2001, Lee Bradshaw wrote:

> Your message reminded me of a similar problem. My dell cpx500 has

That's me - always reminding people of problems :)

> I'm inclined to think the current scripts are buggy. Locking the
> machine is not good.

I agree - the ac_power check should be delegated to the scripts in the
event.d directory - after all, the suspend is _going_ to happen anyway, 
apmd_proxy can't stop that, so it should simply pass this info on to each
sub-script.

> The script does say kernel support must be enabled, but what does that
> mean? Is there some way to ask the kernel if it has the required

I think it just means that apm support should be available, either
compiled in or in a loaded module. I don't think it really matters if
there is no APM support, since the kernel won't resopnd to APM signals
from the hardware, which therefore won't proceed with the suspension. [1]
[Except maybe for critical suspends, but you're in dangerous territory by 
then anyway]

> support? I think it would be much better to query the running kernel
> for this support than to lock the machine if it's not present.
> I'm probably going to file a bug on this if there's not one already
> there. But I was hoping someone on the list might be able to propose a
> good solution.

It _should_ be sufficient to check for the existence of, and possibly
parse the contents of, /proc/apm. 

PS: section 4 - isn't that the section of the metal health act that you
can be, well, sectioned under? Or is this a reference to something else?
[just curious]

[1] Unless I've misunderstood completely how APM works.

-- 
Just one nuclear family can ruin your whole life.


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]