This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot connect to ASL 3.202 after adding second NIC

After installing ASL 3.202 I can access the system fine from the internal NIC, but after I add the configuration for my second NIC it seems to lock the system out from any sort of webadmin access. I can still log in if I'm sitting at the system.

This thread was automatically locked due to age.

Parents

0 Andy_01 over 23 years ago

might be a routing problem. do you have a default gateway on both interfaces??? you can change that in /etc/wfe/conf/itf.conf
Cancel
Vote Up 0 Vote Down

Cancel
0 dmmcfar over 23 years ago in reply to Andy_01

Yes I have a default gateway on both, The webadmin would load perfectly fine before I added the definition for the second NIC then it just stops.
Cancel
Vote Up 0 Vote Down

Cancel
0 Tmor over 23 years ago in reply to dmmcfar

im assuming u reinstalled the ASL software and reloaded a saved config file?
Cancel
Vote Up 0 Vote Down

Cancel
0 dmmcfar over 23 years ago in reply to Tmor

Even if I go from scratch it'll lock up after I add the second interface definition.
Cancel
Vote Up 0 Vote Down

Cancel
0 Andy_01 over 23 years ago in reply to dmmcfar

what i was saying is, don't enter gateways on both interfaces...
Cancel
Vote Up 0 Vote Down

Cancel
0 dmmcfar over 23 years ago in reply to Andy_01

OK I only entered a gateway on one of the NICs and still came up with the same problem.
Cancel
Vote Up 0 Vote Down

Cancel
0 Maurice over 23 years ago in reply to dmmcfar

Originally posted by dmmcfar:
OK I only entered a gateway on one of the NICs and still came up with the same problem.
Can you post your NIC configurations?
Also, have you checked cables/connections etc.?

Maurice
Cancel
Vote Up 0 Vote Down

Cancel
0 dmmcfar over 23 years ago in reply to Maurice

How much of my configuration do you need? Also I've already checked cables and connections. The reason I had to go to 3.202 is because the system is a K6-2/450 which in straight 3.2 won't do DHCP on a second NIC.
Cancel
Vote Up 0 Vote Down

Cancel
0 Maurice over 23 years ago in reply to dmmcfar

Originally posted by dmmcfar:
[QB]How much of my configuration do you need?[QB]
The NIC configuration should do.

Maurice

[size="1"][ 23 July 2002, 08:12: Message edited by: Maurice ][/size]
Cancel
Vote Up 0 Vote Down

Cancel
0 Tmor over 23 years ago in reply to Maurice

not much help i know, however i have one 3.202 with 6 interfaces/networks and everything works fine.

i am using standard Dlink, Intel, and 3com 10/100 cards.

basically troubleshooting is difficult without being able to reproduce the problem.
Cancel
Vote Up 0 Vote Down

Cancel
0 dmmcfar over 23 years ago in reply to Tmor

Ok since I can't get into webadmin to access the config I'll just have to try to explain it. IF0 is statically assigned to my internal 192.168 net
for ip,netmask,gateway and IF1 is set to DHCP for ip,netmask,gateway. I've tried setting either one to not have a gateway while the other did and it didn't work. Any help will be appreciated.
Cancel
Vote Up 0 Vote Down

Cancel
0 hl. over 23 years ago in reply to dmmcfar

hi mate,
have a look at my thread: http://www.astaro.org/ubb/ultimatebb.php?ubb=get_topic;f=2;t=001176

maybe we speak about the same problem ...
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 hl. over 23 years ago in reply to dmmcfar

hi mate,
have a look at my thread: http://www.astaro.org/ubb/ultimatebb.php?ubb=get_topic;f=2;t=001176

maybe we speak about the same problem ...
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 dmmcfar over 23 years ago in reply to hl.

HL - Yep sounds like the exact same problem, what kind of hardware are you using? maybe we can find a similarity. I'm using a K6-2/450 with a 3com and davicom network card (both 10/100)
Cancel
Vote Up 0 Vote Down

Cancel
0 hl. over 23 years ago in reply to dmmcfar

hi.
i'm using an appliance by pyramid (germany). it has an intel cpu and intel 10/100 mbit cards ...
the exact specs can i only get when i am at the install-site. that'll be maybe next week.

but i think it's NOT the hardware.
hmm, i modified one script for one NIC (DSL.sh --> ACRetry=70 and PPPOERETRY=60, and the named.conf, FORWARDERS only).
But it worked like 6 days ... then no more...
Cancel
Vote Up 0 Vote Down

Cancel