Scooter
At 06:20 PM 12/22/97 -0000, you wrote:
>We are running V 3.32 as of about a month ago. We have a site which
>has a static route defined in end.cnf as
>
>configure interface dynamic auto-route biancxppp add 199.4.235.100/32
metric 1
Why isn't this in startup.cnf? I can see no benefit to placing it in end.cnf .
>
>we define several local sites in end.cnf to work around the multiple
>bugs in the save configuration code. In this case, it does not work:
What bugs?
>
>when a save is done, the following line was added to startup.cnf
>
>configure interface dynamic auto-route biancxppp add 2.0.0.0/32
Something else is happening here to you. This is not possible under normal
operation.
>
>and now when 199.4.235.100 connects, both routes are added to the
>routing table. The 2.0.0.0/32 route has precedence, and the netblazer
>sends ICMP redirect messages to all the hosts which are directly on
>the 199.4.235 net to route directly to 199.4.235.100, they can access
>the files they need to work on, or our local nameserver, or anything
>on our local net until I manually delete the 2.0.0.0/32 route,
>
You should be using auto-arp here, not auto-route.
>The worst part seems to be that there is no way to 'undo' the initial
>auto-route command, short of a reboot, because even though I deleted
>the route yesterday, today when they connected, I got another phone
>call that they couldn't get any work done, and sure enough, the
>2.0.0.0/32 route was back.
>
>We've been pretty happy with our netblazers, but this save
>configuration stuff has been a pain in the butt from the beginning.
>
>sdb
>
>
Call support in the morning and get a trouble ticket started.
Happy Holidays;
Scooter
If the dial-in uses an address from the local LAN, then you want to use
an AUTO-ARP rather than an AUTO-ROUTE. The auto-arp will then invoke an
auto-route.
The difference is that the arp will allow the remote user to access
hosts on the local LAN.
You say "The 2.0.0.0/32 route has precedence"... if that's the way it's
working, then there is something wrong: routes are CUMULATIVE... ie
they should ALL work. Same for ARPs (and auto-arps).
I suspect you think it's taking precedence because the route to the
199.4.235 net doesn't work, because you need the auto-arp (rather than
the auto-route).
To remove an auto-route, you would use the "auto-route del" command,
and not the "route del".
Usage: auto-route <interface> <add|delete> <ip_addr[/bits] ...>
[private] [metric <metric>]
## Add ip address(es) to automatically add routes for when this
interface starts. The "metric" option is only valid when adding
auto-routes ##
Usage: auto-arp <interface> <add|delete>
<ip_addr ...> [public] [metric <metric>]
## Add ip address(es) to automatically arp for when this interface
starts. The "metric" option is only valid when adding auto-arp
addresses ##
You can see that the auto-arp command is very similar to the auto-route
command, with the single exception that auto-arp works for just a
single IP address (and not a subnet). To auto arp for more than one
address, just repeat the command.
As for what the 2.0.0.0/32 route is doing there I don't know..... is
THAT a route or an auto-route (do an "interface list biancxppp", and
any auto-routes will show up there)
Good luck!
Paul B
## Paul Blitz tel 01635 524155 ##
## Tech Support fax 01635 38578 ##
## KNS Distribution, 27 Kingfisher Court,##
## Newbury, Berks, England, RG14 5SJ. ##
## (the views I express are mine, and ##
## may not be the same as my employer's)##
+-------------------------------------------------------------+
| KNS Distribution make no representation or warranties as to |
| the accuracy or completeness of the information disclosed |
+-------------------------------------------------------------+
----------
>On 22 Dec 1997 18:20:58 -0000, netb...@ssr.com wrote:
>We are running V 3.32 as of about a month ago. We have a site which
>has a static route defined in end.cnf as
>
>configure interface dynamic auto-route biancxppp add 199.4.235.100/32
>metric 1
>
>we define several local sites in end.cnf to work around the multiple
>bugs in the save configuration code. In this case, it does not work:
>
>when a save is done, the following line was added to startup.cnf
>
>configure interface dynamic auto-route biancxppp add 2.0.0.0/32
>
>and now when 199.4.235.100 connects, both routes are added to the
>routing table. The 2.0.0.0/32 route has precedence, and the netblazer
>sends ICMP redirect messages to all the hosts which are directly on
>the 199.4.235 net to route directly to 199.4.235.100, they can access
>the files they need to work on, or our local nameserver, or anything
>on our local net until I manually delete the 2.0.0.0/32 route,
>
Thanks Paul. I've followed your advice and installed the auto-arp, but
the problem seems to be the same. Everything works fine as long as the
site is connected, but when they are not connected the workstations on
the lan still try to route packets to them (they have a default route
through our netblazer). When this happens, the netblazer sends ICMP
redirects, which installs bad route to the remote. When they
reconnect, this doesn't seem to change, resulting in the situation
that they can get packets to us, but our workstations don't have a
route back to them. Is there a way to get the netblazer to send host
unreachable messages, or not send redirects when the remote is down?
Or is there another solution to this problem? The workstations are
suns, running 4.1.3_U1.
sdb
--
s...@ssr.com
I am going to change IP routing feeds to/from the Internet. My problem/question is how do I setup default routes when I will have two feeds to the Internet during my 90 days of conversion? As I bring up networks on the new IPs from the new feed I will need a way to set default routes for those IP numbers to use my new Internet feed (default #2). Old IPs have no porblem - they just go to default.
NOTE: (One Netblazer router using one Frame Relay Feed and many PVCs - amoung which one is default route)
So... what to I do to have two default routes
Kinda like this:
1.2.3.X and 1.2.4.X and 1.2.5.X and 1.2.6.X (lans and frame relay interfaces) all have default routed through my default route.
No I have new IPs to manage from my second Internet IP feed. 5.6.7.X and 5.6.8.X and 5.6.9.X (new lans and frame relay interfaces). How do I source route these IPs through a second default route to the othere IP provider.
I think both providers are blocking me sending out source IPs which are not within their network. There must be as easy solution if someone had (lets say) MCI as their default feed and they were then switching to UUNET - and - it would take 90 days or more to renumber everything...
Thanks
Tom Jones
DMI Computers
****************************
<color><param>ffff,0000,0000</param>
<underline>________________________________________
</underline></color><paraindent><param>out</param><bold><color><param>8080,0000,0000</param><bigger><bigger><bigger><bigger><bigger><bigger>Tom
Jones
</bigger></bigger></bigger></bigger></bigger></bigger></color></bold></paraindent><color><param>0000,0000,8080</param>mailto:</color><color><param>0000,0000,ffff</param><bigger>to...@dmi.net
</bigger></color><color><param>0000,0000,8080</param>Thanks
</color><color><param>0000,0000,ffff</param>http://www.users.dmi.com/tomj/thanx.wav
</color><color><param>0000,0000,8080</param>Thanks
</color><color><param>0000,0000,ffff</param>http://www.users.dmi.com/tomj/thanks.avi
</color><color><param>0000,0000,8080</param>
<bigger>DMI Computers
</bigger>1101 Ironwood Dr.
Coeur d'Alene, ID. 83814
Tel: (208) 664-1340
My personal home page
</color><color><param>0000,0000,ffff</param>http://www.users.dmi.com/tomj
</color><color><param>0000,0000,8080</param>DMI home page
</color><color><param>0000,0000,ffff</param>http://www.dmi.net
</color><underline><color><param>ffff,0000,0000</param>________________________________________
</color></underline>