I've seriusly start to learn Perl! :)Nothing complicated.
Unfortunately, the actual most fascionable language is Python,
moreover Cisco has elected it as the developing language for it's
echo system CISCO DNA.
Yes, but it is the pearl that is built into the HPT. ;)
I would use one line..
route crash 21:1/190 21:1/190.*
If you want mail for 21:1/190 and all it's points sent to 21:1/190.
Thanks, it also seems based on Deon's feedback I can run with the following
route crash boss 21:1/190.*
One other thing I am not clear on is ... does the route statement
cover files routed with netmail messages or do I need to set up
routefile statements for all nodes in addition to their route
statements? e.g.
Thanks, it also seems based on Deon's feedback I can run with the following
route crash boss 21:1/190.*
Yes, that works, but only for points. I would still use one line..
If you want to route files for a node you need a routefile line as well. route crash 21:1/190 21:1/190.*
routefile crash noroute 21:1/190
Consider carefully routing files.
If you just want to attach a file to a node, attach the file to a
message and crash it there. No routefile line is needed for that.
Ttyl :-),
I tested this and it did not route netmail from 1/100 sent to 1/191.1
via 1/191 :(
I found these two options did work
route crash routevia 21:1/190 21:1/190.*
route crash 21:1/190 21:1/190.*
But that boss option was a zero on the success meter :)
If you want to route files for a node you need a routefile line
as well. route crash 21:1/190 21:1/190.* routefile crash noroute
21:1/190
OK thanks, will look to add something for each node then.
I have not played much with netmail file attaches as Mystic I don't
think offered it and I know little of how to do so in golded yet.
But your statement above sort of looses me. At present I just use fileboxes with established nodes to send files.
But if I did want to do a file attach via netmail my suspicion is that
I need that routefile line in for each node I HUB for. Right?
Thanks for the reply. :)
But your statement above sort of looses me. At present I just use fileboxes with established nodes to send files. But if I did want to
do a file attach via netmail my suspicion is that I need that
routefile line in for each node I HUB for. Right?
Last comment..
OK thanks, will look to add something for each node then.
Are you sure? I have no routefile lines in my config presently. Only add them when/where needed.
Yep, that is not an option with mystic. Fileboxes work OK but no
attaches.
Yes, fileboxes take out all the guesswork. I like them.
I doubt you need or want that routefile line at all. It is only used if you receive netmail with files attached. That should never happen
without your prior approval.
The routefile keyword is not needed for file areas, just routing files.
the fileboxes we have today makes all this much simpler. Are there any cases where you want to route files? If not I would not use the keyword
at all.
Thanks for the reply. :)
Any old time.. :)
Thanks, it also seems based on Deon's feedback I can run with the following
route crash boss 21:1/190.*
Yes, that works, but only for points. I would still use one line..
route crash 21:1/190 21:1/190.*
That works for 21:1/190 and any points he might have. Use the method that works for you and your setup.
Thanks, it also seems based on Deon's feedback I can run with the following
route crash boss 21:1/190.*
(Right Deon?) but I am wondering could/should I also have a noroute for 21:1/190 stated before or after this from completeness? Something like..
route crash boss 21:1/190.*
route crash noroute 21:1/190
Thanks, it also seems based on Deon's feedback I can run with the following
route crash boss 21:1/190.*
(Right Deon?) but I am wondering could/should I also have a noroute for 21:1/190 stated before or after this from completeness? Something like..
route crash boss 21:1/190.*
route crash noroute 21:1/190
Right, but you dont need the "noroute" option as well (I dont) - because you are "the" hub for 21:1/*.
Is there a way I can stop mail for these points that don't exist off
my own node from being routed and sent out?
route hold noroute 2:335/364.1
route hold noroute 2:335/364.2
route hold noroute 2:335/364.3
This is what I have now..
route crash boss 21:1/190.*
(Right Deon?) but I am wondering could/should I also have a noroute f
21:1/190 stated before or after this from completeness? Something lik route crash boss 21:1/190.*
route crash noroute 21:1/190
Right, but you dont need the "noroute" option as well (I dont) - because you are "the" hub for 21:1/*.
If you wanted to route to my point, you wouldnt use route crash boss, but rather just "route crash 21:2/100 21:2/*", "route crash 21:3/100 21:2/116.*"
So to clarify, it should be suffice to have "route crash boss 21:1/*" - because you are the hub for 21:1/* - which will ensure all downstream points get their mail from their boss (your downlink).
route hold noroute 2:335/364.1
route hold noroute 2:335/364.2
route hold noroute 2:335/364.3
This is what I have now..
Did you have another config before?
The route hold statement shouldn't allow hold outbound to go to
another route.
The combination of route hold noroute does not make sense.
Hold is defined as "stay here and wait" and shall not go elsewhere.
Yes. Inform the "from:" sender that the point does not exsist.
A netmail tracker would be your friend.
Very interesting attack scenario.
Netmails from unknown points to unknown points would create a pingpong
war between two trackers. :-)
so does this line need to be first or last in the route file, can't recall does it match on the first thing it encounters or the last?
I found these two options did work
route crash routevia 21:1/190 21:1/190.*
route crash routevia 21:1/190 21:1/190.*route <flavour> <routeVia> <target>
But that boss option was a zero on the success meter :)
If you want to route files for a node you need a routefile line
as well.
route crash 21:1/190 21:1/190.* routefile crash noroute
21:1/190
OK thanks, will look to add something for each node then.
Consider carefully routing files.
If you just want to attach a file to a node, attach the file to a
message and crash it there. No routefile line is needed for that.
I have not played much with netmail file attaches as Mystic I don't
think offered it and I know little of how to do so in golded yet.
Sigh...
route hold boss 21:3/116.*
route hold boss 21:3/115.*
route hold boss 21:3/112.*
route hold boss 21:3/106.*
route hold boss 21:3/101.*
route hold boss 21:3/999.*
Would this work in one line, like
route hold boss 21:3/101.* 21:3/106.* 21:3/112.* ...
route hold noroute 2:335/364.1
The combination of route hold noroute does not make sense.
I was thinking that when I setup my first point but the above seems to work. Is there a better way to write that out?
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,036 |
Nodes: | 15 (0 / 15) |
Uptime: | 199:49:16 |
Calls: | 726 |
Calls today: | 19 |
Files: | 95,167 |
U/L today: |
3 files (545K bytes) |
D/L today: |
34,377 files (2,031M bytes) |
Messages: | 298,313 |
Posted today: | 2 |