All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gaiarin <gaio@sv.lnf.it>
To: lartc@vger.kernel.org
Subject: 'RTNETLINK answers: File exists' error
Date: Wed, 10 Mar 2021 08:52:19 +0000	[thread overview]
Message-ID: <20210310085219.GC3397@sv.lnf.it> (raw)


Sometime in my firewall (based on debian), using my custom script and
with policy routing enabled, i hit this error:

 ifup vlan191
 Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
 Added VLAN with VID = 191 to IF -:eth2:-
 RTNETLINK answers: File exists
 Failed to bring up vlan191.

this typically happen when i 'play' with an interface (eg, i tear it up
and down many times for testing); after a bit of play (but something
suddenly) the interface go into a undefined state; interface is up (eg,
'ifconfig' return the correct data) but routing is a mess.


Sometime the only thing to do is reboot the firewall.


Probably i do something wrong in my script, but... how can i 'cleanup'
the mess without rebooting?


Thanks.

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''          http://www.lanostrafamiglia.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
      http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)

             reply	other threads:[~2021-03-10  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10  8:52 Marco Gaiarin [this message]
2021-03-10 17:19 ` 'RTNETLINK answers: File exists' error Grant Taylor
2021-03-10 18:02 ` Marco Gaiarin
2021-03-12  9:44 ` Marco Gaiarin
2021-03-12 17:40 ` Grant Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210310085219.GC3397@sv.lnf.it \
    --to=gaio@sv.lnf.it \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.