On 10 Jan 2013, at 17:26, Dave McGuire <mcguire at neurotica.com> wrote:
On 01/10/2013 05:19 PM, Cory Smelosky wrote:
Yay! It works properly.
This is good news! Just to confirm, this is using GNS3/Dynamips, correct? Are you using one ethernet card or two?
Config generated in GNS3 and then migrated to pure dynagen + dynamips, yes.
One card. I'm willing to give my configuration if anyone wants it.
I gotta say i'm starting to like IOS. :)
IOS is really, really nice.
I'm glad you got it working, this is very cool!
Now for the crazy part getting it to handle dynamic IPs. :) (Doesn't seem too hard, quick googling shows IOS supports a CRON-like feature that can be used to update the IP on a tunnel periodically but does it support a powerful enough scripting language to re-resolve it in the config only if ping doesn't return anything?)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 01/10/2013 05:19 PM, Cory Smelosky wrote:
Yay! It works properly.
This is good news! Just to confirm, this is using GNS3/Dynamips, correct? Are you using one ethernet card or two?
Config generated in GNS3 and then migrated to pure dynagen + dynamips, yes.
One card. I'm willing to give my configuration if anyone wants it.
I gotta say i'm starting to like IOS. :)
IOS is really, really nice.
I'm glad you got it working, this is very cool!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2013-01-10, at 1:59 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
Anyone ever mess with this?
wonko at fred$ smidump -f python OLD-CISCO-DECNET-MIB.my
OLD-CISCO-DECNET-MIB.my:15: failed to locate MIB module `RFC-1212'
OLD-CISCO-DECNET-MIB.my:17: failed to locate MIB module `RFC1213-MIB'
OLD-CISCO-DECNET-MIB.my:19: failed to locate MIB module `CISCO-SMI'
OLD-CISCO-DECNET-MIB.my:21: unknown object identifier label `temporary'
OLD-CISCO-DECNET-MIB.my:283: index element `dnArea' of row `dnAreaTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:443: index element `dnHIdx1' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:451: index element `dnHIdx2' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:476: unknown object identifier label `ifIndex'
smidump: module `OLD-CISCO-DECNET-MIB.my' contains errors, expect flawed output
smidump: aborting due to severe parsing errors
smidump: use the -k option to force continuation
wonko at fred$
I need to do that so I can convert it into whatever nonsense PySNMP needs.
Brian,
If you need a real Cisco running decnet to point to for playing, I'll volunteer.
Ian
Attaching...
On Jan 10, 2013, at 5:21 PM, wrote:
I think you need some more switches to point smidump to the place where the standard MIB files (the ones complained about at the start) can be found. Actually, it looks like you can just supply those files as additional command line arguments.
Try the attached, I fixed some of the errors. I can't figure out why it's complaining about ifIndex, but I do see the same message for some other MIBs I tried -- including a copy of the standard RFC 1156 MIB...
However, the output looks fine if you use -k with that.
paul
On Jan 10, 2013, at 4:59 PM, Brian Hechinger wrote:
Anyone ever mess with this?
wonko at fred$ smidump -f python OLD-CISCO-DECNET-MIB.my
OLD-CISCO-DECNET-MIB.my:15: failed to locate MIB module `RFC-1212'
OLD-CISCO-DECNET-MIB.my:17: failed to locate MIB module `RFC1213-MIB'
OLD-CISCO-DECNET-MIB.my:19: failed to locate MIB module `CISCO-SMI'
OLD-CISCO-DECNET-MIB.my:21: unknown object identifier label `temporary'
OLD-CISCO-DECNET-MIB.my:283: index element `dnArea' of row `dnAreaTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:443: index element `dnHIdx1' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:451: index element `dnHIdx2' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:476: unknown object identifier label `ifIndex'
smidump: module `OLD-CISCO-DECNET-MIB.my' contains errors, expect flawed output
smidump: aborting due to severe parsing errors
smidump: use the -k option to force continuation
wonko at fred$
I need to do that so I can convert it into whatever nonsense PySNMP needs.
-brian
I think you need some more switches to point smidump to the place where the standard MIB files (the ones complained about at the start) can be found. Actually, it looks like you can just supply those files as additional command line arguments.
Try the attached, I fixed some of the errors. I can't figure out why it's complaining about ifIndex, but I do see the same message for some other MIBs I tried -- including a copy of the standard RFC 1156 MIB...
However, the output looks fine if you use -k with that.
paul
On Jan 10, 2013, at 4:59 PM, Brian Hechinger wrote:
Anyone ever mess with this?
wonko at fred$ smidump -f python OLD-CISCO-DECNET-MIB.my
OLD-CISCO-DECNET-MIB.my:15: failed to locate MIB module `RFC-1212'
OLD-CISCO-DECNET-MIB.my:17: failed to locate MIB module `RFC1213-MIB'
OLD-CISCO-DECNET-MIB.my:19: failed to locate MIB module `CISCO-SMI'
OLD-CISCO-DECNET-MIB.my:21: unknown object identifier label `temporary'
OLD-CISCO-DECNET-MIB.my:283: index element `dnArea' of row `dnAreaTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:443: index element `dnHIdx1' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:451: index element `dnHIdx2' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:476: unknown object identifier label `ifIndex'
smidump: module `OLD-CISCO-DECNET-MIB.my' contains errors, expect flawed output
smidump: aborting due to severe parsing errors
smidump: use the -k option to force continuation
wonko at fred$
I need to do that so I can convert it into whatever nonsense PySNMP needs.
-brian
On 10 Jan 2013, at 17:17, Ian McLaughlin <ian at platinum.net> wrote:
On 2013-01-10, at 2:15 PM, Cory Smelosky <b4 at gewt.net> wrote:
Yay! It works properly.
This is good news! Just to confirm, this is using GNS3/Dynamips, correct? Are you using one ethernet card or two?
Config generated in GNS3 and then migrated to pure dynagen + dynamips, yes.
One card. I'm willing to give my configuration if anyone wants it.
I gotta say i'm starting to like IOS. :)
Ian
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 2013-01-10, at 2:15 PM, Cory Smelosky <b4 at gewt.net> wrote:
Yay! It works properly.
This is good news! Just to confirm, this is using GNS3/Dynamips, correct? Are you using one ethernet card or two?
Ian
On 10 Jan 2013, at 16:56, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 4:36 PM, Cory Smelosky wrote:
Well. It works fine now. Wooo.
marianne#ping 33.15
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 33.15, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 392/429/476 ms
marianne#ping 1.13
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 1.13, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 180/219/252 ms
I wonder why the times are so high :)
Works here too. Looks like the routing tables probably just needed to sort themselves out.
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 76/79/84 ms
bart#
Yay! It works properly.
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Peter Lothberg
Verzonden: woensdag, januari 2013 15:03
Aan: hecnet at Update.UU.SE
Onderwerp: [hvlems at zonnet.nl: Re: [HECnet] Request for comments on
<lots of useless bytes removed>
No Peter, you didn't miss anything at all. Sometimes the topic carries me
away and I reply from my blackberry. Sometimes that works for all of you,
more often it doesn't...
Hans
Anyone ever mess with this?
wonko at fred$ smidump -f python OLD-CISCO-DECNET-MIB.my
OLD-CISCO-DECNET-MIB.my:15: failed to locate MIB module `RFC-1212'
OLD-CISCO-DECNET-MIB.my:17: failed to locate MIB module `RFC1213-MIB'
OLD-CISCO-DECNET-MIB.my:19: failed to locate MIB module `CISCO-SMI'
OLD-CISCO-DECNET-MIB.my:21: unknown object identifier label `temporary'
OLD-CISCO-DECNET-MIB.my:283: index element `dnArea' of row `dnAreaTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:443: index element `dnHIdx1' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:451: index element `dnHIdx2' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:476: unknown object identifier label `ifIndex'
smidump: module `OLD-CISCO-DECNET-MIB.my' contains errors, expect flawed output
smidump: aborting due to severe parsing errors
smidump: use the -k option to force continuation
wonko at fred$
I need to do that so I can convert it into whatever nonsense PySNMP needs.
-brian