From: Heiko Z. <he...@zu...> - 2010-01-05 12:50:35
|
Is anybody using wvdial? If not, then I may nuke the package. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Frank W. <Fra...@ct...> - 2010-01-05 14:17:54
|
Heiko Zuerker wrote: > Is anybody using wvdial? I don't. But I wonder if you want responses from non-users also? Regards, Frank > > If not, then I may nuke the package. > -- _______________________________________________ Centre de Technologie de l'Education 29 avenue John F. Kennedy L-1855 Luxembourg-Kirchberg email: Fra...@ct... tél.: +352 247-85973 fax: +352 333797 _______________________________________________ |
From: Heiko Z. <he...@zu...> - 2010-01-05 15:55:03
|
Quoting Frank Weis <Fra...@ct...>: > Heiko Zuerker wrote: >> Is anybody using wvdial? > > I don't. But I wonder if you want responses from non-users also? I think I found a workaround for my problem, so I can leave it in (for now). -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Aaron M. <aa...@uw...> - 2010-01-13 15:22:29
|
Hi All, I'm wondering if anyone knows of a way to add a second IP in the same subnet to a tagged VLAN interface? We use Devil Linux to implement a Quarantine network on campus, currently provided by two boxes. I would like to consolidate the boxes by merging one into the other, and easiest way to migrate things would be to give the primary box the IPs of the secondary in addition to its own. Both boxes have around 30+ networks them via tagged interfaces. Initially, I tried this by taking the interface and using the technique you'd use on a normal one, eg: cp ifcfg-vlan274 ifcfg-vlan274:1 And I edited to :1 version to have the second IP. This only seemed to overwrite the first interface though when I restarted network services. Is there another way to do this? -- Aaron McDonnell Network Administrator Network Operations Centre University of Western Ontario Tel: 519-661-2111 ext. 86558 |
From: Marcello D. <mar...@st...> - 2010-01-13 17:24:04
|
Hi Aaron, I'm quite sure to have had it working... Did you edit the DEVICE= line? Following your sample it should be: DEVICE=vlan274:1 Ciao Marcello Il giorno mer, 13/01/2010 alle 10.21 -0500, Aaron McDonnell ha scritto: > Hi All, > > I'm wondering if anyone knows of a way to add a second IP in the same subnet > to a tagged VLAN interface? > > We use Devil Linux to implement a Quarantine network on campus, currently > provided by two boxes. I would like to consolidate the boxes by merging one > into the other, and easiest way to migrate things would be to give the > primary box the IPs of the secondary in addition to its own. Both boxes > have around 30+ networks them via tagged interfaces. > > Initially, I tried this by taking the interface and using the technique > you'd use on a normal one, eg: > > cp ifcfg-vlan274 ifcfg-vlan274:1 > > And I edited to :1 version to have the second IP. This only seemed to > overwrite the first interface though when I restarted network services. Is > there another way to do this? > > -- > > Aaron McDonnell > Network Administrator > Network Operations Centre > University of Western Ontario > Tel: 519-661-2111 ext. 86558 > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Heiko Z. <he...@zu...> - 2010-01-13 17:26:19
|
Quoting Aaron McDonnell <aa...@uw...>: > Hi All, > > I'm wondering if anyone knows of a way to add a second IP in the same subnet > to a tagged VLAN interface? > > We use Devil Linux to implement a Quarantine network on campus, currently > provided by two boxes. I would like to consolidate the boxes by merging one > into the other, and easiest way to migrate things would be to give the > primary box the IPs of the secondary in addition to its own. Both boxes > have around 30+ networks them via tagged interfaces. > > Initially, I tried this by taking the interface and using the technique > you'd use on a normal one, eg: > > cp ifcfg-vlan274 ifcfg-vlan274:1 > > And I edited to :1 version to have the second IP. This only seemed to > overwrite the first interface though when I restarted network services. Is > there another way to do this? As far as I recall you have to edit the file and change the line: DEVICE=eth2 to DEVICE=eth2:1 The name of the file doesn't provide any functionality, the content if what counts. In addition to that, uou may have to start counting at 0. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Aaron M. <aa...@uw...> - 2010-01-13 17:49:28
|
Hi Heiko, Thanks to you and Marcello for the responses. I gave this a try, but it does not fix the issue. I should provide a bit more info for you... In the /etc/sysconfig/nic directory, there are a number of interface config files for the various vlans involved. What I tried this time was to copy the file "ifcfg-vlan274" to "ifcfg-vlan274a", and in the new file, I changed the device entry from "DEVICE=eth0" to "DEVICE=eth0:0", and also changed the IP address to the second IP I needed in that VLAN. When I restarted the network services, it again overwrote the first IP with the second, and the second IP behaved oddly and I could not attach to it. I reverted back to the single IP in VLAN 274. Any other ideas? -- Aaron McDonnell Network Administrator Network Operations Centre University of Western Ontario Tel: 519-661-2111 ext. 86558 On 13/01/2010 12:26 PM, Heiko Zuerker wrote: > Quoting Aaron McDonnell<aa...@uw...>: > >> Hi All, >> >> I'm wondering if anyone knows of a way to add a second IP in the same subnet >> to a tagged VLAN interface? >> >> We use Devil Linux to implement a Quarantine network on campus, currently >> provided by two boxes. I would like to consolidate the boxes by merging one >> into the other, and easiest way to migrate things would be to give the >> primary box the IPs of the secondary in addition to its own. Both boxes >> have around 30+ networks them via tagged interfaces. >> >> Initially, I tried this by taking the interface and using the technique >> you'd use on a normal one, eg: >> >> cp ifcfg-vlan274 ifcfg-vlan274:1 >> >> And I edited to :1 version to have the second IP. This only seemed to >> overwrite the first interface though when I restarted network services. Is >> there another way to do this? > > As far as I recall you have to edit the file and change the line: > DEVICE=eth2 > to > DEVICE=eth2:1 > > The name of the file doesn't provide any functionality, the content if > what counts. > > In addition to that, uou may have to start counting at 0. > > |
From: Marcello D. <mar...@st...> - 2010-01-13 18:43:04
|
Il giorno mer, 13/01/2010 alle 12.43 -0500, Aaron McDonnell ha scritto: > In the /etc/sysconfig/nic directory, there are a number of interface config > files for the various vlans involved. What I tried this time was to copy > the file "ifcfg-vlan274" to "ifcfg-vlan274a", and in the new file, I changed > the device entry from "DEVICE=eth0" to "DEVICE=eth0:0", and also changed the > IP address to the second IP I needed in that VLAN. I would try the following: 1st file: ifcfg-vlan274 DEVICE=eth0 2nd file: ifcfg-vlan274:0 DEVICE=vlan274:0 Note that the former points to the physical device while the latter points to the "vlan" device. This is because the fist file is a "vlan definition" and the DEVICE value is used together with the VLANID value as parameter to the vconfig command in order to define a NEW vlan on the specified physical nic. The second file is a "standard alias definition" (regardless of the interface type you're defining the alias on) and the DEVICE value is used as a parameter to the ifconfig command. And the command you want the system to execute for the second IP is something like: ifconfig vlan274:0 $IPADRR netmask $NETMASK broadcast $BROADCAST Hope it helps. Ciao Marcello > > When I restarted the network services, it again overwrote the first IP with > the second, and the second IP behaved oddly and I could not attach to it. I > reverted back to the single IP in VLAN 274. Any other ideas? > > -- > > Aaron McDonnell > Network Administrator > Network Operations Centre > University of Western Ontario > Tel: 519-661-2111 ext. 86558 > > On 13/01/2010 12:26 PM, Heiko Zuerker wrote: > > Quoting Aaron McDonnell<aa...@uw...>: > > > >> Hi All, > >> > >> I'm wondering if anyone knows of a way to add a second IP in the same subnet > >> to a tagged VLAN interface? > >> > >> We use Devil Linux to implement a Quarantine network on campus, currently > >> provided by two boxes. I would like to consolidate the boxes by merging one > >> into the other, and easiest way to migrate things would be to give the > >> primary box the IPs of the secondary in addition to its own. Both boxes > >> have around 30+ networks them via tagged interfaces. > >> > >> Initially, I tried this by taking the interface and using the technique > >> you'd use on a normal one, eg: > >> > >> cp ifcfg-vlan274 ifcfg-vlan274:1 > >> > >> And I edited to :1 version to have the second IP. This only seemed to > >> overwrite the first interface though when I restarted network services. Is > >> there another way to do this? > > > > As far as I recall you have to edit the file and change the line: > > DEVICE=eth2 > > to > > DEVICE=eth2:1 > > > > The name of the file doesn't provide any functionality, the content if > > what counts. > > > > In addition to that, uou may have to start counting at 0. > > > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Heiko Z. <he...@zu...> - 2010-01-13 18:57:37
|
Quoting Aaron McDonnell <aa...@uw...>: > Hi Heiko, > > Thanks to you and Marcello for the responses. I gave this a try, but it > does not fix the issue. I should provide a bit more info for you... > > In the /etc/sysconfig/nic directory, there are a number of interface config > files for the various vlans involved. What I tried this time was to copy > the file "ifcfg-vlan274" to "ifcfg-vlan274a", and in the new file, I changed > the device entry from "DEVICE=eth0" to "DEVICE=eth0:0", and also changed the > IP address to the second IP I needed in that VLAN. > > When I restarted the network services, it again overwrote the first IP with > the second, and the second IP behaved oddly and I could not attach to it. I > reverted back to the single IP in VLAN 274. Any other ideas? It's been a very long time since I did something like that. Try not using just "eth0" alone, always specify it as "eth0:x", even on the main interface. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Aaron M. <aa...@uw...> - 2010-01-13 19:25:47
|
Hi Marcello, Thank you - starting to have some progress. Your suggestion did not work directly, but it did remind me to just try adding the address separately too see what the results were. I was able to create a vlan274:0 interface and assign it the second IP needed, and both IPs were reachable on the network. The difference is that when binding the second IP as a sub-interface, it's already in that vlan, so adding a VLANID is unnecessary. So in the second file, I commented out the VLANID and otherwise went with your suggestion - that worked! Thank you for your help - this makes a migration project MUCH easier. :) -- Aaron McDonnell Network Administrator Network Operations Centre University of Western Ontario Tel: 519-661-2111 ext. 86558 On 13/01/2010 1:42 PM, Marcello Desantis wrote: > Il giorno mer, 13/01/2010 alle 12.43 -0500, Aaron McDonnell ha scritto: >> In the /etc/sysconfig/nic directory, there are a number of interface config >> files for the various vlans involved. What I tried this time was to copy >> the file "ifcfg-vlan274" to "ifcfg-vlan274a", and in the new file, I changed >> the device entry from "DEVICE=eth0" to "DEVICE=eth0:0", and also changed the >> IP address to the second IP I needed in that VLAN. > > I would try the following: > > 1st file: ifcfg-vlan274 > DEVICE=eth0 > > 2nd file: ifcfg-vlan274:0 > DEVICE=vlan274:0 > > Note that the former points to the physical device while the latter > points to the "vlan" device. > > This is because the fist file is a "vlan definition" and the DEVICE > value is used together with the VLANID value as parameter to the vconfig > command in order to define a NEW vlan on the specified physical nic. The > second file is a "standard alias definition" (regardless of the > interface type you're defining the alias on) and the DEVICE value is > used as a parameter to the ifconfig command. And the command you want > the system to execute for the second IP is something like: > ifconfig vlan274:0 $IPADRR netmask $NETMASK broadcast $BROADCAST > > Hope it helps. > > Ciao > > Marcello > > >> >> When I restarted the network services, it again overwrote the first IP with >> the second, and the second IP behaved oddly and I could not attach to it. I >> reverted back to the single IP in VLAN 274. Any other ideas? >> >> -- >> >> Aaron McDonnell >> Network Administrator >> Network Operations Centre >> University of Western Ontario >> Tel: 519-661-2111 ext. 86558 >> >> On 13/01/2010 12:26 PM, Heiko Zuerker wrote: >>> Quoting Aaron McDonnell<aa...@uw...>: >>> >>>> Hi All, >>>> >>>> I'm wondering if anyone knows of a way to add a second IP in the same subnet >>>> to a tagged VLAN interface? >>>> >>>> We use Devil Linux to implement a Quarantine network on campus, currently >>>> provided by two boxes. I would like to consolidate the boxes by merging one >>>> into the other, and easiest way to migrate things would be to give the >>>> primary box the IPs of the secondary in addition to its own. Both boxes >>>> have around 30+ networks them via tagged interfaces. >>>> >>>> Initially, I tried this by taking the interface and using the technique >>>> you'd use on a normal one, eg: >>>> >>>> cp ifcfg-vlan274 ifcfg-vlan274:1 >>>> >>>> And I edited to :1 version to have the second IP. This only seemed to >>>> overwrite the first interface though when I restarted network services. Is >>>> there another way to do this? >>> >>> As far as I recall you have to edit the file and change the line: >>> DEVICE=eth2 >>> to >>> DEVICE=eth2:1 >>> >>> The name of the file doesn't provide any functionality, the content if >>> what counts. >>> >>> In addition to that, uou may have to start counting at 0. >>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > |