| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: [OS2HW] Help Change from Injoy to Dlink DI604 |
In , on
08/03/05
at 02:10 PM, "Don(ald) O. Woodall"
said:
>> - add the IP address of each NIC port to your diagram because
>> it will help you visualize what you need to do
> Umm, here you have me going.
> I have two IP addresses.
> I have three NIC's.
> "I" associate each address with a computer, not a NIC.
No can do. Each ethernet port needs a unique IP address. This includes
the ethernet ports on the DLink.
> By the way, this brings up a question of mine. On my
>"Firewall Computer" (192.168.49.11), how do I software wise
>confirm which NIC is "LANO" and which NIC is "LAN1"?
Look at setup.cmd or use:
ifconfig lan0
and
ifconfing lan1
>> - use
>> netstat -r
>> to ensure that the routing you defined in setup.cmd is
>> really what you meant
> This is probably going to mess things up.
How?
> Here is a netstat -r from the old, half working connection.
I'll annotate it a bit for you.
You have a dial up connection.
>default 69.209.127.254 0.0.0.0 0 UGP ppp0
All packets that are not sent elsewhere get sent to 69.209.127.254. This
is the IP address of your side of the ppp interface.
>67.36.55.26 69.209.127.254 255.255.255.255 0 UGHW3 ppp0
>68.142.229.13 69.209.127.254 255.255.255.255 0 UGHW3 ppp0
>68.142.229.41 69.209.127.254 255.255.255.255 0 UGHW3 ppp0
These are routes discovered and cached by the tcpip stack.
>69.209.118.42 127.0.0.1 255.255.255.255 0 UH lo
This is either a manual hosts entry to prevent spam or maybe something set
up by injoy.
What is your DSL IP address?
>69.209.127.254 69.209.118.42 255.255.255.255 0 UH ppp0
Another cached route.
>127.0.0.1 127.0.0.1 255.255.255.255 0 UH lo
>128.118.25.3 69.209.127.254 255.255.255.255 0 UGHW ppp0
Another cached route.
>192.168.49 192.168.49.11 255.255.255.0 0 UC lan0
The route to your firewall computer probably.
> I want to reduce my electrical usage. I want to eliminate my
>Firewall computer and replace it with the DLink DI604 router.
This is easy. Use Philip's diagram as a guide.
As far as IP addresses go, it can be as simple as what I use on the box I
am currently typing on:
route -fh
ifconfig lo 127.0.0.1
ifconfig lan0 192.168.0.2 netmask 255.255.255.0
:: from 1492 to 1500 16 Sep 03 SHL
ifconfig lan0 mtu 1500
route add default 192.168.0.1 -hopcount 1
ipgate off
192.168.0.1 is the DLink. 192.168.0.2 is this box. Note what I said
above. Two ethernet ports. Two unique IP addresses.
After adjusting the IP addresses, this is all you need on the existing
firewall box to talk through the DLink to your DSL provider. Ping should
respond:
[j:\tmp\00instal]ping 192.168.0.1
PING 192.168.0.1: 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0. time=0. ms
64 bytes from 192.168.0.1: icmp_seq=1. time=0. ms
Immediately after running setup.cmd, netstat -r says:
[j:\tmp\00instal]netstat -r
destination router netmask metric flags
intrf
default 192.168.0.1 0.0.0.0 1 UGSP
lan0 127.0.0.1 127.0.0.1 255.255.255.255 0
UH lo 192.168 192.168.0.2 255.255.255.0
0 UC lan0
What this says is that everything other than lookback packets go to the
router via the lan0 interface. This includes packets addresses to
192.168.x.x because both 192.168.0.2 and 192.168.0.1 are on the same
network segment.
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67
#10183 Warp4.something/14.100c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/os2hardware/
To unsubscribe from this group, send an email to:
os2hardware-unsubscribe{at}yahoogroups.com
Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
---
* Origin: Waldo's Place USA Internet Gateway (1:3634/1000)SEEN-BY: 633/267 270 5030/786 @PATH: 3634/1000 12 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.