I have a raspberry pi which I have installed freebsd on. It is a Model “B” 512 MB version.
I have been asking around and had a great deal of trouble connecting via shh to this via ethernet cable (Cat 5E).
The Pi is only connected to this machine (workstation-xw62.home) via a cable from the ethernet plug in the rear of the computer, and, likewise on the front of the Raspberry Pi.
When I am connected to the Pi from xw62.home I am not connected to the internet or modem/router/bridge.
I was just looking through some previous posts before and I saw mention of wicked, so I thought I would try it. In the process of doing this the initialization of the network interface allowed me to connect or something. I switched back to network manager after reading some of the help on the dialogue. After that I just plugged the computer into the internet so that network manager would initialize and it worked… I could ssh to the Pi.
My network setup is not well done. For now though I would like to fix the ssh behaviour so that I can connect to the Pi. I have spent some time investigating the FreeBSD end of the problem and am trying this side now.
That’s a network problem, rather than an “ssh” problem. You just happen to notice it when using “ssh”.
Your “ifconfig” outputs show a link-local IPv6 address, but no IPv4 address.
AFTER PLUGGING IN MACHINE xw62 to INTERNET
I’m not sure what you are saying there.
If your computer was not connected to a network, then it is not surprising that you could not make a network connection. And it is not surprising that plugging in to a network changed this.
If your ssh is just back to the same computer, then use “ssh localhost” to connect. That only depends on a virtual local network. If you ssh is to another home computer, then you need some sort of connection to the local network for that.
I am probably still not understanding the problem.
but the entire ifconfig of that interface is missing ipv6 info, maybe. Unfortunately I um unsure which to change and how to do it the Raspberry Pi or The xw6200. On the xw6200 which is running OpenSUSE, I can go into the Network dialog in YAST and turn ipv6 off. I tried that though and it does not seem to work.
Thats Ok, when I end up looking for help I am usually exasperated. I am typing on a hp xw6200 workstation, this is my main computer. After I connect the ethernet from the modem to this machine (xw62.home), I can access the internet. Once Network Manager or some subsystem establishes a connection, I can then unplug the ethernet cable from the modem and plug the ethernet cable from the RPi into it establishing a connection that I can use for ftp and ssh. If I don’t do this trick it does not work.
So the sequence relative to the code I pasted is this;
1.) Starts without label, at this point the xw6200(xw62.home) is disconnected from everything.
2.) AFTER PLUGGING IN MACHINE xw62 to INTERNET – corresponds to the main computer getting connected to modem via ethernet.
3.) AFTER PLUGGING RPi BACK INTO XW62 — corresponds to unplugging the ethernet cable (from the modem) and replacing it
with the ethernet cable (from the RPi).
4.) AFTER CONNECTING VIA SSH – corresponds to connecting with ssh after this sequence which results in a successful ssh
session
INFO
LOCAL – readouts from the xw6200, my main computer and the machine I am typing and using ssh from (to RPi), which is running
OpenSUSE openSUSE 13.2 (Harlequin) (x86_64) 64-bit and Gnome Version 3.14.1
RPi — readouts from Raspberry Pi running FreeBSD while connected via ssh (from xw6200)
but the entire ifconfig of that interface is missing ipv6 info, maybe.
That should not matter.
Thats Ok, when I end up looking for help I am usually exasperated. I am typing on a hp xw6200 workstation, this is my main computer. After I connect the ethernet from the modem to this machine (xw62.home), I can access the internet. Once Network Manager or some subsystem establishes a connection, I can then unplug the ethernet cable from the modem and plug the ethernet cable from the RPi into it establishing a connection that I can use for ftp and ssh. If I don’t do this trick it does not work.
Okay. I think I’m beginning to understand your problem.
Your issue is that your network card is not initialized unless you are connected to the modem. But you want to disconnect that, so that you can plug the RPI into the same connector.
The best way of solving your problem, is to use a home router.
Your router plugs into the modem (or not, if you don’t want that).
You connect both your main computer and your RPI to the router.
Your computer will then have an IP address from the router, even if the router is not connected to the modem. And you won’t have to switch cables around to connect your RPI.
Okay, that takes a router and maybe an additional ethernet cable. I’m not sure of your budget, but there are probably low cost routers available.
If you lived in the Chicago area, I’d tell you to buy me a coffee and give you an old router (no longer used) and a short cable. But that’s too long a drive from where you live. Maybe there’s a local computer hobbyists club where somebody has a working but no-longer-used router.
I was under the impression that they had to have the same type to interface, but this is vague knowledge.
Budget OK, I appreciate the thought, really! That is very kind of you. That is not really what I am looking for. I intend to have the raspberry as a server and connected to the internet all the time. The only reason I am connecting to it from the xw6200 is to configure it and tinker. I do not think I need a router although I think it would make the current problem go away. I am trying to figure out the configuration details to get it to work, when I plug it in (the Pi).
I mean, I guess simply put, I want the raspberry pi to recognize the xw6200 everytime I connect them via ethernet not only when I switch the xw6200 from the raspberry pi to the modem back to the raspberry pi.
Like I said I have looked at the network configuration stuff in YAST but don’t really get it. Suffice it to say I think it is this end (xw6200, OpenSUSE) that needs to be configured.
To configure a network connection, you need to give it an IP address.
The standard practice is to use “DHCP” to request an IP address from a DHCP server somewhere.
The trick you are using allows your main system to request an IP address, probably from an ISP provided server. And that allows the network to be configured.
An alternative would be for you to manually configure an IP address. But since this has to match what your ISP expects, that can cause problems if the ISP ever changes how it is assigning and routing IP addresses.
When you use a SOHO router (“Small Office Home Office”), that router will run a local DHCP server. The router DHCP server gives out private IP addresses such as 192.168.1.5. When you communicate with the Internet, the router translates all of the packets so that they go out using the public IP address provided by the ISP.
You could still manually assign IP addresses that way. But you would assign addresses within the private IP range supported by the router. Then, even if your ISP changes how it is routing, your home router will manage that part and it won’t affect what you are doing. That will make it a lot easier to do what you are trying.
So, is it possible all I have to do is change the /etc/hosts file to something that is reasonable and it will all work? I have purchased a static ip but am learning how to use it.:shame:.
If you are using NetworkManager, then you will need to edit the settings for your ethernet connection. Otherwise, use:
Yast –> Network Devices –> Network Settings
and edit the settings for the ethernet device (give it a fixed IP address).
If you are using NetworkManager, then you will need to edit the settings for your ethernet connection. Otherwise, use:
Yast –> Network Devices –> Network Settings
and edit the settings for the ethernet device (give it a fixed IP address).
I see Network Connections and Network Settings, when I go into Network Settings I now see a warning that
Warning
Network is currently handled by network manager or
completely disabled YaST is unable to configure some options
and I cannot edit the connection/device.
When I go into Network Connections which appears to be
nm-connection-editor (1) - network connection editor for NetworkManager
I have the options, without entering password, to choose
Network Connections —> Wired Connection 1 —> EDIT ----> IPV4 Tab —> Method, Automatic (DHCP), Automatic (DHCP) addresses only, Manual, Link Local Only, Shared to other computers, and Disabled.
From this I gather that the computer is not designed to do something as ad-hoc as plugging in and replacing ethernet cables. This should have been obvious. If I am guessing right, I would choose Link Local Only if this was to be plugged into the raspberry pi and Automatic (DHCP) if it was to be connected to the internet. As you mentioned A router is what is indicated I here I think, or maybe a hub, although I was not intending to do that.
That’s the default for laptops and probably machines that look like laptops to the installer.
You can change that if you want. When in Yast Network Settings, go to the “Global Options” tab. There, you can change to using “ifup settings” (versions of opensuse up through 13.1) or “wicked service” (opensuse 13.2).
I don’t think you ever mentioned which version of opensuse you are running.
Whether you should change is a different issue. Given your general unfamiliarity with networking, it might be best to put off that decision for a while.
When I go into Network Connections which appears to be
nm-connection-editor (1) - network connection editor for NetworkManager
I have the options, without entering password, to choose
Network Connections —> Wired Connection 1 —> EDIT ----> IPV4 Tab —> Method, Automatic (DHCP), Automatic (DHCP) addresses only, Manual, Link Local Only, Shared to other computers, and Disabled.
If you choose “Manual”, you should be able to specify an IP address, such as the static IP assigned by your ISP.
From this I gather that the computer is not designed to do something as ad-hoc as plugging in and replacing ethernet cables.
NetworkManager is designed for the needs of laptops. And they are used in a way that depends on plugging or unplugging ethernet cables or connecting to WiFi networks.
This should have been obvious. If I am guessing right, I would choose Link Local Only if this was to be plugged into the raspberry pi and Automatic (DHCP) if it was to be connected to the internet. As you mentioned A router is what is indicated I here I think, or maybe a hub, although I was not intending to do that.
If you have a static IP assigned by your ISP, then use manual and specify that IP address.
Let’s talk a little about hardware.
A switch: At one time, people use hubs. These days we use switches which do roughly the same job but do it better.
With a switch, you would connect the switch to your modem. Then you would connect each computer to the switch.
From the point of view of a computer, this is pretty much the same as directly connecting the computer to the modem, except that if there are two or more computers they are also connected to each other. That would already make life easier for you.
A router: Here, I am talking of a home router, not a large router such as your ISP might have. The home routers are designed to allow several computers to share a network connection, when your ISP has set things up for you to have only one device. The router makes itself the one device that your ISP thinks you have. And then it allows multiple devices to share that connection by using what is called “IP masquerading” or NAT (network address translation) or NAPT (network address and port translation). The router typically has a built-in switch to allow up to 4 devices to directly connect. You can add an additional switch to connect more.
Either a switch or a home router would help you with your setup. I recommend a router, though it may look a tad more complex to setup. You can get an idea of prices by browsing to Amazon or NewEgg or other online computer store.
An additional note. Many routers come with software to setup under Windows. You do not need that software and you do not need to be running Windows. You can set it up with a web browser. And you can ask on this forum, if you need help setting it up. Usually it will work out of the box, and you only need to go into setup to do non-standard things (such as making your RPI a server).
xw6200
openSUSE 13.2 (Harlequin) (x86_64) 64-bit
Gnome Version 3.14.1
RPi
FreeBSD 10.1
Modem
Motorola Surfboard SB6141
If you choose “Manual”, you should be able to specify an IP address, such as the static IP assigned by your ISP.
Yes, I understand, I am trying to fix a problem with the Pi, so I needed to access it locally. I am not sure how I was going to go about having access to the internet from both computers. I had a reasonable concept of hubs, and routers. I was not aware that one could buy a switch.
If you have a static IP assigned by your ISP, then use manual and specify that IP address.
That is manual in Network Manager. OK. Again though, not sure about how I am going to go about this and I was only trying to temporarily access the raspberry pi through ssh.
Right. And you had problems with that, because it needed an IP address (on both systems) in order to communicate.
You can actually just make up IP addresses to use (of the form n.n.n.n where each “n” is an 8-bit number). Have the two computers agree in all but the last of those numbers and they will be able to communicate.
A made up IP only becomes a problem when you connect to the Internet, because you might have made up an IP that properly is used in Australia or Japan or wherever.
IP addresses that begin 192.168. are safe to use at home. That range is reserved for private networks, so they will never conflict.
What a router would do, is make up those two IP addresses for you, and allow you to request them with DHCP (which your computers are probably already trying to do).
Yes, and that is exactly what I saw going on, in fact in the info that I posted early on. The Pi has taken up the 77.44.113.89 while the xw6200 has 77.44.113.83. I am interested in understanding this, which is one of the reasons I don’t really want to buy a router. I was thinking that it is possible with what I have. I think I set the RPi to have that IP and then the xw6200 assumed that it could take the other one. Have to read some stuff about this now.