[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: faking the hardware address?



Nils Rennebarth wrote:

> You could try:
> 1)
> ifconfig eth1 1.2.3.1 pointopoint 1.2.3.2
> route add -host 1.2.3.2 device eth1
> 
> and as the 1.2.3.2 host is a win95 box, that certainly can't handle ethernet
> in pointopoint mode, you need
> 
> arp -s 1.2.3.0 <hardware address of eth1> netmask 255.255.255.0 pub
> 
> I never tried that. I don't know if ethx interfaces like to be or may be put
> at all in pointopoint mode. Could make sense however with a twisted Twisted
> pair...

I'll see if I can try this.

> 2)
> (This one needs a few more addresses, but it is clean and will work)
> ifconfig eth0 1.2.3.4 netmask 255.255.255.0 broadcast 1.2.3.255
> route add -net 1.2.3.0 device eth0
> 
> ifconfig eth1 1.2.3.1 netmask 255.255.255.252 broadcast 1.2.3.3
> route add -net 1.2.3.0 device eth1
> 
> and on the win95 side set IP address 1.2.3.2, netmask 255.255.255.252 and
> default gateway 1.2.3.1 I hope win95 understands netmasks that are not on
> byte boundaries ... If not, use IP 1.2.3.2, netmask 255.255.255.0,
> default gateway 1.2.3.1 and add
> 
> arp -eth1 -s 1.2.3.0 <hardware address of eth1> netmask 255.255.255.0 pub
> 
> as setup command on the linux box.

I do understand this, but now I have to tell you my _actual_ IP
addresses. The ones I used in the example were from the campus scenario.

Unfortunately, the gateway for the cable company is 1.2.3.1, and
my addresses are 1.2.3.244 through 1.2.3.248 inclusive. Does this mess
up the subnetting?

So, here I've reworked what you gave me. I think there is a problem at
the end on the Win95 side.

ifconfig eth0 1.2.3.248 netmask 255.255.255.0 broadcast 1.2.3.255
route add -net 1.2.3.0 device eth0
 
ifconfig eth1 1.2.3.245 netmask 255.255.255.252 broadcast 1.2.3.247
route add -net 1.2.3.244 device eth1
 
and on the win95 side set IP address 1.2.3.246, netmask 255.255.255.252
and
default gateway 1.2.3.245 I hope win95 understands netmasks that are not
on
byte boundaries ... If not, use IP 1.2.3.246, netmask 255.255.255.0,
default gateway 1.2.3.245 and add
 
arp -eth1 -s 1.2.3.244 <hardware address of eth1> netmask 255.255.255.0
pub

Should the arp be 1.2.3.244 or 1.2.3.0? Will this work just as well as
your proposed arrangement?

-- 
...RickM...


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: