[Bug 483233] New: tap network device not fully supported and breaking routing

older
[Bug 490568] New: Bootloader sets...

bugzilla_noreply＠novell.com

8 Mar 2009 8 Mar '09

11:58

https://bugzilla.novell.com/show_bug.cgi?id=483233 Summary: tap network device not fully supported and breaking routing Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ralf@huelsmann.name QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; InfoPath.2; MS-RTC LM 8; .NET CLR 3.5.21022; OfficeLiveConnector.1.3; OfficeLivePatch.1.3) The tap device seems to be not implented in such way, that it works without a additional bridge. That does not make sense, since the tap itself act a a ethernet broadcast domain (hub) and many usecases (e.g. in virtualization) are perfectly fullfilled with "tap only". while this would not be a big deal, it even breaks the routing by removing the standard gateway each time the network module in Yast is run and brings up partly information about the tap in Yast. Restart parameters seem to be not definable via the sysconfig/network/ifcfg-tap0 . Reproducible: Always Steps to Reproduce: 1. set up a system without a tap, including functional network config with a standard gateway 2. add a tapp via Yast2 (does not matter wether GUI or CLI) 3. try to add an IP-adress to the tap 4. close Yast2 with the tap configured Actual Results: 1. you are not able to add an IP via Yast2 2. your standard gatway is lost (at least on 4 seperate testmachnines on X86, X86_64) Expected Results: 1. you could configure a persistent IP 2. standard gateway is untouched The bad thing is: it breaks the standard gateway. And it breaks it each time you call the network module and finish saving it. The not so bad thing is: IP must be configured at CLI via ifconfig tap0 192.168.100.1. Furthermore the tap is not persistent, so next time you need to go through Yast again (but be beware, standardgateway gets lost) or use CLI tunctl –u root -t tap0 . The setup is documente (in german) at http://www.ralf-haifisch.biz/DE-vbox_auf_suse_11.shtml -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

17 Mar 17 Mar

17:51

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c1 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |ralf@huelsmann.name --- Comment #1 from Cyril Hrubis 2009-03-17 11:51:13 MST --- Please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22:59

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User ralf@huelsmann.name added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c2 --- Comment #2 from Ralf Hülsmann 2009-03-17 16:59:35 MST --- Created an attachment (id=280162) --> (https://bugzilla.novell.com/attachment.cgi?id=280162) y2log - see later pdf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23:19

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User ralf@huelsmann.name added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c3 --- Comment #3 from Ralf Hülsmann 2009-03-17 17:19:57 MST --- Created an attachment (id=280166) --> (https://bugzilla.novell.com/attachment.cgi?id=280166) screenshoots how the log was generated -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23:29

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 Ralf Hülsmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|ralf@huelsmann.name | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19 Mar 19 Mar

13:41

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mzugec@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

24 Mar 24 Mar

10:27

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c4 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@novell.com --- Comment #4 from Marius Tomaschewski 2009-03-24 04:27:15 MST --- (In reply to comment #0)

...

Steps to Reproduce: 1. set up a system without a tap, including functional network config with a standard gateway 2. add a tapp via Yast2 (does not matter wether GUI or CLI) 3. try to add an IP-adress to the tap 4. close Yast2 with the tap configured Actual Results: 1. you are not able to add an IP via Yast2 2. your standard gatway is lost (at least on 4 seperate testmachnines on X86, X86_64)

Expected Results: 1. you could configure a persistent IP 2. standard gateway is untouched

The bad thing is: it breaks the standard gateway. And it breaks it each time you call the network module and finish saving it.

That yast2 does not allow to set IP for the tap is a bug. That a default route gets deleted, is a bug too. We've to investigate why this happens (yes, it is a bad thing).

...

The not so bad thing is: IP must be configured at CLI via ifconfig tap0 192.168.100.1.

Since yast2 can't set it (at the moment), you've to correct it manually: echo "IPADDR='192.168.100.1/24'" >> ifcfg-tap0 and call then: ifdown tap0 ifup tap0 or rcnetwork restart tap0

...

Furthermore the tap is not persistent, so next time you need to go through

