Adam, Thanks! It works now. My bad. I had an extra space at the front of my IPAddress string. Picky little rascal whatever that parser is! 😊
Richard -----Original Message----- From: Adam Lackorzynski <[email protected]> Sent: Wednesday, June 4, 2025 4:50 PM To: Richard Clark <[email protected]> Cc: Lonnie via l4-hackers <[email protected]> Subject: Re: Can't tcp into VM? Hi Richard, there's no firewall or iptables or anything related to that in the ramdisks. Could you throw tcpdump in there and check whether this gives some hints? Adam On Mon Jun 02, 2025 at 20:38:48 +0000, Richard Clark wrote: > Hey Adam! > > I’ve gotten the lwip stack working, and two vms running, and the > ramdisks expanded a little, and some test processes statically built > so I can run them… and the results suggest a firewall in the way, but > I don’t see a way to enable the port I want… > > So lwip stack native to l4re, ipaddr 192.168.1.100, > Vm1 at 192.168.1.2 > Vm2 at 192.168.1.3 > > The vms can ping eachother. > The vms can ping the lwip stack. > Vm1 can establish a tcp connection TO the lwip stack. (and send > packets!) Lwip cannot establish a tcp connection TO vm1. > > I would have tweaked the firewall, but I don’t see one, or any firewall > utilities, in your default ramdisks. > Suggestions? How would I enable port 5000 from 192.168.1.100 (lwip) to be > allowed into vm1? > Worst case, I guess I could just start all the connections from the > vm, but still, it would be nice to know why it isn’t being allowed. > > I think this is the last little piece I am missing, and then I can run demos > for our customer! > 😊 > > > Thanks! > > Richard _______________________________________________ l4-hackers mailing list -- [email protected] To unsubscribe send an email to [email protected]
