Hi, I was trying to connect the BBB wireless to the internet using the usb connection cable to a laptop which is using the internet on home wifi. I followed the steps in:
but it did not work out. I even lost wifi connection between my laptop and home wifi. After disconnecting the bridging, I regained wifi network access. However, I no longer be able to launch 192.168.7.2 via Firefox. I also cannot connect to the BBB wifi via putty anymore. Anybody knows how to fix this?
I am still trying to get traceroute installed. Debian9 on BBB does not seem to be as easy to use as Ubuntu. I have forwarded your question to IT department. For the time being, let’s get it working in home wifi network first.
It could be worth typing this on your BBB:
netstat -rn
and paste the entire output.
If the 0.0.0.0 destination is pointing to your router IP address, and you can ping the router as you’ve mentioned, then the issue is very likely elsewhere (i.e. the router). As to what that issue could be, I’m not sure : (
You should just copy-paste the entire output, since it’s just a few lines. Since you do not know the precise areas of the output to examine, let those that do know have the opportunity to examine it, to better help you.
That’s not how local area networks work. Sharing your LAN address makes no difference to a hacker. This is like pulling teeth, it could have been so much simpler if you’d stop information-hiding. I’ve asked twice now for the details from netstat -na. Instead you try to blame the equipment. Anyway best of luck.
On Fri, 6 Sep 2019 11:56:18 -0700 (PDT), user pc
<petercohen8877@gmail.com> declaimed the
following:
But that would include posting ip address of home network for possible
hackers to hack my network. Is there another way to do it?
Unless your home network is very badly configured, all it should show
is a PRIVATE LAN IP number, provided by your router. Normal routers
(cable/DSL/etc.) perform NAT (network address translation) -- internal
(LAN) addresses are never passed outside (if they are, you have a bad
router, and would be causing confusion as every model of the same router
uses the same IP addresses on the LAN side).
And, unless you've opened ports on your router, it should also be
running a firewall which blocks unsolicited inbound connection attempts.
Mainly because the NAT table will not have an entry saying "routerIP/port#"
translates to "LAN IP/port#". Opening a port tells the router than anything
it sees coming in with that port# as destination will be sent to whatever
internal LAN IP was specified to handle it. OR you have a DMZ node -- and
the router is configured to send ALL unsolicited inbound traffic to that
single computer (the "opened ports", at least on my router, can have a
different computer for each port listed -- so a port 80 webserver could be
on one computer while a NNTP server is on another... and any other port is
dropped unless a DMZ catch-all is defined)
md_admin@microdiversity:~$ netstat -na
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 64 192.168.1.252:22 192.168.1.66:50592 ESTABLISHED
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:36950 0.0.0.0:*
udp6 0 0 :::5353 :::*
udp6 0 0 :::49137 :::*
raw6 0 0 :::58 :::* 7
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 DGRAM 8448
/run/systemd/journal/syslog
{REST of UNIX domain excluded}
md_admin@microdiversity:~$ sudo route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 202 0 0
eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 202 0 0
eth0
md_admin@microdiversity:~$
Go ahead -- try to ping/traceroute my R-Pi server using that
information.