3 deleted 78 characters in body
source | link

I am trying to setup a simple test system emulated under qemu.

Problem is I seem unable to connect to web applications using the standard command line because applications usually listen to a well defined port, but after they try to open a separate websocket for actual communication.

This behavior is consistent between the toolkits I commonly use (e.g.: Remi or bottle, both are python packages)

Other net applications (e.g.: ssh) work as expected.

The command line I'm using to start qemu is:

qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user,hostfwd=tcp::7777-:7777,hostfwd=tcp::7722-:22

and I try to connect to http://127.0.0.1:7777 (connection reset) or ssh -p 7722 root@127.0.0.1 (succeeds).

What am I missing?

UPDATE (as requested):

I tested with the standard "demo" of both Remi and bottle. They both behave essentially in the same way: after initial connection communication is reset.

Remi actually works a bit better and manages to diplaydisplay the page, but functionality (via websocket) is not there.

I'm unsure ifWhat am I can attach a full example here.missing?

I am trying to setup a simple test system emulated under qemu.

Problem is I seem unable to connect to web applications using the standard command line because applications usually listen to a well defined port, but after they try to open a separate websocket for actual communication.

This behavior is consistent between the toolkits I commonly use (e.g.: Remi or bottle, both are python packages)

Other net applications (e.g.: ssh) work as expected.

The command line I'm using to start qemu is:

qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user,hostfwd=tcp::7777-:7777,hostfwd=tcp::7722-:22

and I try to connect to http://127.0.0.1:7777 (connection reset) or ssh -p 7722 root@127.0.0.1 (succeeds).

What am I missing?

UPDATE (as requested):

I tested with the standard "demo" of both Remi and bottle. They both behave essentially in the same way: after initial connection communication is reset.

Remi actually works a bit better and manages to diplay the page, but functionality (via websocket) is not there.

I'm unsure if I can attach a full example here.

I am trying to setup a simple test system emulated under qemu.

Problem is I seem unable to connect to web applications using the standard command line because applications usually listen to a well defined port, but after they try to open a separate websocket for actual communication.

This behavior is consistent between the toolkits I commonly use (e.g.: Remi or bottle, both are python packages)

Other net applications (e.g.: ssh) work as expected.

The command line I'm using to start qemu is:

qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user,hostfwd=tcp::7777-:7777,hostfwd=tcp::7722-:22

and I try to connect to http://127.0.0.1:7777 (connection reset) or ssh -p 7722 root@127.0.0.1 (succeeds).

I tested with the standard "demo" of both Remi and bottle. They both behave essentially in the same way: after initial connection communication is reset.

Remi actually works a bit better and manages to display the page, but functionality (via websocket) is not there.

What am I missing?

2 added 493 characters in body
source | link

I am trying to setup a simple test system emulated under qemu.

Problem is I seem unable to connect to web applications using the standard command line because applications usually listen to a well defined port, but after they try to open a separate websocket for actual communication.

This behavior is consistent between the toolkits I commonly use (e.g.: Remi or bottle, both are python packages)

Other net applications (e.g.: ssh) work as expected.

The command line I'm using to start qemu is:

qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user,hostfwd=tcp::7777-:7777,hostfwd=tcp::7722-:22

and I try to connect to http://127.0.0.1:7777 (connection reset) or ssh -p 7722 root@127.0.0.1 (succeeds).

What am I missing?

UPDATE (as requested):

I tested with the standard "demo" of both Remi and bottle. They both behave essentially in the same way: after initial connection communication is reset.

Remi actually works a bit better and manages to diplay the page, but functionality (via websocket) is not there.

I'm unsure if I can attach a full example here.

I am trying to setup a simple test system emulated under qemu.

Problem is I seem unable to connect to web applications using the standard command line because applications usually listen to a well defined port, but after they try to open a separate websocket for actual communication.

This behavior is consistent between the toolkits I commonly use (e.g.: Remi or bottle, both are python packages)

Other net applications (e.g.: ssh) work as expected.

The command line I'm using to start qemu is:

qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user,hostfwd=tcp::7777-:7777,hostfwd=tcp::7722-:22

and I try to connect to http://127.0.0.1:7777 (connection reset) or ssh -p 7722 root@127.0.0.1 (succeeds).

What am I missing?

I am trying to setup a simple test system emulated under qemu.

Problem is I seem unable to connect to web applications using the standard command line because applications usually listen to a well defined port, but after they try to open a separate websocket for actual communication.

This behavior is consistent between the toolkits I commonly use (e.g.: Remi or bottle, both are python packages)

Other net applications (e.g.: ssh) work as expected.

The command line I'm using to start qemu is:

qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user,hostfwd=tcp::7777-:7777,hostfwd=tcp::7722-:22

and I try to connect to http://127.0.0.1:7777 (connection reset) or ssh -p 7722 root@127.0.0.1 (succeeds).

What am I missing?

UPDATE (as requested):

I tested with the standard "demo" of both Remi and bottle. They both behave essentially in the same way: after initial connection communication is reset.

Remi actually works a bit better and manages to diplay the page, but functionality (via websocket) is not there.

I'm unsure if I can attach a full example here.

1
source | link

How to setup qemu networking for web app server on guest?

I am trying to setup a simple test system emulated under qemu.

Problem is I seem unable to connect to web applications using the standard command line because applications usually listen to a well defined port, but after they try to open a separate websocket for actual communication.

This behavior is consistent between the toolkits I commonly use (e.g.: Remi or bottle, both are python packages)

Other net applications (e.g.: ssh) work as expected.

The command line I'm using to start qemu is:

qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user,hostfwd=tcp::7777-:7777,hostfwd=tcp::7722-:22

and I try to connect to http://127.0.0.1:7777 (connection reset) or ssh -p 7722 root@127.0.0.1 (succeeds).

What am I missing?