Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I made a crossover cable to connect my laptop to my BeagleBone without router. The problem is without router my BB doesnt have IP address so I can't ping it. How do I configure my BB and my laptop to assign a static IP connection between my BB (running latest debian image) and my laptop (running Windows 8.1)?
You setup a static address inside the BB. Then it can be addressed just as in a normal network. You just have to make sure that the routine ruleset on your notebook known which network interface to use to reach the BB.
So typically the BB gets a static address in a a separate local network. Same for the notebook, you configure a static address inside that separate network for the network interface you use to connect to the BB. That way the system known what packages to send and receive via which network adapter.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I would really appreciate some help :)
Worked from home, connected normally for months.
Went back to work, same HoloLens, same laptop, different Wi-Fi.
Won't connect now - cannot access the device portal (https://192.168.1.110/).
Can normally acces over USB (http://127.0.0.1:10080/).
Tried:
2 networks - office and tethering over mobile
3 browsers
reseting both the HL and the laptop multiple times
I'm using Windows 10.
Any ideas? Thanks :)
As discussed in the comments, the problem was that the IP address had changed: the IP address will be assigned by the network's DHCP server, and is generally persistent once assigned in helpful networks, but when you switch to a different network or different DHCP server the IP address is likely to change.
In home networks or small office networks the DHCP server is probably built into your router. It would be possible to set up an address reservation for the HoloLens in your router's configuration, if you wanted to preserve or change the address, provided both routers use the same IP address range for attached devices.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have this routing table:
I used SSH to be able to use my Raspberry Pi on my laptop screen. Everything was fine until I opened my browser and wanted to ping Google in the terminal. I can't, though.
When I try to ping 8.8.8.8 (Google's nameserver), I get the message below the routing table in the image above. But the strange thing is, when I run SSH with PuTTY on a different laptop, the Internet connection is fine. So probably the problem is on my laptop.
How can I fix this issue?
Seems like you are using 192.168.1.1 as a gateway, yet you have configured 192.168.137.0/24 as the network.
You should either try to configure the default gateway to - perhaps - 192.168.137.1 or your IP address to 192.168.1.x.
An ifconfig output would be handy.
Edit:
Add default gateway:
route add default gw 192.168.137.1
You might also need to remove current default gateway(s).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
We are running WDS on server2012 and it's doing fine with older machines. But we bought new stack of HP's with Intel i217-lm NIC, it is using Boot agent GE v.1.5.50.
When we are trying to boot it gets ip via dhcp, but ends with error:
PXE-E55: ProxyDHCP service did not reply to request on port 4011
I tried to change dhcp scope options by MS recommendations:
Option 60= PXEClient
Option 66= WDS server name or IP address
Option 67= Boot file name
Any suggestions
To see if the DHCP process is where the problem lies, one test to try is running Wireshark on the DHCP server to see if the packet was received by the server, and if the server sent the packet back to the i217 adapter.
If the packet reached the DHCP server but didn't get sent back maybe it is a firewall issue. I would also check the IP address leases and make sure everything looks error-free (ie no duplicate IPs, bad addresses).
Also if you want to verify that there are not known PXE issues with the i217 adapters, or if there any quirks, you can ask the Wired Ethernet blog at communities.intel.com about the issue you're seeing. They usually have someone who can help from Intel on there.
Workaround was booting from network in UEFI mode. There is limitations regarding new Intel's boot agent
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Folks,
I have Kali linux running on VM machine..there are 2 interfaces configured on this machine..1 interface is configured as "share with my Mac" and the other interface is configured as "Private to Mac".And i believe "private to Mac" option will allow me to connect my VM linux machine to the local machine.... ifconfig command doesn't show any output. i have manually configured the IP address to both interface by editing vi /etc/network/interfaces and restarted the network services using the command "/etc/init.d/networking restart"...but still ifconfig doesn't give any result....
Actually i want to communicate on port ssh from my local machine to the linux vm machine..since the machines do not communicate each other.i am not able to work anymore..Can someone please have a look in this issue and let me know what changes are required to complete my requirement...
Have you tried sudo ifconfig ? If it doesn't work the problem could be the drivers of your network card. I'm not sure this will works but you can watch this tutorial How to install network card to Kali
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am trying to setup openvpn on a server so that I have 2 different tap interfaces (tap0 and tap1) and then a bridge connecting those interfaces. The idea is that a client on tap0 will be able to talk to a client on tap1 and vice-versa.
There is no physical NIC involved in the bridge and the Bridge interface is setup with no ip/netmask/broadcast.
I am able to ping between the 2 when they are both connected however I see no traffic when trying to tcpdump the bridge interface.
I am a bit confused on some things:
Do I need to have an ip configured on the bridge interface at all? I don't quite see the reason for it as all it will do is to make to virtual interfaces talk to each other
Is the fact that the bridge interface does not have an assigned ip/netmask/broadcast the reason I am not able to see the ping traffic on the bridge interface when tcpdumping that interface?
If the answer to number 2 is Yes, I assume that it is not either possible to use iptables to block/allow traffic on that interface, correct? If so is there any other way to accomplish what one would do with iptables on an interface like that?
I guess this wasn't the proper place to put this question but I thought I'd put an update anyway to close the issue.
Turns out that you do not need an assigned ip address on the bridge and it is possible to tcpdump. I happened to be working in containers which made the traffic go outside the vpn when pinging.