Forum Replies Created
-
AuthorPosts
-
it requires my UEs to send certain files to an apache server running on some other node
Host the Apache server within FABRIC, as part of your slice.
Or, make reverse port forwarding from your laptop:
- In the UPF node, edit /etc/ssh/sshd_config to have GatewayPorts yes.
- From the laptop, SSH into the UPF node with -R 8000:apache.example.net:8000 flag.
- The UEs can then access http://10.30.6.48:8000 (use the internal IP address of enp3s0 interface) to reach the Apache server.
I’ve tested 5G software, both on and off FABRIC. I don’t see the necessity to have Internet access for the 5G network. Typically, I run traffic generators (iperf3 etc) between UEs and UPFs, to measure the performance of 5G network.
- Add a Fabnetv4Ext interface and a Fabnetv6Ext interface to the node that runs UPF.
- Assign RFC1918 and ULA addresses to UEs.
- Setup NAT on the UPF machine, to reach the Internet via Fabnetv4Ext and Fabnetv6Ext interfaces.
IPv6 NAT sucks, but Fabnetv6Ext doesn’t offer routed subnets, so that it’s either NAT or NDP proxy.
- This reply was modified 1 month, 3 weeks ago by yoursunny.
Powder Testbed has USRP devices.
You can make a facility port on FABRIC and communicate with Powder nodes via Ethernet.
Where’s the proxy?
A switchport mirror is a network instrumentation technique. It doesn’t involve any proxy software.
One possible idea:
- Create a FABNetv4Ext or FABNetv6Ext network.
- Insert IP routes so that the traffic to the Internet goes through FABNetv4Ext/FABNetv6Ext interface, instead of the management interface.
- Setup switchport mirroring.
- Capture the traffic on the mirror port.
I wonder how you determined “interfaces for L2 connections on some of my nodes gets deleted”?
On the IPv4 sites, number of VMs that can be provisioned is limited with the available IPv4 addresses in the subnet.
Can “management IP address” show up as a resource on Fabric Portal – Resources page?
This would allow the experimenter to avoid this limitation.Oversubscription support – EDC and EDUKY sites have been enabled to support CPU over subscription.
I remember the CPU core capacity of STAR site was 384.
It’s now 768.
Did this site receive new hardware or is it oversubscription?The entire FABRIC is red this week: https://portal.fabric-testbed.net/resources/all
See notice here: https://learn.fabric-testbed.net/forums/topic/multi-day-fabric-maintenance-january-1-5-2024/
Look at this part:
On other sites, slices will continue running, and slivers will be accessible during the maintenance, however, we will place the testbed in maintenance mode between Jan 1-5, therefore it will not be possible to perform slice operations (create, extend, delete).
Will the FABNetv4Ext peering point (located in WASH) be affected?
November 9, 2023 at 12:06 pm in reply to: “channel 0: open failed: connect failed: No route to host” Error #6080channel 0: open failed: connect failed: No route to host
This error typically means the VM is turned off / deleted, or is otherwise unreachable via management netif.
The fastest solution is simply deleting the experiment slice and creating a new one.
Upper limit for a VM connected with only one component would map to a single Numa Node.
What happens if there are multiple components that are on distinct NUMA sockets?
Is it possible to specify how much RAM to pin to each NUMA socket?Max limit on memory for a numa node is 64G so exceeding that limit would not work.
If we pin a CPU core or certain amount of RAM onto a NUMA socket, does it prevent other VMs from using the same CPU core or RAM capacity?
Is there a way where I can convert my rspec into a FABRIC native object?
This would make a nice hackathon project. It should be feasible to make a converter that covers the topology, links, IP assignments, and startup scripts.
It’s even better if FABRIC platform can directly accept Request RSpec and return Manifest RSpec, so that existing tooling for Emulab can still work.
Management IP cannot communicate with each other, to prevent abuse.
You should create FABNetv4 or FABNetv6 network service in each slice. They can all communicate with each other, regardless of whether the slides are on the same or different sites.
-
AuthorPosts