OK!
from the headless:
[EMAIL PROTECTED]:~> /sbin/ifconfig
eth1 Link encap:Ethernet HWaddr 00:06:5B:80:49:0D
inet addr:10.7.99.20 Bcast:10.7.99.255 Mask:255.255.255.0
inet6 addr: fe80::206:5bff:fe80:490d/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:624774 errors:0 dropped:0 overruns:1 frame:0
TX packets:40275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:87231966 (83.1 Mb) TX bytes:35820219 (34.1 Mb)
Interrupt:5 Base address:0xec80
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1302 errors:0 dropped:0 overruns:0 frame:0
TX packets:1302 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:563148 (549.9 Kb) TX bytes:563148 (549.9 Kb)
my mini the controller:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::20d:93ff:fe7a:e4a4%en0 prefixlen 64 scopeid 0x4
inet 10.7.99.23 netmask 0xffffff00 broadcast 10.7.99.255
ether 00:0d:93:7a:e4:a4
media: autoselect (100baseTX <full-duplex>) status: active
supported media: none autoselect 10baseT/UTP <half-duplex>
10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback>
100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-
duplex,hw-loopback>
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:0d:93:ff:fe:7a:e4:a4
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
then I tried to chang my mini's mac address:
daves-mini:~ davidallred$ ifconfig en0 hw ether 00:06:5B:80:49:0D
ifconfig: hw: bad value
Form the man page on my mini:
alias Establish an additional network address for this interface.
This
is sometimes useful when changing network numbers, and
one wishes
to accept packets addressed to the old interface. If
the address
is on the same subnet as the first network address for
this
interface, a netmask of 0xffffffff has to be specified.
I am a bit confused about what I need to do about them being on the
same sub-net.
When I get this too work I can authenticate my mini as the headless,
right?
What about during christmas, my mini will probably be at home and the
headless here!
SSH to the CS computer(schizo.cs.byu.edu (if you have a CS account)
and ssh.et.byu.edu (if you have a CAEDM account) I don't have an
account at either but I can there is a physics Fedora machine...)
set it up so I would change the mac address of the CS to that of the
headless and authenticate there.
which points to needing a script.
On Dec 2, 2005, at 4:18 PM, Jared Lundell wrote:
Then 'ssh -D 1337 headless.machine.byu.edu', and set your
browser's SOCKS
proxy to use localhost port 1337. Now you appear to be coming
from the
headless machine.
I believe the real problem is how can he rig up a script to keep
his mac
address registered with OIT. If he doesn't do this he can't ssh into
his box in any way, since it goes to a firewalled IP address and
won't
be unblocked until he goes through that web-based system.
Michael
`ifconfig eth0 hw ether <insert mac address here>` will change the mac
address to whatever you want. Together with the `ssh -D` idea you
could
write a script to let you authenticate for that machine from
elsewhere.
Capture what the web interface posts, and you might be able figure out
how to make it fully automatic.
-Jared
--------------------
BYU Unix Users Group
http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-
UUG.
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
--------------------
BYU Unix Users Group
http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
