Answers in-line:
>One question what is this ifx you keep referring to. I
tried a google
>search but it just pulled up a bunch of worthless
information.
>
>I also checked babel over at
>http://www.geocities.com/ikind_babel/index.html & found
no reference to
>ifx. So what you typed is very confusing.
ifx is short for "interface", i.e. "network
interface", "ethernet interface", etc.
>Also since you said you are Running Internet Connection
Sharing on the
>multi-homed computer are you running the MN-500 in
bridge mode or router
>mode.
Routing mode. So it will firewall and serve DHCP to the
system connected to it.
>You will also have to explain the network better then
>DSL --> DSL Modem --> MN-150
>
>Because it doesn't say what comes after the MN-150 which
is where it
>seems the problem is.
The next sentence did. Here's another attempt at a
picture:
DSL -- DSL Modem -- MN-150 -- MN-500 -- 3 computers
| |
{public static addr} {private DHCP addr}
| |
[a server with two interfaces]
I have no idea if that will come out readable in html.
>(E-Mail Removed) wrote:
>
>> Yes, here's a textual attempt at a description:
>>
>> DSL-->{DSL Modem}-->{MS MN-150 switch}
>>
>> Both the static ifx of the server and the MN-500 plug
>> into the MN-150 side-by-side.
>>
>> All other computers plug into the MN-500.
>> There is a 2nd ifx on the server (DHCP) that goes from
>> the server to the MN-500.
>>
>> As I said, the 2nd ifx on the server (the DHCP one)
gets
>> the correct gateway. All of the other systems on the
MN-
>> 500 get the IP of the DHCP ifx on the server.
>>
>> This actually works ok, but if the server is down, the
>> systems on the MN-500 can't get out.
>>
>> -R
>.
>