Can someone please tell me how I can configure IPencap (IP Protocol 4) interface using Yast’s Network Settings?
Since I’ve been thus far unsuccessful, my next question would be how I could launch a script that could configure this as root on start up?
tia
Wil
What version of openSUSE please?
openSUSE 12.3 as listed in the subject line.
Sorry, my fault.
I have no idea what that IPcap is. Is it a (hardware) networkdevice? When yes, do you mean it is not in the list of devices show by YaST in YaST > Network Devices > Network Settings?
And also, when it is USB connected please show
lsusb
When it is PCI connected show
/sbin/lspci
So we can at least see if it is detected by the system.
No problem Henk,
No this is not a device that is plugged in to the computer. I would say it is one of the oldest ways of doing point to multi-point networking over the internet, and some what similar to vpn. And the building blocks are apart of most linux distributions, which surprises me that it’s not in YaST in YaST > Network Devices > Network Settings.
What it does is encapsulate an ip packet within an ip packet which is sent to a similarly configured system that then decapsulates the packet, and then sends the payload packet onto the intended host on the far end. The first step for me to manually set this up is to load the appropriate kernel module,
modeprobe ipip
then configure and up the interface,
ip addr add 44.x.x.x/32 dev tunl0
ip tunnel change ttl 64 mode ipip tunl0
ip link set dev tunl0 up
Now the interface is visable with ifconfig, and routing etc is handled via ip commands and iptables.
20 +/- years ago I had rc.d, and ifup/down scripts that would do this, but with the fancy gui’s and the close integration with /ets/sysconfig. etc. it’s next to impossible to do this easily, or so it appears.
Hope this explains what I’m trying to accomplish.
Wil
I figure at this point someone might ask, so here it is.
I have been a licensed radio amateur since 1984. Around 1989 I was introduced to the services digital radio communications system known as packet radio. Previously developed and approved by the ITU was an HDLC like connection layer set of protocols know as AX25, which I eventually learned along with it’s routing protocols would allow me to use software to encapsulate ip packets with in the lower level connection layer. With the software I was using it allowed me to eventually download source code, which made me updated versions of this communications software. This long before public access to the internet via radio connections to a gateway located at a university well over 70 mile from my home.
“LINUX” is the “ONLY*”* operating system that has native kernel level support of amateur radio’s AX25, and related protocols!
I learned this in the mid 90’s when I forced into an old slackware release do to what seemed like a scsi driver issue in an SCO install I was attempting. And when it comes to a unix environment, I’ve never looked back. Since I’ve tried various distros since then most on the rpm side of the house, for some time I keep coming back for one reason, or another to what is now openSUSE. For the most part I’m really pleased, but it sure would be outstanding if I could boast that the developers have gone the extra mile, with working with us to come up with a simpler way to be able to configure what’s already there, or in some cases with additional already available packages.
Guess I’d better wakeuplol!
Wil
On 2014-03-06 14:06, hcvv wrote:
>
> Sorry, my fault.
> I have no idea what that IPcap is.
IPcap or IPencap? The subject line says “IPencap” :-?
Google shows a hit on the wikipedia for the second one:
+++··················
IP in IP, sometimes called ipencap, is an example of IP encapsulation
within IP and is described in RFC 2003. Other variants of the IP-in-IP
variety are IPv6-in-IPv4 (6in4) and IPv4-in-IPv6 (4in6).
··················+±
http://en.wikipedia.org/wiki/IP_tunnel
I’m not aware if YaST supports it.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-03-07 01:36, WilNix2k wrote:
> modeprobe ipip
>
> then configure and up the interface,
>
> ip addr add 44.x.x.x/32 dev tunl0
> ip tunnel change ttl 64 mode ipip tunl0
> ip link set dev tunl0 up
>
> Now the interface is visable with ifconfig, and routing etc is handled
> via ip commands and iptables.
>
> 20 +/- years ago I had rc.d, and ifup/down scripts that would do this,
> but with the fancy gui’s and the close integration with /ets/sysconfig.
> etc. it’s next to impossible to do this easily, or so it appears.
>
> Hope this explains what I’m trying to accomplish.
Huh. rc.d? Isn’t that what BSD used?
In SuSE/openSUSE, “rc.d” was just a symlink to “init.d”. If that means
System V, yes, it has been dropped in favour of systemd.
ifup still exists in openSUSE, so that part should still work. You have
to select it in YaST network settings instead of Network Manager.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I don’t know the origins of rc.d, but your correct it may have been in Old RH OSS it used symlinks to init.d. I sort of thought I read a naming SysVinit or the likes. At one point I did have a peek at some of the scripts, and it may be above my pay grade. I know what I want is not in YaST network settings or Network Manager. I also don’t know if I were to add to ifup and the associated scripts if it will show up in Yast. I’ve been part way there in the past, and lets just say there are good reasons why they keep single user mode.
Wil
So in order to make this dream a reality, I wonder if someone can answer a few questions?
If I’m successful at making the necessary changes to the file/s in sysconfig and ifup, will the/se interface/s show up in Yast’s network setting, and the SUSEFirewall2?
How hard is it to make patch files so I could share them with friends, or developers?
I also had some daemons that I use to launch from init.d where do these configs now go?
Thanks again,
Wil
Sorry, but I want to recap.
Is it correct that my conclusion ii that you have the software (a kernel module if I am right). That you can do all the things you want by using the appropriate commands and that you only want a way to execute those commansd ons system boot?
In that case you should dive into Systemd and how to make a systemd unit.
There are examples here on the forums. Sorry, but I should have studied this better, but I didn’t. 
On 2014-03-14 03:56, WilNix2k wrote:
>
> So in order to make this dream a reality, I wonder if someone can answer
> a few questions?
>
> If I’m successful at making the necessary changes to the file/s in
> sysconfig and ifup, will the/se interface/s show up in Yast’s network
> setting, and the SUSEFirewall2?
As I’m not familiar with this type of interface, I’m unsure. I think
that the interfaces will be listed, but I doubt you can manipulate them
from YaST.
> How hard is it to make patch files so I could share them with friends,
> or developers?
Huh. I don’t know, I never created them.
What I do is write a text document with what I change on each file in
plain English, and full copies of the new files I create, if any. Thus
people reading it much later can see what I do and why, and adapt to
changes in other releases.
> I also had some daemons that I use to launch from init.d where do these
> configs now go?
Well, should be replaced by systemd service files instead, which works
differently.
Old init.d scripts may continue to work, though. Have a look at the few
that still exist.
My knowledge in this area (systemd) is limited. There is a chapter in
the openSUSE reference book, though; have a read there.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Yes in a nutshell.
Already wearning my goggles…
Yes the more references the better at this point as for me it’s somewhat uncharted waters.
As I move forward I guess I’ll find out.
What I was thinking about is used more around changes to source code.
Direct references would really be helpful. Would I be better asking questions in/to a different forum?
Just got love these steep learning curves.
On 2014-03-30 11:36, WilNix2k wrote:
> What I was thinking about is used more around changes to source code.
Ah, yes, then you need to learn about patches. I’m not the right person
to answer about that, then.
>> My knowledge in this area (systemd) is limited. There is a chapter in
>> the openSUSE reference book, though; have a read there.
> Direct references would really be helpful.
Direct links are a problem, because the doc changes from version to version.
Try doc.opensuse.org, for starters 
The new site is activedoc.opensuse.org, though. Click on the refference
guide. Systemd is in part III, “System”. Chapter 8 is “systemd”. So here:
http://activedoc.opensuse.org/book/opensuse-reference/chapter-8-the-systemd-daemon
but in a few months it could be a different chapter :-p
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)