Hello,
I've setup Bochs 2.6 to use the E1000 plugin, but so far no luck with sending/receiving anything...
My configuration (not interesting lines are omitted):
# to load the E1000 plugin during the start of bochs:
plugin_ctrl: unmapped=1, biosdev=1, speaker=1, extfpuirq=1, parallel=1, serial=1, gameport=1, e1000=1
# to setup the E1000 plugin itself:
e1000: enabled=1, mac=fe:fdad:be:ef, ethmod=win32, ethdev=\Device\NPF_{26D4BA9E-AAAF-465D-A8C1-19C9AD1A13BD}, script=none, bootrom=
The ethdev is really the living and connected ethernet card in my PC, doublechecked...
WinPCAP is installed, too, no errors when the E1000 logging is set to log everything - but no packets leaves Bochs and enter the network and vice versa...
Any tip, clue, idea what I am doing wrong is appreciated.
Thanks a lot !
Vladimir
E1000 in Bochs (no data are being sent/received)
- thepowersgang
- Member
- Posts: 734
- Joined: Tue Dec 25, 2007 6:03 am
- Libera.chat IRC: thePowersGang
- Location: Perth, Western Australia
- Contact:
Re: E1000 in Bochs (no data are being sent/received)
The absence of any posted code seems to indicate that you are not doing anything. Hence, you will not get anything out.
Kernel Development, It's the brain surgery of programming.
Acess2 OS (c) | Tifflin OS (rust) | mrustc - Rust compiler
Currently Working on: mrustc
Acess2 OS (c) | Tifflin OS (rust) | mrustc - Rust compiler
Currently Working on: mrustc
Re: E1000 in Bochs (no data are being sent/received)
Maybe my fault, my question was not clear enough, sorry.
The problem is not in *any* code I've written, but in the Bochs setup itself. I've tested the e1000 also inside the DSL Linux, everything seems to be ok, but no packets leave Bochs and no packet enter Bochs (tested via PING, telnet, etc... - the E1000 "LED" is happily blinking, no errors are written back to the console of Bochs, but nothing is being sent/received).... so I suspect I have some problem with the Bochs setup itself. That's the problem I have...
So, once again, any idea ?
Thanks.
Vladimir
The problem is not in *any* code I've written, but in the Bochs setup itself. I've tested the e1000 also inside the DSL Linux, everything seems to be ok, but no packets leave Bochs and no packet enter Bochs (tested via PING, telnet, etc... - the E1000 "LED" is happily blinking, no errors are written back to the console of Bochs, but nothing is being sent/received).... so I suspect I have some problem with the Bochs setup itself. That's the problem I have...
So, once again, any idea ?
Thanks.
Vladimir
[ MicroBe OS ]
Re: E1000 in Bochs (no data are being sent/received)
A mature software that being used by thousand, if not million people, are the last thing to doubt.online wrote:The problem is not in *any* code I've written, but in the Bochs setup itself.
Check your host machine firewall, router mac-filtering setting (if you do bridged network), the testing method (eg winpcap may not capture local loopback packets in windows in some setting), etc
Bottom line, bochs's network emulation works properly in my system.
Re: E1000 in Bochs (no data are being sent/received)
I don't suspect Bochs being wrong - please, read carefully next time I suspect the setup made by me being wrong...
Anyway:
- there's no MAC filter present
- there's no firewall turned on (and Windows firewall is turned off, too)
I've tested it on two different Windows 7 machines... and still no luck, maybe I forgot something ? This is why I am asking - and not to blame Bochs...
thx.
Anyway:
- there's no MAC filter present
- there's no firewall turned on (and Windows firewall is turned off, too)
I've tested it on two different Windows 7 machines... and still no luck, maybe I forgot something ? This is why I am asking - and not to blame Bochs...
thx.
Last edited by online on Fri Nov 09, 2012 4:58 am, edited 1 time in total.
[ MicroBe OS ]
Re: E1000 in Bochs (no data are being sent/received)
Finally it's solved.
The Checkpoint Firewall has been stopped, but not unbind from the interface, causing that the packet filtering was still active....
The Checkpoint Firewall has been stopped, but not unbind from the interface, causing that the packet filtering was still active....
[ MicroBe OS ]