Re: [leaf-user] restoring vlan's after reboot: /proc/net/vlan not there
On Mon, 11 Nov 2002 23:27:14 PST Scott wrote: using Intel Pro/100 82559 chipset using eepro100 Revision 1.36 using bering rc4 On boot I'm getting the error: SIOCGIFFLAGS: Operation not supported by device Interesting. It's hard to say exactly what's causing it without a bit more context. I doubt that error message directly affects the vlan configuration though. If you're really curious, set VERBOSE=1 and DEBUG=1 in /linuxrc, backup initrd, and reboot. You should get more verbose startup messages that will probably include the command that causes the SIOCGIFFLAGS error. I load the 802.1q driver (8021q.o). I configure my vlan with the following command lines: vconfig add eth1 11 vconfig add eth2 12 vconfig add eth3 13 etc... I backup the vlan. When I reboot, it is not finding the devices eth1.11, eth1.12, and eth1.13. I check /proc/net/vlan and it's empty where there used to be entries for each virtual device. /var/lib/lrpkg/vlan.list: sbin/vconfig etc/network/if-pre-up.d/vlan etc/network/ip-up.d/ip etc/network/if-post-down.d/vlan var/lib/lrpkg/vlan.* By default there is no entry in vlan.list for /proc/net/vlan. There shouldn't be since /proc isn't a real filesystem. The trick is to make the vconfig commands persistent across reboots... I tried adding it, but it bombs when I try lrpkg -i vlan later with a tar error. Any suggestions how to have those vlans active when I boot? Otherwise shorewall doesn't have anything to configure. The approach I would probably use is: 1) Copy 8021q.o into /lib/modules . 2) Add 8021q to /etc/modules . 3) Backup the modules package. 4) Use the up option in /etc/network/interfaces to run the vconfig commands. As an example: auto eth0 iface eth0 inet static address 11.22.33.44 masklen 29 [..] up vconfig add eth1 11 5) Test with: svi network restart; svi shorewall restart (After insmoding 8021q.o manually if necessary.) 6) Backup the etc package if everything works as expected. There are also pre-up, down and post-down options. Gory details at http://leaf-project.org/devel/jnilo/manpages/interfaces_man.html Hope that helps. --Brad --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
RE: [leaf-user] restoring vlan's after reboot: /proc/net/vlan not there
It seems that your floppy must have been almost full when you ran the backup, ending up with a corrupted vlan.lrp... I guess you must redo the config again. -Original Message- From: Scott [mailto:leaf;troutpocket.org] Sent: Tuesday, November 12, 2002 7:27 AM To: [EMAIL PROTECTED] Subject: [leaf-user] restoring vlan's after reboot: /proc/net/vlan not there using Intel Pro/100 82559 chipset using eepro100 Revision 1.36 using bering rc4 On boot I'm getting the error: SIOCGIFFLAGS: Operation not supported by device I load the 802.1q driver (8021q.o). I configure my vlan with the following command lines: vconfig add eth1 11 vconfig add eth2 12 vconfig add eth3 13 etc... I backup the vlan. When I reboot, it is not finding the devices eth1.11, eth1.12, and eth1.13. I check /proc/net/vlan and it's empty where there used to be entries for each virtual device. /var/lib/lrpkg/vlan.list: sbin/vconfig etc/network/if-pre-up.d/vlan etc/network/ip-up.d/ip etc/network/if-post-down.d/vlan var/lib/lrpkg/vlan.* By default there is no entry in vlan.list for /proc/net/vlan. I tried adding it, but it bombs when I try lrpkg -i vlan later with a tar error. Any suggestions how to have those vlans active when I boot? Otherwise shorewall doesn't have anything to configure. -Scott --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] restoring vlan's after reboot: /proc/net/vlan not there
Le Mardi 12 Novembre 2002 08:27, Scott a écrit : Scott: Have you gone through: http://sourceforge.net/mailarchive/message.php?msg_id=2304008 Also it seems that you have a problem with backup. Suggestion by Luis to check available disk space of the quality of the floppy seems reasonable Jacques using Intel Pro/100 82559 chipset using eepro100 Revision 1.36 using bering rc4 On boot I'm getting the error: SIOCGIFFLAGS: Operation not supported by device I load the 802.1q driver (8021q.o). I configure my vlan with the following command lines: vconfig add eth1 11 vconfig add eth2 12 vconfig add eth3 13 etc... I backup the vlan. When I reboot, it is not finding the devices eth1.11, eth1.12, and eth1.13. I check /proc/net/vlan and it's empty where there used to be entries for each virtual device. /var/lib/lrpkg/vlan.list: sbin/vconfig etc/network/if-pre-up.d/vlan etc/network/ip-up.d/ip etc/network/if-post-down.d/vlan var/lib/lrpkg/vlan.* By default there is no entry in vlan.list for /proc/net/vlan. I tried adding it, but it bombs when I try lrpkg -i vlan later with a tar error. Any suggestions how to have those vlans active when I boot? Otherwise shorewall doesn't have anything to configure. -Scott --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd522.html leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
