Point to point with UTP - Raspberry Pi Forums
hi everyone
has heard of straight , cross utp-cable, 1 used switches, other point point. teacher told me modern appliances detect if cable straight or crossed themselves. anyway, i'm trying hook pi windows pc via utp, can ssh it(i managed shell via wireless router, can't carry router around everywhere). anyway, googled little , turns out no-one every cared enough point-to-point document novice how it's done... please me?
has heard of straight , cross utp-cable, 1 used switches, other point point. teacher told me modern appliances detect if cable straight or crossed themselves. anyway, i'm trying hook pi windows pc via utp, can ssh it(i managed shell via wireless router, can't carry router around everywhere). anyway, googled little , turns out no-one every cared enough point-to-point document novice how it's done... please me?
it depends little bit on how working computers , network really. , if wrong, run risk of not being able connect rpi again in easy way. if have monitor , keyboard connected, no problem really, if run rpi headless do, can inconvenient @ best :)
if computer , rpi not on other network connection single wired ethernet connection can following. if either computer connected network via second interface wifi, need step explain below.
need edit /etc/network/interfaces file on rpi , change eth0 entry this:
iface eth0 inet static
address 192.168.5.10
netmask 255.255.255.0
network 192.168.5.0
broadcast 192.168.5.255
gateway 192.168.5.1
whole command, lose connection rpi depending on network set up. make sure type in whole line, if first part, network not come without restart of rpi. if there mistake in interfaces file, rpi might not connect network @ all:
sudo ifdown eth0 && sudo ifup eth0
on windows pc need config ipv4 entry wired ethernet connection. set manually configure , give windows machine same entries except address entry, make like:
192.168.5.11
change last set of digits on windows pc other address gave rpi.
if windows pc (or rpi) connected network via different interface wifi, want make sure dummy network info , addresses not conflict real network. why 3rd number in ip addresses 5, typically home networks 192.168.1.0 or 192.168.0.0, using 192.168.5.0 here should avoid conflicts, should check first if connected network @ same time direction connection rpi.
should direct utp cable connection between computer , rpi. teacher right, current auto-sensing no longer need cross on cable. told rpi auto-sensing , need 1 side of connection auto-sensing, should go.
if computer , rpi not on other network connection single wired ethernet connection can following. if either computer connected network via second interface wifi, need step explain below.
need edit /etc/network/interfaces file on rpi , change eth0 entry this:
iface eth0 inet static
address 192.168.5.10
netmask 255.255.255.0
network 192.168.5.0
broadcast 192.168.5.255
gateway 192.168.5.1
whole command, lose connection rpi depending on network set up. make sure type in whole line, if first part, network not come without restart of rpi. if there mistake in interfaces file, rpi might not connect network @ all:
sudo ifdown eth0 && sudo ifup eth0
on windows pc need config ipv4 entry wired ethernet connection. set manually configure , give windows machine same entries except address entry, make like:
192.168.5.11
change last set of digits on windows pc other address gave rpi.
if windows pc (or rpi) connected network via different interface wifi, want make sure dummy network info , addresses not conflict real network. why 3rd number in ip addresses 5, typically home networks 192.168.1.0 or 192.168.0.0, using 192.168.5.0 here should avoid conflicts, should check first if connected network @ same time direction connection rpi.
should direct utp cable connection between computer , rpi. teacher right, current auto-sensing no longer need cross on cable. told rpi auto-sensing , need 1 side of connection auto-sensing, should go.
raspberrypi
Comments
Post a Comment