| View previous topic :: View next topic |
| Author |
Message |
alex.blackbit
Advocate
Joined: 26 Jul 2005
Posts: 2397
|
 Posted: Thu Jul 10, 2008 1:16 pm Post subject: ATM CLIP connection under gentoo |
 |
|
hi,
according to this, gentoo has clip support, which is great.
i found clip.sh even in baselayout 2, under /lib64/rc/net.
no, how do i use that correctly?
i tried to do a symlink net.lo -> net.atm0 and added some entried to /etc/conf.d/net, but when i try to start that interface, it is treated like a normal (already existing) network device, which of course fails.
any pointers welcome.
thx. |
|
| Back to top |
|
 |
g.tomassoni
n00b
Joined: 13 Aug 2005
Posts: 51
|
| Posted: Tue Jul 29, 2008 12:53 pm Post subject: |
|
|
Why "of course"?
Successfully starting a clip connection yields a well-configured atmX interface. ClIP means "Classical IP", thereby what you get is a net interface which looks like a classic (i.e.: ethX) one.
If you are trying to configure a clip connection to your ISP, you need to know the IP address which have been assigned to you, the IP address of your peer and the VPI/VCI values you have to use.
Seldom the ISP doesn't tell you your peer's address. In that case you can use any fictious address you like in the net you have been assigned to. In example, if your ISP assigns to you the address 1.1.1.1/24, you can use 1.1.1.254 as your peer. |
|
| Back to top |
|
|
alex.blackbit
Advocate
Joined: 26 Jul 2005
Posts: 2397
|
| Posted: Tue Jul 29, 2008 6:09 pm Post subject: |
|
|
thanks for your answer.
maybe i should have stated clearer that the rc system tried to start atm0 like a ethernet interface, and this of course fails, because the interface atm0 does not exist before you start "atmarpd" and fire "atmarp -c atm0". "a atmarp -s ..." is needed too after "ifconfig atm0 ip up". i found out that lately. rc did not do this and failed.
what i didn't know is the syntax i have to use in /etc/conf.d/net.
this does the trick: | Code: |
clip_full="no"
clip_atm0=( "10.0.0.2,0.33" )
config_atm0=( "10.0.0.1/24" ) |
no i have other problems.
g.tomassoni, do you have experience with atm under linux?
i am trying to set up a point-to-point connection between 2 hosts with a crossed out MM fibre and 2 fore HE622M cards between a x86_64 and a alpha computer, which makes trouble. |
|
| Back to top |
|
|
g.tomassoni
n00b
Joined: 13 Aug 2005
Posts: 51
|
| Posted: Tue Jul 29, 2008 7:52 pm Post subject: |
|
|
| alex.blackbit wrote: | thanks for your answer.
maybe i should have stated clearer that the rc system tried to start atm0 like a ethernet interface, and this of course fails, because the interface atm0 does not exist before you start "atmarpd" and fire "atmarp -c atm0". "a atmarp -s ..." is needed too after "ifconfig atm0 ip up". i found out that lately. rc did not do this and failed.
|
The atm*d daemons have to start from clip.sh: that script is exactly meant to do that (apart few other details).
| alex.blackbit wrote: | what i didn't know is the syntax i have to use in /etc/conf.d/net.
this does the trick: | Code: |
clip_full="no"
clip_atm0=( "10.0.0.2,0.33" )
config_atm0=( "10.0.0.1/24" ) |
no i have other problems.
|
This conf looks fine to me.
What problems are you experiencing now?
| alex.blackbit wrote: | | g.tomassoni, do you have experience with atm under linux? |
You may find the author name at the beginning of the clip.sh script... 
| alex.blackbit wrote: | | i am trying to set up a point-to-point connection between 2 hosts with a crossed out MM fibre and 2 fore HE622M cards between a x86_64 and a alpha computer, which makes trouble. |
Oh, I already read of your problem in the linux-atm list.
No, I'm sorry: I'm not used to the fore HE622M. I mostly use ClIP in the CPE side of an internet connection, through SpeedTouch Pro or-the-like ATM modem.
I would suggest to you to keep asking to the linux-atm list: your seems not a Gentoo-specific problem.
Also it would be advisable to try to put in loopback each card: in a card you need only to "short" its two fiber connectors together. You could probably use an SC patch to do this. This way you could better identify the failure, since you are not mixing OSes together anymore. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