This is AFAIS not true. I've tested it just now and yast2 created a persistent tap config (/etc/sysconfig/network/ifcfg-tap0): BOOTPROTO='static' STARTMODE='onboot' TUNNEL='tap' TUNNEL_SET_GROUP='' TUNNEL_SET_OWNER='' TUNNEL_SET_PERSISTENT='yes' # added manually IPADDR='192.168.100.1/24' You can also set owner/group in yast2, but uid 0 as owner is default. Further, you can use PRE_UP_SCRIPT, POST_UP_SCRIPT, PRE_DOWN_SCRIPT, POST_DOWN_SCRIPT or scripts in ifservices-tap0 or also if-{up,down}.d to start/stop whatever you like when the tap interface gets up and down via ifup and ifdown (e.g. network restart). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:31

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c5 --- Comment #5 from Marius Tomaschewski 2009-03-24 04:31:56 MST --- BTW: Please note also, that tap interfaces are started by the /etc/init.d/network-remotefs (requires already mounted $remote_fs [nfs, cifs]) script. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:32

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c6 --- Comment #6 from Marius Tomaschewski 2009-03-24 04:32:44 MST --- When the system is booting I mean. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:47

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c7 --- Comment #7 from Marius Tomaschewski 2009-03-24 04:47:07 MST --- (In reply to comment #0)

...

Furthermore the tap is not persistent, so next time you need to go through

It was created with TUNNEL_SET_PERSISTENT=yes -- from your logs: network/lan/address.ycp:182 initTunnel $["BOOTPROTO":"dhcp", "STARTMODE":"onboot", "TUNNEL":"tap", "TUNNEL_SET_GROUP":"", "TUNNEL_SET_OWNER":"", "TUNNEL_SET_PERSISTENT":"yes"] [It even cannot be created non-persistently via ifcfg file or yast2. A non-persistent interface can be created only by a daemon driving the tap, that actively holds the interface open and starting of such a daemon is not supported yet in the ifup-tunnel script (this error message you'll get from ifup when you try to set it to "no").] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:22

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c8 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |ralf@huelsmann.name --- Comment #8 from Marius Tomaschewski 2009-03-24 05:22:39 MST --- (In reply to comment #0)

...

Steps to Reproduce: 1. set up a system without a tap, including functional network config with a standard gateway

I was unable to reproduce that the default route gets deleted. Did you add the default route manually? Or was it configured in /etc/sysconfig/network/{routes,ifroute-eth0} ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:55

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c9 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|ralf@huelsmann.name | --- Comment #9 from Michal Zugec 2009-03-24 05:55:01 MST --- I reproduced it /etc/sysconfig/network/routes information is deleted by YaST (I'm going to fix it) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:43

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c10 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #10 from Michal Zugec 2009-03-24 07:43:18 MST --- fixed in yast2-network-2.18.22 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:35

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User ralf@huelsmann.name added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c11 --- Comment #11 from Ralf Hülsmann 2009-03-24 12:35:26 MST --- so there is no step needed from my side any more ? will this be available by YOU after a while ? cheers Ralf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Mar 25 Mar

09:26

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c12 --- Comment #12 from Michal Zugec 2009-03-25 03:26:11 MST ---

...

...
so there is no step needed from my side any more ?

correct

...

...
will this be available by YOU after a while ? No, because it was fixed for 11.2. It's not security bug But I'll create fixed package in my OBS

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:31

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c13 --- Comment #13 from Michal Zugec 2009-03-25 03:31:44 MST --- http://download.opensuse.org/repositories/home://mzugec/openSUSE_11.1/ fixed version is yast2-network-2.17.78 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

26 Mar 26 Mar

11:13

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c16 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #16 from Marius Tomaschewski 2009-03-26 05:13:09 MST --- The deletion of the default route is IMO at least major. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

30 Mar 30 Mar

14:09

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User swamp@suse.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c19 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:running:23570 --- Comment #19 from Swamp Workflow Management 2009-03-30 08:09:27 MDT --- The SWAMPID for this issue is 23570. Please submit the patch and patchinfo file using this ID. (https://swamp.suse.de/webswamp/wf/23570) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

1 Apr 1 Apr

08:18

New subject: [Bug 483233] tap network device not fully supported and breaking routing

https://bugzilla.novell.com/show_bug.cgi?id=483233 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483233#c22 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #22 from Michal Zugec 2009-04-01 02:18:46 MDT --- close as fixed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

5515

Age (days ago)

5539

Last active (days ago)

List overview

Download

18 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 483233] New: tap network device not fully supported and breaking routing

tags

participants (1)