HiYou could look up the technical information provided by websites that review your computer.
mount -o rw
HiOk that was good information to see.
Perhaps we could get the Intel Wifi working instead.
Remember how you mounted the memstick installer. Same situation again but different file to modify.
Boot to memstick installer and chose LiveCD mode
mount -o rw
Hit escape key to exit and save this file.Code:
Now you can reboot and run memstick installer and your wifi should now show up in list of network adapters. Interface name=iwm0
If this works you will need to add these settings to your new FreeBSD install after you reboot or at the post install shell.
(This is a shell provided at the very end of FreeBSD install, after Exit.)
Same instructions needed without the
Reaction score: 2,149
So you run both Windows & FreeBSD on the same machine? Then in addition to what Phishfry said above: why not check the network settings of your Windows installation first and then use those on your FreeBSD setup? It's either static (pre-configured IP address) or dynamic (DHCP).I am able connect through Windows machine using same LAN Cable, in fact i write this message from the same machine!
This is what worries me. I believe all this is for naught as the router is not configured correctly.I am using same cable on a MS Windows XP machine to write you this message, although sometimes it takes Automatic Private Address, but acquires DHCP IP after several reboots.
I am able connect through Windows machine using same LAN Cable, in fact i write this message from the same machine
network-problems-under-dualboot-with-win-7/808020This may be due to a flaw in Windows, which can be repaired easily.
If you have a dual bootable PC with Windows, and you've just used Windows, you may not get an IP address after a reboot in Linux. And so no internet connection.
This has the following reason: every network card has a unique MAC address. This address is ingrained in your NIC. The DHCP server in your router remembers this MAC address.
When you access the internet in Windows and then reboot in Linux, in many cases you'll get no IP address from the DHCP server in your router. Because this server will recall that it previously issued an IP address for that very same MAC address, and won't issue a new one.
You can solve this by forcing Windows to release the IP address, before you reboot the PC. By the way: Linux by default does release the IP address on shutdown.
HiThis thread looks like a mess
So you run both Windows & FreeBSD on the same machine? Then in addition to what Phishfry said above: why not check the network settings of your Windows installation first and then use those on your FreeBSD setup? It's either static (pre-configured IP address) or dynamic (DHCP).
Sounds like the only problem which could go wrong is the issue of FreeBSD actually supporting your NIC but I seem to recall reading that it did.
HiThis is what worries me. I believe all this is for naught as the router is not configured correctly.
Trying to avoid dragging that work into the forum.
HiJust for reference the Huawei HG8121H is a FTTH modem router combo using PPPOE. I read a bunch on it last night but nothing stood out to me.
Just a few points that did.
WAN- Make sure it is not set to Bridge WAN.
In my world wired ethernet is always primary, wireless should be secondary. Just my particular feelings.
But I hate to start into any firewall rules or other settings. This is a slippery slope. Not for FreeBSD forums.
Bad thing is if I was onsite this would be done in 20 minutes.
That is a good idea. Maybe you can find someone local to help with your Huawei.To rule out router issue i plan to go to a Cyber Cafe today and use their LAN instead to connect to Internet!
Reaction score: 2,497
This thread looks like a mess
Tag your it!This thread looks like a mess
HiIn post # 33 and #36 your image shows a WAN tab right next to the LAN tab. Top of screen.
That is a good idea. Maybe you can find someone local to help with your Huawei.